How Much Traffic Does a SaaS Actually Need?

Every founder who has shipped something asks a version of this question within the first six months. It usually arrives as a number with a shrug attached: three thousand visitors and no signups, eleven thousand impressions and a hundred clicks, a launch that did great numbers and nothing else. The advice that comes back is almost always the same, which is to go get more traffic.

We were able to test that advice directly. Our revenue intelligence corpus tracks 8,600+ startups that publish verified recurring revenue, and a large slice of them also publish monthly visitor counts and Google search impressions. After filtering to the products that report both traffic and revenue, we had 740 companies where the question can be answered with measurement instead of opinion.

The answer is not the one the advice implies. Traffic does rise as revenue rises, but nowhere near fast enough to explain the revenue. Across the ladder from under $100 a month to the $10,000 to $50,000 band, median monthly traffic multiplies by about 39. Median revenue multiplies by about 596. The difference is absorbed almost entirely by one number, which is how much each visitor is worth, and that number moves 25x.

How much traffic does a SaaS need? The short answer

What revenue per visitor means, and why it is the number that matters

Revenue per visitor is monthly recurring revenue divided by unique monthly visitors.A SaaS with $500 in MRR and 2,000 monthly visitors has a revenue per visitor of $0.25. It is sometimes abbreviated RPV. It is not the same as conversion rate, which counts how many people acted, and it is not the same as average revenue per user, which only counts the people who already pay. Revenue per visitor is the only one of the three that prices your entire audience, including everyone who looked and left.

It matters here because it is the term that closes the gap between traffic and revenue. Monthly visitors multiplied by revenue per visitor equals monthly recurring revenue, by definition. So when revenue is too low there are exactly two places the shortfall can live, and measuring the second one tells you which. Across our 740-company sample, the second one accounts for roughly 93.5% of the difference between the bottom and top of the revenue ladder.

Three terms are used throughout this page with specific meanings. Monthly visitors means unique people over the trailing 30 days, not sessions and not pageviews. Search impressions means the number of times Google displayed the product in results over the same window, before any click. Monthly recurring revenue means subscription revenue in US dollars, excluding one-time payments.

Why the question keeps recurring

The question is not naive. It is the correct question asked with the wrong denominator. A founder who has shipped has spent months on a product and weeks on a launch, and the only feedback loop available is the analytics dashboard. So traffic becomes the proxy for progress, and the gap between traffic and revenue becomes inexplicable.

The founder communities are full of this shape. “Anyone else spending more time finding users than building?” is the top-voted framing of it we found, from r/SaaS. The same subreddit carries “30k visitors, 5k users, $0 marketing spend” as a celebration post, with no revenue figure attached anywhere in the title. And the bluntest version, also r/SaaS: “My SaaS just made $0.000 revenue in 60days after launch and I am so grateful.”

One thread reduces the whole problem to a single comment. Replying to a founder reporting three thousand customers, someone wrote: “How you only have $271 on 3000 customers lmao what” (r/SaaS). That is a revenue-per-user problem wearing the costume of a growth story, and it is the most common failure mode in this dataset.

The advice industry has an incentive to answer the traffic question rather than the yield question, because traffic is the thing that can be sold to you. Very little published work measures the other side. We checked what ranks for this query before writing, and the first page is dominated by advertising-revenue math meant for content sites, plus articles that state plainly that no public benchmark exists for software. One of the better ones puts it in exactly those words: B2B SaaS has no public revenue-per-visitor benchmark yet. That is the gap this page is trying to close, and it is why we are publishing the distribution rather than a rule of thumb. If you want the adjacent question of how long any of this takes, we measured that separately in how long it actually takes to grow a SaaS.

How we measured

Every figure on this page comes from one corpus: 8,600+ startups that publish verified recurring revenue, nearly all of which also carry a traffic record. We used four fields. Monthly visitors over the trailing 30 days, Google search impressions over the trailing 30 days, monthly recurring revenue in dollars, and reported customer count. Revenue in this dataset is in dollars, not cents, and we did not transform it.

We report medians rather than means everywhere, because the distribution is violently skewed. The largest single traffic record in the corpus is over 22 million monthly visitors, which is four orders of magnitude above the median. A mean would be a description of that one company. The same skew is why we report medians in the state of indie SaaS revenue and the TrustMRR revenue benchmarks. Where a band has fewer than roughly 25 members we say so in the table, and where it has fewer than 15 we decline to draw a conclusion from it.

Revenue per visitor is computed per company and then the median is taken, rather than taking total revenue over total visitors. Those two methods give very different answers on a skewed corpus, and the second one describes the largest company in the set rather than the typical one. We have stated which method we used at each table so the numbers can be reproduced. The same discipline is applied in our SaaS revenue benchmarks by categoryand in the metrics benchmarks page.

Where this data was hiding

Worth recording, because it nearly killed this analysis. The typed traffic columns in our warehouse are populated for exactly zero rows. A reasonable reading is that the data does not exist and the question cannot be answered.

It does exist. The source payload carries visitors, search impressions and revenue per visitor on all but a handful of the 8,600+ records, and the typed columns are a parse that never ran. An empty column is far more often a broken pipeline than absent data, and the check costs one query. We now treat that as a standing rule, and it is the same discipline that produced the churn distribution we later folded into our metrics benchmarks.

