Send a proposal that closes, not one they rewrite.
Their problem in their words, the scoped solution, value-framed pricing, plain terms, and one dated next step.
Inside: The problem recap, the scoped solution, value pricing, and one next step.
Install it in one line, or paste it in.
~/.claude/skills/ and runs automatically when it is relevant.Connect your context. Set it to your motion.
it reads the account, deal size, stage, and the contacts automatically, so the recap and the pricing match the real opportunity.
pulls the buyer's own words on the problem and the outcome they wanted, so the recap sounds like them, not you.
pulls the accurate line items and terms, so the numbers are right the first time.
This was built for a B2B SaaS org selling scoped annual contracts. Set these to your stack:
The value metric is yours. The skill frames the price against the outcome you choose, not a generic one.
| Set this | What it is | Default / Example |
|---|---|---|
| DEAL fields | account, size, stage, contacts | Opportunity.AmountStageNameContactRole |
| PRICING model | how you package and price | per-seatper-usageflat platform fee |
| VALUE metric | the outcome the price maps to | hours savedpipeline addedcost avoided |
| TERM fields | length, start, payment terms | 12-monthnet-30start on signature |
| NEXT_STEP | the single action you want them to take | signbook the kickoffforward to procurement |
| BRAND | tone and format of the send | your templateyour voice |
Everything the skill does, in full.
Takes what you know about a deal and produces a proposal that moves it forward. It leads with the buyer's problem stated the way they stated it, scopes only the solution that solves it, frames the price against the value returned rather than a feature list, lays out the terms with no surprises, and closes on a single unambiguous next step. The output is written to send, not to be rebuilt from scratch.
- 1The problem recap (their words, not yours)
Open by restating the problem the buyer described, in language they would recognize as their own. This proves you listened and sets the frame the rest of the proposal answers to. If you cannot state their problem clearly, the proposal is not ready and the skill says so.
- 2The scoped solution (only what solves it)
Describe the solution as the answer to that problem, nothing more. Cut every feature that does not map to the problem you just recapped. Scope creep in a proposal reads as padding and slows the signature.
- 3Pricing framed on value (anchor to the outcome)
Present the price against the value it returns, not against a list of features. Tie the number to the VALUE metric the buyer cares about. The price should feel like the smaller number in a comparison the buyer already accepts.
- 4Terms, stated plainly
Lay out length, start date, payment terms, and anything that affects what they sign. No buried conditions. A term the buyer discovers late is a term that stalls the deal in legal.
- 5The one next step
End with a single, specific, dated action. Not "let us know your thoughts." One step, one owner, one date. A proposal with two next steps has none.
- The problem recap uses the buyer's language where it is available, never a generic restatement.
- Every scoped item maps to the recapped problem; anything that does not is cut.
- The price is framed against a named value metric, never presented as a bare feature list.
- Terms are stated in full, with nothing that would surprise the buyer in legal review.
- The proposal ends with exactly one next step, with an owner and a date.
- Any number in the proposal is shown as given or sourced, never invented to look precise.
PROPOSAL · Acme Corp (illustrative) The problem you described Reps rebuild the same account research by hand before every call, and it is costing your team roughly a day a week each. What we propose The workflow that pulls that research automatically, in the CRM your reps already live in. Nothing they have to learn separately. Investment $60K / year. Against ~1 day/week/rep returned to selling, this pays back inside the first quarter (illustrative figure). Terms 12-month term, starts on signature, net-30. No usage caps. Next step Sign by the 30th and we run kickoff the first week of next month.
Where an operator takes this next.
The manual version proves the shape works. Here is the scaled version once it does.
The proposal still needs a human signature on the strategy. This just gets it to their desk faster.
Trigger this in Salesforce or HubSpot the moment a deal hits Proposal stage, so the draft is waiting before the AE opens it.
Connect Gong or your email tool so the problem recap comes from the call transcript, not a rep's paraphrase.
Wire the finished draft into your e-signature tool via a scheduled Claude task, so the AE reviews and sends instead of building from scratch.
One skill is the on-ramp.
A single skill does one job. Chained into a playbook, or run as a full build, it becomes a system. Here is where this one plugs in.