R28Map a broad offering
Pro

Suite to entry route

Present the suite as one outcome, let the visitor pick by role, industry or module, then return them to the shared platform value.

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. OrientSuite promise
  2. NavigateChooser
  3. DemonstrateModule detail
  4. ProveCommon layer
  5. ConvertTrial or demo

How the page argues

  1. 1

    State the suite as one outcome, so the portfolio has a thesis.

  2. 2

    Offer the chooser early: role, industry or module, whichever the visitor knows about themselves.

  3. 3

    Give the chosen module real depth, not a teaser card.

  4. 4

    Return to the common layer, which is what makes the suite worth more than its parts.

  5. 5

    Convert on the chosen module while keeping the platform route open.

What each section has to be

OrientSuite promise
One outcome the whole portfolio serves, stated without listing modules.
NavigateChooser
One chooser dimension — role, industry or module — chosen because visitors actually know it about themselves.
DemonstrateModule detail
Real depth for the chosen module: interface, outcome and its own proof.
ProveCommon layer
The shared data, identity or workflow layer, with one example that spans two modules.
ConvertTrial or demo
Conversion scoped to the chosen module, with the platform conversation available but not forced.

Is this the right sequence?

Who it is for

Enterprise buyers who arrive for one module and will be sold the platform only after their own need is met.

Products it suits

Broad portfolios where different buyers legitimately need different first modules.

Not for

Products where every buyer should take the same first action, and a chooser only adds a decision.

Evidence strategy

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

  1. Primary: module depth, because the visitor came for one thing.
  2. Secondary: the common layer, which is the platform argument.
  3. Tertiary: the chooser itself, which proves the vendor understands the visitor's starting point.

CTA plan

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

Primary
Trial the module you chose
Secondary
See the platform, or talk to someone about a portfolio rollout
Placement
Module-scoped action inside the module detail; the platform route sits with the common layer.

Responsive behavior

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

  • The chooser becomes a horizontally scrollable chip row or a select control, with the choice deep-linkable.
  • Module detail keeps its own proof when stacked; never reduce it to a title and an icon.
  • The common layer becomes an ordered list rather than a diagram on small screens.

Anti-patterns

The failure modes that make this sequence stop working.

  • Two chooser dimensions at once, which doubles the decision before any value is delivered.
  • Module cards with no depth behind them.
  • Skipping the common layer, which turns a suite into a price list of separate products.
  • A chooser that resets on navigation, losing the visitor's stated context.

Build spec

Pro

What an agent needs in order to build Suite to entry route: 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.

  • suite-promise
  • single-chooser
  • module-depth
  • common-layer
  • module-scoped-cta