Of those 8,600+ records, 1,457 report more than zero monthly visitors and 375 report more than zero search impressions. 740 report both traffic and revenue above zero. That last number is the denominator for most of this page, and we name it every time we use it.

How much traffic does a SaaS have at each revenue level?

This is the table the question was asking for. Read the middle columns as the honest range: the 25th and 75th percentile inside each band, because the spread inside a band is wider than the gap between bands.

Two things in that table are worth sitting with. The first is how small the numbers are at the bottom. A quarter of the products earning under $100 a month get fewer than 75 visitors in a month, which is two and a half people a day. The second is that the jump from $5,000 to $50,000 in revenue, a 10x move, comes with a traffic increase of about 63%. The traffic is not doing the work. For what those revenue bands look like in absolute terms, see what it costs to get there and real micro SaaS examples.

What is a good revenue per visitor for a SaaS?

Pull the last column out and the shape becomes obvious. $0.08, then $0.26, then $0.47, then $1.25, then $1.98. Each step is roughly a doubling to a tripling, and the total run is 25x. There is no other variable in this dataset that moves that cleanly with revenue.

Stated as a planning number: at $0.08 a visitor you need 12,500 monthly visitors to reach $1,000 a month. At $1.98 you need 505. The founder who has 3,000 visitors and $50 in revenue is not three thousand visitors short. They are about twenty cents a visitor short, and no amount of additional traffic fixes that, because the multiplier is applied to a near-zero base.

This is why the community advice to “just ship more content” so often produces nothing. It is also why one of the better-voted threads we found asks the inverted question directly: “The smallest change that doubled your conversion rate (without getting more traffic)?” (r/EntrepreneurRideAlong). Doubling yield at 1,000 visitors is worth exactly as much as doubling traffic at the same yield, and it is usually much cheaper.

39x against 596x

Run the arithmetic across the full ladder. Median traffic goes from 278 to 10,807, a factor of 38.9. Median revenue goes from $28 to $16,697, a factor of 596. Traffic explains about 6.5% of the revenue growth. Yield explains the rest.

We want to be precise about what that does and does not prove. It is not a claim that traffic is irrelevant, because every band above the bottom has more of it. It is a claim about where the binding constraint sits. If traffic were the constraint, the two factors would be close to each other. A 15x gap between them says the constraint is somewhere else.

The most likely candidates for “somewhere else” are price, audience and category, and we test all three further down. The one that is easiest to change in a weekend is price, which is the subject of what micro SaaS actually chargesand our SaaS pricing strategies guide.

How many SaaS products have traffic and no revenue?

The 740-company table only includes products that have both traffic and revenue. Widen it to every product with measurable traffic and the picture gets considerably darker. Of the 1,457 products reporting more than zero monthly visitors, 717 report no recurring revenue at all. That is 49.2%, which is close enough to a coin flip to be worth stating plainly.

Include those zero-revenue products and the median revenue per visitor across the whole traffic-having population falls to about $0.03 to $0.06 depending on the segment. The $0.08-to-$1.98 ladder describes the products that got somewhere. The population number describes the products that exist.

This is the measured version of the observation that topped r/SaaS during our capture window: “AI made everyone a builder. It forgot to make more buyers.” The supply of shipped software with an audience has outrun the supply of people willing to pay for it. We looked at the same phenomenon from the competition side in the state of micro SaaS competitionand our saturation analysis.

Can you have 10,000 visitors and still earn nothing?

The zero-revenue group is not made up entirely of products nobody has seen. 122 of them draw more than 1,000 monthly visitors and report no revenue. 29 draw more than 10,000 monthly visitors and report no revenue.

Ten thousand monthly visitors is a real audience. It is more traffic than the median product in our $10,000-to-$50,000 revenue band has. Those 29 companies are the cleanest possible refutation of the traffic hypothesis, because they have already won the thing the advice tells you to go win, and it did not convert into anything.

The community equivalents are easy to find once you look for them. One r/microsaas post reports “3,152 users, $110 MRR” in its title. Another describes a Chrome extension that went “from 60 to ~5.8k users” in two weeks and is now “trying to convert the people who already installed it.” A third, from r/startups, is the most surgical: “Spent €174 on Reddit ads for a B2B SaaS. 111,927 impressions, 1,579 clicks, zero customers.” A hundred and eleven thousand impressions bought fifteen hundred visits and no revenue at all.

If any of this sounds familiar, the diagnosis is not a marketing diagnosis. One r/microsaas commenter put the uncomfortable version well: “Having few users doesn’t necessarily mean your marketing is bad. Sometimes, people simply don’t want your SaaS.” We pulled the failure patterns apart in why startups fail and the failure statistics.

What do Google search impressions actually buy a SaaS?

375 products in the corpus report Google search impressions above zero, and 350 report both impressions and visitors. The median among them is about 2,314 monthly impressions producing about 57 visitors from search. That is a 2.4% click-through from impression to visit.

