Sales-ready proof claims

Raw source preview

Raw, unprocessed file text shown below.

# Sales-ready proof claims

This draft is for founder review. The goal is to turn the positioning into short repeatable claims that can be used in demos, deck language, and live sales conversations.

## How to use this sheet

- Pick the 3 to 5 claims that should appear most often in founder conversations.
- Pair each claim with a product screen, workflow example, or internal usage signal.
- Keep the wording short enough to say naturally, not just to write on a slide.

## Recommended core claims

### We help teams catch weak research earlier

- Say: `Before launch, <un>peel helps teams catch the questionnaire problems most checkers miss — whether the screener qualifies the right people, whether the logic holds together, whether earlier questions are shaping later answers, and which fixes actually need approving.`
- Proof hook: Research Architect, Research Guard, the pre-launch review flow, and the junior-safer / senior-faster value story.
- Best used in: the opener or the design-quality part of the pitch.

### We keep confidence visible while the work is still live

- Say: `Teams do not have to wait until the end of a project to see whether the work is holding up.`
- Proof hook: the confidence-through-the-workflow story, Trust Centre use of 38+ quality metrics, question-level signal combinations, automated checks on open-ended text answers, and human-in-the-loop review.
- Best used in: the workflow section of the deck or demo.

### We help teams validate answers after the study, not just during it

- Say: `The work does not disappear into folders and decks once the report is done. It stays connected so the team can validate the next answer against the evidence behind it.`
- Proof hook: Insight Navigator and the connected evidence layer.
- Best used in: the value section after the workflow has been explained.

### AI help stays tied to the evidence

- Say: `AI support is built into the workflow with traceability, instead of sitting off to the side as a black box.`
- Proof hook: the auditable confidence narrative and governance story.
- Best used in: trust or defensibility questions.

### This is a connected research platform with QA and QC built in

- Say: `<un>peel is a connected research platform that bakes quality assurance and quality control into the design, collection, and reporting of insights.`
- Proof hook: the before-during-after workflow story, Research Guard redesign governance, Trust Centre, connected evidence layer, and platform-expansion story.
- Best used in: category framing and competitive contrast.

## Guardrails for live use

- Do not claim Research Guard already matches Qualtrics or Conjointly where the review is built directly into the survey-authoring tool or where one-click use already exists.
- Do not claim Trust Centre already matches Qualtrics-class post-field response-quality coverage end to end.
- Do not claim enterprise security, procurement, or connector maturity beyond what can be shown today.

## Validation still needed

- Confirm which 3 claims should be the founder defaults.
- Tighten any wording that feels too strong or too abstract.
- Decide which proof snippets are strongest enough for external use in the deck, one-pager, and demo.