Early access · Stripe only, on purpose
sumwerk computes MRR from the state of your Stripe subscriptions, not from prorated invoice amounts. Every euro that moves comes with its reason and the Stripe event behind it.
Most analytics tools reconstruct MRR from invoices. Invoices are great evidence of what was billed. They are a poor definition of what a customer is worth per month.
An upgrade mid-cycle creates proration lines for a few days of the old and new plan. Invoice-based tools extrapolate MRR from those fragments.
= sumwerk reads the new price and quantity at the moment of the change. One expansion, dated to the second.
Replace one item with two, or cancel and re-create a subscription, and you get churn plus a reactivation that never happened.
= Everything a customer does within an hour is netted into one movement, or none if nothing changed.
A 6-month plan billed up front is easy to count six times too high, or to lose for months when the change produced no invoice.
= Any interval is normalised exactly: a 6-month plan counts one sixth, a 2-year plan one twenty-fourth.
Create a restricted Stripe key with read permissions and paste it. sumwerk checks every permission and refuses keys that could write.
Subscriptions, prices (archived ones too), coupons, invoices and events are copied verbatim. Events are kept as an append-only log.
MRR, new business, expansion, contraction, churn and reactivation, each movement with its cause: price change, quantity, discount ended, pause, cancellation.
Connect Stripe in two minutes and compare the result with the numbers you trust today.