How do we communicate the value behind our pricing?

What should our pricing explanation actually do?

A pricing explanation should help a buyer decide whether a particular exchange is worthwhile under stated conditions. Explain what the commitment will set in motion in the buyer’s company, what the buyer must contribute, and how both parties will recognize useful progress.

A price needs neither an apology nor a story about how hard the seller works. The relevant question is whether the buyer should direct resources into this offer rather than the best available alternative. For a post-seed B2B startup, keep three jobs separate:

• Create value: deliver an improvement in the customer’s actual work.
• Set the price: choose commercial terms that account for alternatives, willingness to pay, delivery economics and strategy.
• Communicate value: make the relevant improvement and its conditions understandable and credible.

Confusing these jobs produces familiar mistakes. A polished explanation cannot repair a product that fails in use. A large modeled benefit does not establish purchasing authority or available funding. Your delivery costs matter to business viability, but do not establish what the buyer gains.

The useful discipline is to make the comparison contestable. A buyer should be able to correct the baseline, reject an assumption or choose a simpler alternative without being told they failed to understand your value.

Which buyer and alternative should our value proposition address?

A pricing value proposition should compare the offer with the alternative a specific buyer would actually choose. That alternative may be an internal workaround, existing software, another supplier or postponing the work. Naming a competitor does not establish that the competitor is the relevant comparison.

In their 2006 HBR article, Anderson, Narus and van Rossum offer a framework for identifying the differences customers value most, not a controlled estimate of conversion improvement.

Distinguish three kinds of claim. A difference changes the comparison. A point of parity meets a requirement both alternatives satisfy. A point of contention is something buyer and seller disagree about and must investigate. Compatibility may deserve prominent treatment because it removes a mistaken concern, even when it is not distinctive.

Do not turn every stakeholder’s priorities into a different promise. Keep the underlying claim consistent and change the evidence each person needs:

Buyer role	What the buyer contributes or risks	What the value explanation must establish
User or operations owner	Training, review work and disrupted routines	Which work disappears, which remains and whether output quality holds
Economic buyer	Resources and responsibility for the decision	Why the improvement matters now and how it compares with alternatives
Technical evaluator	Integration effort and responsibility for failures	Compatibility, access, recovery and ongoing maintenance
Internal champion	Coordination time and personal credibility	An explanation colleagues can verify without the seller present

Write down both sides of the exchange. The supplier commits to agreed delivery, support and evidence; the buyer commits payment, access, staff time and approvals. Specify ownership and handover so the buyer knows which usable work remains if the engagement ends.

Ask for the last occurrence of the problem, then examine its records. Compare what people say matters with work they actually perform, purchases they considered and reasons they deferred a decision. Segment by the circumstances that change value, rather than using company size as the entire explanation. Start with product features translated into provable sales messages, then add the commercial comparison.

How do we estimate value without inventing ROI?

A value estimate should expose the incremental benefit against a credible alternative, including disadvantages and transition work. Use operational units when those are defensible; do not convert hours released into financial return until the buyer can explain how that capacity will be used or expenditure will change.

Economic value estimation has a reference component and a differentiation component:

Economic value estimate = reference value of the next-best alternative + favorable differences minus unfavorable differences.

For a purchasable alternative, the reference is its price for a comparable scope and period. Differences may include operating effort, reliability or implementation burden. If the comparator is a manual process, establish its relevant resource use rather than inventing an equivalent supplier quote. Include the alternative’s advantages as well as its weaknesses.

LeveragePoint’s 2014 explanation separates estimating relative economic potential from determining what can be charged, offering vendor guidance rather than experimental evidence of willingness to pay or realized value.

Anderson and colleagues use value word equations to make the inputs behind a comparison inspectable. The worked example below stops at capacity because it has no defensible financial inputs.

Illustrative reporting-workflow model, prepared 5 November 2026. Every input is an editorial assumption, not a customer observation or result. The comparison assumes the same reporting volume and acceptance standard in both workflows.

Input	Assumed value	What a real buyer must verify
Current preparation and rework	12 hours each week	A task log that includes corrections and handoffs
Proposed review and exception handling	4 hours each week	A representative run, including failures
Transition work	16 hours once	Setup, access, training and parallel running
Evaluation horizon	6 weeks	A period relevant to the buyer’s decision

The capacity equation is:

Net hours released = (current weekly work minus proposed weekly work) × evaluation weeks minus transition hours.

With those assumptions, (12 minus 4) × 6 minus 16 = 32 hours of net capacity released over the evaluation period. The recurring difference is 8 hours each week; the initial transition absorbs part of it. These are calculations from the stated hypothetical inputs, not measured savings.

Stress the assumption most likely to fail. If review and exceptions instead require 10 hours each week, the same calculation gives (12 minus 10) × 6 minus 16 = minus 4 hours. The proposed workflow then consumes additional time within that horizon. A longer horizon may change the comparison, but does not make the initial burden disappear.

Compare the complete workflows, including the review and exception work that remains after automation.

