Free Client Proposal Prompt Generator

TL;DR: An AI proposal generator is a prompt that turns ten inputs (client, the problem in their words, scope in, scope out, deliverables, timeline, pricing model, assumptions, risks, next step) into a structured client proposal in about a minute. The generator below is free and runs in any chatbot. The scope and assumptions fields do most of the winning.

What is an AI proposal generator, and what does it actually generate?

An AI proposal generator is a prompt template that converts a filled-in brief into a finished proposal document. It generates structure, ordering and consistent language. It does not generate facts, and the moment you let it try, you have shipped a document with invented dates and a case study that never happened.

That distinction is the whole game. A blank request like "write a proposal for a website redesign" produces a document full of confident nothing, because you gave it nothing. A brief with ten specific fields produces a document you can send after a fifteen-minute edit.

Here is the generator. Fill the brackets, paste the whole thing, get a draft.

You are a proposal writer for an independent [DISCIPLINE] working with
[CLIENT TYPE] clients. Write a client proposal using ONLY the inputs below.
Do not invent facts, figures, case studies, credentials or dates. If an
input is missing, write [NEEDS INPUT: what you need from me] in place of a
guess. Never fill a gap with a plausible sentence.

CLIENT
  Company: [NAME]
  Person deciding: [NAME, ROLE]
  Others who will read this: [ROLES, e.g. finance, a technical lead]

THE PROBLEM, IN THEIR WORDS
  What they actually said: "[QUOTE THEM VERBATIM FROM THE CALL]"
  What it is costing them: [MONEY, HOURS OR RISK, as they described it]
  Why now: [DEADLINE, EVENT OR PRESSURE THEY MENTIONED]

SCOPE, IN
  1. [DELIVERABLE]
  2. [DELIVERABLE]
  3. [DELIVERABLE]

SCOPE, OUT (state plainly, do not soften, do not apologise)
  1. [THING THEY MIGHT ASSUME IS INCLUDED AND IS NOT]
  2. [THING THAT WOULD NEED ITS OWN PROPOSAL]
  3. [THING THAT DEPENDS ON A THIRD PARTY]

DELIVERABLES AND FORMAT
  What they receive: [ARTEFACT, FILE FORMAT, QUANTITY]
  Definition of done: [THE TEST THAT SETTLES "IS IT FINISHED"]
  Revisions included: [N] rounds per deliverable
  A revision means: [CHANGE WITHIN THE AGREED DIRECTION]
  A new request means: [NEW DIRECTION, BILLED AT THE RATE BELOW]

TIMELINE
  Start: [DATE, or "N business days after the deposit clears"]
  Milestones: [MILESTONE, DATE]
  Delivery: [DATE]
  Client turnaround required: [N] business days per review round

PRICING
  Model: [FIXED FEE / PHASED FIXED / MONTHLY RETAINER / DAY RATE]
  Amount: [FIGURE AND CURRENCY]
  Payment schedule: [e.g. 50% on acceptance, 50% on delivery]
  Out-of-scope rate: [FIGURE] per hour or per change request

ASSUMPTIONS (what must be true for that price and that date to hold)
  1. [ACCESS, ASSET, APPROVAL OR DEPENDENCY]
  2. [ACCESS, ASSET, APPROVAL OR DEPENDENCY]
  3. [ACCESS, ASSET, APPROVAL OR DEPENDENCY]

RISKS
  [RISK] :: [WHAT CHANGES IF IT LANDS: date, fee or scope]
  [RISK] :: [WHAT CHANGES IF IT LANDS: date, fee or scope]

NEXT STEP
  [ONE ACTION] [ONE LINK] [ONE DATE]

OUTPUT RULES
1. Sections, in this order: Summary / What You Told Us / What We Will Do /
   What Is Not Included / Deliverables / Timeline / Fee / Assumptions /
   Risks / Next Step.
2. Open with three sentences that restate their problem in their language,
   before any mention of me, my process or my experience.
3. No adjectives about my own work. Ban: passionate, world-class,
   best-in-class, holistic, bespoke, industry-leading.
4. Every date and every figure comes from the inputs above. Nothing else.
5. Whole document under 900 words.
6. End with the Next Step as one sentence and one link.

