Find the one funnel step losing revenue, then fix the cheapest leak first
A practical diagnostic for founders: map the funnel, rank leaks by revenue impact, and test the cheapest fix.

If your funnel has been live long enough to show drop-off, the practical first move is to repair a broken step, not to add features or buy more traffic. In a mature funnel, one or two leaky steps can account for 60-80% of all drop-off. Repairing the one or two most leaky steps in a funnel can raise completion rates by 20-40% without adding new features.
The diagnostic turns drop-off into a repair list
- Map the steps before you judge them. Start with the path a user must complete, from an early meaningful action to purchase, signup, or renewal. Build a short table with a step name, the number of users entering, and the number leaving. Merge any step that is not a decision point into the previous step, so the path can be explained in one sentence. A long list hides the decision points that actually move revenue.
- Calculate drop-off at each step. Divide users lost by users entering, then multiply by the revenue at risk. Use the same revenue definition for every step: expected revenue from a trial, not list price, and average order value for checkout. The result should be a column you can sort without arguing about what counts. If the revenue definition changes between steps, the ranking will be wrong.
- Benchmark each step against a realistic range. In ecommerce checkout flows, a 65-75% conversion from add-to-cart to purchase is treated as healthy, and a sub-50% rate signals friction. Do not borrow a benchmark from a different business model. A free signup path and a paid checkout path are not the same problem. Use the benchmark only to flag a step, then let your own data decide the size of the gain. A benchmark that is too broad turns a real leak into a false alarm.
- Rank leaks by revenue impact and intent. A user who has added an item to a cart is closer to a decision than a user who landed from a broad search. A user on a pricing page is closer than a user reading a general article. For pricing or checkout exit issues, a 10% gain is typically more important than a bigger gain on a low-intent blog page. Put high-intent, high-revenue steps above low-intent pages, even if the percentage drop-off is smaller. Intent matters because the same percentage loss is worth more when the user is already close to paying.
- Select the cheapest fix to test. Prefer fixes that reduce effort: remove a field, clarify a price, shorten a confirmation, make an error message actionable, or move a required step later. The test needs a named change, a named metric, and a short window. A cheap test should be reversible and small enough to judge before you commit more budget.
The usual mistake is fixing the most obvious number
Operators often chase the number that stands out, or the step that feels most technical. That is the wrong order. The step with the biggest percentage loss may be low-intent traffic that was never likely to buy. The step with a modest loss may sit on the path to a paid plan, a checkout, or a renewal.
Costa Coffee's loyalty registration funnel had a 30% drop-off rate. In Costa Coffee's loyalty registration flow, 15% of users encountered an invalid-password error, and a simpler error message with inline validation raised registrations by 15%.
A 2021 study in the International Journal of Contemporary Hospitality Management looked at app value perception, specifically user judgments of convenience and usefulness in digital services. If your users are deciding whether to continue, convenience is the metric you can improve without a new feature.
The repair should be cheap enough to test
If the fix needs a new feature, a new integration, or a redesign, park it until the cheap test has run. Put the biggest leak in front of your team with the revenue number, the benchmark, and the cheapest fix you can ship. Do not start another project until the test has a result.