How Consultants Cut Proposal Time From 6 Hours to 45 Minutes: 7 Steps With Claude

Every consultant I know has the same Sunday. The call went great on Thursday. The client is warm. And the proposal is still sitting there, unwritten, glaring at you from the corner of your brain while you try to watch a movie.

So you finally open the laptop at 4pm, you go find the last proposal you sent, you start deleting the old client's name out of it, and six hours later you have something you are only about 70 percent happy with. You send it Monday morning, three days after the call, which is roughly three days after the moment they were most excited to say yes.

That gap is the expensive part. Not the writing. The delay. Warm goes cold faster than anybody wants to admit, and the consultant who sends a sharp, specific proposal within 24 hours wins deals that a better consultant loses at day five.

Here is the thing nobody tells you: the six hours is not really writing time. It is remembering time. You are re-reading your notes, trying to recall what they actually said, rebuilding your scope language from scratch, second-guessing your price, and rewriting the same "about me" paragraph you have written 40 times. Almost none of that is thinking. It is retrieval.

AI is very, very good at retrieval. So that is the part we hand off.

Below is the exact system, seven steps, that takes a discovery call and turns it into a proposal you are proud to send in about 45 minutes. No coding. No new software beyond the AI itself.

1. Stop taking notes on the call

This is step one and it changes the other six.

When you take notes during a discovery call, you are half present. You are typing while they are talking, which means you catch the facts and miss the feeling. And the feeling is where the deal lives. The sentence that sells the proposal is almost never "we need help with our marketing." It is the thing they say 22 minutes in, slightly frustrated, when they stop performing for you.

Turn on a recorder, tell them you are recording so you can be fully present with them (clients love this answer, it is not a workaround, it is a better call), and then actually look at the person.

After the call you have a transcript. That transcript is worth more than any notes you would have taken, because it has their exact words in it, and their exact words are what you are going to put in the proposal.

2. Build the proposal project once, not every time

Open a Project called something boring like "Proposals." Inside it, put the things that never change:

• Your service descriptions, in your real language
• Your pricing logic (not just numbers, the reasoning: what makes a project a 5k versus a 15k)
• Two or three past proposals that actually closed
• Your standard terms, timelines, and what is out of scope
• A short note on your voice: how formal you are, whether you use "we" or "I," what you never say

This is the 40 minutes that saves you the six hours, and you only do it once. Everything after this is a five-minute prompt against a workspace that already knows who you are.

Most consultants skip this and then wonder why the AI output sounds generic. It sounds generic because you gave it nothing. Feed it your real work and it stops guessing.

3. Turn the transcript into their words, not your summary

Drop the transcript in and ask for extraction, not a summary. There is a big difference. A summary flattens everything into your language. Extraction keeps their language, and their language is what makes a client read a proposal and think "this person actually listened."

Here is the transcript of my discovery call. Pull out: (1) the problem in their exact words, quoted, (2) every business consequence they mentioned, in dollars or hours where they gave numbers, (3) what they have already tried and why it did not work, (4) who else is involved in the decision, (5) any timeline or deadline they mentioned, and (6) the three moments where they sounded most frustrated. Quote them directly. Do not paraphrase.

That last one is the sleeper. The frustration moments tell you what the proposal has to solve emotionally, not just operationally. Two clients can need the same deliverable for completely different reasons, and the one who feels understood signs faster.

4. Draft the scope from their problem, not from your service menu

Here is the mistake that makes proposals feel like brochures. You go to your list of services, you pick the three that fit, and you paste in the descriptions you already wrote. The client reads it and correctly senses that they are being sold a package, not a solution.

Flip it. Start from the problem you just extracted and let the scope be built backwards from it.

Using the problem and consequences you just pulled out, draft a scope of work. Structure it as outcomes first, then the work required to reach each outcome, then the deliverables. Every deliverable has to trace back to something they actually said on the call. If something in my service list does not solve a problem they raised, leave it out and tell me why you left it out.

That last sentence is the quiet workhorse. Ask AI to tell you what it excluded and you will catch yourself padding. Consultants pad scope out of insecurity, and padded scope is the number one reason a proposal gets "let me think about it" instead of a signature.

5. Price it three ways so they choose how, not whether

One price is a yes or no question. Three options is a which one question, and which one is a much friendlier conversation to be having.

Build three options from this scope. A smaller entry engagement that solves the single most urgent problem they named, the recommended middle option that solves the full problem, and a larger option that includes ongoing support after delivery. For each one, write what it is, what it costs, what it does not include, and who it is right for. Use my pricing logic from the Project. Flag anywhere the middle option is priced in a way that makes the top option look unreasonable.