Two notes. Quote the client verbatim in the problem field, awkward phrasing included: their words are the strongest signal that a human was listening, and the first thing a generated draft sands off. And if you cannot fill the SCOPE, OUT block, you are not ready to send a proposal. You are ready for another call.

Is this a proposal, or is it actually an estimate?

A proposal is a decision document and an estimate is an information document. Sending the wrong one is the most common unforced error in freelance sales, because it hands the client a reason to think rather than a thing to sign.

The tell that you have written an estimate while believing you wrote a proposal: the document ends with a range, a caveat about final requirements, and an invitation to discuss. Nothing in it can be accepted. The client's only available action is to reply, and replies decay.

Why do proposals fail? Scope boundaries and assumptions

Proposals almost never lose on prose. They lose on ambiguity, and the loss usually shows up in week three of a project you already won, when the client asks for something you both silently assumed different things about.

There are three failure modes and they compound.

Implied scope. The client reads "a new marketing site" and pictures copywriting, photography, a blog migration and someone entering 40 pages of content. You pictured a build against supplied copy. Neither of you was unreasonable. The document simply never said.

Unstated dependency. Your date assumes brand assets on day one, a staging environment by week two, and one named approver. When the assets arrive late from a third party, the date slips, and because the proposal never named the dependency, the slip looks like your fault.

Undefined done. Without a definition of done and a revision count, "finished" becomes whatever the client feels on the day. This is how a fixed fee quietly turns into an hourly rate that falls every week.

The fix is two lists, and they are the two most valuable paragraphs in the whole document.

The "not included" list

Write five to eight lines naming what a reasonable person would assume is included and is not. Do not soften them into hedges. A hedge is ambiguity wearing a suit.

By discipline, the usual suspects: source files and working files, hosting, DNS and domain transfers, content entry and data migration, stock or music licensing, third-party plugin or subscription costs, training and handover sessions, ongoing maintenance, accessibility remediation beyond a stated standard, and anything at all that requires access you have not been granted.

Clients do not read this list as defensive. Procurement people read it as the mark of someone who has run projects before.

The assumptions register

An assumption is not reassurance. It is a condition attached to a number. Every line should be written so that if it turns out to be false, the consequence is already agreed in writing.

The format that survives contact with a dispute:

This scope and fee assume final brand assets are supplied by 3 September. If they arrive later, delivery moves by the same number of business days.

This scope and fee assume one named approver with authority to sign off each round. If review requires more than two people, additional consolidation time is billed at the out-of-scope rate.

Compare that with the version most drafts produce: "We assume the client will provide assets in a timely manner." It commits nobody to anything and it will not help you in October.

Once you have a draft, run it through this second prompt. It is more useful than the generator itself, because it attacks your own document from two directions using persona prompting.

Read the proposal below twice, in two passes.

PASS 1. You are the client's procurement lead. You are not hostile, you
are careful. List every place where you could reasonably believe something
is included that the document does not explicitly include. For each one,
quote the exact sentence that creates the ambiguity.

PASS 2. You are a freelancer who has been burned by an unpriced
dependency. List every dependency in this project that is not priced, not
dated, or not owned by anyone. For each, write the assumption line that
should appear in the proposal, in exactly this format:
"This scope and fee assume [X]. If [X] is not available by [DATE], then
[specific consequence to the date or the fee]."

THEN OUTPUT, and nothing else:
A. "Not Included" list, 5 to 8 lines, written for the client to read.
B. "Assumptions" list, 4 to 6 lines, in the format above.
C. The single sentence in my proposal most likely to cause a dispute in
   week three, quoted, with one rewrite.

Do not rewrite the whole proposal. Do not add scope I did not mention. If
you cannot find something in a category, say "none found" rather than
inventing one.

PROPOSAL:
"""
[PASTE YOUR DRAFT HERE]
"""

The "say none found rather than inventing one" line matters. Without it the model will manufacture a risk to satisfy the request, and a fabricated risk in a client document is worse than no risk section at all. This is ordinary hallucination pressure, and an explicit escape hatch is the cheapest defence against it.

How should a proposal present price?

Put the cost of the problem before the cost of the solution, and use their number rather than one you invented. If they told you the manual reporting eats four hours a week, that figure belongs in the document, in their phrasing, one paragraph above your fee. You are not anchoring against a made-up benchmark. You are reminding them what they already said.

