Design the product, price, and plan objects for an offer
Translates a new or changed offer into the correct product/price/billing objects in the payment processor, resolving edge cases like proration, instalment schedules, and trial/coupon structure before any config is touched.
In / outOffer spec (type, price, billing interval, instalment terms, access rules) → product/price/plan object blueprint with proration, currency, and trial/coupon decisions resolved
You might say…
“Every time I launch a new offer I have to reverse-engineer what to configure in Stripe — there's always some billing edge case I miss.”
What it does
Given a new or changed offer (course, cohort seat, membership tier, payment plan), reasons the correct set of product/price objects, billing intervals, instalment schedule, and trial/coupon structure to model it in the processor — resolving edge cases like proration, currency, and how a payment plan maps to access. Used before touching processor config, when an offer needs translating into a billing structure.
Trigger: Use when translating a new or changed offer (course, cohort seat, membership tier, payment plan) into processor configuration before touching the billing system.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation