Estimating a competitor's MRR is not about finding the exact number. It is about understanding the order of magnitude: does this product make hundreds, thousands, or tens of thousands of dollars a month? That single fact changes everything about whether you enter a niche.
When you know competitors are earning well, perceived risk drops. When you discover nobody in the niche seems to have recurring revenue, that is a warning worth heeding. Either way, estimating MRR replaces gut feel with parameters.
This guide covers practical methods for estimating a competitor's revenue using only public data. No method is fully accurate, but combining several usually produces an estimate good enough to decide whether building is worth it.
Why estimating competitor MRR matters
MRR (Monthly Recurring Revenue) is the most important metric in SaaS. It shows whether a product has recurring revenue, whether it is growing, and how large the market opportunity is.
For a Micro SaaS builder, estimating competitor MRR answers questions that actually change decisions:
Is there money circulating in this niche?
Is the average price compatible with what I want to charge?
Can a small product capture a meaningful slice of this market?
Does the competitor rely on volume (many cheap customers) or on high ticket size?
Is there room for a new entrant, or is the market already consolidated?
Without those answers you can spend months building for a niche where nobody pays, or where the ticket is too small to justify the cost of acquiring anyone.
Method 1: Public pricing as your anchor
The simplest method starts with price. If a competitor publishes pricing, you already have an anchor.
The answer depends less on the market than on you: capital, risk tolerance, revenue ambition, and appetite for managing people. Eight criteria compared.
A data "começou a veicular em" mostra quando o anúncio entrou no ar — e é um dos sinais mais úteis da Biblioteca de Anúncios. Entenda o que ela revela, o que ela esconde e como usá-la para ler concorrentes.
Write down every plan and price.
Identify which plan appears to be the most popular (visual emphasis, "most popular", recommended).
Estimate a simple distribution: for example, 60% on the middle plan, 25% on the entry plan, 15% on the top plan.
If a SaaS has plans at $19, $49, and $99, and you estimate 200 paying customers, the math works out to:
120 customers x $49 = $5,880
50 customers x $19 = $950
30 customers x $99 = $2,970
Estimated MRR: roughly $9,800
But how do you estimate the customer count? That is what the next methods are for.
Method 2: Reviews as a proxy for customer base
Platforms like G2, Capterra, Product Hunt, and the Chrome Web Store publish review counts. Reviews are an imperfect but useful proxy for the size of a user base.
Typical review rates in SaaS:
B2B enterprise: 1 review per 50 to 100 customers.
B2B SMB: 1 review per 20 to 50 customers.
B2C or productivity: 1 review per 100 to 500 users.
Example: if a B2B SaaS aimed at small businesses has 80 reviews on G2, a reasonable customer estimate falls between 1,600 and 4,000.
Combine that with your estimated average price and you have an MRR range.
Method 3: Headcount on LinkedIn
LinkedIn is an underrated competitive intelligence source. Employee count, especially across product, engineering, sales, and customer success, tells you a lot about the size of the operation.
Rough relationships:
SaaS with 3 to 10 employees: MRR likely between $10k and $60k.
SaaS with 10 to 30 employees: MRR likely between $60k and $300k.
SaaS with 30 to 100 employees: MRR likely above $300k.
These bands vary heavily by segment and country. A team operating in a lower-cost region can run on a smaller MRR than a US-based team of the same headcount.
Pay attention to team composition as well:
Dedicated salespeople usually mean a higher ticket.
A CS team usually means active retention work.
Engineers only can mean an early-stage product, or a heavily automated one.
A marketing team usually means they are investing in growth.
Method 4: Active ad signals
Companies that advertise consistently generally have an LTV (Lifetime Value) high enough to justify their CAC (Customer Acquisition Cost). That is an indirect signal of healthy revenue.
What to look at:
Number of active ads per channel.
Campaign duration (ads that survive weeks or months).
Creative diversity (testing indicates budget).
Channel used (Google Ads suggests captured intent; Meta Ads suggests demand creation).
If a competitor runs dozens of ads across Meta and Google simultaneously, they are almost certainly not doing it on $2k of MRR. Media spend has to be paid for by recurring revenue.
Tools like Similarweb, Ahrefs, and SEMrush estimate a site's organic and paid traffic. The estimates carry real margin of error, but they show direction.
If estimated traffic grows month over month, the SaaS probably is too. Flat or declining traffic can signal stagnation.
Pair that with conservative conversion rates:
B2B SaaS with a trial: 1% to 3% visitor-to-customer conversion.
Freemium SaaS: 2% to 5% free-to-paid conversion.
SaaS with direct checkout: 0.5% to 2% conversion.
Example: a SaaS gets 50,000 visits a month, offers a free trial, and converts 1.5% of visitors. That is 750 new customers a month. At an average price of $29, new monthly MRR would be around $21,750, on top of whatever accumulated from prior months.
Method 6: The right tool speeds all of this up
Running each of these analyses by hand across several competitors takes hours. That is why competitive intelligence tools like Noctral exist.
Noctral centralizes signals you would otherwise chase across a dozen tabs:
A SaaS database with MRR estimates.
Growth signals by category.
Active ads per product and channel.
Side-by-side competitor comparison.
Continuous opportunity monitoring.
Instead of estimating MRR in a spreadsheet, you start from organized data and dig deeper only on the cases that actually matter.
If you want to run the math on your own numbers, the MRR and ARR calculator handles the projection side.
Using estimates responsibly
MRR estimates are never exact. Treat them as magnitude parameters, not as facts.
Good practice:
Use a range, not a single number. For example: "MRR between $15k and $40k".
Combine at least three different methods.
Revisit estimates quarterly.
Compare competitors against each other rather than in isolation.
Prioritize trends over point-in-time numbers.
If three competitors in the same niche estimate out to between $10k and $25k in MRR, you have a signal that the market supports products of that size. If all of them sit below $2k, the niche may be too small to justify a new entrant.
Estimating competitor MRR is not about getting the number right. It is about reducing uncertainty. With public pricing, review counts, LinkedIn signals, active ads, and competitive intelligence tooling, you can build a realistic view of how large the opportunity is.
Noctral exists to make that work faster. Instead of losing hours scraping data by hand, you research in a structured way and decide with more context. Building in the dark is expensive. Building with data is strategy.
Frequently asked questions
Can you find a competitor's exact MRR?
No, unless the company publishes it (open startups do). What you can do is estimate within a useful margin: cross-reference public pricing, visible customer counts (reviews, case studies, counters), traffic, and paid acquisition signals.
Which signal is most reliable for estimating revenue?
None on its own — the strength comes from combining them. Review counts (G2, Capterra) plus pricing give you a floor; traffic and active ads help calibrate the ceiling. Treat the output as a range, never as an exact figure.
Why estimate competitor MRR at all?
To size the opportunity before entering. A niche where small players sustain $10k-25k in MRR can support one more. A niche where nobody clears $2k probably will not pay for the effort. See also how much SaaS companies make.
How often should you redo the estimates?
Quarterly for direct competitors, or whenever a strong signal changes (new pricing, a wave of ads, a hiring push). The signs a Micro SaaS is growing tell you when it is time to reassess.
