Tool · Planning

Revenue Target Planner

Start with the number you want to hit and work backward. Enter your revenue goal and where your funnel stands today, and the planner shows what it would take to get there: more traffic, better conversion, or a higher revenue per customer, each on its own, so you can see the size of each move.

Your numbers stay in your browser. This calculator doesn't save or transmit them. The fields start with an example. Replace them with yours.

Your goal

Use one consistent period (a month works well).

$
Where you are now

Your funnel today, over that same period.

%
$

The read

Example data

Customers
needed / period

Goal ÷ revenue per customer, rounded up.

Customers now
(estimate)

Visitors × conversion.

Revenue
gap

Goal minus today's revenue.

What each lever would have to become

Each lever doing all the work, while the other two stay where they are today.

How these are calculated (and what to distrust)

Customers needed = goal ÷ revenue per customer, rounded up (a fractional customer can’t buy). Each lever solves for one input while holding the other two at today’s values: traffic = goal ÷ (revenue per customer × conversion), conversion = goal ÷ (revenue per customer × visitors), revenue per customer = goal ÷ (visitors × conversion). When you already have revenue, all three targets are the same multiple of today — the panel is one required lift shown three operational ways, not three independent options. Showing each lever alone is for scale, not a plan; a real plan moves two or three levers a little rather than one a lot. Model only the revenue this funnel is responsible for — if existing customers generate revenue outside it, take that out of the goal first. Two limits worth holding in mind: the levers interact (cheaper traffic often converts worse, and changing price or offer mix moves both conversion and revenue per customer), and this is a steady-state snapshot, not a promise the gain lands next period.

An MMS Vegas Imprint · Las Vegas, NV

The Operator’s Library

Field manuals, guides, and tools for the people who have to make the system actually work — written from production, not theory.

Verified Current

Every manual and guide is checked against the current release and carries the month it was last verified.

Corrected Openly

When a tool changes or we get something wrong, the fix is dated and noted on the affected guide.

Built by an Operator

Written by one person running the same automations, checkouts, and campaigns these books document. By Brian Kasday →