Early access · built on Stripe
Billing, pipeline, revenue and customer success in one customer record. sumwerk sells your plans, opens and closes the deals, explains every euro of MRR and tells you who needs you, from the first call to the renewal. Free while you build.
One record, four jobs
Most startups stitch billing, a CRM, an analytics tool and a support tool together and spend their evenings keeping them in step. In sumwerk they are one record: the trial that started, the deal it belongs to, the invoice it became and the MRR it added are the same customer.
Plans and what each gives, grouped in tiers, trials, extras and credits, a checkout of your own on your domain, billing pages and contracts for your customers, and the limits checked in your app. Stripe stays your payment processor; sumwerk only reads it until an owner switches on billing management, and shows Stripe's preview before money moves.
More about billingA booked call, a sign-up or a trial opens a deal; the first payment wins it with the MRR it really brought. Customers who reach a limit show up for expansion, yearly plans before their renewal, customers at risk for retention.
More about pipelineMRR from the state of each Stripe subscription, not from prorated invoices. Every movement names its cause and the Stripe event behind it, months close and stay closed, and every sync is checked against Stripe's own invoices. Cohorts show what each quarter's customers still bring, by plan and tier.
More about revenueFailed payments, scheduled cancellations and your own risk rules flag revenue while it still counts. Support conversations from Plain, notes, tasks, email sequences and automations sit next to the numbers.
More about successVideo · 1:44
From your Stripe products to plans, prices, extras and what each plan gives. Shown on invented example data.
The guide, step by stepRevenue you can prove
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.
How it works
Click Connect with Stripe and approve the sumwerk app in Stripe; your history is read at once, nothing to copy or paste. A getting-started list leads through the rest, from checking one number you know to importing your customers.
Send sign-ups, trials and usage through the API or the SDK. Your app asks sumwerk what a customer may do and gets the answer from a cache next to it.
Deals open and close by themselves, every MRR movement is explained, months close, and revenue at risk is flagged while it still counts.
Tasks for your team, email from your own mailbox, sequences and automations that follow up by themselves. Everything is in the API and an MCP server too.
Principles
“We pay for a subscription analytics tool every year and the chart is still often wrong, especially when customers change plans. How hard can it be?”
Read the story: How Kitchn.io is replacing ChartMogul with sumwerk
Roadmap
MRR, churn and retention from Stripe, every number traceable to the Stripe event behind it.
One record per customer, and deals that open and close themselves from calls, sign-ups, trials and payments.
Sell your plans on Stripe without writing billing code, and know in your app what every customer may do.
Know which customers need you before they leave, and what to do about it.
Record your screen in the browser and send it to a customer; see who watched it on their record.
What was said on a call, next to the deal it was about.
What a company that runs its billing on sumwerk needs to see.
On your phone
No separate app and no cut-down version: the overview, a customer with their tasks and notes, and who is at risk, on the screen you have with you. Tables become cards, buttons are big enough for a thumb.
Features
Plans and what each gives, trials, a checkout of your own on your domain, billing pages for your customers, and the limits checked in your app.
Deals open and close by themselves from booked calls, sign-ups, trials, plan limits and Stripe payments, for new business, expansion, renewals and retention.
sumwerk computes MRR from the state of each Stripe subscription, not from prorated invoices, and links every movement to the Stripe invoice or event behind it.
Customer churn, gross and net MRR churn per month, net and gross revenue retention over twelve months, and revenue cohorts, each with its definition.
A month closes a few days after it ends. A later change becomes a restatement with its reason, and every subscription is checked against Stripe's invoices.
sumwerk flags revenue that still counts but is in doubt - failed and overdue payments, scheduled cancellations - by severity, without changing your MRR.
Paying customers, MRR, churn and trial conversion per plan, billing interval, owner, tag or any attribute you send. Every row opens its customers.
A customer in sumwerk exists independent of Stripe: leads and trials from your product, several Stripe customers under one record, attributes, tags, owners.
Write notes, log calls with their length and keep tasks per customer in sumwerk - with the MRR, the ledger and the payment risk on the same page.
When a trial starts, a payment fails or a cancellation is scheduled, sumwerk adds a task, sets the owner, tags the customer or calls your webhook.
Email customers from sumwerk with templates and merge fields, run sequences with waits, send from your own Google mailbox, see every email on the timeline.
Leads, trials and trial-to-paying conversion by the month a trial started, with days to first payment, and every number opening into its customers.
Pull MRR, movements and customers out of sumwerk, push leads, trials, product usage, notes and tasks in, manage automations and receive signed webhooks.
sumwerk is an MCP server. Connect Claude or another AI assistant and ask about MRR, churn, segments, revenue at risk and single customers, from live data.
One sandbox for staging, one per developer. The same team and settings, their own data and swk_test_ tokens. No email leaves, nothing reaches your numbers.
Import your ChartMogul CRM data into sumwerk: customers with all ids, tags, owners and attributes, contacts, notes, call logs and tasks.
Connect Stripe in two minutes. Every module is free during early access. Sign-ups go through a waitlist for now: we let companies in one by one.