About this block

Journey Stages organizes the FAQ by where the customer is, not by topic. A centered heading and lede sit above a vertical rail of numbered stage nodes that walks from evaluating, through the first weeks, to scaling, and each stage carries its own caption and a short stack of bold questions with muted answers. The lede tells readers the questions arrive in the order they will hit them.

The stages are one array, each with a number, title, caption, and its own list of pairs, and a hairline connector line joins the nodes down the rail. It is static markup with theme tokens only, so you can add a stage, rename a step, or move a question between stages without disturbing the connector or the spacing.

When to use

Reach for this block when the questions a buyer asks change as they move from comparing tools to living in one, and a flat list would mix a switching worry in with a scaling one. Grouping by stage lets an evaluator read only the before you switch node while an existing customer jumps to the growth questions. It suits products with a real onboarding arc rather than a single purchase moment.

A natural flow around it on a Marketing Pro page:

Before

• Migration detailing the switch the first stage reassures buyers about

After

• Pricing for the seat and billing questions the later stages raise
• CTAs to start the journey the stages just mapped

What you can display

One strong use is the evaluate, onboard, and scale arc shown here. Other journeys:

• Trial stages. Sign up, first value, and the decision to convert.
• Rollout stages. Pilot team, department, and company wide adoption.
• Lifecycle stages. Launch, renewal, and expansion questions kept in order.

Tip: keep each stage to a few questions so the rail stays short enough to read in one pass.