Section 1
Key takeaways
• Buyers must internally justify the spend, and an activity list gives your champion nothing to defend it with in the room you are not in. • Quantified value selling wins more: value-selling research reports meaningfully higher win rates and larger deals for sellers who quantify outcomes versus those selling features . • A quantified business case also shortens cycles and reduces discounting pressure, because the number anchors the price to value rather than to your hourly cost . • Buyers reward decision confidence, and a proposal full of concrete numbers is a confidence-building instrument . • The framework is the number-per-line audit: for every deliverable, state the metric it moves, the baseline, and the expected direction, even when the number is an honest estimate.
Section 2
Why activity-based proposals stall in the finance room
The core failure of an activity proposal is that it describes your inputs and stays silent about the buyer's outputs. "Monthly reporting" is your input. What the buyer wants to fund is the decision that reporting improves or the waste it eliminates. When you list the input and skip the output, you force the buyer to do the translation from "things you do" to "value we get," and buyers rarely do that translation. They just see cost with no anchored return, and cost with no anchored return is what gets cut. The problem compounds because the person defending your proposal is usually not the person who felt the pain. Your enthusiastic contact takes your proposal to a finance lead or an executive whose default question is "why this, why now, why this much?" A quantified proposal answers all three before the question is asked, which is exactly what a documented ROI business case is built to do: give the internal buyer the numbers to win the approval conversation . An activity proposal leaves your champion stammering. You are not writing the proposal to persuade the person who read it, you are writing it to be defended by that person to someone tougher. This is why quantified value selling outperforms. When sellers attach numbers to outcomes, win rates rise, deals get larger, and cycles get shorter, because the buyer can build the internal case instead of guessing at it . Quantification also reduces discounting: when the price is anchored to a documented outcome rather than to your hours, there is less room for the buyer to treat it as an arbitrary number to negotiate down . And it feeds directly into decision confidence, the sentiment Gartner ties to high-quality purchases, because a buyer holding concrete numbers feels far more certain than one holding a list of tasks .
Section 3
The honest-estimate objection, handled up front
The most common reason founders skip quantification is that they feel they cannot promise a number. This is a real concern and it deserves a real answer, not a dodge. You are not required to guarantee an outcome. You are required to make the value legible. There is a large difference between "this will generate $400,000" as a promise and "based on your current 18% close rate and $40,000 average deal, moving close rate to 24% is worth roughly $X in new revenue on your existing pipeline" as a modeled estimate the buyer can inspect and challenge. The second version quantifies without guaranteeing. It shows the buyer the logic, uses their own baseline numbers, and states the assumption openly. If the buyer disputes the assumption, good, now you are having a value conversation instead of a price argument. An honest, transparent estimate the buyer can pressure-test builds more confidence than a vague claim and more trust than a guarantee you cannot keep. Quantify the mechanism and the math, and let the buyer own the assumptions.
Section 4
The BGA framework: the Number-Per-Line Audit
Go through your proposal line by line and refuse to let any line survive without a number. For each deliverable, answer three questions: what metric does this move, what is the current baseline, and which direction and how much do we expect it to change. 1. Attach a metric to every deliverable. For each line, name the one number the buyer cares about that the work moves. If a deliverable does not connect to any metric the buyer values, question whether it belongs in the proposal at all. Every line either moves a number or justifies its own removal. 2. Anchor to the buyer's baseline, not to industry averages. "Improve your close rate" is weak. "Move your close rate from 18%, where it is today, toward 24%" is strong, because it uses the buyer's real starting number. Gather these baselines during discovery specifically so your proposal can quantify against them. The buyer's own numbers are the most persuasive numbers you can use. 3. State the value as a transparent estimate, with the assumption visible. Show the math: baseline, change, and the resulting dollar or time value, with the key assumption stated so the buyer can challenge it. This quantifies without guaranteeing, and it converts a price objection into a value discussion, which is where you want the conversation . 4. Translate the total into the buyer's justification language. Somewhere in the proposal, roll the line-level numbers into one sentence your champion can carry into the finance room: "the engagement costs $X, and on your current pipeline the target outcomes are worth roughly $Y, a Z-to-one return if we hit the midpoint." That sentence is the whole point. It is what gets defended when you are not there. 5. Where you genuinely cannot quantify, quantify the cost of inaction instead. Some value resists a clean number. In those cases, quantify what the buyer loses by doing nothing, the deals ghosting, the hours wasted, the churn, so the proposal still carries a number even where the upside is hard to model. A quantified downside is still a quantified line, and it is often the most motivating number on the page. This is the value-quantification discipline that turns a proposal into a business case.
Section 5
Your proposal passes the audit when…
Your proposal passes when you can read it line by line and find a number on every line, whether that number is an outcome target, a baseline it moves, or a cost of inaction it removes. It passes when every number is anchored to the buyer's own figures gathered in discovery, not to generic industry benchmarks. It passes when there is one sentence your champion can repeat in a finance meeting to defend the entire spend. And it passes when your deals stop stalling after the proposal goes out, not because you raised your prices or lowered them, but because you stopped sending activity lists to buyers who needed a business case, which is the only version of a proposal that survives the room where the real decision gets made without you.