The interpretation matters more than the arithmetic. Capacity released can support another task without reducing expenditure. Avoided expenditure requires an actual change in spending. Additional revenue requires a further causal chain: the released time must reach an activity that produces an attributable commercial result. Do not add a time-saving claim and a revenue claim when both describe the same benefit. The buyer also needs the actual commercial terms before judging whether the modeled improvement warrants your price.

Record who supplied each input, when, from which records and with what uncertainty. Check volume changes, staffing changes and unfinished work. An apparent improvement that merely shifts review onto another team is a transfer of effort. Keep risk reduction separate unless the failure probability and consequence are defensible; a speculative avoided catastrophe should not carry the buying argument.

What evidence can we use before we have case studies?

A startup without case studies can demonstrate capabilities, disclose assumptions and agree a prospective measurement plan. Process evidence shows how work will be performed and checked. It cannot establish that a customer outcome has already occurred.

Use a demonstration to support the narrow claim it actually tests. A reporting automation can demonstrate a scheduled import, an access failure, a visible alert and a recoverable output. Those observations do not prove net time saved across a customer team, let alone commercial return.

Töytäri and Rajala’s 2015 exploratory study of nine global industrial companies supports identifying, quantifying, communicating and verifying value as connected organizational capabilities, without establishing a causal sales uplift for early-stage software or services.

Before work starts, agree the baseline, output acceptance criteria, customer inputs, measurement owner and review date. Preserve the distinction between intended benefits, demonstrated behavior and observed outcomes. If the work is exploratory, describe it as such. The same discipline applies when turning design partnerships into market proof.

Carry the record through onboarding and renewal, including when turning successful pilots into lasting customer relationships. Replace assumptions with observations as evidence develops, including misses. Ask the champion to forward the explanation internally and have the recipient identify the alternative, required effort and unresolved questions. Correct misunderstandings before treating a signed agreement as proof of understanding.

Should we disclose our costs to make the price feel fair?

Cost disclosure can change a buyer’s interpretation of a price, but supplier cost is neither customer value nor proof of fairness. Distinguish disclosure of production costs, visibility into operating work, and clarity about the customer’s full commitment. They answer different questions.

Three research findings are useful, with boundaries:

• Kahneman, Knetsch and Thaler’s 1986 telephone surveys found that respondents distinguished protecting an established profit position from exploiting a demand shock, describing fairness judgments rather than modern B2B purchasing behavior.
• Bolton, Warlop and Alba’s 2003 studies found that consumers overlooked some vendor costs and attributed price differences to profit, with corrective explanations only modestly effective, rather than establishing that explaining overhead resolves a procurement objection.
• Mohan, Buell and John’s 2019 author working paper reports increased soup purchasing with cost disclosure in a preregistered cafeteria experiment and subsequent online experiments investigating trust and purchase interest, without establishing that opening a B2B startup’s cost structure improves conversion or retention.

The practical implication is selective clarity, not a universal instruction to publish margins. Explain the work and responsibility that matter to delivery: exception handling, maintenance, review and support. Disclose costs when they genuinely help the buyer evaluate the arrangement, such as a pass-through dependency. Make clear whether a breakdown is complete and which assumptions can change.

Do not pad the explanation with internal activity to make the invoice look deserved. More labor may mean more care, an inefficient process, or work the buyer does not need. Equally, a higher price is not itself evidence of higher quality. Show the relevant reliability, scope or service behavior directly.

What belongs beside the price on a page or proposal?

A pricing page or proposal should put the decision facts beside the commercial commitment: intended buyer, supported outcome, scope, dependencies, evidence and terms. Benefits orient the buyer; specifications and boundaries let the buyer check whether those benefits apply.

Choose the form according to what is already known:

Buying situation	Useful presentation	When that presentation is a poor fit
Stable scope and predictable customer requirements	A direct package comparison with complete terms	Material implementation dependencies remain unknown
Known problem but variable integration or delivery effort	A scoped proposal showing assumptions and responsibilities	The meeting merely repeats information that could be public
Uncertain feasibility or buyer benefit	A bounded evaluation with a decision question and stopping criteria	The parties already have enough evidence to decide
A satisfactory existing process	An honest comparison that permits staying with it	The seller assumes every buyer needs an upgrade

Give each tier a recognizable use situation and a reason to choose it. Explain both its useful boundary and its limitations. Features required for the stated outcome belong in the comparison; placing essential work in an unexplained add-on makes the advertised package hard to evaluate.

State the charging unit, billing cadence, included work, exclusions, customer effort, minimum commitment, mandatory dependencies and change or exit terms. Distinguish usage limits from delivered outcomes. If billing grows with usage while the benefit depends on successful adoption, explain both relationships. A charging metric is not automatically a value metric.

Morwitz, Greenleaf and Johnson’s September 1998 Marketing Science Institute paper reports consumer experiments in which splitting a price into a base and a surcharge increased demand and lowered the recalled total, without establishing better comprehension or lasting B2B trust; make the complete commitment visible upfront as the honest basis for acceptance.

For outsourced work, ask for a fixed scope, a maximum number of hours and an end date. A buyer should know what happens when the scope changes rather than discovering the rule after delivery begins.

How should we respond when a buyer says it is too expensive?