Keep the recommendation explicit. Say plainly which one you would pick if it were your business and why. Clients are not offended by a recommendation, they are relieved by it. Ambiguity is what they hate.

6. Answer the objections before they get raised

Every proposal you have ever lost, you lost to one of about five objections. Too expensive. Bad timing. We could probably do this internally. We need to talk to someone who is not on this call. How do we know it will work.

You already know them. Put them in the document.

Based on this specific call, predict the three objections most likely to come up after they read this, and who is most likely to raise each one. For each, write a short honest section for the proposal that addresses it without being defensive. No hype. If an objection is genuinely valid, say so and tell them how we would handle it.

The honesty matters more than the polish. A proposal that says "if your timeline is really six weeks, this is not the right project and here is what I would do instead" builds more trust than one that promises everything. And if there is a decision maker who was not on the call (there almost always is), write a short section aimed at that person, because your proposal is going to be forwarded to them without you in the room.

7. Read it out loud, then fix the three things that are wrong

You are now about 35 minutes in and you have a draft. Do not send it yet.

Read the whole thing out loud. Out loud, not in your head. You will hear the two or three sentences that are not yours, and you will hear the place where the scope got mushy. Fix those by hand. That is the part that is your job, and it is the part that makes it good instead of fine.

Then run one last pass:

Read this proposal as if you are the client. Where would you hesitate? What is unclear about what happens next? What am I asking them to do, and is it obvious? Give me the five weakest sentences and why they are weak.

Fix those five. Send it. You are done, and it is still the same day as the call.

What the 45 minutes actually looks like

Roughly: five minutes to pull the transcript and get the extraction, ten minutes on the scope, ten minutes on pricing and options, five minutes on objections, and fifteen minutes of you reading, cutting, and making it sound like a human wrote it. That last fifteen is not optional and it is not a place to save time. It is the difference between a proposal and a template.

The first one you do will take longer, probably 90 minutes, because you are building the Project while you work. The second one is 45. The fifth one is 30 and you will start wondering what you were doing for six hours all those years.

The part that matters more than speed

Speed is the headline, but it is not the real win. The real win is that you stop dreading proposals, and when you stop dreading them, you send more of them. You follow up on the lukewarm lead. You write the one for the smaller project you would have talked yourself out of. You send it Thursday night instead of never.

Most consultants do not have a closing problem. They have a "the proposal took so long that the moment passed" problem. That one is fixable this week.

Frequently asked questions

Do I need to be technical to set this up?

No. I do not write code either. Every step here is you typing a normal sentence and reading what comes back. If you can write an email to a client, you can do this. The people who struggle are not the non-technical ones, they are the ones who ask for something vague and then decide AI does not work.

Will my proposals start sounding like everyone else's?

Only if you skip the Project step. Generic in, generic out. When you load your real past proposals, your real pricing logic, and your real voice, the output comes back sounding like you on a good day. And you are still the editor on every single one. Nothing goes out that you did not read out loud.

Is it safe to put a client transcript into AI?

Use judgment and strip what you do not need. Take out names, company identifiers, and anything covered by an NDA before you paste. The AI does not need to know it is Acme Corp to write a good scope, it needs to know what the problem is. If you work under strict confidentiality agreements, check your terms first and use a business plan with the right data settings. That habit costs you two minutes and protects the relationship.

What if I do not record my calls?

Start. It is the single highest leverage change in this whole system. If you truly cannot, dictate a five minute voice memo the moment the call ends, while it is fresh, and use that as your raw material instead. Messy and immediate beats tidy and three days later.

How is this different from just using a proposal template?

A template gives you the same document every time and you fill in the blanks. This builds the document backwards from what one specific person said on one specific call, in their words. The structure is consistent, the content is not. Clients can feel that difference in the first paragraph.

Will this work for retainers and ongoing work, not just projects?

Yes, and it is arguably better there. Retainer proposals live or die on whether the client understands what they get each month, and that is exactly the kind of clarity this process forces. Ask for the scope to be written as a monthly rhythm instead of a delivery timeline.

How long before this actually saves me time?

The first proposal is roughly break-even because you are building your Project as you go. The second one is where you feel it. By the fourth or fifth, most consultants are landing somewhere between 30 and 45 minutes, start to finish.

Want help building it?

If you want to build this next to people who will look at your actual proposal and tell you where it is padded, that is what Club Jam on Skool is for. It is $47 a month with a 7-day free trial, over 220 training modules, and a room full of everyday business owners and consultants who are not developers and never planned to be. I have trained more than 7,500 people, and almost none of them walked in knowing what they were doing.

You do not need to be technical. You need one recorded call and one slow hour. Come start with us at jamout.ai. 🧡