Foundations
Credibility
Credibility is the degree to which the other side believes your promise will actually hold in their circumstances.
It is promise-specific and party-specific. It is not a general reputation score, and it is not a synonym for social proof. The same organisation can be highly credible about one promise and not credible at all about a larger one made to a different party.
“A promise creates value only to the extent the other side believes it will hold.”
The useful question is not “are we credible?” It is: what must they believe for this promise to carry its intended value? That question has answers you can act on. The general one does not.
It also follows that a stronger promise creates a larger credibility burden. If you raise the claim and leave the evidence unchanged, the offer usually gets weaker — the other side discounts the whole thing, including the parts you could have proven.
Decompose the required beliefs
A promise is rarely doubted as a whole. It is doubted at one or two specific joints. Which of these apply depends on the transaction — a licensing deal and a services sale load different ones.
The mechanism works
The thing you say produces the result actually produces it.
You can perform
Your organisation can deliver this, at this scale, on this timeline.
It works here
It holds in their circumstances, not only in the reference cases.
Dependencies will hold
The inputs, third parties, and assumptions behind it are realistic.
The timing is real
The horizon you named is achievable, not a best case.
They can do their part
They can implement, adopt, integrate, or participate as required.
Incentives stay aligned
You will still want to deliver this after the agreement is signed.
The rights are real
Access, exclusivity, or entitlements promised will actually be available.
Where doubt comes from
Doubt is usually not expressed directly. It surfaces as delay, extra approval steps, redlines, or a request for a discount. Locating it is more useful than answering the stated objection.
Your capability
“Can they do this at all, in our situation?”
Execution
“Can this particular team deliver it, reliably?”
Mechanism
“Is the causal story actually true?”
Evidence
“Is the proof relevant, or borrowed from a different problem?”
Applicability
“Do the reference cases resemble us in any way that matters?”
Dependencies
“Will the things this rests on hold?”
Our own execution
“Even if it works, will we get the result?”
Incentives and continuity
“Will they still be here, and still care, in year three?”
Evidence has to match the doubt
More testimonials and more logos are not a generic answer. If the doubt is “will this work on our data volumes,” a reference from a smaller company answers nothing. If the doubt is “will your team still be here in three years,” a case study is irrelevant and an ownership or continuity commitment is not.
Understanding the problem precisely is real evidence — of competence, and of having seen this situation before. It is not proof that the outcome will arrive. Do not let a good diagnosis stand in for a missing demonstration.
Evidence they experience generally beats evidence they are asked to trust, when the experience is genuinely predictive of the result. A pilot on a representative slice is worth more than a polished deck. A pilot on an unrepresentative slice can be worse than nothing, because it proves the wrong thing and invites a fair objection.
Credibility mechanisms
Pick by doubt, not by habit. Most organisations reach for the two or three they are used to producing.
Demonstration
Show the thing working, on something recognisable.
Pilot or sample
Let them experience a bounded version before committing.
Measured results
Case studies with real numbers and comparable conditions.
Third-party validation
Audits, certifications, independent tests, credible references.
Precise diagnosis
Describe their problem better than they can — evidence of competence.
Transparent mechanism
Explain how it works well enough to be checked.
Track record
History and brand, where they are genuinely predictive.
Expertise
Named people with demonstrable relevant experience.
Guarantees and remedies
Consequences if the result does not arrive.
Process controls
Milestones, gates, reporting, acceptance criteria.
Party-specific proof
Benchmarking or analysis run on their own data.
Two things that get confused
Guarantees are not proof
A guarantee, warranty, or remedy primarily reallocates risk: it changes who absorbs a bad outcome, not how likely the good one is. It can signal confidence, and that signal has some value. But a party who does not believe the mechanism works will not be convinced by a refund — they were never worried about the money alone.
Burden shapes belief
Where success depends heavily on the other side's execution, they may fully believe the capability works and still doubt that they will get the result. That is a credibility problem you solve structurally — by taking implementation work onto your side — not with more evidence. Burden and credibility interact; they are not the same thing.
Credibility by design
The strongest credibility interventions change the offer itself rather than the material that describes it.
- Observable milestones instead of a single delivery date
- Transparent workflows the other side can inspect while running
- Measurable outputs defined before work starts
- A pilot or staged commitment ahead of the full structure
- Implementation performed by you, with defined service levels
- Benchmarking run on their own data, not on a reference case
- Reversibility: an exit that costs them little if it fails
- Proof generated by the work itself as it proceeds
These are also deal moves: each one changes commitment, timing, or burden as well as belief. That is the point — credibility is bought with structure, and the structure has a price.
Credibility audit
- 01State the promise you are actually making.
- 02List what they must believe for it to carry its intended value.
- 03For each belief, identify where the doubt would come from.
- 04Inventory the evidence you already have, honestly.
- 05Match evidence to doubt — and mark the gaps where nothing matches.
- 06Design an intervention for the largest gap, preferring structural ones.
- 07Ask whether the promise should narrow instead.
- 08Test the revised offer with a real party, not internally.
Note step seven. Narrowing the promise is a legitimate answer, and often the fastest one. A smaller claim you can prove is usually worth more than a larger one they discount.
Where this sits in the framework
Credibility is not being introduced as an eighth dimension. Like Promise, it is an offer-design concept the current six-dimensional model underrepresents. The six dimensions remain in place provisionally while the architecture is reconciled through use.
Credibility relates closely to Risk without being identical to it. Risk covers uncertainty, downside, and who bears it. Credibility is whether the other side believes the promise will hold at all. A guarantee can reduce their downside without raising the probability of success by a single point — and sophisticated parties know the difference.
Both concepts also run through Burden: what the other side must do affects whether the promise is realised and whether they believe it will be.
Deal Geometry Diagnostic
Find the belief your deals are failing on.
The Deal Geometry Diagnostic reviews a sample of recent transactions and identifies the structural issues slowing your deals down.