Chain that together. Roughly 2,300 impressions become 57 visits, and rich-result eligibility only changes the click side of that chain, never the yield side. At the $0.26 revenue per visitor typical of the $100-to-$1,000 band, those 57 visits are worth about $15 a month. That is the actual dollar value of a mid-sized search footprint for a small SaaS, and it is why search is a compounding channel rather than a launch channel. The related discipline of getting quoted by answer engines rather than just ranked is covered in our AI Overviews guide.

Impressions without revenue

The same trap repeats one level up. Of the 350 products with measurable search impressions, 188 report no recurring revenue. That is 53.7%, slightly worse than the traffic population. And 34 of them clear 10,000 monthly impressions while still earning nothing.

Impressions are the most seductive vanity metric available to a founder, because they move fastest and require the least. A single indexed page can generate thousands. One r/SaaS post during our window is titled “Asking Claude to do a SEO pass on my site doubled my impressions,” and the thread contains no revenue figure. A more honest one from r/microsaas asks: “What did your first 8 weeks of Search Console look like? Mine is 11.2K impressions and 109 clicks.” That is a 1% click-through, which at the median yield in this corpus is worth somewhere around ten to thirty dollars a month.

None of this is an argument against search. It is an argument against reading impressions as progress, the same way install counts mislead in Chrome extension monetization and WordPress plugin sales. The number that matters is the one at the end of the chain, and our MRR tracking tools roundup covers the instrumentation side of connecting the two.

How many visitors does it take to get one SaaS customer?

The folk rule is that one visitor in a hundred becomes a customer. Among the 45 products in our corpus that report both a traffic figure and a customer count, the median visitor-to-customer rate is 2.33%, or roughly one customer per 43 monthly visitors.

We do not think that means the rule is wrong by a factor of two. We think it means the sample is biased, and badly. A product only appears in that subset if it has customers to report, so every product that converted nobody is excluded by construction. The honest reading is that 2.33% is an upper bound on what a working product does, not a planning assumption for a new one.

The best published treatment of this question is good on the mathematics and explicit that its own figures are illustrative rather than measured. The point we can add is the one they cannot: the real distribution includes the 49% that converted nobody, and any planning number that omits them is describing a survivor. We took the same approach to survivorship in our solo developer revenue examples.

Customer count against price

Splitting the same small sample by traffic band shows where the money is actually coming from, with the caveat that each cell holds only 8 to 14 companies and should be read as directional.

The under-500 row is the interesting one. It has the highest visitor-to-customer rate in the table at 4.29% and the lowest revenue of any row, because the median customer pays $1.50. High conversion at a price nobody could build a business on is not a funnel success. It is the signature of a free-adjacent product, and it converts precisely because almost nothing is being asked.

One r/indiehackers thread title states the mechanism without needing our data: “your low price is be scaring customers away.” The price-to-perceived-seriousness relationship is the least intuitive lever in early SaaS and the one with the shortest feedback loop. Ourpricing guide for micro SaaS walks the mechanics.

Which SaaS category earns the most per visitor?

The single biggest determinant of what a visitor is worth is not your funnel. It is what you sell. Across the fourteen categories with at least a dozen measured companies, median revenue per visitor spans 8.5x.

A marketing tool and a design tool with identical traffic are not in the same business. At the medians above, a thousand visitors is worth $510 a month in marketing and $60 in design tools. Changing your funnel will not close that. Changing what you sell will.

Why marketing tools lead

Marketing tools top the table at $0.51 with the third-lowest median traffic in it, 819 visitors. That combination is the definition of a high-yield category: a small, expensive, highly qualified audience.

The mechanism is that a marketing tool is bought out of a budget that already exists and is measured against revenue the buyer can attribute. Fintech at $0.39 works the same way. Both sit next to money, and proximity to money is the most reliable predictor of what a visitor is worth in this entire dataset, and it is why B2B SaaS ideas and industry-specific opportunities tend to price better. It is the same signal that drives category-level differences inthe most profitable SaaS niches and profit multiples by category.

Artificial intelligence sits third at $0.32 across the largest sample in the table, 207 companies. That is a genuinely healthy yield, and it is worth noting because the prevailing narrative is that AI products are commoditized wrappers that cannot charge. On this measure they out-earn general SaaS, productivity and developer tools per visitor. We looked at the revenue side of that claim separately in the AI SaaS revenue reality check.

The traffic-rich, revenue-poor categories

Now read the table by the traffic column instead. Education has 3,142 median monthly visitors, the highest in the table, and $0.12 revenue per visitor, the second-lowest. Design tools have 2,603 visitors and the worst yield on the board at $0.06. Social media and mobile apps are similar shapes.

These are the categories where the traffic advice is actively harmful, because traffic is the one thing they already have. An education product with three thousand monthly visitors and $229 in revenue does not need a content strategy. It needs a reason for one of those three thousand people to pay more than seven cents. Finding problems worth solving and finding ideas from real pain points both start from that reason rather than from traffic.

Developer tools deserve a specific note. They have the second-lowest median MRR in the table at $52 and a low yield at $0.14, on a healthy sample of 38 companies. Developers are famously willing to evaluate and famously unwilling to expense, and this is what that looks like when you measure it. If you are building for developers, the yield problem is structural and needs to be designed around from the start rather than discovered at month nine. We sized who actually buys in who micro SaaS actually sells to.

