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.

Free involved Pricing & Packaging Offers

What it adds

The builder splits your delivery into implementation effort and ongoing service, pricing each independently so the setup fee covers real onboarding work while the recurring figure remains easy to approve. It converts by keeping the number the buyer compares against alternatives small, and by making the setup fee legible as specific work rather than an arbitrary charge. The goal is funded onboarding paired with a recurring price that survives comparison.

What your builder is told to do

The actual instructions, in order.

1
Read the onboarding and service-cost source files and itemize every task performed before the customer is fully operational, with the effort each one requires.
2
Price the setup fee against that itemized work and present it as a deliverable list with a completion definition, so the buyer sees purchased outcomes rather than an entry charge.
3
Price the monthly figure against ongoing value and cost only, deliberately excluding any amortised setup effort, which is what keeps the recurring number competitive in comparison.
4
State a setup completion milestone with a target timeframe drawn from the source files, and define when recurring billing begins relative to it, since billing before value arrives is the main objection to this structure.
5
Show the first-year total alongside both components, because buyers will calculate it regardless and presenting it first prevents the setup fee from reading as a hidden cost.
6
Offer one structured alternative for buyers who resist the upfront amount, such as a higher recurring rate with reduced or waived setup, and state the crossover point at which each option becomes cheaper.
7
Specify responsive behavior: on mobile, show setup and monthly as two clearly separated blocks with the first-year total between them and the deliverables list collapsible; on tablet, place setup deliverables and recurring inclusions in parallel columns with the total beneath; on desktop, present setup, recurring, and first-year total in one row with an onboarding timeline running below.

Edge cases it handles

The things an agent skips when you only say "build a setup fee plus monthly offer".

Setup that overruns its timeframe needs a stated position on whether recurring billing is delayed accordingly.
A customer cancelling shortly after setup completes must have a defined outcome for the setup fee.
Complex accounts may require more onboarding than the standard fee covers, so a scoped variation path must exist.
If the buyer supplies their own implementation resources, the fee needs a stated reduction rule or an explicit statement that it is fixed.
If onboarding effort is undocumented in the source files, the setup fee is unjustified and must be reported as an assumption.

Definition of done

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

The setup fee is backed by an itemized deliverables list with a completion definition.
The recurring price excludes amortised setup cost and is justified by ongoing value.
Setup timeframe and the start of recurring billing are both stated.
The first-year total is displayed alongside the two components.
An alternative structure is offered with its crossover point stated.
Mobile, tablet, and desktop layouts each separate setup and recurring as specified.
The builder reports which source files supplied onboarding effort and service costs, and lists any fee or timeframe 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

Decoy Pricing

Steer buyers toward the plan you want chosen by adding a deliberately weaker option that makes the target look obviously better.

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.