Writing a proposal is one of the least enjoyable jobs an owner does. It arrives at the end of a good sales call, when the momentum is high and your calendar is full, and it takes an evening you did not plan for. So the temptation to hand it to an AI tool is strong.

That instinct is correct, with limits. I have watched owners cut proposal time by more than half using a chat tool, and I have also seen a proposal go out with a service line in it that the company does not offer. Both outcomes came from the same tool. The difference was the setup and the review.

What AI is genuinely good at in a proposal

Three jobs, and it does all three better than a tired person at nine in the evening.

Structure. Give it your rough notes and ask for a proposal with a situation section, a recommendation, a scope, an investment section, and a next step. It produces a sensible skeleton every time. If your proposals are inconsistent because you write each one from scratch, this alone fixes the problem.

The first draft of the narrative. The hardest part of a proposal is the opening page where you describe the buyer's situation. AI is good at taking half a page of scrappy notes and producing three clean paragraphs. You will rewrite parts of it. Rewriting is much faster than starting.

Reformatting what you already have. This is the underrated one. You have a call recording, a page of notes, and an old proposal for a similar job. Asking the tool to combine those into a new draft is a mechanical task with a clear right answer, which is exactly the shape of work these tools handle well.

It also removes the blank page problem, which is a real cost. Plenty of quotes go out late because the owner could not face starting, not because the writing was hard.

What it gets wrong, and why it looks convincing

The failures cluster into three categories, and all three read as confident, well-written prose.

Pricing judgment. A model has no idea what your work is worth, what your margin is, what this client can pay, or what you charged the last three clients for similar scope. If you ask it to suggest a price, it produces a number that sounds plausible and has no connection to your business. Some owners use it as a sanity check. I would not. Set the price yourself, then let the tool write the section around it.

Claims about your capability. This is the dangerous one. Ask for a proposal for a manufacturing client and the model will helpfully add a line about your experience with lean process improvement, because that is what such proposals usually contain. You did not say you do that. It filled the gap. A buyer reads it as a commitment, and if you win the job you now have to deliver something you never offered.

Anything factual about the client. Company size, the systems they run, who reports to whom, what they told you about their timeline. If a detail was not in your notes, the tool will produce a reasonable-sounding substitute. Sending a proposal that misstates a buyer's own business is the fastest way to signal that you were not listening.

Notice the pattern. The model fails exactly where it has no information and cannot say so. It has no mechanism for leaving a gap, so it fills it.

The setup that makes the output usable

Most people get bad proposal drafts because they typed one sentence into an empty chat. The quality of what comes back tracks almost entirely with what you put in.

Two inputs matter.

Your own past proposals. Take the three best proposals you have sent, ones that won. Paste them in and say: this is how we write proposals, match this structure and this tone. The model now has your actual voice, your actual sections, and your actual service descriptions to work from instead of a generic template averaged from the internet. This single step changes the output more than any prompt wording.

Real discovery notes. Not a summary you wrote from memory two days later. The notes from the call, with the buyer's phrases in them. If you record calls and get a transcript, paste the transcript. The value of the draft depends on how much specific material it has about this buyer, and a transcript carries far more than your recollection does. A good set of discovery questions produces notes that are worth feeding in.

Then be explicit about the boundaries. Tell it: use only the services listed here, do not add any service we have not named, leave the price as a placeholder I will fill in, and mark anything you are unsure about in square brackets. That last instruction is worth more than it sounds. It gives the model permission to flag a gap rather than fill it, and it works most of the time.

Build this as a reusable setup. Save the instruction block, save the sample proposals, and start each new proposal from the same place. The first hour of work makes every proposal after it faster.

The review step you cannot skip

Ten minutes, four passes, in this order.

  1. Capability pass. Read every sentence that describes what you will do. For each one ask: do we do this, and would I be happy to be held to it in three months? Delete anything you cannot answer yes to twice.
  2. Fact pass. Every statement about the client. Company details, systems, timelines, names, the problem description. Check each against your notes. If it is not in the notes, cut it or confirm it.
  3. Money pass. The price, what is included, what is excluded, payment terms, and anything that reads as a guarantee. This is where a vague sentence costs you money later.
  4. Voice pass. Read it aloud. AI drafts tend toward inflated words and long balanced sentences. Cut the adjectives it added and put your own plainer phrasing back. A buyer who has spoken to you will notice if the document sounds like a different person.

Never skip the capability pass because you are in a hurry. That is the failure that follows you into delivery. The rest are embarrassing; that one is expensive.

Client details in a tool you do not control

Pasting a call transcript into a chat tool means the buyer's business information leaves your building. That is a real question and most owners have not thought about it.

Two things decide the answer.

First, what account you are using. Consumer versions of these tools and business versions of the same tools handle your data differently, and the business or enterprise tiers generally commit in writing that your content is not used to train the underlying model. Read the current terms for the specific product and tier you pay for, because they change and because the difference between the free tier and the paid business tier is where the commitment usually sits. If your company puts client material into an AI tool regularly, use a business account. The cost difference is small next to the exposure.

Second, what you have already signed. Plenty of B2B contracts, especially with larger clients, in professional services, and anywhere regulated, contain confidentiality clauses that restrict sending client information to third-party services. Some now name AI tools directly. Check your master service agreements before this becomes a conversation you have after the fact.

A practical middle path: strip identifying details before pasting. Replace the company name with "the client", remove people's names, and take out anything genuinely sensitive. You lose little draft quality, because the model mostly needs the shape of the problem rather than the identity. The wider version of this question is covered in risk, privacy and policy for AI.

How much time this actually saves

Be honest about the arithmetic, because the marketing around these tools is not.

A proposal that took three hours does not become fifteen minutes. What happens is that the drafting portion, which was maybe two of those three hours, drops to twenty or thirty minutes including the setup. The review adds ten. The thinking, deciding what to recommend and what to charge, does not move at all, because that is your judgment and no tool has it.

So call it three hours down to about an hour, once the setup exists. Across a company sending six proposals a month, that is twelve hours back. Worth doing.

There is a second effect that owners report more often than the time saving. Proposals go out faster because the starting friction is gone. A quote that leaves the same day instead of four days later wins more often, and that gain is larger than the hours. If quotes sit in your drafts folder, the tool is fixing a scheduling problem as much as a writing one.

None of this helps if the underlying document is weak. A fast draft of a proposal that buries the price on page six and opens with your company history is still a losing proposal. Get the structure right first, then make it faster.

The takeaway

Use AI for the writing and keep the judgment. Feed it your three best past proposals and your real discovery notes, tell it not to invent services and to leave the price blank, and run the four-pass review before anything goes out.

The confidentiality question deserves ten minutes of your attention once. Use a business account, check what your client contracts already say, and strip names out of what you paste.

My verdict: this is one of the clearest wins available to a small B2B company right now, because the task is repetitive, the input already exists, and the output gets checked by a human before it leaves. The risk is contained and the hours are real.