Is B2B or B2C better for revenue per visitor?

Splitting the traffic-having population by stated audience gives a cleaner comparison than the category table, because it includes the zero-revenue products rather than filtering them out.

B2B products get about 26% less traffic than B2C products and extract about twice as much from each visit. That is the entire B2B case stated in two numbers, and it survives the acquisition cost adjustment, and it is why the standard advice to build for businesses holds up on this measure.

The column that complicates it is the last one. B2B has the highest share of products earning nothing at all, 40.5%. Higher yield when it works, higher chance it never works. That is a different risk profile, not a strictly better one, and founders choosing between them should price both halves. Our fuller treatment of that choice, including where the consumer majority actually sits, is in who micro SaaS actually sells to.

How much traffic should a SaaS have in its first year?

Splitting by company age gives the most useful expectation-setting table on this page, because it answers the question a founder is really asking, which is whether their numbers are normal.

The median first-year product earns zero per visitor, because 54.4% of first-year products with traffic earn nothing at all. If you are eight months in with a few hundred visitors and no revenue, you are not an outlier. You are the median.

That is worth saying without softening it, because the community timeline is distorted by survivorship. The posts that get voted up are “$1k MRR in 6 months” and “I launched a tool in April, now has 9,000 signups and $26K/mo in revenue.” The posts that describe the median outcome are the quiet ones: “My side project finally reached ~$1k MRR after almost 3 years” (r/SaaS), and “Took a year from 0 to $200 MRR and first 10 paid users” (r/buildinpublic). We measured the full timeline inhow long it actually takes to grow a SaaS and the road to the first $1k MRR.

Does revenue per visitor keep improving as a company ages?

The fourth row breaks the pattern and is the most interesting thing in the table. Median traffic drops from 1,927 at two-to-four years to 871 at four-plus, revenue per visitor stays flat at $0.053, and the share earning nothing goes back up to 42.6%.

We can think of two readings and we cannot separate them with this data. The first is survivor composition: products that are still listed at four years with low traffic may be small, stable and deliberately un-marketed, which is a real and respectable shape. The second is decay: a product that stopped being worked on keeps its listing and loses its traffic.

What we can say is that revenue per visitor stops improving after about year two. Whatever yield you have built by then is roughly the yield you keep, which makes the first two years the window where the per-visitor number is actually movable, and it is why churn and lifetime value become the binding metrics afterwards. That matches the growth-rate decay we measured separately in how fast SaaS startups actually grow.

Do faster-growing SaaS products have more traffic?

Splitting the traffic population by last-month MRR growth produces a result that looks backwards until you think about the denominator.

The 20%-plus growers have less traffic and a third of the yield of the single-digit growers. That is a base effect, not a paradox: going from $40 to $50 is 25% growth and going from $8,000 to $9,000 is 12.5%, and only one of those is a business. The steady sub-20% growers are the substantial companies in this corpus.

The row that actually matters is the third one. 913 of 1,457 products with measurable traffic are flat or declining, at a median of 352 visitors and a median yield of zero. That is 63% of the traffic-having population sitting still. Percentage growth rates quoted without a base are the most misleading number in indie SaaS, alongside the ones we unpick in the SaaS metrics benchmarks,, which is why we broke down the definitions inMRR against ARR against TTM revenue.

Does the payment processor affect revenue per visitor?

Splitting by payment processor is tempting and mostly misleading, so we are publishing it with the caveat attached rather than leaving it out.

Do not read this as a recommendation. The newer rails are disproportionately chosen by newer products, and newer products are the ones earning nothing, so the rail is standing in for age. The only row we would draw anything from is RevenueCat at $0.072, which is mobile-first billing and reflects a different monetization model rather than a better processor. We cover the merchant-of-record question properly insubscription against one-time purchase.

What this means for your SEO plan

It does not mean stop. It means size the prize before you spend six months on it. Take your category yield from the table above, multiply by the traffic a realistic content program can produce, and see whether the answer is a business.

Worked example. A developer tools product at $0.14 per visitor that gets to 5,000 monthly visitors is looking at roughly $700 a month. A marketing tool at $0.51 doing the same work lands near $2,550. Same effort, same traffic, 3.6x difference, decided before either founder wrote a word. Choosing a profitable niche and sizing the market are the upstream versions of this decision. Our SaaS market research guide covers sizing this before you commit.

The corollary is that the yield number is the thing to move first, because it multiplies every future visitor you will ever earn. Doubling revenue per visitor before starting a content program doubles the return on the entire program. Doing it afterwards only doubles the return on what is left.

What this means for launches

Launch traffic is the lowest-yield traffic in existence and the easiest to mistake for progress. The community data on this is unusually concrete. One r/SaaS commenter reports: “Do a post on Hacker News as well, I got 3000 visitors in 10 minutes there the other day.” Another thread title reads “One Reddit post yesterday = 415K views, 1,100 users, 30 subs in 24 hours.”

