R16Map a broad offering
Pro

Progressive reveal

Present one simple primary job, keep secondary complexity behind tabs, and let depth appear only when it is asked for.

Back to page recipes

Section sequence

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

  1. OrientPrimary job
  2. ActPrimary action
  3. NavigateJob tabs
  4. NavigateRole filters
  5. ProveDeep-dive route
  6. ConvertStart or contact

How the page argues

  1. 1

    Lead with one primary job stated simply enough for the least informed visitor.

  2. 2

    Offer one immediate action so simplicity does not mean passivity.

  3. 3

    Put the other jobs behind tabs, labelled by job rather than by module.

  4. 4

    Let role filters refine the tabbed content for visitors who self-identify.

  5. 5

    Keep the deep material one deliberate click away, never inline.

  6. 6

    Give both the self-serve start and the assisted route at the end.

What each section has to be

OrientPrimary job
The single job that covers most visitors, in language that needs no product knowledge.
ActPrimary action
One immediate action tied to that job, available before any tab is touched.
NavigateJob tabs
Three to six tabs named by job. The default tab is the most common case, not the newest feature.
NavigateRole filters
Optional refinement inside a tab for visitors who know their role.
ProveDeep-dive route
Links to architecture, security and pricing depth — visible but never expanded inline.
ConvertStart or contact
Self-serve and assisted routes side by side, labelled by which visitor each is for.

Is this the right sequence?

Who it is for

A mixed audience arriving at one page: the curious, the specialist and the procurement lead.

Products it suits

High-density horizontal products that must serve several jobs without a different landing page for each.

Not for

Products whose differentiation depends on the visitor grasping the whole system at once.

Evidence strategy

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

  1. Primary: relevance — every visitor finds their own job named on the page.
  2. Secondary: the tab content, which proves each job is genuinely supported.
  3. Tertiary: the deep-dive route, which satisfies the specialist without taxing everyone else.

CTA plan

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

Primary
Start with the primary job
Secondary
Open the tab that matches your job, or talk to someone
Placement
Primary action in the first screen; a tab-specific action inside each tab; the fork at the end.

Responsive behavior

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

  • Tabs become a horizontally scrollable row with the active tab always in view and an edge fade to signal more.
  • Never convert tabs into an accordion that lets every panel open at once — that defeats the recipe.
  • Role filters collapse into a single select control on mobile.

Anti-patterns

The failure modes that make this sequence stop working.

  • Tabs named after internal modules, which forces the visitor to translate.
  • A default tab chosen for novelty rather than for the majority case.
  • Content that only exists in tabs, so nothing is understandable without interaction.
  • Deep enterprise material expanded inline, which buries the simple primary job.

Build spec

Pro

What an agent needs in order to build Progressive reveal: 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.

  • progressive-disclosure
  • job-tabs
  • role-filter
  • default-tab
  • deep-dive-route