The numbers, and the work around them
sumwerk starts with MRR that can be checked against Stripe, and adds what a team needs next to it: who the customers are, which revenue is in doubt, what was said, what is next, and what should happen by itself.
-
MRR you can provesumwerk 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.
-
MRR at risksumwerk flags revenue that still counts but is in doubt - failed and overdue payments, scheduled cancellations - by severity, without changing your MRR.
-
CustomersA customer in sumwerk exists independent of Stripe: leads and trials from your product, several Stripe customers under one record, attributes, tags, owners.
-
Tasks and notesWrite 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.
-
AutomationsWhen 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 and sequencesEmail customers from sumwerk with templates and merge fields, run sequences with waits, send from your own Google mailbox, see every email on the timeline.
-
FunnelLeads, trials and trial-to-paying conversion by the month a trial started, with days to first payment, and every number opening into its customers.
-
APIPull MRR, movements and customers out of sumwerk, push leads, trials, product usage, notes and tasks in, manage automations and receive signed webhooks.
-
Import from ChartMogulImport your ChartMogul CRM data into sumwerk: customers with all ids, tags, owners and attributes, contacts, notes, call logs and tasks.