Plans

sumwerk knows every customer’s plan and billing interval without you sending anything: both are read from the Stripe subscription.

How a plan is read from Stripe

• The plan is the Stripe product of the largest item of the customer’s running subscriptions, by monthly value. An add-on therefore never names the plan as long as the plan costs more.
• A customer who left keeps the plan they had last, so churn can be read per plan.
• The billing interval comes from the same item: Monthly, Yearly, Every 6 months.
• A lead or a trial that is not in Stripe has no plan yet.

Your plans are not your product catalogue

A Stripe account collects products over the years: the plan as it was priced in 2023, a monthly and a yearly twin of the same plan, a product per region, one made for a single deal. For analysis most of them are the same plan. Account → Plans is where you say so.

• Suggestions. Products whose names differ only by billing words (“Business Plan - Monthly Billing”, “Business Plan - Yearly Billing (20% Discount)”) are offered as one plan. One click, and you can change the name before or after.
• Group by hand. Tick the products that belong together; a bar appears that offers a name and groups them. Type the name of a plan that exists to add products to it.
• A plan is a card: its paying customers, its MRR and its products as chips. Rename it by typing into its name, take a product out with the ×, or dissolve it.
• Products nobody pays for today are folded away at the end of the list. They still name the plan of customers who left, so group them too if you want churn by plan to be right.

Nothing changes in Stripe, and no number changes: only how customers are grouped. Customers follow a change at once.

Where plans show up

• Segments: paying customers, MRR, churn of the last twelve months and trial conversion by plan or by billing interval, each row opening its customers.
• Customers: the plan is on the customer’s page, a filter of the list (?plan=Team) and two columns of the CSV export.
• Rules: plan and billing_interval are fields for conditions, in automations (“when a customer on Scale schedules a cancellation, tell the founder”) and in your own at-risk rules.
• API and AI assistant: every customer carries plan and billing_interval; GET /api/v1/segments?by=plan.

Questions

A customer has two subscriptions. The largest item across all running subscriptions names the plan. Their MRR is the sum of both, as everywhere in sumwerk.

We sell add-ons that cost more than the plan. Then the add-on would name the plan. Group the add-on’s product into the plan it belongs to, or tell us: mapping single prices instead of products is on the list.

Do plan names change history? No. MRR, movements and closed months are untouched; a plan is a label on the customer, read again at every sync and renamed the moment you change a name.

Can I set plans through the API? Not the grouping, yet. The plan itself needs no API: it comes from Stripe.