client-proposal
/client-proposal
Use this skill when a proposal is due and it is about to be the last one with the name changed. Produces a proposal built from what the prospect actually said: their situation in their own words, the firm's named approach, scope with explicit exclusions, the objection they already raised answered directly, pricing options, and the proof the firm can stand behind. Also use for "I need a proposal out tonight", "respond to this RFP", "write the SOW", "pitch document".
- Author
- agiea-brain ↗
- Repository
- agency-skills ↗
- Licence
- MIT
- Last repository change
- 04.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 04.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use this skill when a proposal is due and it is about to be the last one with the name changed. Produces a proposal built from what the prospect actually said: their situation in their own words, the firm's named approach, scope with explicit exclusions, the objection they already raised answered directly, pricing options, and the proof the firm can stand behind. Also use for "I need a proposal out tonight", "respond to this RFP", "write the SOW", "pitch document".
Triggers from the description
Original author description
Use this skill when a proposal is due and it is about to be the last one with the name changed. Produces a proposal built from what the prospect actually said: their situation in their own words, the firm's named approach, scope with explicit exclusions, the objection they already raised answered directly, pricing options, and the proof the firm can stand behind. Also use for "I need a proposal out tonight", "respond to this RFP", "write the SOW", "pitch document".
How it works
- The play
- What good looks like
- Rules
SKILL.md preview
--- name: client-proposal title: Client proposal description: | Use this skill when a proposal is due and it is about to be the last one with the name changed. Produces a proposal built from what the prospect actually said: their situation in their own words, the firm's named approach, scope with explicit exclusions, the objection they already raised answered directly, pricing options, and the proof the firm can stand behind. Also use for "I need a proposal out tonight", "respond to this RFP", "write the SOW", "pitch document". category: Sales tags: [proposals, rfp, scope-of-work, pricing, new-business] --- Applies after a discovery call, when the firm knows what the prospect wants and has to put it in writing. Produces the proposal. ## The play 1. Write the situation section first, in the prospect's own language, before anything else in the document. If they said they were flying blind on what works, that sentence goes in, not "attribution challenges". This section is what makes the rest of the proposal land, and it is the one competitors skip. Everything after it is read more generously when the prospect recognises themselves at the top. 2. Name the approach using the firm's own methodology, with the firm's own names for its stages. A proposal that walks through this firm's named process is differentiated by default. One that walks through a generic four-phase engagement is interchangeable with every other proposal on the desk. 3. Answer the objection they already raised, early and in its own section. If they complained the last firm never reported, reporting gets addressed before the scope, not buried where they will miss it. The objection they volunteered is the thing they are actually buying against. 4. Scope the work: deliverables, how many, how often, who produces each. Then write the exclusions explicitly. Vague scope is what turns a signed deal into an unprofitable one by month three, and the exclusions section is where that is prevented. 5. Set the timeline against the prospect's stated deadline, with real milestones on real dates. 6. Build two or three pricing options with a genuine difference in scope between them, not the same work at three service levels. Price from what comparable engagements actually went for. A guessed price is either leaving money on the table or losing the deal, and both are expensive. 7. Add only proof the firm can stand behind: results with periods attached, clients confirmed as nameable. If nothing in the library fits, leave a marked gap rather than reaching for something adjacent. A result the prospect checks and finds overstated loses the deal and the referral. 8. Close with terms and one specific next step on a date. "Let us know your thoughts" ends a proposal with nothing happening. ## What good looks like - First thing I check that most people skip: whether the document contains one sentence the prospect themselves said. If I can swap the name out and send it to somebody else, we have written a brochure and they will read it as one. - The mediocre version: last quarter's proposal with the name replaced and the scope adjusted. It is faster, it is obviously faster, and it loses to whoever spent the extra hour on the situation section. - I know it is right when the prospect quotes our own situation section back to us on the next call. That means they recognised themselves in it, and everything after that gets read generously. - Second test: the scope has exclusions. A scope with nothing excluded means nobody has thought about month three, and month three is where the margin goes. - Red flag: one pricing option. It forces a yes or no on the whole engagement instead of a conversation about shape, and it leaves the prospect nothing to negotiate with except the price. ## Rules - MUST write the situation section in the prospect's own words, first. - MUST use the firm's named methodology rather than a generic phase structure. - MUST answer the objection the prospect raised, in its own section, early. - MUST write explicit exclusions alongside the scope. - MUST give pricing options a real difference in scope. - MUST attach a time period to every result cited. - MUST end with one dated next step. - NEVER invent a client name, a metric, a case study or a price. Mark the gap and ask. - NEVER name a competitor. - NEVER open with a capabilities tour.
Versions
The database has no other skills named client-proposal.
Database snapshot: 13.11.2026 · package version a17f31858579 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100proposal-pricing
When the user wants to build a proposal, structure pricing, create an SOW, or present a deal to a prospect. Also use when the user says 'write a proposal,' 'help me price this deal,' 'create an SOW,' 'build a pricing page,' 'put together a quote,' 'send them pricing,' 'scope… - 100agency-proposals
When an agency needs to write a winning proposal, SOW, or pitch document for a prospective client. Also use when the user mentions "proposal," "SOW," "pitch deck," "statement of work," "scope document," "how do we win this deal," or "quote for the client." Produces a… - 90proposal-generator
Creates professional, customized sales proposals and quotes for small business deals. Auto-brands with the sender's identity from session context or memory. Use when user says 'write a proposal', 'create a quote', 'draft a bid', 'put together a proposal for [client]', 'help me… - 100sales-proposal-writer
Writes a B2B sales proposal or SOW that restates the buyer's problem in their own words, quantifies the cost of inaction, presents price as anchored options, and drives one dated next step. Use when someone asks "write a proposal for this client", "turn my discovery notes into a… - 100proposal-writer
Writes the document that asks a named client to buy a named engagement at a named price: their situation in their own words, two to four measurable outcomes, an approach described by what each phase produces, deliverables precise enough to settle a later dispute, a timeline… - 90b2b-proposals
When the user wants a B2B proposal, SoW, scope of work, or RFP response that wins. Also use when the user mentions "proposal," "SoW," "scope of work," "RFP response," "win rate," or "discounting.