Note what that second one is actually reporting. 415,000 views produced 1,100 users and 30 subscriptions. That is a 0.26% view-to-user rate and a 2.7% user-to-subscription rate, and it is one of the better launch outcomes anyone posted during our capture window. Most launches produce the spike without the tail, which is the pattern behind most early failures and the reason validating before building pays for itself.

Which is why one of the queries our own search console shows us ranking for is, verbatim, “looking for product directories that send consistent traffic over time not just launch day spike.” That is a founder who has already learned this lesson. We ranked the options inwhere to launch your startup, the startup directories list and Product Hunt alternatives.

The directory spike trap

A launch-day spike inflates your 30-day traffic number and therefore deflates your revenue per visitor, sometimes by an order of magnitude. A product with 400 steady monthly visitors and $200 MRR is at $0.50 a visitor, which is top-quartile. Add one good launch that brings 5,000 people in a day and the same product reads as $0.037 a visitor.

This matters for anyone using our tables to benchmark themselves. Compute your number on a month without a launch in it, or the comparison is meaningless. It also means the 29 traffic-rich zero-revenue companies mentioned earlier may include a few that simply got measured during a spike, which is a limitation we state again in the methodology. We apply the same spike correction in do vibe-coded apps make money.

Where the traffic actually comes from

The corpus does not carry a channel breakdown, so this section is community evidence rather than measurement, and we are labelling it as such. Among the founders posting real numbers during our capture, the recurring pattern is that the highest-yield early traffic is conversational rather than algorithmic.

One r/micro_saas operator reports “Reddit brings about 30% of our traffic.” An r/SaaS founder describes getting “my A/B testing SaaS to over $2k MRR (mostly from Reddit, slow growth, and zero hacks).” The question that recurs underneath these is the sequencing one: “SEO compounds later, so did the early ones come from Reddit, direct outreach, communities, or was search already working that early?”

That sequencing intuition matches the age table. Search yield takes two years to arrive, and the median first-year product earns nothing per visitor, so first-year traffic has to come from somewhere with a shorter payback. We cover that channel work inhow to get your first 100 SaaS users, how to get customers for a startup and finding business ideas on Reddit.

What founders are actually posting

Our corpus says what the distribution looks like. The community says what it feels like from inside. These are real figures founders published in public founder subreddits during our September 2026 capture window, anonymized to the subreddit and reproduced as posted. Read the right-hand column, because that is where the pattern is.

Twelve of those fifteen lead with a traffic, view, install or signup number. Three lead with revenue. That ratio is the reporting culture this page is arguing with, and it is why the median founder’s sense of what is normal is calibrated against the wrong metric. The quieter counterweight, also from r/microsaas, is worth keeping next to the table: “Having few users doesn’t necessarily mean your marketing is bad. Sometimes, people simply don’t want your SaaS.”

How do I tell if I have a traffic problem or a conversion problem?

The diagnostic is one division. Take your recurring revenue for last month, divide by your unique visitors for the same month, and put the result against the ladder.

The asymmetry in that last column is the practical takeaway of the whole page. Traffic is the right thing to work on at the top of the ladder and the wrong thing at the bottom, and most founders asking the question are at the bottom.

The three numbers to pull before you do anything

Before any decision, get these three, from a month with no launch in it.

• Unique visitors, not sessions or pageviews. Pageviews inflate the denominator with returning users and reloads, which makes your yield look worse than it is.
• Recurring revenue, not total collected. One-time payments and refunds distort a monthly figure badly at small scale.
• Customer count, so you can split yield into conversion and price. A $0.10 yield from 5% converting at $2 is a completely different problem from 0.2% converting at $50.

That third split is the one almost nobody does, and it is the difference between a pricing problem and a funnel problem. How to calculate MRR and the SaaS metrics dashboard guide cover the mechanics.

When is traffic genuinely the problem?

There are three cases in this data where the traffic answer is correct.

• Your yield is already above $0.50 a visitor. You are converting at a rate the top two bands convert at. The measured constraint is volume.
• You are under about 200 monthly visitors. A quarter of sub-$100 products sit below 75 visitors a month. At that scale you cannot distinguish a bad funnel from a small sample, and the first job is getting to a number you can measure.
• You sell in a high-yield category at low volume. A marketing or fintech product at 800 visitors is leaving the category multiplier on the table.

When is traffic not the problem?

And four cases where it is not, each tied to a number above.

• You are one of the 717 with traffic and zero revenue. Multiplying zero does nothing. Something upstream of traffic is unresolved.
• You are above 1,000 visitors and under $50 MRR. That is the 122-company group. Your funnel has been tested and it answered.
• You are in education, design tools, social or mobile. Those categories already carry the highest median traffic in the table and the lowest yields.
• Your revenue per customer is under about $5. The under-500-visitor row converts at 4.29% and still earns $21 a month, because the price is the problem.

Lever one: price

Price is the fastest lever because it moves yield immediately and needs no new visitors. The counter-intuitive part, which shows up repeatedly in the community data, is that raising it frequently improves the rest of the funnel too. One r/microsaas founder writing up eight months to $1.7k MRR put it directly: “When I raised prices, more committed users, lower churn, and even better conversion.”

