Show Them the Dollars They Earned Because of You. Watch Retention Move.
Customers don't cancel things that show them their score. The three-step playbook for instrumenting a value running total into your product.
Ramez Chedly
Founder•4 min read
Most cancellations don't happen because the product stopped working.
They happen because the customer stopped noticing it was working.
What I'm going to walk through is how to design a value-running-total inside your product so every time a user logs in, they see the exact dollar amount, hour amount, or progress amount they've earned because of you.
Done right, this single design move outperforms every email sequence you'll ever write. Customers don't cancel things that show them their score. They cancel things that go quiet on them.
Almost no founders build this in. Here's why.
Why the running total never gets built
Most founders skip this because they're optimizing the wrong stage.
There are five reasons it stays in the backlog.
- They build for new users, not retained users. The first 7 days of the experience is gorgeous. The day-90 experience is unchanged from day 7.
- They have no instrument for "how much value did this customer get this month?" The data isn't collected, so it can't be surfaced.
- They confuse value with engagement. Time-on-platform isn't value. Outcome is value. They show the wrong number.
- They think the value is obvious. It isn't. Customers forget. The wins from month 2 are invisible by month 4.
- They've never measured what happens to retention when the running total ships. So the ROI feels speculative, and it gets deprioritized.
Here's how to install it.
Step 1: Define the unit of value your customer cares about most
Every product has a primary outcome.
Pick it before you build anything else. Get this wrong and the rest of the build is wasted.
For a grant-finder, it's grants applied for and grants won. For a sales tool, it's pipeline value generated. For a fitness app, it's workouts completed and consistency streaks. For a finance tool, it's dollars saved or earned.
The wrong unit is the unit that's easy to count but doesn't move the customer's heart. Logins is the wrong unit. Sessions is the wrong unit. Pick the outcome.
If you can't write the unit on a sticky note that a customer would actually care about, you don't have it yet.
Step 2: Instrument the running total and pipe it back to the customer
Where most founders go wrong: they instrument the metric for analytics dashboards, then never surface it back to the user.
The data lives in Mixpanel and dies there.
The data you collect for product analytics is the same data the user wants to see. Build the running tally and route it into the product UI directly. Not in a settings page. Not in a monthly summary email. In the product, on the dashboard.
A specific example. A founder I worked with surfaces a single line on the home view: "Since you joined, you've earned $12,400 in funding." It updates weekly. That single number moved their cancellation rate down by 45% inside one quarter.
The mistake to avoid: collecting the data but only showing it to your team. The user is the audience for this number, not your investor deck.
Step 3: Make the running total the first thing they see
The light at the end of the tunnel is this.
When the running total is buried in a sub-page, it works for the 10% of users who go looking. When the running total is the first thing they see at login, it works for everyone.
The pattern: a single hero number on the dashboard. Above the fold. Updated weekly. Optionally, a small change indicator like "+$1,200 this month" so the trend is visible too.
What this all ladders up to is a product where the customer logs in and immediately remembers why they're paying you.
Cancellations stop being about price. Renewals stop being about email sequences.
The product itself is the retention mechanism.
The customers who churn are the ones who forgot.
The fix is to never let them forget.
This is one of three plays inside a larger playbook for founders moving from courses to software businesses that don't churn. The full reframe — including how to move from "consumed" to "operated" and why owned software beats affiliate links — is here: From Course to Software: A Founder's Playbook for Businesses That Don't Churn.
