proposal-drafting-framework
Skill0 starsChanged 4 months agoMITView on GitHub
Build a proposal from messy call notes by leading with their problem, scoping the work in their terms, and pricing it as an outcome. After discovery, when the owner needs a proposal or scope of work that actually reflects what the prospect said.
In this repository29 other files it gives its agents.
- devils-advocate-first-passSkill
- load-bearing-assumptionSkill
- pre-mortemSkill
- reversibility-checkSkill
- three-option-framingSkill
- boundary-setting-declineSkill
- cold-intro-structureSkill
- customer-reply-tone-matchSkill
- quote-follow-upSkill
- subject-line-not-filteredSkill
- end-of-day-reflectionSkill
- inbox-triageSkill
- project-scaffoldingSkill
- quote-drafting-from-notesSkill
- vendor-invoice-categorizationSkill
- competitor-pricing-extractSkill
- customer-voice-extractSkill
- source-verificationSkill
- tactic-extractionSkill
- vertical-landscape-scanSkill
- discovery-call-note-captureSkill
- lead-qualificationSkill
- objection-handlingSkill
- stack-the-deck-closeSkill
- dont-be-a-chatbotSkill
- honest-hedgingSkill
- lead-with-the-actionSkill
- specific-over-genericSkill
- write-like-the-userSkill
The file
Files
Turn Notes Into a Proposal
A proposal that wins reflects the call back to them. Open on the problem they described, scope the work as the solution to that problem, and price it against the outcome — not as a parts list.
The technique
- Open with their problem in their words — proof you were listening, before a single line item.
- Scope the work as outcomes, then the steps under each. "Stop losing jobs to slow quotes" → the system that fixes it. Not a naked feature list.
- Price against the outcome, not the hours. Anchor to what the problem costs them, so the number reads as a deal.
- Make the path obvious: what happens first, what you need from them, when it's done. No mystery.
- One clear next step at the end — sign here, reply yes, book the kickoff. Not three options that stall the decision.
Do this, not that
Do: Open: "You said you're losing two days a week to invoicing and it's costing you jobs." Then scope the fix, price it against the cost of those lost days, and end with "Reply 'go' and we start Monday."
Don't: Send a generic template that opens with your company bio and lists features and hourly rates with no connection to anything they said on the call.
Why this works
A prospect reads a proposal asking one question: does this person understand my problem? Leading with their own words answers yes before you've asked for the sale. Pricing against the outcome reframes the number from a cost to a return — "$5k to stop losing $2k a week" sells itself, where the same $5k as a line item invites haggling.
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
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.