That is not a universal law and we cannot test it on this corpus, because we observe one price per company rather than a before and after. What we can say is that the products at the bottom of our yield table are overwhelmingly cheap, and that the $1.50 median revenue per customer in the under-500-visitor row is not a price anyone can build on.

For the measured distribution of what small software actually charges, including where freemium helps and where it does not, see what micro SaaS actually chargesand SaaS pricing strategies.

Lever two: audience

The B2B table gives the size of this lever: roughly 2x yield for roughly 26% less traffic. Moving a product from a consumer framing to a business framing, without changing the code, is one of the few interventions that can plausibly double revenue per visitor.

The catch is in the same table. B2B also has the highest share of products earning nothing, so the move increases variance as well as expected value. It works when the underlying job is something a business already pays someone to do, which is exactly what freelance job posts and documented business pain points let you check, and fails when you are simply charging a company for a consumer habit. Finding problems worth solvingand who micro SaaS actually sells to go deeper.

Lever three: category

The 8.5x category spread is the largest single number on this page, and it is the one decided earliest and changed least often. A product adjacent to someone’s revenue is worth several times a product adjacent to someone’s hobby, at identical traffic.

For a product already built this is a repositioning question, not a rebuild: which of your existing capabilities sits closest to a budget. For a product not yet built it is the single highest-leverage decision available, which is the argument behindthe most profitable SaaS niches, low-competition SaaS ideas and SaaS ideas backed by real pain points.

Almost nobody can measure this on their own product

There is a structural reason this question is answered with folklore. Traffic lives in one system and revenue lives in another, and joining them is work that most small teams never do. The gap shows up clearly in software review data.

Across our review corpus of 1M+ complaints and feature requests from Capterra, G2 and the app stores, reporting and analytics gaps are one of the most requested categories in the entire dataset. The requests are consistently about connection rather than charts. A web developer reviewing a payments platform writes that “managing multiple payment channels without a streamlined report is a headache.” A sales manager on the same product asks for “clearer analytics to determine which payments are successful or delayed.” An owner writes simply that “it’s not easy to see financial metrics at a glance.”

The pattern repeats across unrelated categories. A franchise manager: “We should be able to see all of our locations’ performance in one view, but instead, I’m exporting data every week.” A marketing operations reviewer: “Having to pull manual reports detracts significantly from time spent strategizing rather than reporting.” A senior analyst: “I spend too much time on weekly analytics due to the lack of automation.”

Every one of those is the same unmet need as the founder who cannot tell whether traffic is the problem: the join between activity and money is manual, so it does not get done. That is also, not incidentally, a recurring micro SaaS opportunity shape, which we catalogue ininternal tool ideas and tools to find customer pain points.

What the review corpus adds

Two things, both of which support the yield reading rather than the traffic reading.

First, the complaints that kill software are almost never about discoverability. Across the categories we have analysed in depth, the recurring themes are cost, support, integration and reporting. Nobody writes a one-star review saying they could not find the product. They write it after they found it, paid, and were disappointed. That is a yield-side failure, the same one behind the most hated software and the reviews vendors ignore, and we broke the category-level detail out incustomer support software limitations, email marketing software limitations and sales software limitations.

Second, the complaint corpus is where the price objection actually lives. When buyers say a product stopped being worth it, they are describing the exact moment revenue per visitor collapses for that company. We used that signal to buildwhy SaaS customers churn, and it is the retention-side mirror of everything on this page, alongside the features buyers keep asking for.

What founders get wrong, in order

• Counting sessions instead of people. The single most common instrumentation error, and it makes yield look roughly 30 to 50% worse than it is.
• Benchmarking against a launch month. One spike ruins the denominator for thirty days.
• Treating signups as the finish line. The 3,152-users-at-$110-MRR shape is signups mistaken for traction.
• Reading impressions as demand. 53.7% of products with measurable search impressions earn nothing.
• Assuming the 1% rule. It is 2.33% among products that work and effectively 0% among the half that do not.
• Comparing to survivor posts. The median first-year product earns zero per visitor, and that outcome is never the one that gets upvoted.
• Fixing the funnel before the price. At $1.50 per customer no funnel produces a business.

The benchmark table, in one place

How this compares to published benchmarks

There is very little to compare against, which is the point. The best-sourced public figures for revenue per visitor are ecommerce benchmarks, typically quoted in the range of roughly $0.30 for early-stage stores up to $2.00 and above for best-in-class, per published profit-per-visitor data. Several of the pages that publish them state outright that no equivalent public benchmark exists for B2B software.

Our measured software ladder runs from $0.08 to $1.98, which brackets the ecommerce range at the top and sits well below it at the bottom. That is the expected shape. Ecommerce converts a visit into a one-time transaction at a known basket size, while software converts a visit into a subscription that may take months to start. The bottom of the software distribution is therefore much thinner than anything ecommerce reports, and the top is comparable.

The other widely circulated figure is visitor-to-lead conversion for B2B sites, commonly given as 1.5% to 2.5% average against 8% to 15% for the top decile. Our 2.33% visitor-to-customer median is suspiciously close to that average lead rate, which we read as a sign that our 45-company subset is measuring something closer to activation than to payment, and we have flagged it as survivor-biased for that reason rather than presenting it as a conversion benchmark.

