Customer Churn Tracker.
Log every cancellation with reason and MRR lost, then see what is actually driving churn.
About this template
A cancellation log for customer success teams: record each churned account with churn date, MRR lost, primary reason, competitor if any, and whether a save was attempted. Charts show monthly logo and revenue churn, churn by reason, and churn by plan so patterns stop hiding in a spreadsheet tab.
The live demo ships with sample data: About 90 seeded cancellations over 12 months with realistic reasons like missing features, price, and switching to a competitor, weighted so a clear top churn driver emerges in the charts.
The prompt behind this template
This is the exact description the Prized agent built it from. Yours can be one sentence: the agent fills in the rest, and you refine from there.
Show the full prompt
Build a customer churn tracker for the customer success team at Relayform, a fictional B2B forms automation SaaS on three plans: Starter, Team, and Business. Layout: a compact summary strip across the top with four small stats: MRR lost in the last 12 months (about $41,200), logos lost (90), average MRR per cancellation (about $460), and top churn reason (Missing features). Below it, two tabs. Tab 1, Churn log, is the default. A sortable table of every cancellation: customer name, churn date, plan, MRR lost, primary reason as a colored badge, competitor name when the reason is a competitor switch, save attempted (yes or no), and a short note. Default sort is newest first. Above the table: filter chips for date range (Last 30 days, Last quarter, Last 12 months, All), a reason filter, and a plan filter. A prominent Log cancellation button opens a dialog form capturing all of those fields; the reason comes from a fixed list: Missing features, Price, Switched to competitor, Low usage, Support experience, Went out of business. The form is member only and the page must read perfectly without it. Tab 2, Insights. Four charts computed from the log: monthly logos lost as bars with monthly MRR lost as an overlaid line across the last 12 months; a donut of MRR lost by reason; a horizontal bar of cancellations by plan; and a small comparison of save attempted versus not attempted, split by accounts above or below $500 MRR. Data to seed: about 90 cancellations spread over the last 12 months with realistic fictional company names (Alder and Vine, Cobalt Freight, Pinehurst Clinics), MRR lost between $49 and $2,400, and one sentence notes. Plant this story: Missing features is the clear top driver, about a third of all cancellations and over 40 percent of MRR lost, and its share grows in the most recent three months; notes on those rows repeatedly mention needing API access and SSO. Competitor switches mostly name two fictional rivals, Formaloop and Wavelet. Saves were attempted on fewer than a third of high value accounts, which should read as an obvious miss. Color coding: each reason keeps one consistent color across badges and charts, with red reserved for competitor switches and amber for price. Save attempted shows green for yes, gray for no. Visual identity: a teal accent on a clean light base for primary actions, active tabs, chart emphasis, and summary strip highlights.
More like this
All templatesSaaS MRR Dashboard
Track MRR, new business, expansion, contraction, and churn in one revenue view.
User Engagement Dashboard
Daily and monthly active users, stickiness, and retention curves for a consumer app.
Feature Request Board
Collect requests with votes, status, and effort, then show customers what shipped.