How to estimate a SaaS company's revenue from website traffic

You can estimate a SaaS company's monthly revenue by multiplying its monthly visits by the share of visitors who pay and by the price of the plan they choose. The result is only a rough range, but it is useful for screening ideas, comparing competitors and checking whether a claimed revenue figure is plausible.

This guide gives the formula, a worked example, realistic conversion ranges and the cases where traffic gives the wrong answer.

The basic formula

Revenue is the product of three things:

Monthly revenue = monthly visits x paying share x average price

Each input has its own uncertainty, so the output is a range and not a point. Still, three honest inputs beat a guess.

StartupsIntel uses a fixed version of this formula for its estimates. It takes modelled monthly visits, assumes 3 percent of them pay, and uses the lowest paid plan as the price, with 80 percent of customers on monthly billing and 20 percent on yearly. The assumptions are public on the methodology page, and every figure is labelled as an estimate.

Step 1: get a traffic number

You need monthly visits for the product's own site. Most small companies do not publish this, so you rely on a model.

You can look up any domain in the traffic checker. It models monthly visits from five free popularity lists: Tranco, Cloudflare Radar, Chrome UX Report, Cisco Umbrella and Majestic. Using several lists helps because each has its own bias. The report at /site/<domain> also shows top regions, which matters for pricing in step 3.

Two reminders about traffic numbers:

• They are modelled, so treat a figure like 48,000 as meaning "roughly tens of thousands," not exactly 48,000.
• Marketing sites and app sites can sit on different domains or subdomains. If the product lives at app.example.com, the main domain may undercount real usage.

Step 2: choose a paying share

This is the most uncertain input. It depends on how visitors reach the site, whether there is a free tier and how much the product costs.

Public benchmarks offer a guide. ChartMogul's SaaS conversion report discusses free-to-paid conversion across products. It shows a wide spread, with a quarter of freemium products converting under 2.5 percent. Most other published sources put typical freemium conversion in the low single digits. Our companion piece on freemium conversion rates goes deeper.

Remember that visitors are not users. A visitor must first sign up, then use the product, then decide to pay. Funnel guides often put visitor-to-signup in the range of roughly 2 to 5 percent, and visitor-to-customer much lower, often around 0.5 to 2 percent for many SaaS businesses.

So why does a model use 3 percent paying share? Because it is applied to a simplified definition and it is a deliberate midpoint. For your own research, try three scenarios:

Scenario	Paying share of visits	When it fits
Low	0.5 percent	Broad consumer traffic, big free tier
Middle	1 to 3 percent	Typical self-serve product
High	5 percent or more	Narrow, high-intent audience

Step 3: pick a price

Use the real pricing page. Find the lowest paid plan, because most paying customers start there, and note whether it is billed monthly or yearly.

Then adjust for the mix. If the entry plan is $20 a month, or $192 a year, a simple blend of 80 percent monthly and 20 percent yearly gives an average of about $19.20 a month. Yearly plans lower the monthly equivalent, so the mix matters, as we show in monthly versus yearly plans.

If the product sells mainly through sales calls with custom quotes, the formula will understate revenue, because a few large contracts outweigh many small ones.

A worked example

Suppose a hypothetical AI writing tool shows about 60,000 monthly visits. Its lowest paid plan is $20 a month.

• Low case: 60,000 x 0.5 percent x $20 = $6,000 a month
• Middle case: 60,000 x 2 percent x $20 = $24,000 a month
• Our method at 3 percent: 60,000 x 3 percent x about $19.20 = about $34,560 a month

That is a spread from $6,000 to roughly $35,000. It looks wide, and it is. But it already tells you something: the tool is probably not earning $500,000 a month, and probably not $500 a month either.

Where traffic misleads you

The formula breaks in predictable ways. Check for these before you trust a figure.

• Free tools with big traffic. Calculators and generators attract millions of visits and few buyers.
• Enterprise products. Low traffic and high contract values produce a revenue that traffic cannot see.
• Mobile apps. Revenue may flow through app stores, while the website is only a brochure.
• Launch spikes. A viral post lifts visits for a week, and the average over a stable month is lower.
• Paid acquisition. Bought traffic converts poorly, so revenue per visit falls.
• Marketplaces and APIs. Usage happens outside the website, so visits hide the real activity.
• Regional mix. Visitors from lower-income regions often convert less or pay less, and the country breakdown in a report helps you adjust.

Cross-checking the estimate

A single number is fragile, so test it against other evidence.

1. Compare with peers. Look at similar products in the same category, such as those in AI writing or AI video, and see whether the estimate sits in the same band.
2. Check headcount and costs. A two-person team rarely supports a seven-figure monthly burn.
3. Look at the pricing page. A product with a generous free plan and a $9 paid plan has a lower ceiling than one starting at $99.
4. Watch traffic trend. Rising visits often precede rising revenue. The trending revenue rankings show products moving up.
5. Ask for verified data when real money is on the line. The Buy a startup marketplace lists revenue verified from the payment provider.

What to do with the number

Use the estimate to rank, to filter and to decide where to dig deeper. Do not use it to value a company or to make an offer. A rough range answers "is this worth a closer look," and nothing more.

If you want to compare many domains quickly, the bulk checker accepts a list and returns the same modelled figures side by side.

A quick checklist before you share an estimate

If you plan to quote a number in a report, an investor note or a blog post, run through a short list first.

• State the traffic source and the month it covers.
• Show the paying share you assumed and why.
• Quote a range with a low and a high case, never a single figure.
• Name the price you used and whether it was monthly or yearly.
• Say plainly that the result is an estimate and not a reported number.

This small amount of discipline protects your credibility. Readers forgive an honest range, but they rarely forgive a confident figure that turns out to be far off. It also makes your work repeatable, so a colleague can rerun the same steps next quarter and see how the picture has changed.

FAQ

How accurate is revenue estimated from traffic?

It is accurate enough to tell the order of magnitude, such as thousands versus hundreds of thousands per month, and not accurate enough for a precise figure. The spread comes mostly from the assumed paying share and the true price mix.

What conversion rate should I use for SaaS?

For a typical self-serve product, a range of about 0.5 to 3 percent of visits turning into paying customers is a reasonable planning band. Narrow, high-intent audiences can do better and broad free tools do worse, so test several scenarios.

Why do some companies earn far more than their traffic suggests?

They usually sell high-priced contracts through sales teams, earn through app stores or APIs, or serve customers who do not browse the site much. Traffic only sees the self-serve web funnel.

Can I use this to value a startup?

No. Treat it as a screening tool. For a valuation, you need verified payment data, churn, margins and the cost to acquire customers.