SaaS founders walk into a quarter already knowing most of the number. Contracted revenue, deferred revenue — the plan starts 80% done.

Ecommerce walks in acting like the number is zero.

New quarter, new target, new campaigns, new money. The same fight from scratch, four times a year.

But the real starting point isn’t zero. If customers are replenishing, reordering, subscribed — a piece of next quarter’s revenue already exists. It just isn’t labeled.

Future Revenue Coverage is that label: the share of your next-quarter revenue target that existing customers are expected to deliver — before you acquire anyone new.

Future Revenue Coverage = expected revenue from existing customers ÷ next-quarter revenue target

Not guaranteed. Not zero. Backed by observable behavior.

Two brands, one target

Both brands need $20M next quarter.

Brand A’s customer base is expected to deliver $11M of it. Coverage: 55%. The quarter starts at $11M, and the job is to create $9M.

Brand B’s base covers $4M. Coverage: 20%. The job is to find $16M in ninety days.

Same target. Completely different quarters. One team is executing a plan. The other is placing a bet.

Nobody signed a contract for Brand A’s $11M. But it isn’t hope either — it’s replenishment cycles, open reorder windows, active subscriptions. Behavior you can count.

The plan splits in two

Once you see coverage, the quarterly plan stops being one number.

Protect the $11M. That’s retention work — replenishment timing, reorder windows, subscription health. It needs an owner and a budget.

Create the $9M. That’s acquisition, reactivation, conversion. Different owner, different budget, different math.

Most plans skip straight to the second job and leave the first one unmanaged. That’s how covered revenue quietly leaks out while everyone is busy chasing new customers.

Page one of the plan needs four numbers:

✓
The Operator Playbook
Four numbers on page one
The front page of a quarterly plan that takes its own customer base seriously.
 
✓
Revenue Target.
What the quarter has to deliver. You have this one already.
✓
Future Revenue Coverage.
Coverage = expected revenue from existing customers ÷ revenue target
How much of the target today’s customers are expected to deliver — weighted by recency, frequency, and reorder behavior.
✓
Uncovered Revenue Requirement.
Target minus covered revenue — the part that has to be created from scratch this quarter.
✓
Required New-Customer Contribution.
What acquisition, reactivation and conversion must produce — a real number, not “the rest.”
✦  Try the AI Analyst  →

This is not ARR

The pushback I get: “Nothing is contracted. You’re just forecasting.”

Correct. That’s why the weighting matters.

A customer who ordered twice in the last ninety days and a customer who’s been silent for a year are not the same input. Coverage is built customer by customer — recency, frequency, replenishment cycle, subscription status. Not customers × average spend.

And expectation decays. The likelihood that a customer delivers again drops from 68% at 30 days since their last order to 49% at 90 and 31% at 180. Build that curve in and the number stays honest. Leave it out and you’ve invented ARR for a business model that doesn’t have it.

Why your forecast misses

Most ecommerce forecasts are top-down. Last year, times a growth rate, adjusted by gut feel.

When a top-down number misses, it can’t tell you why. Coverage can — because it’s built bottom-up, from customers you can name.

A disappointing quarter separates cleanly: either the covered revenue didn’t show up (a retention problem), or the gap didn’t get filled (an acquisition problem). Two different fixes that usually get treated as one.

Coverage won’t make the forecast perfect. It makes the error legible.

The better question

Retention isn’t just LTV and repeat rate. It’s revenue visibility.

Every point of coverage you add is a point of next quarter you no longer have to buy.

So instead of asking “How do we hit $20M?”, ask: “How much of the $20M already exists — and what would it take to start every quarter more covered than the last?”

Your customer data already holds the answer.

– Alex