How to Calculate the Total Addressable Market (TAM) for Your Open Source Startup
Build your TAM from your own community data and a sharp Ideal Customer Profile, unit by unit.
GitHub stars don’t pay the bills. Neither do fork counts or Docker pulls. They’re the best top-of-funnel signal a commercial open-source founder will ever get, and they tell you almost nothing about the size of the business you can build. Every credible go-to-market plan starts somewhere less flattering, with an honest count of the people who will actually open their wallets.
Total Addressable Market (TAM) is that count, expressed as a ceiling. It’s the revenue you’d book if you won every enterprise customer on earth who could buy your commercial offering, the theoretical top of your business rather than your project. Two things hang on the number. It sets the line you draw between the free tier and the paid one, and it’s the figure an investor uses to decide whether your model can return a venture-scale fund.
Most founders get TAM wrong in the same direction, upward. Your open-source database does not have a TAM of $100 billion just because that’s what the world spends on databases. That slide looks impressive until someone asks how close you are to displacing Oracle or AWS, and the answer is “not close.” A TAM built on total community downloads is a vanity number. It aims your sales budget at people who were never going to pay, and it drains the runway you raised to find the ones who would.
You run two funnels at once. The community funnel feeds on free downloads, stars, and developer goodwill. The commercial funnel feeds on enterprise features, managed cloud, and SLAs. Confusing the two is the original sin of COSS finance, and experienced investors smell it on contact, because claiming the entire database spend as your market is the same as admitting you can’t tell a free user from a buyer.
A tight definition does the opposite. It keeps your strategy anchored to the slice you can actually win, and it proves to a board that you did the arithmetic before you asked for the check.
The crowd at the door is not the market
Open source democratizes technology, which is the whole point and also the source of the confusion. Your software gets downloaded by students, hobbyists, weekend tinkerers, three-person startups, and the Fortune 50, all from the same release page. That produces an enormous pool of Total Addressable Users, basically every developer who could benefit from running your code for free. Your TAU dwarfs your TAM. Always.
Your TAM is the much smaller subset who work somewhere with the budget, the operational scale, and the specific pain that needs your paid offering. The crowd at the door isn’t the market. It’s the reason the market exists at all.
The classic mistake is multiplying total deployments by enterprise contract value. A hundred thousand active open-source deployments times a $50,000 enterprise tier looks like a $5 billion TAM, and it’s a mirage. Somewhere between 95 and 99 percent of those deployments will never send you a dollar, which is open source working exactly as designed. Your free users are your marketing engine and your QA department. They aren’t your buyers.
Getting to a real number means running those users through a brutal, realistic conversion filter.
Your pricing model decides your market
In traditional SaaS, TAM is close to a multiplication problem: companies that need the software times the subscription price. In COSS, the number swells or collapses depending on how you decide to charge for free code. Pick the vehicle before you run the math.
The support-and-services model is the Red Hat path. You give the software away and sell SLAs, training, and emergency patches. The customer base is wide, but contract values stay low, margins stay thin, and your ceiling is whatever companies will pay for insurance against their own infrastructure.
Open-core is the path Elastic and GitLab took. The core is free, and the enterprise features live behind a license: SSO, RBAC, compliance reporting, and high availability. Contract values climb, but the market narrows to mid-market and enterprise buyers with real security and compliance obligations. A ten-person startup never enters your TAM because nobody that small needs row-level access control.
Then there’s managed cloud, the MongoDB Atlas and Confluent path, which usually produces the largest and most defensible market of the three. You stop selling features and start selling uptime and the elimination of a DevOps payroll line. The market widens at both ends, small companies that lack the talent to self-host, and large ones that would rather hand off the operational burden than staff for it.
Whatever you pick, the TAM has to reflect its pricing and its limits, not a generic count of everyone who could install the thing.
Three ways to size it
You have three methods, and a COSS founder needs all three, because each one answers a different person in the room.
The analyst filter, from the top down
Top-down starts wide and narrows. You find a Gartner or Forrester line that reads “global enterprise spend on monitoring and observability is $15 billion a year,” and you carve it down.
A generic startup says “capture 5 percent and the TAM is $750 million” and stops there. A COSS founder keeps filtering. Start with the $15 billion. Strip out the spend locked into legacy proprietary mainframes that will never touch open infrastructure; if 40 percent of the market is actively modernizing, you’re down to $6.0 billion. Then ask how much of that $6.0 billion belongs to organizations willing to pay a vendor for managed open source rather than running it themselves. Call it 30 percent, and the top-down number lands at $1.8 billion.
This view is fast and imprecise by construction. It rests on broad assumptions about how a whole market behaves, which makes it useful for a sanity check or a macro vision and dangerous as a sales quota. Use it to prove the market is real. Don’t let anyone on your team carry it into a forecast.
The open-source funnel, from the bottom up
Bottom-up is the method that wins Series A rooms. You build the number from your own community data and a sharp Ideal Customer Profile, unit by unit, and the act of building it proves you know exactly who buys and what they pay.
The equation is a chain of filters:
TAM = (target organizations) × (share with the specific pain) × (COSS conversion rate) × (average contract value)
Walk it with real numbers. If your tool requires Kubernetes, your universe is companies running Kubernetes in production, say 50,000 mid-market and enterprise accounts worldwide. Now the pain filter. Your commercial product does multi-region replication, which only matters to companies large enough to need multi-region setups, so 20 percent qualify and the pool drops to 10,000. Then the conversion rate, which is the number that actually governs your business. Of the companies that need the technology, how many pay rather than self-host the free build? Successful open-core conversion runs 2 to 5 percent of the active base. Be aggressive, take 5 percent of these highly qualified orgs, and you get 500 paying customers. Price the managed enterprise cloud at a $50,000 ACV from early pilots or competitor benchmarks, and the chain closes:
10,000 qualified orgs × 5% conversion × $50,000 ACV = $25,000,000.
A $25 million beachhead sounds small to a founder dreaming in unicorns. It’s far more persuasive to a Series A partner than a fabricated $10 billion top-down claim, because it shows you know how to land your first 500 logos. Expansion comes later, when you add features, open new regions, or drop a self-serve tier that lowers the floor.
Value theory for the market that has no report yet
Value theory earns its keep when you’re creating a category, replacing a legacy giant, or solving a problem in a way nobody has named. Instead of carving up existing software spend, you price the problem itself. In open source, the problem usually gets measured in reclaimed engineering hours and infrastructure you no longer have to run.
The question to ask: if an enterprise adopts our managed open-source cloud, what’s the dollar value of the DevOps salaries, the downtime, and the legacy licenses they delete?
Picture a next-generation open-source vector database for AI workloads. No analyst tracks “vector database spend” yet, so you reason from value. Companies shipping AI features pay specialized engineers roughly $200,000 a year to hand-build data pipelines on databases that were never meant for the job. Your managed cloud removes half that custom work, saving $100,000 a year. Because you’re handing the customer $100,000 in hard value, a $30,000 ACV is easy to defend; it leaves $70,000 in their pocket. Estimate 15,000 companies actively deploying generative AI in your target regions, and the math is:
15,000 companies × $30,000 ACV = $450 million.
Value-based TAM is speculative, and without strong case studies it’s hard to hold under questioning. For founders leading a genuine shift, it’s often the only honest way to size an uncharted market. Be ready to defend, line by line, what a DevOps engineer’s time is worth to a CFO who would rather not believe you.
When the hyperscaler forks you
Every COSS pitch reaches the same question, and you should want it asked early. What happens when AWS, GCP, or Azure forks your project and runs it as a managed service? Does your TAM go to zero?
This is the recurring fear of commercial open source, and it isn’t paranoid. A hyperscaler that wraps your free code in its billing console can, in theory, take the entire managed-cloud market you just sized. It has happened. When Elastic relicensed Elasticsearch under the SSPL in 2021, AWS forked the last open version and shipped it as OpenSearch, billing console and all. A credible TAM doesn’t pretend the threat away. It shows the moat in the numbers.
Licensing is the first wall. A Business Source License or SSPL legally blocks the hyperscalers from offering your software as a competing managed service. It protects the market, and it costs you goodwill with the open-source purists, so price that trade deliberately. The second wall is the enterprise delta. Your commercial TAM has to rest on features the open-source core doesn’t carry. AWS can fork the core and still lack your control plane, your advanced security modules, your specialized console, which means your market is defended by the parts you never gave away. The third wall is multi-cloud. Enterprises are afraid of AWS lock-in, and a managed service that runs cleanly across AWS, Azure, and GCP holds customers an Amazon-only fork can only trap.
A strong presentation names the hyperscaler threat out loud, then shows the arithmetic for why a buyer pays the people who built the project instead of the cloud renting it back to them.
An example, sized two ways
Say you’re building MeshFlow, an ultra-lightweight open-source service mesh aimed at mid-sized companies on Kubernetes.
The top-down pitch sells the vision. Global enterprise spend on cloud infrastructure software hits $120 billion next year; networking and security are roughly 10 percent of it; the macro TAM is $12 billion.
The bottom-up pitch sells the execution, and it’s where the company actually lives. Fortune 50 banks are entrenched with legacy gear and heavyweight tools like Istio, so you skip them. Your sweet spot is the mid-market, companies with 100 to 1,000 engineers who need simplicity more than they need knobs. Tech-stack scraping turns up 30,000 mid-sized SaaS and tech companies on Kubernetes worldwide. About 30 percent of them, 9,000 orgs, have hit the microservices complexity where a mesh stops being optional. Your own telemetry shows 10 percent of those, 900 orgs, are already running the free build. MeshFlow Cloud manages the control plane for $25,000 a year:
9,000 target orgs × $25,000 ACV = $225 million beachhead.
In the room, you say both numbers in one breath:
“Our beachhead TAM is $225 million: 9,000 mid-market Kubernetes shops that need a simplified service mesh at a $25k ACV, and we already have open-source deployments inside 10 percent of those accounts, which is a warm pipeline our sales team can work today. As we ship multi-cluster compliance and move upmarket, we have a clear line into the broader $12 billion cloud-native networking market.”
That tells a coherent story. It separates the macro-market you can imagine from the developer segment you can win this year, and it shows you know the difference cold.
Open source builds the market it later sells to
The COSS model does something proprietary software can’t. It doesn’t just take a share of an existing market, it grows a new one. Enterprise software is expensive, gated behind a sales call, and a chore to trial. Open-sourcing the core drops the barrier to zero, and a developer who could never get a $100k legacy license approved pulls your tool down in seconds.
Those developers carry your software into industries, geographies, and company sizes the legacy vendors never bothered to address. The small accounts grow. Their usage scales. Some convert into paying customers for your commercial tier, and they arrive already knowing the product, having run it for a year before anyone signed anything.
When you present TAM, claim that effect explicitly. Open source is a wedge that keeps widening the borders of your market by raising buyers the top-down B2B playbook would have ignored.
A small market can be the whole point
Founders panic that a small TAM sinks the raise. Investors do love big markets. They love fast, efficient, dominant businesses more, and in open source a tightly drawn market is often the asset rather than the liability. Developers distrust the generic all-in-one platform. They adopt the opinionated tool that solves one acute pain perfectly, and they adopt it hard.
Take an open-source tool built only to manage compliance configurations for FinTech startups running Terraform. Maybe 2,000 well-funded startups on earth fit the profile. In raw dollars the TAM looks like a rounding error. But the pain is severe and regulatory, so adoption inside that niche is fast and loyal, and the community standardizes on your tool because there’s no second choice worth evaluating. Conversion to your commercial compliance-auditing cloud runs far above the open-core norm, maybe 20 percent instead of 5, and the contracts are large and long because a failed audit costs millions:
2,000 orgs × 20% conversion × $75,000 ACV = $30 million in defensible, high-margin revenue.
That’s stable revenue and enviable net revenue retention, earned while you own the mindshare of an entire industry. Investors who know open source recognize the shape. Winning is far easier when your roadmap is laser-focused and you’re not out-marketing 50 generic competitors at once. The best open-source VCs say a version of the same thing: better to own 100 percent of the mindshare in a critical niche than to be the tenth proprietary option in a loud, crowded one.
Domination doesn’t stay contained, either. The community pulls your product into adjacent markets on its own. Developers change jobs and bring your tool from FinTech into Healthcare, and the TAM expands organically while you sleep. The niche was the tip of the spear, never the ceiling.
What to actually do with the number
Know your numbers. Separate the free crowd from the paying buyers. Be honest with yourself about where your monetization model stops, even when honesty shrinks the slide.
Build the TAM bottom-up on assumptions you can defend one at a time and hold the number in its proper place: not a promise of revenue, but a direction for your focus. A TAM done right tells your team and your investors the same thing about you. You have the operational maturity to turn a popular repository into a business, and you already know which 500 customers come first.