# Results Page Blueprint

Build a results page that feels structured, believable, and commercially useful instead of vague, inflated, or stale.

## Results Architecture

A strong results page usually needs five layers:

1. `Context`
2. `Metrics`
3. `Case proof`
4. `Method or process`
5. `Caveats and next step`

That structure gives readers and retrieval systems enough signal to understand what the page is showing and why it matters.

## What the Page Should Do

- prove the business can create meaningful outcomes
- explain what type of work produced those outcomes
- show enough evidence to feel credible
- avoid overclaiming
- route the reader into the right next step

## Metrics Selection

Choose metrics that are:

- visible
- commercially meaningful
- reasonably repeatable
- explainable with context

Examples:

- average time to response improvement
- revenue recovered
- no-show reduction
- review growth
- booked-consult lift

## Proof Layers

Use several proof formats together:

- aggregate metrics
- compressed case stories
- process screenshots or workflow snapshots
- quote cards
- before/after operating changes

One proof format alone usually feels weak.

## Narrative Blocks

For each proof block, answer:

- what was broken?
- what changed?
- what improved?
- why does that matter?

That keeps the page from becoming a raw stat wall.

## Metrics Governance

Create rules for what can go on the page:

- only publish metrics with a clear source
- qualify averages and ranges
- note when samples are limited
- remove stale or unsupported figures
- avoid metrics that sound impressive but say nothing useful

## Caveat Design

Trust grows when the page is honest about limits.

Useful caveats include:

- results vary by starting point
- some businesses have more existing demand than others
- implementation quality matters
- timelines depend on operational readiness

## Update Cadence

### Monthly

- review top proof blocks
- remove stale numbers
- add one fresh result or case note

### Quarterly

- rebuild the aggregate summary
- compare the page against new objections or proof gaps
- improve page sections that feel thin

## 45-Day Rollout

### Days 1-10

- gather proof sources
- choose metrics and case stories

### Days 11-20

- build the page outline
- write short proof blocks with caveats

### Days 21-30

- add visuals, screenshots, and next-step links

### Days 31-45

- publish
- review how the page changes buyer questions, sales calls, and citation quality