How I Use Claude to Find the Holes in My Proposals Before Clients Do
I asked Claude to read my proposal as if it were the client. It found 4 holes I'd missed.

The project was a website for a restaurant in Manila. I had my call notes and an old proposal I liked.
Here's what I did, step by step.
Step 1: Draft the proposal
I pasted my notes and the old proposal into Claude. I asked for a new proposal in the same structure, with 3 price tiers, a timeline in weeks, and every guess marked in [brackets]. Before writing, it listed what was missing from my notes.
Step 2: Make Claude the client
Then I asked it to become the restaurant owner and give me the 4 toughest objections. They were fair:
- "What exactly am I paying for? I could build this on Wix myself."
- "What will I really pay in year one, with the plan, domain and retainer?"
- "Who supplies the food photos? If I'm late, does the date move?"
- "What if I hate the design? Who owns the Wix account when you're done?"
Step 3: Write the answers
Claude switched back and wrote a short, calm answer to each one. Those became my notes for the follow-up call.
What it caught
My proposal never stated the number of revisions, who pays for Wix and the domain, who owns the account, or who supplies photos. Four short lines. All fixed before the client saw anything.
Time from notes to proposal, objections and answers: 5 minutes. I still edit every word before it goes out. But I'd rather Claude find the holes than my client.
The prompts
Prompt 1 (the proposal):
"I'm a freelance UX/UI designer. I just had a discovery call. My notes and one past proposal are below. Write a proposal in the same structure, 3 tiers, timeline in weeks, under 900 words. First list anything missing. Mark your guesses in [brackets]."
Prompt 2 (the objection pass):
"Act as this client reading the proposal. Give me your 5 toughest objections. Then switch back and write a short, calm answer to each one."
Try it on your next proposal. Then tell me what it found.



Comments