R17Answer the objection
Pro

Measured scale band

Make a concrete promise, follow it with dated, unit-labelled scale facts, then tie each fact to the surface that produces it.

Back to page recipes

Section sequence

5sections, in the order the visitor meets them. Bar height is the section's weight in the page.

  1. OrientConcrete promise
  2. ProveMetric band
  3. ProveFact-to-surface link
  4. ProveReliability detail
  5. ConvertEvidence route

How the page argues

  1. 1

    Make one concrete promise before any number appears.

  2. 2

    Follow immediately with three to five facts, each with unit, scope and date.

  3. 3

    Link every fact to the product surface that produces it.

  4. 4

    Add the reliability detail that a serious buyer will look for anyway.

  5. 5

    Route to the evidence: status page, report, documentation.

What each section has to be

OrientConcrete promise
The claim the numbers will support, stated in one sentence without superlatives.
ProveMetric band
Three to five facts, each carrying its unit, its scope and the date it was measured.
ProveFact-to-surface link
Each metric attached to the product surface that produces it, so numbers are not free-floating.
ProveReliability detail
Uptime definition, incident history or redundancy model — the follow-up question, pre-answered.
ConvertEvidence route
Status page, compliance report or docs, so the numbers can be verified rather than believed.

Is this the right sequence?

Who it is for

Buyers whose risk is volume and continuity, not capability: they need to know it holds at their size.

Products it suits

Infrastructure, networks and mature platforms with defensible, auditable numbers.

Not for

Early products whose metrics are small or unqualified, where a stat band invites the wrong comparison.

Evidence strategy

Which proof modes carry the page, in the order they land.

  1. Primary: measured scale, with units and dates that make the numbers checkable.
  2. Secondary: the product surface behind each number, which stops the band reading as decoration.
  3. Tertiary: verifiable artifacts — status pages and reports the visitor can open now.

CTA plan

What the page asks for, what it offers instead, and where.

Primary
Open the live status or the current report
Secondary
Read how each number is measured
Placement
Verification route directly under the band; the commercial CTA stays below, after the reliability detail.

Responsive behavior

What the sequence has to do when the viewport stops cooperating.

  • The band reflows from a single row to a two-column grid; never shrink figures below body-text legibility.
  • Units and dates stay on the same line as their figure at every breakpoint.
  • Long metric labels wrap rather than truncate, since a truncated unit is a misleading number.

Anti-patterns

The failure modes that make this sequence stop working.

  • Numbers with no unit, scope or date, which cannot be assessed and therefore are not proof.
  • Vanity metrics that describe the company rather than the buyer's risk.
  • A stat band with no product linkage, which reads as an investor slide.
  • Stale figures with no as-of date, which quietly become false.

Build spec

Pro

What an agent needs in order to build Measured scale band: what each section must contain, the copy rule that keeps it honest, the slots to resolve from your product, and the order to build in.

Checking access to the build spec

Agent tags

The vocabulary an agent matches this recipe on.

  • scale-band
  • unit-labelled-metric
  • as-of-date
  • fact-to-surface
  • verification-route