Credit-Pack Pricing

Replace confusing per-action charges with one credit currency, letting buyers purchase capacity once and spend it as they choose.

Pro moderate Pricing & Packaging Offers

What it adds

The builder maps every billable action in your source files to a credit cost, then designs packs whose sizes match real usage patterns and whose larger packs carry a visible per-credit advantage. It converts by collapsing many pricing decisions into a single purchase and by letting the buyer control spend without watching a meter. The goal is upfront revenue with buyers self-selecting into larger packs.

What your builder is told to do

The actual instructions, in order.

1
Read the action catalogue and cost source files and list every billable action with its underlying cost and how often a typical account performs it.
2
Set the credit unit so that the most common action costs a small whole number of credits, keeping the arithmetic mental rather than decimal, and map every remaining action onto the same scale in proportion to cost.
3
Size the packs around jobs rather than round numbers: a pack that completes one representative project, one that covers a normal month, and one that covers a quarter, with each size traceable to usage patterns in the source files.
4
Price the packs so the per-credit rate declines with size, display that rate on every pack, and make the largest pack the value anchor by showing its per-credit figure against the smallest.
5
Define the credit lifecycle in writing: whether credits expire, what happens to unused balance, whether packs stack, whether credits are refundable, and how a partially consumed action is charged.
6
Build the in-product spend surface showing the current balance, the credit cost of an action before it is confirmed, a low-balance threshold with a top-up prompt, and a spend history the buyer can audit.
7
Specify responsive behavior: on mobile, show packs as full-width cards ordered small to large with per-credit rate on each and a persistent balance chip in the header; on tablet, use a three-across pack row with a cost-per-action reference table below; on desktop, present packs alongside the action-to-credit table so the buyer can price their own intended work before purchasing.

Edge cases it handles

The things an agent skips when you only say "build a credit-pack pricing".

An action that fails partway through needs a stated rule for whether credits are consumed or returned.
Buyers who run out mid-task require a top-up path that resumes the task rather than discarding it.
Changing the credit cost of an action devalues balances already purchased and needs a grandfathering or notice rule.
Very large balances purchased at a discount can be spent after a price change, so exposure must be considered before setting pack sizes.
If the source files do not contain per-action cost data, the credit mapping is arbitrary and must be reported as such.

Definition of done

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

Every billable action from the source files has an assigned credit cost on one consistent scale.
Pack sizes correspond to real jobs or periods evidenced in the source files, not arbitrary round numbers.
Per-credit rate is displayed on every pack and declines as pack size increases.
Expiry, refund, stacking, and partial-consumption rules are all stated in visible copy.
The product shows balance, pre-action cost, low-balance warning, and spend history.
Mobile, tablet, and desktop layouts each match the specified pack and reference-table behavior.
The builder reports which source files supplied action costs and usage patterns, and lists any credit mapping it had to assume.

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

Decoy Pricing

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

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.