R15Map a broad offering
Pro

Capability constellation

Lead with one umbrella job, arrange the capabilities around it, and give every visitor a route in plus a shared layer to return to.

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. OrientUmbrella job
  2. NavigateCapability map
  3. NavigatePersona routes
  4. ProveCommon layer
  5. ConvertOne entry action

How the page argues

  1. 1

    Commit to one umbrella job the whole constellation serves.

  2. 2

    Arrange capabilities around it as a map, not a list, so relationships are visible.

  3. 3

    Give persona and job routes for visitors who already know their entry.

  4. 4

    Name the shared layer — the data, context or identity that makes the suite one thing.

  5. 5

    Reduce the exit to a single first action, despite all the breadth above.

What each section has to be

OrientUmbrella job
The one outcome the whole platform serves, stated before any module name appears.
NavigateCapability map
Capabilities positioned by relationship, with the ones most visitors need placed first.
NavigatePersona routes
Two to five entries for visitors who know their role or job, so they can skip the map.
ProveCommon layer
The shared data, context or identity layer that makes the collection a platform rather than a bundle.
ConvertOne entry action
A single first action, chosen so it works regardless of which capability the visitor cares about.

Is this the right sequence?

Who it is for

Buyers evaluating a platform against several tools at once, who need to see the whole surface without drowning.

Products it suits

Suites and platforms whose capabilities genuinely compound because they share data or context.

Not for

A narrow product where showing breadth reads as unfocused rather than capable.

Evidence strategy

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

  1. Primary: the common layer, which is the actual argument for buying a suite.
  2. Secondary: the map, which proves the breadth is organized rather than accumulated.
  3. Tertiary: persona routes, which prove someone has thought about this visitor specifically.

CTA plan

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

Primary
Start with the capability you came for
Secondary
Enter by role, or read how the shared layer works
Placement
One primary action in the first screen and again after the common layer; per-capability links stay secondary.

Responsive behavior

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

  • The map degrades to grouped lists with the group relationships stated in text, not implied by position.
  • Persona routes become a chip row directly under the umbrella job on small screens.
  • Never render the constellation as a pinch-zoom image: it must be real markup at every size.

Anti-patterns

The failure modes that make this sequence stop working.

  • A capability grid with no umbrella job, which reads as a price list for parts.
  • Twenty equally weighted tiles, which forces the visitor to do the prioritization.
  • Claiming a shared layer that does not exist technically.
  • A different CTA on every tile, so the page has no first action at all.

Build spec

Pro

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

  • umbrella-job
  • capability-map
  • persona-route
  • common-layer
  • suite-entry