proposal-writer

Write a proposal

A proposal is a persuasion document with a number at the end. It must be credible, specific, and easy to say yes to.

Language / Idioma

Write in the client's language. Ask if unclear (the user may speak Spanish but pitch an English-speaking client).

Gather inputs first (ask only what you can't infer)

• Client + their problem — who, and the pain in their words.
• Scope — what's explicitly in, and what's explicitly out (out-of-scope prevents disputes).
• Deliverables — concrete artifacts the client receives.
• Timeline — phases/milestones with rough dates.
• Commercials — price model (fixed / time & materials / retainer), amount, payment terms, currency.
• Proof — relevant past work, capabilities. Pull from the second-brain (vault Projects/, .brain/ context) rather than inventing credentials. Never fabricate references, logos, or case studies.

If a critical field (price model, deadline, decision-maker) is missing, ask before drafting.

Structure

1. Cover / title — client name, project title, date, your name/org.
2. Executive summary — 3–4 sentences: their problem → your solution → the outcome they get. Written so a busy decision-maker can approve from this alone.
3. Understanding / context — restate their problem in their words. Proves you listened. (This is what wins trust.)
4. Proposed solution — what you'll do, at the right altitude for the reader. Tie each piece back to a stated need.
5. Scope & deliverables — bulleted, concrete. Include an explicit Out of scope list.
6. Timeline — phases/milestones table with dates or durations.
7. Investment / Inversión — the price, the model, what's included, payment schedule, validity ("valid for 30 days").
8. Assumptions & dependencies — what you need from them (access, data, sign-offs) and what you're assuming.
9. Why us — short, evidence-backed (real prior work from the brain). No fluff.
10. Next step / Call to action — exactly what happens when they say yes (sign here, kickoff date). Make it one easy action.

Style

• Client-centric: "you/your" more than "we/our". Their outcome leads; your activity supports it.
• Specific and quantified: dates, counts, deltas, money — vague proposals read as risky.
• Confident, not hedged. State what you'll deliver.
• Honest about scope boundaries and assumptions — this protects both sides and signals professionalism.
• Format: clean Markdown; offer to render a branded PDF/HTML (pair with frontend-design).

Guardrails

• ⚠ Do not invent capabilities, certifications, team members, or case studies. If the brain has no evidence for a claim, leave it out or flag it for the user to confirm.
• ⚠ Do not commit to a price or deadline the user hasn't approved — present it as a draft for their sign-off.
• ✅ End by listing every assumption you made so the user can correct it before it goes out.