A price objection needs diagnosis before persuasion. The buyer may question the comparison, distrust the evidence, lack authority, face an implementation constraint or simply prefer another use of resources. Understanding the benefit does not oblige the buyer to buy.

Ask: “Compared with which alternative, and what makes that alternative preferable for you?” Then establish whether the concern is the expected benefit, complete commitment, timing or ability to implement. Check scope before defending a difference between quotations. Another supplier may genuinely offer the more suitable arrangement.

Before the conversation turns to price, put the scope of the cheaper quote and your own side by side in one table with rows for parity, difference and contention. Record what both include, where delivery or responsibilities differ, and which disputed claims need evidence.

For the hypothetical reporting workflow, usable wording is:

The comparison is with preparing and correcting the reports manually. The automation still requires review and exception handling. We have not measured your net time saving yet. Before recommending a commitment, I would check the current workload, run representative reports and count the work left with your team. If review absorbs the expected benefit, we should keep or improve the manual process.

Do not answer a feasibility concern with a discount, or an affordability constraint with an ever larger return forecast. Narrowing the scope may help, but explain what benefit is removed with it. If a buyer can accurately repeat the comparison and still declines, record the reason as evidence about fit or commercial terms. Repeating the pitch does not resolve that finding.

How do we explain a price increase to existing customers?

A price-change explanation should identify what changes, when it applies, why it changes and which choices remain. Separate a change in delivery scope from a correction to the seller’s commercial terms. Describe the actual reason rather than attributing every increase to improved customer value.

Campbell’s 1999 research found that inferred motive influenced perceived fairness, with reputation affecting that inference, without establishing an effective notification template or actual B2B renewal behavior.

Homburg, Hoyer and Koschate’s 2005 abstract reports that satisfaction moderates how increase magnitude and perceived motive fairness affect repurchase intentions, without establishing actual B2B renewal behavior.

Prepare a comparison the account owner can check: existing scope, revised scope, changed responsibilities and unchanged elements. If only the commercial terms change, say so. Distinguish changes outside your control from your own choices. An explanation of your reason is not evidence that the buyer receives an additional benefit.

An example opening, suitable only when the stated reason is accurate:

At your next renewal, the commercial terms for the current scope will change. The included work stays the same. The reason is to bring those terms into line with the resources required to deliver that scope. I can walk through the revised proposal, consider a narrower scope or explain how to end the engagement under our agreement.

The final notice must include the actual effective date and applicable terms. Send it with time for the customer’s decision process and follow the existing agreement. Avoid introducing the change as though the customer has already accepted it, or making access to their data depend on accepting a broader package.

What should a buyer’s AI agent be able to read?

A buyer’s agent should be able to extract the offer, comparison, conditions and unresolved questions from maintained text. Publish the same decision facts a careful person needs, with evidence attached to claims. Treat successful extraction as something to check, not an assumed consequence of adding markup.

Google Search Central’s guidance, checked on 5 November 2026, recommends important content in textual form and structured data matching visible content, with no special machine-readable file or schema required for its AI search features, without establishing how every purchasing assistant reads a pricing page.

Keep inclusions, exclusions, billing basis, implementation duties, evidence dates and current terms accessible without relying on a screenshot, hover interaction or an uncompleted form. Link detailed exceptions from the relevant claim. For custom offers, explicitly mark which commercial facts require confirmation. Unknown terms should remain unknown, rather than looking like missing conditions an assistant can safely infer.

Ask an assistant to compare your public offer with the named alternative and quote its sources. Check the result against the page, including omitted dependencies and confused package boundaries. A correct extraction checks that task on that occasion; it proves neither broad discoverability nor purchasing accuracy. Use the fuller guidance on making a startup offer easy for buyer agents to evaluate.

When is better pricing communication the wrong fix?

Pricing communication is the wrong fix when the buyer understands the offer but the exchange is unattractive, infeasible or unsupported by evidence. Change the product, scope, segment, timing or commercial terms when that is what the evidence requires.

If implementation effort exceeds the plausible benefit, simplify delivery. If the claimed outcome does not occur in use, investigate the product. If the evidence applies to a different segment, narrow the claim or collect relevant evidence. If buyers like the idea but cannot name a current problem it resolves, research the problem before refining the pricing page. The distinction between a GTM problem and a product problem helps locate the work.

The studies discussed here do not establish an optimal B2B pricing-page layout or predict the effect of your revision. Judge a revision by what buyers can explain, which assumptions they challenge and whether suitable opportunities proceed with a shared understanding. Track unresolved objections and later delivery findings alongside progression. More acceptances accompanied by misunderstood scope or disappointing adoption would not establish better value communication. The aim is an informed commitment that remains intelligible after the sale.

How can Poldermarketing help make that comparison clear?

Piet Baudoin at Poldermarketing works remotely in Dutch and English with post-seed startups building their go-to-market. He connects positioning and messaging with findability in Google and AI answers, and builds and runs AI automations for lead follow-up, enrichment, qualification, CRM setup, reporting, content distribution and tool integrations.

He has no case studies. The starting point is an inspectable scope and measurement plan tied to the buyer’s workflow. A free growth scan can identify where the current explanation leaves the buyer unable to judge the offer.