Is anyone actually searching for this

Worth checking before investing in a topic. Google Trends over the last five years shows “saas conversion rate” on a clear multi-year rise, essentially flat near zero through 2022 to 2024 and climbing steadily from mid-2025 to a peak in March 2026. “Revenue per visitor” follows the same shape at much lower volume, with no meaningful signal before late 2025.

Two caveats we will not skip. Trends is relative to its own peak and cannot tell you volume, so the only claim available is direction. And the final several weeks of both series read near zero, which is a reporting-lag artifact of the window rather than a collapse in interest. Read the direction, ignore the tail.

On our own property, Google Search Console shows no page owning this query family, which is why this page exists. The methodology for that kind of first-party gap check is inour market research guide.

What would change this analysis

• A channel breakdown. We measure total visitors, not source. If a large share of the traffic in the low-yield bands is launch or social traffic, the yield gap between bands would narrow considerably.
• A time series. Every figure here is a single snapshot. We cannot say whether a given company’s yield improved, only that older cohorts have higher medians.
• Self-reporting correction. Revenue in this corpus is verified through payment connections, but traffic is self-reported. If founders overstate traffic, every yield figure here is a floor.
• Coverage beyond the top band. We have 29 companies between $10k and $50k and too few above $50k to publish. The ladder may flatten or steepen above that and we cannot see it.

Methodology

All figures were computed on September 21, 2026 against a live warehouse. Monthly visitors and Google search impressions are trailing-30-day values from the source payload. Recurring revenue is in US dollars. Revenue per visitor is computed per company as monthly revenue divided by monthly visitors, and the median of those per-company values is reported. Where we report a population median we include companies reporting zero revenue; where we report a ladder median we do not, and each table caption states which.

Bands with fewer than 25 companies are labelled with their sample size in the table. Bands with fewer than 15 are published with an explicit directional warning and no conclusion is drawn from them alone. No figure on this page is an average, because the underlying distributions are skewed by three to four orders of magnitude.

Community quotes were captured from public founder subreddits during September 2026, filtered to an in-audience allowlist, and are attributed to the subreddit only. Usernames, post identifiers and any other identifying information are stripped. Review quotes are attributed to the review platform only, with reviewer names and identifiers removed.

Data sources and what each one cannot tell you

Coverage honesty

Three things we could not do, stated so the numbers are not over-read.

We cannot break traffic down by channel. That is the single most useful missing dimension on this page, and it means every statement about search is inference from the impressions field rather than direct measurement of search traffic.

We have no time series. Every number is one snapshot taken on one day. The age table is a comparison between cohorts, not a trajectory, and older cohorts differ from younger ones in ways other than age.

Our top band stops at $50,000 a month, because above it we have too few companies reporting traffic to publish a median we would stand behind. The ladder as published covers the range most independent software actually occupies, and says nothing about what happens above it.

Run this yourself

The whole analysis is four fields. If you have a warehouse, the recipe is: filter to products with both traffic and revenue above zero, band by monthly revenue, and take the per-company median of revenue divided by visitors inside each band. Do not take total revenue over total visitors, or the largest company in your set will write the answer. If you would rather start from documented demand than from your own analytics, mining reviews and complaints and the pain points database are the entry points.

If you do not have a warehouse, the same numbers are queryable through our research tools. The revenue intelligence tool exposes the underlying company records, the usage guidecovers the filters, and getting started is the five-minute version. For programmatic access, the MCP server setup and the revenue intelligence MCP tools put the same corpus inside Claude or Cursor.

A related question from the same corpus: if the yield on this product is hard to move, is starting another one the answer? We grouped 8,600+ startups by founder to find out indoes shipping more SaaS products make more money. Short version, the totals rise but the per-product odds fall from 43.6% to 23.1%.

Where BigIdeasDB fits

Everything on this page came out of one corpus and four fields, and the reason we could write it is that we already hold the join between what software earns and what it gets seen by. That join is the product. If you are choosing a category, the yield table is a better input than a keyword volume estimate, because it tells you what a visitor in that category is worth before you go earn any.

For the adjacent decisions: how small your MVP should bemeasures scope against revenue, what SaaS homepage headlines actually saymeasures the page that does the converting, and the growth levers founders never pulled measures what sellers admit they left on the table. If you are further along, how to sell your SaaS, valuation multiples and the state of SaaS acquisitions cover the exit side. And if you have not picked a product yet, start with micro SaaS ideas, the best micro SaaS ideas or our guide to finding SaaS ideas.

Frequently asked questions

How much traffic does a SaaS need to make money?

Across 740 revenue-verified SaaS companies, the median product earning under $100 a month gets about 280 monthly visitors, the median at $100 to $1,000 gets about 1,300, at $1,000 to $5,000 about 5,700, and at $10,000 to $50,000 about 10,800. Traffic rises about 39x across that ladder while revenue rises about 596x, so traffic is not what separates the bands.

What is a good revenue per visitor for a SaaS?

