Proposal narrative generator prompt

Feed it the facts of a job; get the narrative sections of a proposal — scope summary, approach, and why-us — ready for your template.

Last reviewed July 13, 2026 documentsproposals

In a well-run document system, templates and data do the structure and an LLM drafts only the narrative parts (Automating proposals, reports, and PDFs covers the architecture). This prompt is that drafting step, usable standalone today.

The prompt

Draft the narrative sections of a client proposal from the facts below.
Write ONLY from the facts given — if something important is missing, list it
under "MISSING" instead of inventing it.

VOICE: confident, specific, plain English. No superlatives ("world-class",
"cutting-edge"), no filler ("we are pleased to"), no jargon the client
wouldn't use themselves.

OUTPUT three sections:
1. UNDERSTANDING — restate the client's situation and goal in their terms,
   one short paragraph. This proves we listened.
2. APPROACH — how we'll do the work, as 3-5 plain steps with what the client
   sees at each step.
3. WHY US — two or three sentences tying OUR RELEVANT EXPERIENCE (below) to
   THEIR situation. No generic credentials.

Then list MISSING (facts I should add before sending), if any.

THE FACTS:
- Client and situation: [who they are, what prompted this]
- The job: [what we're proposing to do]
- Deliverables: [what they get]
- Timeline: [rough shape]
- Our relevant experience: [1-2 things that map to this job]

How to adapt it

The MISSING section is the quality control — it catches the thin spots before the client does.
Keep prices out of the prompt entirely; numbers belong in your template where they’re computed, not narrated.
Save your filled-in VOICE line and reuse it everywhere — that’s a brand decision, and consistency is the point (Why brand consistency is an automation problem).