R22Answer the objection
Pro

Self-serve and sales fork

Name one outcome, then split the page into two honestly different paths: start it yourself, or bring in a team.

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. OrientShared outcome
  2. NavigateThe fork
  3. ProveSelf-serve proof
  4. ProveAssisted-adoption proof
  5. ConvertTwo destinations

How the page argues

  1. 1

    Name the shared outcome both buyers want, once.

  2. 2

    Fork visibly and symmetrically, with each side labelled by who it is for.

  3. 3

    Prove the self-serve path with limits, pricing and time-to-value.

  4. 4

    Prove the assisted path with implementation, migration and governance facts.

  5. 5

    Send the two paths to two genuinely different destinations.

What each section has to be

OrientShared outcome
The one outcome both buyer types want, stated before the fork so the page still has a centre.
NavigateThe fork
Two visually equal paths, each labelled by buyer type and by what happens next.
ProveSelf-serve proof
Free-tier limits, pricing and realistic time to first value for someone acting alone.
ProveAssisted-adoption proof
Implementation support, migration, security review and rollout facts for a team purchase.
ConvertTwo destinations
Sign-up and a qualified conversation — different pages, different next screens, no shared form.

Is this the right sequence?

Who it is for

Two buyers on one page: the individual who wants to start now and the organization that cannot.

Products it suits

Products with genuinely distinct buyer motions and different onboarding realities.

Not for

Products where both paths end in the same contact form, which makes the fork a bait-and-switch.

Evidence strategy

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

  1. Primary: honest qualification — the page tells each visitor which path is theirs.
  2. Secondary: self-serve limits and pricing, which make the free path credible.
  3. Tertiary: implementation facts, which make the assisted path worth a meeting.

CTA plan

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

Primary
Start free (for individuals and small teams)
Secondary
Talk to us (for rollouts, migrations and security review)
Placement
Both actions inside the fork with equal weight, repeated once at the end in the same order.

Responsive behavior

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

  • The fork stacks vertically with the self-serve path first, since it is the lower-commitment option.
  • Each path keeps its qualification label when stacked; never drop the labels to save vertical space.
  • Comparison content becomes two labelled cards rather than a two-column table on mobile.

Anti-patterns

The failure modes that make this sequence stop working.

  • Both paths leading to the same form, which destroys the fork's credibility.
  • A self-serve path with no stated limits, so the visitor discovers the wall later.
  • Making the sales path visually dominant while calling the page self-serve.
  • Qualification labels written as flattery ('for ambitious teams') instead of facts.

Build spec

Pro

What an agent needs in order to build Self-serve and sales fork: 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.

  • buyer-fork
  • qualification-labels
  • self-serve-limits
  • assisted-adoption
  • dual-destination