Starter Plan

Lower the first commitment to one solved problem, so a new customer reaches a real result before they ever consider upgrading.

Pro involved Pricing & Packaging Offers

What it adds

The builder reads your capability list and onboarding notes to carve out an entry plan that completely solves one job at a price that needs no approval, with a ceiling positioned exactly where growing accounts will feel it. It converts by making the first purchase small and self-evident rather than by discounting the full product. The goal is maximum new-account volume that later graduates upward.

What your builder is told to do

The actual instructions, in order.

1
Inspect the capability and onboarding source files and identify the single job a new customer most urgently needs finished in their first week.
2
Include every capability required to finish that job completely, and exclude everything else, because a starter plan that half-solves the problem produces refunds rather than upgrades.
3
Set the price beneath the threshold where the buyer needs anyone else's approval, using any budget or buyer-role information the source files contain to locate that threshold.
4
Choose one ceiling only, expressed in the same value metric the plan above uses, and place it where accounts begin to succeed rather than where they begin to explore, so the limit signals growth instead of restriction.
5
Design the first-run path so the new customer reaches the completed job quickly, with the shortest possible sequence from purchase to visible result, since starter-plan retention is decided in the first session.
6
Build the upgrade trigger at the ceiling: show current consumption against the limit continuously, and when the limit is reached, present the specific capability the next plan unlocks with the price difference rather than the full higher price.
7
Specify responsive behavior: on mobile, keep a compact usage-against-limit indicator in the header and present the upgrade prompt as a bottom sheet at the moment of blocking; on tablet, show the indicator in a persistent sidebar with an inline upgrade panel; on desktop, display usage, limit, and the next-plan difference together in a dashboard strip.

Edge cases it handles

The things an agent skips when you only say "build a starter plan".

A customer who hits the ceiling in their first week is a success signal, so the interface must not treat the block as an error state.
Data created under the starter plan must remain fully accessible when a limit is reached, since withholding a customer's own work destroys the upgrade.
If the plan above shares no metric with the starter plan, the upgrade prompt becomes incoherent and the metric must be aligned first.
Multiple users sharing a single starter account signals a team need and should route to the team offer rather than a higher single-user tier.
If the source files show no clear first job, the starter plan cannot be scoped honestly and the gap must be reported.

Definition of done

Your builder is required to check every one of these before reporting the work finished.

The plan completely solves one named job with no missing dependency.
Exactly one ceiling exists and it is expressed in the same metric as the next plan.
Price sits below the stated no-approval threshold from the source files.
Usage against the limit is visible continuously, and the upgrade prompt shows the price difference rather than the full next price.
Customer data remains accessible when the ceiling is reached.
Mobile, tablet, and desktop presentations of the usage indicator and upgrade prompt each match the specification.
The builder reports which source files defined the first job and the ceiling, and lists any threshold or limit it assumed.

Related offer files

Pricing & Packaging Offers

Multi-Product Bundle

Combine separate products into one subscription that solves a whole workflow, priced below buying each product on its own.

Pricing & Packaging Offers

Setup Fee Plus Monthly Offer

Separate the one-time work of getting started from the ongoing service, so the monthly figure stays low and the launch is funded.

Pricing & Packaging Offers

License Renewal Offer

Renew expiring licenses by showing what was actually used during the term and what continued access protects going forward.

How it works

1

Copy the link

Grab the Markdown blueprint URL for this offer type.
2

Give it to your builder

Paste it into Claude Code, Cursor, Codex, or whatever AI builder is already working in your app.
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.