Median revenue per monthly visitor is about $0.08 below $100 MRR, $0.26 at $100 to $1,000, $0.47 at $1,000 to $5,000, $1.25 at $5,000 to $10,000 and $1.98 at $10,000 to $50,000. Including every product with measurable traffic, even those earning nothing, the median falls to roughly $0.03 to $0.06.

Can a SaaS have lots of traffic and no revenue?

Yes, and it is close to a coin flip. Of 1,457 products with measurable monthly traffic, 717 report no recurring revenue at all. 122 of them draw over 1,000 monthly visitors and still earn nothing, and 29 draw over 10,000.

How many visitors does it take to get one SaaS customer?

Among products reporting both traffic and a customer count, the median visitor-to-customer rate is 2.33%, which is roughly one customer per 43 monthly visitors. The sample is 45 companies and heavily biased toward products that already work, so treat it as an upper bound rather than a planning number.

Do Google search impressions predict SaaS revenue?

Weakly. A median of about 2,300 monthly impressions produces about 57 visitors, a 2.4% click-through. But 188 of the 350 products with measurable impressions earn no recurring revenue, including 34 that clear 10,000 monthly impressions. Impressions measure whether Google will show you, not whether anyone will pay you.

Is 1,000 visitors a month good for a SaaS?

It is roughly the median for a product earning $100 to $1,000 a month. Whether it is good depends entirely on your yield: 1,000 visitors is worth about $80 at the bottom-band rate and about $1,980 at the top-band rate. The visitor count alone carries almost no information.

Should I work on traffic or conversion first?

Divide last month’s recurring revenue by last month’s unique visitors. Below about $0.10 a visitor, work on yield, because more traffic multiplies a near-zero number. Above about $0.50, work on traffic, because the yield is already proven at a rate the top bands convert at.

Which SaaS category has the highest revenue per visitor?

Marketing tools, at a median of $0.51 per monthly visitor across 48 companies, followed by fintech at $0.39 and artificial intelligence at $0.32. The lowest are design tools at $0.06 and education at $0.12, both of which carry above-average traffic.

Why does my SaaS get signups but no paying customers?

Usually because the signup is free and the product has not yet created a moment where paying is the obvious next step. In our data the low-traffic band converts visitors to customers at 4.29%, the highest rate in the table, and still earns $21 a month, because the median customer pays $1.50. High signup conversion at a trivial price is not a funnel success.

Is B2B or B2C better for revenue per visitor?

B2B, by about 2x: $0.06 against $0.03 per visitor including zero-revenue products. B2B also gets about 26% less traffic and has the highest share of products earning nothing at all, 40.5%. Higher yield when it works, higher chance it never does.

How much traffic should a SaaS have in its first year?

The median first-year product with any measurable traffic has 196 monthly visitors and earns nothing per visitor, because 54.4% of first-year products with traffic report no revenue at all. A few hundred visitors and no revenue at eight months is the median outcome, not a failure signal.

Does revenue per visitor keep improving as a company ages?

Not after about year two. Median revenue per visitor is $0.000 in year one, $0.019 in years one to two, and $0.053 in years two to four, where it stops. The four-year-plus cohort holds the same $0.053 with less traffic. The first two years are the window where yield is actually movable.

Do faster-growing SaaS products have more traffic?

No, and the relationship inverts. Products growing 20% or more month over month have a median of 1,514 visitors and $0.130 per visitor, while products growing under 20% have 3,730 visitors and $0.432. That is a base effect: large percentage growth usually means a small denominator.

Does the payment processor affect revenue per visitor?

Not in any way we can separate from product age. Stripe products show $0.017 per visitor and the newer rails show $0.000, but newer rails are disproportionately chosen by newer products and newer products are the ones earning nothing. The rail is standing in for age, not causing anything.

How do I calculate revenue per visitor correctly?

Divide last month’s recurring revenue by last month’s unique visitors, not sessions or pageviews, and use a month with no launch spike in it. A single launch can inflate the denominator enough to move your result by an order of magnitude and make a healthy product look broken.

Is launch traffic worth anything?

Very little per visitor. One well-documented community example reports 415,000 views producing 1,100 users and 30 subscriptions, a 0.26% view-to-user rate, and that was one of the better outcomes posted. Launch traffic is useful for feedback and for the first few customers, and it is the worst possible basis for a benchmark.

Why is there no standard SaaS revenue-per-visitor benchmark?

Because traffic and revenue live in different systems and almost nobody joins them. Published benchmarks exist for ecommerce, roughly $0.30 to $2.00 per visitor, and several of the pages publishing those state explicitly that no B2B software equivalent exists. That join is exactly what our corpus holds, which is why we can publish the distribution.

Does more traffic ever fix a revenue problem?

Only when the yield is already proven. If your revenue per visitor is above about $0.50 you are converting at the rate the $5,000-plus bands convert at, and volume is the binding constraint. At zero, more traffic multiplies zero. The 29 companies in our data with over 10,000 monthly visitors and no revenue are the clearest evidence of that.

BigIdeasDB Research. (2026). How Much Traffic Does a SaaS Actually Need?. BigIdeasDB. Retrieved from https://bigideasdb.com/how-much-traffic-does-a-saas-need