Then present the fee as a choice of shapes, not a single take-it-or-leave-it figure.

"From $X" deserves its own note, because it is everywhere and it is quietly costly. It fails for three reasons. It transfers uncertainty to the buyer at the exact moment you wanted to remove it. It invites them to anchor on the floor, so every figure above the floor feels like a markup rather than a price. And it makes the document unacceptable in the literal sense: there is nothing to sign, so the next step becomes a conversation.

That same report states that companies using interactive pricing "win 2x more proposals and are 21% more likely to close". Treat that as what it is: a software vendor reporting on its own customers, not an independent study. The direction matches what most freelancers find, which is that offering a choice of scopes beats offering one number.

Here is the prompt for the pricing section alone. Run it separately from the main generator, because pricing is the section you will rewrite most.

Rewrite ONLY the pricing section of my proposal from these inputs.

WHAT THE PROBLEM COSTS THEM (their number, from the call):
  "[QUOTE THEM]"

OPTIONS (I have already decided these. Do not invent a fourth.)
  A. Name: [NAME]
     Scope in one line: [SCOPE]
     Fee: [FIGURE]
  B. Name: [NAME]
     Scope in one line: [SCOPE]
     Fee: [FIGURE]
  C. Name: [NAME]
     Scope in one line: [SCOPE]
     Fee: [FIGURE]

PAYMENT SCHEDULE: [SCHEDULE]
OUT-OF-SCOPE RATE: [FIGURE]
I RECOMMEND: [A/B/C] because [ONE REASON DRAWN FROM THEIR SITUATION]

RULES
1. First sentence restates what the problem is costing them, using their
   number, before any of my figures appear.
2. Present the options as a table with identical rows for each option. No
   empty cells. If an option lacks something, write "not included".
3. State the recommendation in one sentence, in their terms, not mine.
4. Payment schedule and out-of-scope rate go directly under the table,
   never in a footnote.
5. No ranges. No "starting at". No "depending on final requirements".
6. Do not describe any option as good value, affordable, competitive, or
   an investment in their future.

How do you make the accept step frictionless?

End with one action, one link and one date. The most common closing line in freelance proposals is some version of "let me know your thoughts", and it is a request for homework rather than a decision.

Four things make acceptance easy:

Name the decision. "Approve Option B" beats "let me know how you would like to proceed". The client should never have to compose a sentence in order to buy from you.

Put the signing link in the document and in the email. Not attached, not "available on request".

Sign it yourself before sending. It costs nothing and it removes the implicit question of whether you are still deciding.

Say what happens the moment they accept. The deposit invoice sends automatically, the kickoff call is booked within two business days, the first milestone lands on the stated date. Certainty about the next 48 hours reduces the perceived risk of saying yes far more than another paragraph about your process.

On the legal side, an electronic signature is not a lesser signature in either of the two largest markets. In the United States, 15 U.S.C. section 7001 provides that a signature or contract "may not be denied legal effect, validity, or enforceability solely because it is in electronic form". In the EU, Regulation (EU) No 910/2014 has applied directly since 1 July 2016 on the same principle. Both carry exceptions by document type, and neither is legal advice for your situation. Checked 26 August 2026.

Write the closing section of my proposal from these inputs.

