Your direct contact loves the proposal. They understand the work, they trust your expertise, and they want to move forward. Then it goes to finance. The CFO has never heard of you, does not understand your methodology, and is looking at a $15,000 line item in a budget that is already under pressure. If your proposal does not speak the CFO’s language, ROI, payback period, cost per outcome, it will not survive that review. The Challenger Sale research found that B2B proposals with documented financial impact data are approved at rates 35–50% higher than those without it. The translation is not optional for high-ticket B2B work.
The CFO’s Native Language
Finance decision-makers evaluate investments on four metrics. Know them before you write the pricing section:
Payback Period. How long until the investment returns its cost? Under 6 months is typically self-approving in most organizations. 6–12 months requires moderate justification. Over 12 months requires a strong strategic case.
ROI Multiple. Total return divided by total investment. A 3x ROI in year one is a strong case. A 5x ROI is compelling. The denominator (your fee) should appear clearly, CFOs are suspicious of projections that obscure the investment.
Cost per Outcome. For clearly defined outcomes (cost per lead, cost per retained employee, cost per compliance incident avoided), this metric translates your fee into the organization’s operational metrics. A $20,000 retention program that prevents three senior employee departures at $40,000 replacement cost each has a cost-per-outcome of $6,667 to prevent a $40,000 event.
Cost of Inaction. What is the financial cost of not engaging? This is the most powerful CFO framing because it removes the “do nothing” option from the table. If the problem your work addresses costs the company $8,000/month, your $15,000 engagement pays back in less than two months, and the CFO who rejects it owns the ongoing monthly cost.
Building the Financial Translation Section
The Financial Translation section lives in the pricing portion of the proposal, after the investment line, not before it. The structure:
1. Identify the measurable outcome your work affects. Revenue, cost reduction, efficiency gain, risk reduction. If you do brand strategy, the measurable outcome might be conversion rate improvement or customer lifetime value increase. Be specific: “a 1.5-point improvement in demo-to-close rate.”
2. Quantify the current state. Use the client’s own numbers when possible (get these in the discovery call). “Your current demo-to-close rate is 18%. Industry benchmark is 24%. The 6-point gap represents approximately $340,000 in unrealized annual revenue at your current demo volume.”
3. Project the impact of your work. Conservative, not optimistic. “This engagement targets a 3-point improvement in the first 90 days, representing approximately $170,000 in first-year incremental revenue based on current pipeline volume.”
4. Calculate payback period. “$17,000 investment ÷ $14,166 monthly impact = 1.2-month payback period.”
When the payback period is under three months, the CFO’s question shifts from “should we approve this?” to “why haven’t we done this already?” That is the frame you want to create.
The Cost-of-Inaction Frame
The most powerful tool in the CFO translation toolkit is cost-of-inaction framing. It redefines the decision as: “How much does it cost us to NOT engage this person?”
The format: “Every month without [your work], this organization is absorbing [specific cost]. At the current rate, that accumulates to [annual cost]. The engagement investment represents [X] months of that ongoing cost.”
Example: “Your current manual reporting process costs approximately 22 analyst hours per month at a fully loaded cost of $12,100. The automation implementation eliminates 18 of those hours. At a project fee of $14,500, the payback period is 1.2 months, and the 10-year NPV of the automation is approximately $1.1M.”
A CFO who sees this math is not evaluating your fee. They are evaluating why they have not already made this decision.
Getting the Numbers From Discovery
None of this works without real client data. The discovery call is where you collect the inputs:
- Current volume metrics (leads per month, employees, transactions)
- Current conversion or efficiency rates
- Known cost lines (employee fully loaded cost, customer acquisition cost, churn rate)
- Prior attempts to address the problem and their outcomes
Ask directly: “To help me frame the ROI case for finance, what do you know about the current cost of [the problem]?” Most buyers will share this information readily, they want you to make the case for them.
The financial translation section is not a projection you invent. It is a calculation you build from the buyer’s own metrics, returned to them in CFO-legible format. You are their internal champion’s ammunition, not your own sales pitch.
When the Numbers Are Soft
Not all work has hard financial metrics. Brand strategy, thought leadership, culture work, and organizational design all produce outcomes that resist clean quantification. In these cases, shift to cost-of-problem framing rather than return-on-investment framing:
“Positioning ambiguity in your market costs an estimated $X per quarter in longer sales cycles and lower conversion rates from inbound leads. This engagement eliminates the ambiguity, but conservative ROI projection is beyond scope here. What I can document is the cost of the current state, which you have already identified as a strategic priority.”
When you cannot quantify the upside, quantify the downside. Every CFO understands downside risk. A credible cost-of-problem calculation, even a soft one, is better than no financial frame at all.
