agentleFS
buildwithreefbuildwithreef/claude-skills/skills/proposal-writer/SKILL.md

proposal-writer

Skill0 starsChanged 4 months agoMITView on GitHub

Turns discovery-call notes into a clear, scoped proposal with pricing presented for maximum close rate — situation, goal, approach, scope fence, investment options, and a dated next step. Use when the user needs to write a proposal or quote for a client, says "turn these notes into a proposal", or asks how to present pricing to a prospect.

29 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use sop-writer, weekly-report and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Dokkabei97Skill

    sop-writer

    Creates Standard Operating Procedures for repetitive tasks. Generates step-by-step documentation with checklists, decision trees, and responsibility assignments to eliminate single points of failure.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    weekly-report

    **WORKFLOW SKILL** — Generate weekly executive reports for the azd team. Pulls PR/issue/release data from GitHub, reads changelogs, combines with team notes, and produces a polished markdown report.

    Also in 5 projects that use this

  • akhilkannurSkill

    content-repurposer

    Also in 4 projects that use this

  • claude-office-skillsSkill

    meeting-notes

    >

    Also in 3 projects that use this

  • LangChainSkill

    linkedin-post

    Write a LinkedIn post based on research findings or a given topic. Use this skill when asked to create LinkedIn content, professional posts, or thought leadership pieces.

    Also in 3 projects that use this

  • seikaikyoSkill

    interview-me

    需求不明時的意圖萃取訪談:一次一題、每題附上自己的猜測、聽出「真正想要 vs 覺得應該要」,直到能預測使用者反應(約 95% 信心)才動工。適用:需求缺少對象 / 動機 / 成功標準 / 約束,或使用者點名「訪談我」「先確認一下」「我們確定嗎」。明確自足的指示、純資訊查詢、機械性操作不適用。

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before writing, extract from the user's notes (ask for whatever's missing):

    line 12
  2. Distinctive:

    No legalese in the proposal body.

    line 48
  3. Distinctive:

    Don't open with your company history.

    line 64
  4. Distinctive:

    Don't include more than one testimonial/case — proposals bloat from insecurity.

    line 65
  5. Distinctive:

    Don't quote a price discovery didn't support.

    line 66
  6. Distinctive:

    Don't send editable files.

    line 67

“Common” is measured: kept by at least 6 in 10 of the 21 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Proposal Writer

A proposal isn't a document, it's the close in writing. The prospect should finish it thinking "they understood us, I know exactly what I'm getting, and I know what to do next."

Step 1 — Mine the discovery notes

Before writing, extract from the user's notes (ask for whatever's missing):

  • The prospect's own words for their problem — quote these back verbatim later
  • The business outcome they actually want (more calls, less admin time — never "a website")
  • Budget signals, stated or implied
  • Who decides, and who else weighs in
  • Their deadline or triggering event ("busy season starts in April")
  • What they've tried before and why it failed (shapes the "why this approach" section)
  • Any competitor in the deal

Step 2 — Build the eight sections

  1. Situation — 3–5 sentences of their world, using their words from discovery. This section closes deals: it proves you listened. No selling here.
  2. The goal — one sentence, business outcome: "Get the phone ringing from Google without you touching marketing."
  3. Recommended approach — what you'll do in phases, each phase = name + what happens + what it produces. Explain why this way in one line per phase, referencing what they've tried before.
  4. What's included / what's not — the scope fence. Bullet both sides. The "Not included" list prevents more scope creep than any contract clause, and it makes the included list look bigger. Be specific: "two rounds of revisions," "content for up to 6 pages," "does not include ongoing ad management."
  5. Investment — never "price," "cost," or "fees" (see Step 3).
  6. Timeline — phases with durations from their trigger: "Live within 5 weeks of kickoff." Tie to their deadline if they gave one.
  7. Proof — one relevant result or testimonial, with numbers. One. A proposal is not a portfolio.
  8. Next step — specific and dated: "To hold the March start, sign below by Friday the 14th; kickoff call the following Tuesday." Include payment terms here (e.g., 50% to begin, 50% at launch).

A worked example is in references/template.md.

Step 3 — Present the pricing right

  • Three options, anchored high. Present the premium option first — it makes the middle (your target) feel reasonable. Single-option proposals convert yes/no; three options convert "which one."
  • Name tiers by outcome, not size: "Get Found / Get Chosen / Run on Autopilot" — never Bronze/Silver/Gold.
  • No hourly line-item breakdowns. Itemized hours invite line-item vetoes ("can we cut the testing?"). Price the outcome per tier; list what's included, not what each piece costs.
  • Monthly framing where true: "$450/month" reads differently than "$5,400/year" — use whichever matches how they budget.
  • Validity date on every proposal (2–3 weeks). Real urgency, honestly framed: your calendar fills.
  • The middle option should be what discovery said they need. The low option is genuinely useful but visibly lighter — never a decoy so thin it insults them.

Step 4 — Language rules

  • Their words > industry words. If they said "the phone stopped ringing," the goal section says that — not "lead generation optimization."
  • "You/your" should heavily outnumber "we/our."
  • No legalese in the proposal body; terms live in the separate agreement.
  • Short. Two to four pages of substance beats ten of filler. Every paragraph earns its spot or dies.

Step 5 — Deliver

Output the full proposal in markdown, then a delivery note:

**Delivery notes:**
- Walk it through live (call or in person) — never email a proposal cold. Email it *after* the walkthrough.
- If they ask for it by email first: "Happy to — I'll send it right after we spend 15 minutes on it together so the numbers have context."
- Follow-up: day 2 ("any questions on what we walked through?"), then the validity-date reminder 3 days before it lapses.

What not to do

  • Don't open with your company history. Nobody has ever bought because of an "About Us" on page one.
  • Don't include more than one testimonial/case — proposals bloat from insecurity.
  • Don't quote a price discovery didn't support; if budget was never discussed, the proposal call is the budget conversation.
  • Don't send editable files; PDF (or a proposal tool with e-sign).

Built by Reef — AI systems for small business → https://buildwithreef.com

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.