Sign in

Service-Then-Software Offer

Begin with hands-on delivery, then hand the customer tooling once the process is proven in their environment.

Pro involved Special Offer Structures

What it adds

The AI builder reads your service delivery documentation, product capability map, and transition playbooks to construct an offer that sells expert delivery first and platform adoption second. It converts because buyers trust a process they have watched work before they trust a tool to run it. The goal is to establish the service relationship while making the eventual software transition a natural, pre-agreed step.

What your builder is told to do

8

The actual instructions, in order.
  1. 1

    Read the supplied delivery and product files and map which service activities have direct software equivalents and which will remain human work permanently.

  2. 2

    Present the offer as two named phases with a defined boundary, and state the criteria that determine when phase one is complete rather than fixing an arbitrary date.

  3. 3

    Describe the service phase deliverables concretely from the playbook — what is built, configured, or documented in the customer's environment.

  4. 4

    Explain what the software phase actually takes over, and be explicit about the activities that never transfer, since overstating automation here creates churn later.

  5. 5

    State the pricing relationship between the phases from the source pricing files, including whether service work is credited, without inventing discounts.

  6. 6

    Add a readiness definition: the observable conditions under which the customer is ready to run the process themselves, drawn from the transition guide.

  7. 7

    Handle breakpoints: on mobile the two phases render as sequential full-width sections with a phase switcher pinned to the top; on tablet phases sit side by side with the transition criteria as a connecting band; on desktop a horizontal phase diagram spans the top with detail panels beneath and the never-transfers list visible alongside.

  8. 8

    Describe the training and enablement included in the transition, sourced from the transition guide.

Edge cases it handles

5

The things an agent skips when you only say "build a service-then-software offer".
  • The customer wants to skip straight to software; state the documented prerequisites for direct adoption rather than refusing outright.
  • Service work reveals the software is a poor fit for their environment; commit to saying so and describe what happens then.
  • Transition readiness criteria are never met; define an ongoing managed option.
  • Staff turnover erases the trained users; describe re-enablement provisions if documented.
  • Pricing for the two phases overlaps ambiguously; flag it rather than presenting a blended figure.

Definition of done

7

Your builder is required to check every one of these before reporting the work finished.
  • Two phases are named with an explicit, criteria-based boundary rather than a fixed date.
  • Service-phase deliverables come from the supplied playbook.
  • Activities that never transfer to software are listed explicitly.
  • Pricing relationship between phases derives from source pricing files with no invented credits.
  • A readiness definition with observable conditions is present.
  • Mobile, tablet, and desktop each present both phases and the transition criteria coherently.
  • The builder reports which delivery and product files it used and which transition criteria 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.