Sign in

Guided Demo Offer

Walk each prospect through a tailored session where the agenda is set by their answers, not your script.

Pro simple Special Offer Structures

What it adds

The AI builder combines your discovery questions, product capability map, and scheduling setup into a booking flow that customizes the session before it happens. It converts because the prospect sees an agenda built from their own inputs, which raises show rates and shortens the session itself. The goal is booked, qualified sessions with a pre-agreed outcome for the call.

What your builder is told to do

8

The actual instructions, in order.
  1. 1

    Read the supplied discovery and demo-script files and extract the branching logic: which prospect answers change which parts of the demonstration.

  2. 2

    Build a short pre-booking form containing only the questions that actually alter the agenda. Every additional question lowers booking rate without improving the session.

  3. 3

    Generate a visible agenda from the answers before the calendar appears, listing the three or four segments the session will cover and roughly how long each takes, drawn from the demo scripts.

  4. 4

    Attach a "what you will leave with" line to the agenda, describing the artifact or decision the prospect gets from the session, taken from the demo documentation.

  5. 5

    Wire the booking to the real scheduling destination in the source files, and pass the agenda through so the person running the session receives it.

  6. 6

    Add a preparation note listing anything the prospect should bring or have ready, sourced from the demo prerequisites.

  7. 7

    Handle breakpoints: on mobile the form is a two- or three-step wizard with large tap targets, the agenda renders as a stacked summary card, and the calendar shows a single-day column at a time; on tablet form and agenda sit side by side with a week view calendar; on desktop the three stages — questions, generated agenda, calendar — display as a single horizontal flow without page transitions.

  8. 8

    Send an on-screen confirmation that restates the agenda and the preparation note.

Edge cases it handles

5

The things an agent skips when you only say "build a guided demo offer".
  • Answers indicate no viable use case; offer a resource path instead of a booking slot.
  • No suitable time slots are available in the prospect's region; capture preferred windows rather than showing an empty calendar.
  • The prospect skips optional questions; fall back to a documented default agenda and label it as general.
  • A prospect books for a product area you no longer support; the branching must exclude deprecated capabilities.
  • Multiple stakeholders need to attend; provide a guest-invite field and state the recommended attendee roles.

Definition of done

7

Your builder is required to check every one of these before reporting the work finished.
  • Every pre-booking question maps to documented branching logic in the demo scripts.
  • A tailored agenda renders before the calendar and reflects the prospect's answers.
  • The session's takeaway artifact or decision is stated.
  • The generated agenda is passed to the scheduling destination named in the source files.
  • A preparation note sourced from demo prerequisites appears before and after booking.
  • Mobile, tablet, and desktop each complete the question-to-agenda-to-booking flow without dead ends.
  • The builder reports which discovery and demo files it used and which branching rules are assumed.

Related offer files

How it works

  1. 1

    Copy the link

    Grab the Markdown blueprint URL for this offer type.

  2. 2

    Give it to your builder

    Paste it into Claude Code, Cursor, Codex, or whatever AI builder is already working in your app.

  3. 3

    It maps, then builds

    Your agent reads the blueprint first, then builds the offer into your app around the product, audience, and stack.

Works with your stack

These blueprints are written to adapt. They tell the agent to detect your framework, match your existing design system, and use your source files instead of guessing the offer.

Need it tighter than that? Customize the offer file and tell it exactly which source docs and stack to use.