R04Get them doing the thing
Pro

Transaction launcher

Open with the parameters of the transaction itself, quote price or availability immediately, then offer the account and the wider catalogue.

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. ActParameter form
  2. DemonstratePrice or availability preview
  3. OrientLocal context
  4. NavigateService switcher
  5. ProveTerms at the quote
  6. ConvertAccount continuation

How the page argues

  1. 1

    Ask for the transaction parameters first: origin and destination, or dates and party size.

  2. 2

    Return a price or availability expectation before asking for identity.

  3. 3

    Give local context so the quote reads as real rather than indicative.

  4. 4

    Offer the service switcher for the visitor who picked the wrong lane.

  5. 5

    Show the terms that bind the quote at the moment the quote appears.

  6. 6

    Continue into the account only when the transaction requires it.

What each section has to be

ActParameter form
The exact fields the transaction needs, in the order a person says them out loud.
DemonstratePrice or availability preview
A real quote or a real availability state, produced from the entered parameters, before any login.
OrientLocal context
City, currency, language and service area, so the quote is legible as local truth.
NavigateService switcher
Adjacent services or fare classes, so a mis-set lane costs one tap rather than a back button.
ProveTerms at the quote
What is included, what varies and what cancellation costs, placed with the number it qualifies.
ConvertAccount continuation
Login or sign-up positioned as completing the transaction, plus a loyalty reason where one exists.

Is this the right sequence?

Who it is for

Visitors with dated or located intent who will judge the page by how quickly it quotes them.

Products it suits

On-demand services, booking flows and anything where the first question is when, where and how much.

Not for

Discovery-first products where a parameter form implies a commitment the visitor has not made yet.

Evidence strategy

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

  1. Primary: transaction utility — the page does the thing the visitor came to do.
  2. Secondary: a concrete quote, which converts a promise into a number.
  3. Tertiary: terms and local availability, which make the number trustworthy.

CTA plan

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

Primary
See the price or availability
Secondary
Switch service, or continue with an account
Placement
Form and quote in the first screen; account continuation only after the quote; catalogue routes below the fold.

Responsive behavior

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

  • The parameter form becomes a full-width stack with large tap targets and native date and location pickers.
  • The quote pins directly under the form on mobile rather than in a side panel.
  • Map or route visuals shrink to a static preview with a tap-to-expand, never a scroll-hijacking canvas.

Anti-patterns

The failure modes that make this sequence stop working.

  • Requiring login before showing any price, which turns the page into a gate.
  • An indicative price with no stated conditions, which trades a click now for distrust later.
  • Hiding the service switcher in the global nav.
  • Running the form in a locale where the service is unavailable, with no availability message.

Build spec

Pro

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

  • transaction-launcher
  • parameter-form
  • price-preview
  • local-context
  • account-continuation