A pattern that has been quietly appearing on B2B testimonial cards over the last eighteen months: the customer-reported ROI methodology disclosure. Beneath a headline ROI claim — 312% return in 14 months, or $2.4M in cost avoidance over two fiscal years — a short methodology paragraph names the inputs, the time horizon, the discount rate, and the assumption set behind the number. The pattern is doing a specific credibility job. It is converting the ROI claim from a vendor-marketing number into a finance-team-defensible number, which is the only kind of ROI claim that survives a buyer's CFO review of the procurement justification.
That conversion is powerful when the disclosure reads as customer-narrated finance work — written in the customer's accounting vocabulary, naming the customer's specific cost categories, and acknowledging the assumptions the customer's finance team would flag. It collapses when the disclosure reads as vendor-supplied calculator output dressed up as customer methodology, when the inputs match the vendor's ROI-calculator categories rather than the customer's chart-of-accounts categories, or when the methodology paragraph is generic enough to apply to any customer in any industry.
This is the breakdown.
The 30-second answer
A customer-reported ROI methodology disclosure earns credibility when the methodology paragraph uses the customer's accounting vocabulary and names the customer's specific cost categories, when the assumption set is acknowledged rather than hidden (including the assumptions the customer's finance team would push back on), and when the time horizon and discount rate match the customer's actual capital-budgeting practice. In that condition, the disclosure converts the ROI claim from a marketing number into a finance-team-defensible justification: the buyer reads it as evidence the customer's finance team approved the methodology, not just the bottom line.
It costs credibility when the methodology paragraph reads as vendor-supplied calculator output rendered in customer-quote phrasing, when the cost categories match the vendor's ROI-calculator schema rather than the customer's chart of accounts, or when the disclosure suppresses the assumptions the buyer's CFO would immediately flag (counterfactual baseline, attribution discounting, productivity-recapture realisation rate). In each case the methodology paragraph triggers an antibody response — the buyer reads the disclosure as a credibility theatre prop rather than as actual finance work.
The right call is to surface the methodology only when the customer's finance team co-authored the disclosure, to require customer-specific cost categories in the customer's accounting vocabulary, and to disclose the assumptions the customer's finance team flagged including the ones that reduce the headline number.
For broader context on attribution dimensions on testimonial cards, see our testimonial card with numeric result and quantified outcome credibility impact breakdown and the testimonial card with deal size and annual contract value attribution credibility impact guide.
What a methodology disclosure actually does on a card
The job of a customer-reported ROI methodology disclosure on a testimonial card is to convert a marketing ROI claim into a finance-team-defensible justification. Before any visitor reads the rest of the page, the disclosure has already done three things:
- Signalled that the customer's finance team participated in the number. A methodology paragraph that names the discount rate, the time horizon, and the cost categories carries an implicit claim that the customer's finance team approved the calculation — which the buyer reads as evidence the number can survive a parallel finance review on the buyer's side. The visible methodology is the receipt of finance-team participation.
- Implied the assumption set is auditable. A disclosure that names the productivity-recapture realisation rate, the counterfactual baseline, and the attribution discounting tells the buyer that the customer reasoned through the assumptions the buyer's CFO will flag. The buyer reads the visible assumptions as a proxy for the assumptions that were not visible but were reasoned through and held against the analysis.
- Triggered a peer-to-peer finance-review frame across the page. When the methodology disclosure reads as customer-finance-team work, the buyer reads the page as a peer customer's documented justification, not as a vendor's sales claim. The frame shift is what unlocks the buyer's willingness to attach the ROI number to their internal business case.
None of these signals are objectively good or bad. They are finance-defensibility signals, and the right signal depends on whether the disclosure reads as customer-narrated work or as vendor-supplied content carrying customer-quote phrasing.
When the methodology disclosure lifts credibility
Three contexts where the disclosure helps the card:
1. The methodology uses the customer's accounting vocabulary
The clearest case. The methodology paragraph names cost categories the way the customer's finance team names them — capitalised software cost, managed-services run-rate, internal-FTE fully-loaded cost including benefits and overhead allocation — rather than the way the vendor's ROI calculator labels them — software cost, services cost, productivity savings. The vocabulary tells the buyer that the customer wrote the disclosure rather than transcribing the vendor's calculator output.
The cue is small but high-density. Fully-loaded cost, capitalised versus expensed, recognised over a 36-month amortisation schedule, net of one-time implementation, risk-adjusted at 12% discount rate — these phrases are not in any vendor's ROI calculator. They are in the customer's finance team's spreadsheet. The presence of customer-finance vocabulary is the signal the disclosure is real.
2. The assumption set is acknowledged rather than hidden
The disclosure earns credibility when the customer names the assumptions the buyer's CFO would push back on — and acknowledges them. A line that reads We attributed 70% of the productivity-recapture to the new platform; the remaining 30% reflects concurrent process improvements we cannot disentangle is doing credibility work no headline number can do. The buyer reads the line and understands that the customer reasoned through the attribution-confounding problem rather than pretending it did not exist.
The same logic applies to the counterfactual baseline (we modelled the no-change scenario as the prior-vendor cost plus the contractual escalator), the time-to-realisation assumption (we did not start counting benefits until month four when the rollout reached 80% of the user base), and the discount-rate choice (we used the corporate WACC of 12% rather than a project-specific hurdle). Each acknowledged assumption is a signal the disclosure was authored by someone who anticipated finance-team scrutiny rather than someone who hoped to avoid it.
3. The time horizon matches the customer's capital-budgeting practice
The disclosure converts when the time horizon matches the customer's actual capital-budgeting practice — typically three years for software, five years for infrastructure, sometimes one year for SaaS subscription justifications. A methodology paragraph that names a three-year NPV calculation, discounted at our corporate WACC of 12%, with terminal value excluded is doing capital-budgeting work the buyer's finance team will recognise immediately as the same approach they use.
The cue is in the time-horizon discipline. A three-year NPV with a stated discount rate and an explicit terminal-value treatment reads as a customer's standard capital-budgeting analysis. A vague over the lifetime of the contract or over the first year of deployment reads as the customer letting the time horizon stretch to whatever produced the headline number — which the buyer's finance team will spot in fifteen seconds.
When the methodology disclosure costs credibility
Three contexts where the disclosure hurts the card:
1. The cost categories match the vendor's ROI calculator schema
The disclosure collapses when the cost categories named in the methodology paragraph match the categories in the vendor's ROI calculator one-for-one. Software cost, services cost, productivity savings — three categories in that order, with no fully-loaded FTE accounting, no capitalisation treatment, no overhead allocation. The buyer reads the schema and recognises the calculator. The credibility shift is sharp: the methodology was not authored by the customer's finance team; the methodology was authored by the vendor's marketing team and transcribed into customer-quote form.
The fix is to require the customer's finance team to rewrite the categories in the customer's chart-of-accounts language, even if the underlying inputs are similar. The vocabulary mismatch between the customer's accounting and the vendor's calculator is the credibility-protection mechanism.
2. The disclosure suppresses the assumptions the CFO would flag
When the methodology paragraph omits the productivity-recapture realisation rate, the counterfactual baseline, the attribution discounting, or the time-to-realisation lag, the buyer reads the omission as deliberate. The buyer's CFO knows that any honest ROI methodology has to address those assumptions, and a disclosure that addresses none of them reads as a number designed to survive marketing copy review rather than finance review.
The cost compounds when the omissions are the obvious ones. A disclosure that names the discount rate but omits the attribution percentage is doing partial credibility theatre — addressing the easy-to-disclose assumption while suppressing the hard one. The buyer's CFO will read past the disclosed assumption and ask immediately about the suppressed one.
3. The methodology is generic enough to apply to any customer
When the methodology paragraph contains no customer-specific operational detail — no industry-specific cost categories, no customer-specific process names, no customer-specific time-to-realisation observations — the disclosure reads as a vendor-template paragraph dropped into a customer card. The buyer's pattern-recognition fires immediately: a real customer's finance team would have written the disclosure in terms of the customer's specific cost stack, not in terms of a generic SaaS ROI framework.
The credibility cost is the same as a generic quote. The buyer reads the methodology and concludes that the entire card is vendor-authored rather than customer-authored, which contaminates the rest of the card. The fix is to require at least one customer-specific operational detail in every methodology disclosure — the name of the legacy system replaced, the specific business process re-engineered, the specific FTE category whose recapture was modelled.
The line-by-line credibility test
A practical test for evaluating a methodology disclosure is the who-could-have-written-this-sentence test, applied line by line.
For each sentence in the methodology paragraph, ask: could a vendor marketing writer have produced this sentence using only publicly available information about the customer and the vendor's standard ROI framework? If the answer is yes, the sentence is weak. If the answer is no — if the sentence requires inside-finance-team knowledge to produce — the sentence is strong.
A strong methodology disclosure has at least three sentences that only the customer's finance team could have written:
- A sentence naming the customer's specific cost-category vocabulary (fully-loaded cost including 28% benefits load and 12% overhead allocation).
- A sentence naming a customer-specific operational assumption (we did not count benefits in months one through three because the rollout was paused for the year-end accounting freeze).
- A sentence naming a customer-specific assumption-set acknowledgment (we attributed 65% of the productivity-recapture to the platform and 35% to the concurrent process redesign, which we cannot fully disentangle).
Three customer-only sentences in a methodology paragraph is the credibility threshold. Below that threshold the disclosure reads as marketing prose. Above it the disclosure reads as finance-team work.
Page-level mix rule
A single principle governs page-level deployment: the methodology disclosure should appear only on the cards where the customer's finance team co-authored it, not on every card with a numeric result. A page where every numeric result has an attached methodology paragraph reads as vendor-template inflation — the buyer's pattern-recognition fires that every customer happens to have a finance-team-co-authored disclosure of the same paragraph length and structure.
The mechanical rule is to surface methodology disclosures on the quantified-result cards where the customer's finance team explicitly agreed to publish the methodology, and to leave the other quantified-result cards with the number and the brief context, without the methodology paragraph. The asymmetric distribution — some cards with disclosures, most without — is itself a credibility signal that the disclosed methodologies are real customer-finance work rather than vendor-template inflation.
For attribution decisions on related dimensions, see our testimonial card with implementation timeline and time-to-value attribution credibility impact guide and the testimonial card with renewal count and year-over-year retention attribution credibility impact breakdown.
The implementation checklist
- Confirm customer finance-team co-authorship. Do not publish a methodology disclosure unless the customer's finance team has reviewed and approved the specific paragraph. A methodology paragraph produced by the vendor's marketing team in customer-quote phrasing is the highest-cost form of credibility theatre on the page.
- Require customer-accounting vocabulary. Cost categories must be named in the customer's chart-of-accounts language, not in the vendor's ROI-calculator schema. Specifically, require fully-loaded cost treatment, capitalisation-versus-expense treatment, and overhead-allocation treatment.
- Disclose the assumptions the CFO would flag. Productivity-recapture realisation rate, counterfactual baseline, attribution discounting, and time-to-realisation lag are the four assumptions every honest methodology has to address. A disclosure that omits any of them is partial credibility theatre.
- Match the time horizon to the customer's capital-budgeting practice. Three-year NPV with a stated discount rate is the standard for software; five years for infrastructure; one year only for SaaS subscription justifications. Vague time horizons signal a stretched calculation.
- Apply the line-by-line credibility test. At least three sentences must be sentences that only the customer's finance team could have written. Below that threshold, drop the disclosure and keep the headline number with brief context only.
The customer-reported ROI methodology disclosure is the highest-leverage credibility signal a quantified-result card can carry when the customer's finance team co-authored the disclosure. It is one of the highest-cost credibility signals when the disclosure is vendor-authored content rendered in customer-quote form. The discipline is in the co-authorship requirement upstream of the page, not in the methodology-paragraph wording downstream.