Sales-ready proof claims

Raw source preview

Raw, unprocessed file text shown below.

# Sales-ready proof claims

This is a founder-review draft for demos, decks, follow-up material, and live private-beta conversations. It uses the current launch narrative: answer faster, stay in control, and make insight travel further.

## How to use this sheet

- Choose three default claims for founder-led conversations.
- Pair every claim with a workflow, screen, approved customer example, or measured operating signal.
- Label the supporting product as live, beta, selected-customer-only, or directional.
- Treat mechanism proof as mechanism proof; do not turn it into an unmeasured customer outcome.

## Recommended core claims

### Answer faster without taking the researcher out of the loop

- Say: `<un>peel helps insight teams move from a research question to a usable answer faster, while keeping the researcher in control of the decisions that matter.`
- Proof hook: live survey and research workflows, structured review, and the human-in-the-loop Trust Centre.
- Maturity note: show only the workflows that are live for the buyer's agreed beta scope.

### Run the research, not just store the outputs

- Say: `Unlike a repository that only receives finished work, <un>peel connects design, fieldwork, quality review, analysis, and evidence reuse across the research lifecycle.`
- Proof hook: the design-collect-connect-share workflow, live core research products, and the connected evidence model.
- Maturity note: this is the platform differentiation; it is not a claim that every planned product is already generally available.

### Keep quality visible while the work is still live

- Say: `Teams can see and review quality signals while fieldwork is running instead of waiting for a hidden cleanup step at the end.`
- Proof hook: the live Trust Centre, its Real / Unique / Engaged review structure, human review, and the approved `38+ quality metrics` claim.
- Maturity note: do not claim Qualtrics-class post-field response-quality or enterprise maturity.

### Make insight travel beyond the final debrief

- Say: `Research stays connected to its evidence so people can find, reuse, and build on what the organisation has already learned.`
- Proof hook: Insight Navigator in controlled beta and the connected evidence layer.
- Maturity note: describe Insight Navigator as controlled beta and Segment Lens as in build; do not imply broad, measured cross-study ROI yet.

### Keep AI work traceable and reviewable

- Say: `AI does useful work inside a governed research workflow, with the source material and human decisions kept visible.`
- Proof hook: evidence-linked retrieval, project history, and reviewable decisions.
- Maturity note: show the exact traceability that exists in the demonstrated workflow; do not generalise beyond it.

## Product claims that need maturity labels

- Surveys, Discussion Groups, Guided Interviews, and Trust Centre: sell the live core that can actually be demonstrated and delivered.
- Discussion Groups V2: in test; do not present the V2 improvement set as fully released.
- Insight Navigator: controlled beta.
- Segment Lens: in build, with the current August-September target.
- Research Guard and Research Architect: October beta targets; preview only where explicitly agreed.

## Guardrails for live use

- Do not lead with `confidence` as the category differentiator. Use confidence, defensibility, audit trail, or governance only when they answer the buyer's question.
- Do not offer the `full designed product set` as though it is all live.
- Do not present Research Guard or Research Architect as generally available.
- Do not claim enterprise security, procurement, legal, connector, or low-touch rollout maturity beyond the current pack.
- Do not use customer names, logos, quotes, or outcomes until the proof-permission register records approval.
- Use `38+ quality metrics` where helpful. Do not use competing `20,000+` or `30,000+ lines` claims until the source and approved wording are reconciled.

## Founder approval required

- Select the three claims that become the default founder talk track.
- Approve the exact screen, mechanism, or evidence attached to each claim.
- Approve which claims can be public and which stay inside private-beta conversations.
- Confirm which named customers, logos, quotes, and results may be used.