How many leads will the business generate? What proportion will become customers? How often will those customers purchase? How much revenue will each purchase produce?
For a transactional business, these questions form a simple equation:
Revenue = Leads × Lead-to-customer conversion × Purchases per customer × Average order value
The formula is straightforward. The discipline lies in making its inputs consistent.
Every number must refer to a compatible customer population, revenue definition, and time period. Otherwise, a mathematically correct spreadsheet can produce a commercially misleading forecast.
Start With What the Equation Actually Measures
The equation above estimates revenue associated with a defined group of leads and the customers acquired from them.
It does not automatically represent total company revenue. It also does not prove that all associated revenue was caused by a particular marketing campaign.
Before calculating anything, define the scope:
“This model estimates revenue earned during the next six months from new customers originating in the lead cohorts included in the plan.”
That sentence establishes three boundaries:
- The revenue period is six months.
- The customer population consists of newly acquired customers.
- The acquisition source is the specified lead population.
Existing customer revenue should be modeled separately unless it is explicitly included in the same framework.
The Four Inputs—and Their Units
Each factor performs a different job.
| Input | Definition | Unit |
|---|---|---|
| Leads | Unique prospects entering the defined funnel | Leads |
| Lead-to-customer conversion | Proportion of those leads that become customers under the model’s timing rules | Customers per lead |
| Purchases per customer | Average number of qualifying purchases made by those customers within the revenue period | Orders per customer |
| Average order value | Revenue per qualifying order | Currency per order |
The units explain why the equation works:
Leads × Customers/Lead × Orders/Customer × Revenue/Order = Revenue
Leads, customers, and orders cancel out. The result is a currency amount.
This is a useful diagnostic. If the units do not cancel cleanly, the model may be combining incompatible measures.
1. Leads: Define the Starting Population
A lead must have a consistent definition.
Depending on the business, it might be:
- A demo request.
- A qualified inquiry.
- A trial registration.
- A prospect accepted into a sales process.
These are not interchangeable.
If a historical conversion rate measures demo requests becoming customers, applying it to all newsletter subscribers changes the meaning of the model.
Also distinguish unique leads from interactions. One person who downloads a report, attends a webinar, and requests a demo should not automatically become three separate acquisition opportunities.
For each lead input, document:
- The qualification criteria.
- The source or channel.
- The segment.
- The entry date.
- The treatment of duplicates.
- Whether existing customers are excluded.
The model should start with a population the team can identify and measure.
2. Conversion: Connect the Same Leads to Their Customers
Lead-to-customer conversion is:
Conversion rate = Customers acquired from the lead population / Leads in that population
If 480 customers emerge from a cohort of 12,000 leads:
480 / 12,000 = 4%
In the revenue equation, use 0.04—not 4.
Keep the cohort and timing aligned
Suppose the business generates 2,000 leads in June and closes 80 customers during June. Dividing 80 by 2,000 does not necessarily measure June lead conversion.
Some of those customers may have originated in earlier months, while many June leads may still be progressing.
A more informative analysis follows the same lead cohort through its conversion window.
Also distinguish:
- Eventual conversion: the proportion expected to become customers over a sufficiently long period.
- In-period conversion: the proportion expected to become customers before the revenue deadline.
A six-month revenue model cannot use eventual conversion without considering when those customers will actually buy.
3. Purchases per Customer: Count Orders Within the Period
Purchases per customer is:
Purchases per customer = Qualifying orders from the customer cohort / Customers in that cohort
If 480 acquired customers place 960 orders during the planning period:
960 / 480 = 2
The average is two purchases per customer.
That does not mean every customer purchases exactly twice. Some may purchase once, others several times.
The figure should include the first purchase if that purchase is included in the revenue calculation. A “repeat purchases” metric that excludes the initial order cannot be substituted without adjustment.
Do not confuse frequency with a time rate
“Two purchases during six months” is different from “two purchases per month.”
If your input is a monthly purchase rate, it needs an appropriate exposure period. Customers acquired in the final month do not have the same time to purchase as customers acquired in the first month.
For newly acquired customers, an in-period cohort average is generally more transparent than applying a full-period frequency to everyone.
4. Average Order Value: Revenue per Transaction, Not per Customer
Average order value is calculated by dividing the relevant revenue by the number of orders for the same period. Shopify uses this basic relationship to explain AOV.
Average order value = Revenue associated with qualifying orders / Number of qualifying orders
If 960 orders generate $1,728,000:
1,728,000 / 960 = 1,800
Average order value is $1,800.
It is not revenue per customer. That figure also depends on how many times customers purchase.
For this cohort:
Period revenue per customer = 2 × 1,800 = 3,600
Define how the model treats discounts, refunds, taxes, shipping, and currency conversion. The objective is not to assume every reporting platform uses the same convention, but to reconcile the chosen AOV definition with the revenue measure being forecast.
A Complete Worked Example
Consider the following illustrative six-month plan.
| Input | Assumption |
|---|---|
| Unique leads per month | 2,000 |
| Lead-generation period | 6 months |
| Total unique leads | 12,000 |
| Conversion to customers within the modeled period | 4% |
| Average purchases per acquired customer within the period | 2 |
| Average revenue per order | $1,800 |
Assume monthly lead counts do not duplicate prospects across months and that the conversion and purchase assumptions already reflect the acquisition schedule.
Step 1: Calculate customers
12,000 × 0.04 = 480
Step 2: Calculate orders
480 × 2 = 960
Step 3: Calculate revenue
960 × 1,800 = 1,728,000
The model produces $1.728 million in revenue from the defined new-customer population during the period.
The complete calculation is:
(2,000 × 6) × 0.04 × 2 × 1,800 = 1,728,000
Each transition is visible: leads become customers, customers generate orders, and orders generate revenue.
Monthly Inputs and Period Totals Are Not Interchangeable
One common error is multiplying by the planning period twice.
If the model starts with 2,000 leads per month, multiplying by six converts that rate into 12,000 leads.
If the model already starts with 12,000 leads for the six-month period, do not multiply by six again.
| Input entered | Treatment |
|---|---|
| 2,000 leads per month | Multiply by six months |
| 12,000 leads over six months | Use directly |
| Two purchases per customer over six months | Use directly |
| Two purchases per customer per month | Apply only to the months each customer is expected to be active |
A model should label every input as a total, rate, percentage, or average.
“Leads: 2,000” is ambiguous. “Unique leads per month: 2,000” is usable.
When You Need a Cohort Model
The simple equation is useful for understanding the mechanics. Timing may require a more detailed version.
Divide leads into acquisition cohorts and calculate the revenue each cohort can produce before the deadline:
R_T = Σ over months m of (L_m × c_{m,T} × f_{m,T} × a_{m,T})
Where:
R_Tis revenue within the planning period.L_mis the number of leads entering in month m.c_{m,T}is their conversion to customers by the period end.f_{m,T}is the average number of in-period orders per converted customer.a_{m,T}is average revenue per qualifying order for that cohort.
This avoids assigning six months of buying activity to a customer acquired near the deadline.
A cohort model is particularly useful when sales cycles are long, repeat purchases take time, or acquisition volume changes materially across months.
Adapt the Model for Subscription Revenue
For subscriptions, “number of purchases” may not be the clearest planning unit.
A more useful structure can be:
Subscription revenue = Σ over cohorts m of (Active customer-months for cohort m × Average recognized revenue per customer-month)
The model can then account for activation, churn, expansion, and partial periods.
Keep revenue separate from cash collection. For a simple annual subscription paid upfront, receiving $1,200 does not necessarily mean recognizing $1,200 immediately. Stripe illustrates an arrangement in which $100 is recognized each month as the service is delivered.
Bookings, cash receipts, ARR, and recognized revenue should not be used interchangeably.
Separate New-Customer Revenue From the Baseline
Suppose the business expects $2.5 million from its existing operations and models $1.728 million from the new-customer program.
Then:
Total modeled revenue = 2,500,000 + 1,728,000 = 4,228,000
This addition is valid only if the two components do not overlap.
The baseline must not already include the same customers or purchases attributed to the new program. Likewise, revenue associated with campaign-sourced customers should not automatically be described as experimentally proven incremental revenue.
Keep the financial model’s scope separate from claims about marketing causality.
Use the Equation to Understand Growth Levers
The equation also shows how changes in assumptions affect the result.
Starting from the $1.728 million scenario:
| Change, holding other inputs constant | Modeled revenue |
|---|---|
| Original assumptions | $1,728,000 |
| Leads increase by 10% | $1,900,800 |
| Conversion increases from 4% to 4.4% | $1,900,800 |
| AOV increases from $1,800 to $1,980 | $1,900,800 |
| Purchases per customer increase from 2 to 2.2 | $1,900,800 |
Each change produces the same mathematical uplift because each factor increases by 10%.
That does not mean each improvement costs the same or is equally achievable. Higher prices may change conversion. Broader acquisition may change lead quality. More purchasing may require additional incentives or service costs.
Use the equation to identify the requirement, then evaluate the operational and financial case for changing it.
A Transparency Checklist for Your Revenue Model
Before using the forecast to allocate resources, confirm:
- The revenue metric is explicitly defined.
- Every input has a unit.
- Monthly rates are distinguished from period totals.
- Leads are deduplicated.
- Conversion follows a defined customer cohort.
- Purchase frequency includes the correct orders.
- AOV uses a consistent revenue definition.
- Sales and purchase timing fit the planning period.
- Existing-customer revenue is not counted twice.
- Historical observations are distinguished from future assumptions.
- Different segments are modeled separately where their economics differ.
- Revenue is not confused with gross profit, cash, or proven marketing impact.
Make the Revenue Forecast Explainable
The revenue equation is not valuable because it makes a spreadsheet look precise. It is valuable because it makes the commercial logic inspectable.
A reader should be able to follow the path from leads to customers, from customers to orders, and from orders to revenue—and understand exactly which period and population each number describes.
In a scenario tool such as PlotGTM, that transparency makes the controls meaningful. Changing lead volume, conversion, order value, or purchase frequency should reveal a conditional outcome, not imply that the chosen input is already achievable.
A clear model shows what the plan would produce if its assumptions hold. Evidence, execution, and ongoing measurement determine whether they do.