THE DECISION I AM ASKING FOR: [ONE THING, e.g. "approve Option B"]
HOW THEY ACCEPT: [e.g. "sign at this link"]
LINK: [URL]
WHAT HAPPENS IMMEDIATELY AFTER: [e.g. "deposit invoice sends
  automatically, kickoff call booked within 2 business days"]
FIRST DATE THAT MOVES IF THEY WAIT: [DATE, and why it moves]
DOES MY OFFER EXPIRE: [DATE, or the word NO. If NO, invent no urgency.]

RULES
1. Maximum 60 words.
2. One decision, one link, one date.
3. Ban these phrases entirely: "let me know your thoughts", "feel free to
   reach out", "happy to discuss", "if you have any questions", "looking
   forward to hearing from you".
4. Do not manufacture scarcity that I did not state above.
5. Second person, present tense. One question mark, on the sentence that
   asks for the decision.

The edit pass: AI drafts structure, it does not know your client

This is where most generated proposals lose the work, and it has nothing to do with grammar. A model can produce a clean, complete, well-ordered document that reads as though nobody was in the room. Clients notice. They have received four of these this quarter.

What the model genuinely gives you: completeness, consistent section ordering, no forgotten payment schedule, no missing revision count, and a first draft in ninety seconds instead of ninety minutes. That is real, and it is most of the value.

What it cannot give you: the pause before they said the budget number. The fact that the marketing director is the person who has to defend this spend to a finance lead who has never met you. The previous agency that overran and left them wary of anything phased. The fiscal year that closes in six weeks. None of that is in your brief unless you put it there, and all of it changes what the proposal should emphasise.

Six edits, in order, on every generated draft:

1. Rewrite the opening three sentences by hand. Use their words, including the ungainly ones. If the model wrote "you are seeking to modernise your digital presence" and they said "our site looks like 2019 and I'm embarrassed to send the link", use theirs.
2. Delete every adjective about yourself. Proven, dedicated, experienced, results-driven. They convert to nothing.
3. Break the symmetry. Models produce three bullets of similar length under every heading. Real scope is lumpy. If one deliverable is 60% of the work, it should visibly be 60% of the section.
4. Check every number against your inputs. Dates, fees, round counts, rates. Anything the model produced that you did not supply is a fabrication, however plausible it looks.
5. Cut a fifth of it. Winning proposals in the Proposify dataset averaged 11 pages against 13 for losing ones, which is a small gap, but no proposal in the history of freelancing lost because it was too short and too clear.
6. Read the Next Step out loud. If it sounds like an invitation to think it over, rewrite it.

One paragraph, before and after, from a real shape of draft:

Generated: We understand that your organisation is looking to improve its reporting capabilities. Our team brings extensive experience delivering data solutions for clients across a range of industries, and we are confident we can help you achieve your goals.

Edited: You said your team loses about four hours every Monday rebuilding the same client report by hand, and that it has already cost you one renewal conversation. This proposal covers automating that report end to end, so Monday takes ten minutes.

Same information density on the page. Only one of them was written by somebody who listened.

How do you reuse this without rewriting it for every client?

The generator holds two kinds of content. The output rules, section order and banned phrases are stable across every client you will ever have. The client, problem, scope and figures change every time. Keeping both in one block is why most people abandon a good prompt after a fortnight: editing becomes search-and-replace, with a fair chance of leaving the last client's name in the file.

Split them. Keep the rules as a saved template, keep the per-client facts as variables you fill at send time, and keep an accumulating file per client with the things you learn about them. We wrote up the mechanics of that in stop rewriting the same prompt for every client, and the wider account-work set in scoping, reporting and client comms prompts.

If you want the neighbouring documents rather than just the proposal, 40 AI prompts for proposals, outreach and client work covers the front end of the pipeline, and the handoff from a signed proposal through to getting paid is in proposal-to-invoice prompt templates. The same split-the-template pattern also drives our free SOP generator prompt, which is the internal-facing sibling of this one.

Prompt Architects does this natively: save the generator as a template, keep client facts in Global Variables and Context Libraries, and the per-client fill becomes a dropdown rather than a rewrite. Enhancement is built in, so there is no API key to supply, and the free plan is enough to test whether the workflow suits you before you pay anything. Current pricing is on the pricing page.

What an AI proposal generator will not fix

Three honest limits, because a page that only sells the upside is not much use to you.

It will not fix an unqualified lead. If the client has no budget, no authority or no deadline, a beautifully scoped proposal loses to the same competitors it would have lost to anyway. The proposal is not where qualification happens.

It will not fix scope you have not thought through. The model cannot decide what is out of scope, because that is a commercial judgement about your risk appetite and your relationship. If the SCOPE, OUT block is empty in your brief, it will be vague in your document.

It will not fix a bad price. If you are fourth of six bidders and the other five are half your rate, formatting is not the variable. Structured pricing options help you win the deals that were winnable. Nothing helps with the rest.

Used within those limits, the generator does one narrow thing very well. It removes the two hours between "we should send them something" and "we sent them something", which for most freelancers is the real reason proposals go out late, thin, or not at all.