Send a proposal that closes, not one they rewrite.
“Why does every proposal I send come back rewritten by the buyer?”
Their problem in their words, the scoped solution, value-framed pricing, plain terms, and one dated next step.
What this skill does
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.
Inputs
- Works today with: what you paste about the deal. The problem they described, what you are proposing, the price, the term, and the next step you want. A short brief is enough to start.
- More powerful connected to a CRM: it reads the account, deal size, stage, and the contacts automatically, so the recap and the pricing match the real opportunity.
- Sharper with a meeting or email tool: pulls the buyer's own words on the problem and the outcome they wanted, so the recap sounds like them, not you.
- Sharper with a pricing or quoting record: pulls the accurate line items and terms, so the numbers are right the first time.
How it works
- 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.
Output format
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.
Tips
- 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.
Turn a discovery call into a qualification scorecard.
Runs your call against your qualification framework, captures the deal, and names the gaps you still have to fill.
Build a demo that maps to the buyer's problems.
Maps every feature you plan to show to a problem the buyer actually stated, and cuts what does not map.