Back to Proof, Pilots, and Onboarding
In progressOwner: Desmond + FounderFounder decision required

Workstream

Proof and credibility

Current proof splits into three layers: mechanism proof is strong, pilot signal is real but mostly unpermissioned, and named commercial proof is still absent. The missing piece is not whether evidence exists, but whether it can be packaged and claimed safely in market-facing materials.

Why this matters

Trust-led positioning lives or dies on evidence. If the company claims defensibility without showing its own, the story weakens immediately.

Strong proof also reduces the founder's burden in sales conversations because buyers can see product truth instead of taking a leap of faith.

Current state

Mechanism proof is real: survey design, Trust Centre, respondent review, pre-launch validation, and workflow continuity are specified at a level that shows genuine product depth rather than concept slides. The new competitive deep dive also shows where that proof is strongest today — governed redesign and methodological traceability — and where it should not be overstated into incumbent-level platform maturity.

Pilot signal is also real: Musgrave walkthroughs, follow-up asks, and Leanne's operations pain points show live customer engagement and concrete value territory. What is missing is permissioned packaging - outcome metrics, quotable evidence, named references, and case-study-grade material that can travel without explanation.

Internal Empathy Research usage can become a proof engine too, but only if the team decides which product claims need full case studies and which can be supported by short customer reviews, usability quotes, or internal dogfood evidence.

Checklist

What still has to happen

Foundation

The minimum decisions and assets needed so the launch story is coherent rather than aspirational.

Ready for betaImportant before first customers

Lead with mechanism proof in all beta materials

The product already has unusually specific capability proof that should be treated as a strength, not hidden because case studies are light.

Private preview

The hardening work required for founder sharing, pilot conversations, and limited buyer-facing use.

In progressImportant before first customers

Rewrite pilot interactions into reusable proof briefs

Musgrave and Leanne material can be converted into short evidence summaries, objection answers, and slide proof points.

In progressImportant before first customers

Define the case-study and customer-review proof plan

Agree which product claims need full case studies with Empathy Researchers or customers, and which can be proven with shorter customer reviews or usability quotes.

Early selling beta

The repeatable selling and operating layer needed to move beyond one-off founder conversations.

Blocked

Secure permissioned customer references and outcome metrics

Named quotes, quantified before-and-after proof, and logo permissions remain a later-stage credibility layer rather than a hard beta prerequisite.

What exists

Product mechanism proof

The company can already point to detailed evidence about questionnaire review, governed redesign, respondent quality, survey readiness, and workflow continuity, even if incumbents still lead on builder-native UX and enterprise proof packaging.

Live pilot interaction

Customer walkthroughs and follow-up items show that real users are engaging with the product, shaping what gets improved, and reacting positively to the workflow direction.

Empathy Research dogfood path

Internal researchers can produce credible before-and-after proof for the workflow changes the platform is meant to create, especially where external customer proof will take longer to permission.

What is missing

  • No polished, permissioned case study or quantified outcomes pack exists yet.
  • Proof is stronger at mechanism and customer-engagement level than at ROI, benchmark, or procurement-friendly reference level.
  • There is not yet an agreed rule for which claims need case studies versus lighter customer reviews or testimonials.

Open strategic questions

  • Choose the beta proof posture: lead with product-mechanism proof only, or supplement it with anonymised pilot stories and named references where permission exists.
  • Set the rule for customer names, logos, and anonymised pilot material in beta materials, especially around Musgrave and any future pilot conversions.
  • Decide which products need Empathy Research case studies, which need customer reviews, and which require permissioned external customer proof before broader launch.