How to Estimate the Market Size: A Practical Playbook

You've probably been in this meeting.

Someone asks for the market size for your new AI service. Maybe it's an investor. Maybe it's a board member. Maybe it's the sales lead trying to understand whether the pipeline target is realistic. You put a big number on a slide, and five minutes later the room starts pulling it apart.

That usually happens because the number was built to impress, not to survive scrutiny.

When people search for how to estimate the market size, they often find advice built for consumer products or broad software categories. That guidance is useful, but B2B services, especially AI and data consulting, need a different level of discipline. You're not counting units on a shelf. You're estimating demand for projects, retainers, workshops, strategy work, automation rollouts, and outcome-driven engagements that vary by buyer maturity, budget structure, and delivery model.

A useful market size estimate does one job well. It helps you make decisions with defensible assumptions, not wishful thinking.

Why Market Sizing Is More Than Just a Number

A weak market size number creates problems fast. It pushes founders to chase the wrong segment, makes sales targets look achievable when they aren't, and gives delivery teams a distorted picture of future demand.

A credible number does the opposite. It tells you where to focus, what kind of clients to prioritize, and how much revenue your current model can realistically support. That's why market sizing belongs in strategy discussions, not just fundraising decks.

What stakeholders are really asking

When someone asks for your market size, they usually aren't asking for a giant industry number. They're asking a bundle of more practical questions:

• Is the problem widespread enough to justify building a dedicated offer?

• Can this team reach buyers in the segment it claims to serve?

• Will the revenue model hold up once you move from a few deals to a repeatable motion?

• Are the assumptions conservative enough that leadership can plan around them?

That's why generic research rarely gets you all the way there. In B2B, you need real segmentation, realistic contract values, and a sober view of who is able to buy.

For teams that are still gathering buyer evidence, outside support can help. A practical starting point is conducting business to business market research in a way that validates demand before anyone locks in a revenue plan.

Practical rule: If your market size can't be traced back to a buyer type, a delivery model, and a pricing assumption, it's not strategy. It's decoration.

Why this matters inside the business

The biggest benefit of market sizing is internal alignment. It forces product, sales, operations, and leadership to use the same definitions.

One team may say “mid-market manufacturers,” while another is thinking “any company with an operations problem.” Those aren't the same market. A sizing exercise forces that ambiguity out into the open.

It also improves planning quality. When teams use structured estimates instead of broad optimism, resource allocation gets sharper. Hiring plans, offer design, and sales coverage become more grounded. That's the same discipline behind stronger data-driven decision-making, where assumptions are explicit and testable instead of buried in intuition.

The TAM SAM SOM Framework Explained

The standard language for market sizing is TAM, SAM, and SOM. It works because it separates the total opportunity from the opportunity you can pursue.

That framework has become a standard way to build investor confidence because it replaces vague ambition with a more structured view of revenue potential.

TAM is the full universe

For an AI consulting business, TAM is the full demand for the category you serve. If your offer is AI-powered process automation for logistics companies, TAM is not “all companies that use software.” It's the full set of organizations that could plausibly buy that kind of solution.

Teams often get lazy at this stage. They define the category too broadly, then pretend the broad category is meaningful.

A better way is to tie TAM to an identifiable buyer group and a pricing logic. If you're selling strategic AI roadmaps, your TAM should be based on the total potential customers and the revenue per customer model that fits that service.

SAM is the market you can actually serve

SAM narrows the universe. You apply the actual constraints of your business here.

Those constraints usually include:

• Geography if your delivery team only operates in certain regions

• Service scope if you only handle strategy, or only implementation

• Industry fit if your references and expertise are concentrated in a few verticals

• Buyer maturity if your service only works for companies with data infrastructure already in place

This is also where an ICP matters. If you haven't defined one clearly, the filtering logic gets sloppy. A useful reference is this software agency ideal customer profile guide, because good market sizing depends on a tighter customer definition than many organizations initially employ.

TAM tells you the market exists. SAM tells you whether your business model fits inside it.

A short explainer can help if your team is new to the vocabulary:

SOM is the number that matters most

SOM is the near-term target. It's the share you can realistically win based on your current offer, team capacity, market access, and sales motion.

This is the number I care about most in practice. TAM is useful context. SAM is necessary filtering. SOM is where strategy becomes operational.

For B2B services, SOM should reflect things like sales cycle friction, implementation complexity, referral strength, delivery bandwidth, and whether buyers need education before they can even purchase. If those realities aren't in the model, the estimate will look clean and fail in execution.

Starting Broad with Top-Down Market Sizing

Top-down sizing is the fast way to get oriented. You start with the broadest market level, then narrow it using filters that match your offer.

The same source notes that the U.S. Small Business Administration emphasizes five critical dimensions for effective market research: demand, market size, economic indicators, location, and market saturation.

When top-down is useful

Top-down is good for early framing. If you're exploring a new service line, you need a quick sense of whether you're looking at a niche with enough room to matter.

It's also useful when you want to compare adjacent opportunities. For example, an AI consultancy might compare process automation in logistics, forecasting in retail, and document intelligence in insurance. A top-down pass can show where the broader spending pools and market conditions look more attractive.

Where top-down goes wrong

The problem is that each filter introduces assumption risk.

A team might start with a large category, then successively trim it by industry, geography, and use case relevance. By the end, the final number looks precise. But the precision is mostly cosmetic if the filters were guessed.

Here are the common failure points:

• The starting category is too broad. “Digital transformation” is not the same as demand for your specific AI service.

• The fit percentage is arbitrary. Teams often pick a neat fraction because it feels reasonable.

• The model ignores delivery constraints. A market may exist, but your current team may not be able to serve it.

• Competitive saturation is underplayed. A reachable market isn't automatically winnable.

Use top-down analysis to frame the conversation. Don't use it as the final number you expect buyers, investors, or leadership to trust.

What works better

The best use of top-down sizing is as a ceiling and a reasonableness check. It gives you context. It doesn't give you a plan.

If your top-down estimate says the opportunity is large, that's interesting. If your bottom-up estimate says the near-term obtainable slice is far smaller, trust the bottom-up number. In service businesses, broad market visibility doesn't automatically translate into contracts.

Building a Defensible Case with Bottom-Up Analysis

Bottom-up sizing is where the fundamental work happens. Instead of starting with a large category and shrinking it, you start with actual target accounts, realistic deal values, and a sober estimate of what your team can win.

For B2B AI services, this is usually the strongest method because it matches how revenue is created. You don't win a percentage of a vague global market. You win named accounts, in specific segments, at a certain contract value, with a certain delivery capacity.

The basic formula that keeps you honest

A widely used standard formula is Total Potential Customers × Average Revenue Per Customer = Market Size, as described in this market size methodology overview. The same source also notes that revenue-per-customer decomposition is more credible when you validate assumptions through customer feedback loops, pilot work, and competitive benchmarking.

For B2B AI solutions, Wall Street Prep's market sizing explanation is especially useful because it pushes teams to model distinct ACV scenarios instead of treating every buyer as identical. It gives examples such as enterprise clients at $150K-500K annually and mid-market clients at $30K-100K, with segment-specific penetration assumptions such as 15% versus 25% to derive a more realistic SOM.

That framing matters because an AI strategy engagement for a large enterprise is not the same product, sales motion, or commercial opportunity as a scoped automation project for a mid-market company.

A practical workflow

Here's the workflow I'd use for an AI consulting offer.

• Starting point: Top-Down Analysis: Broad industry category; Bottom-Up Analysis: Named target accounts or tightly defined segments

• Speed: Top-Down Analysis: Faster; Bottom-Up Analysis: Slower

• Precision: Top-Down Analysis: Lower; Bottom-Up Analysis: Higher

• Best use: Top-Down Analysis: Early framing; Bottom-Up Analysis: Investment decisions and revenue planning

• Main risk: Top-Down Analysis: Assumption stacking; Bottom-Up Analysis: Incomplete account data

• Credibility with operators: Top-Down Analysis: Limited; Bottom-Up Analysis: Stronger

Then build your bottom-up model in steps:

1. Define the segment clearly
   Don't say “retail.” Say “mid-market e-commerce brands with recurring demand forecasting pain and an internal ops or data lead.”

2. Build an account list
   Use LinkedIn Sales Navigator, industry associations, conference attendee lists, directories, CRM history, and partner ecosystems. The output should be countable, not conceptual.

3. Split accounts by commercial profile
   Some buyers fit a workshop-led entry offer. Others fit a larger roadmap or implementation engagement. Don't force one ACV across the whole segment.

4. Assign realistic revenue per customer
   Base this on your actual packaging and pricing. If you're still testing offers, use a conservative range and document why.

5. Apply a realistic obtainable share Use this step to account for sales capacity, credibility, competition, and delivery bandwidth.

Operator's check: If your team can't explain where the customer count came from and why the contract value is plausible, the model isn't ready.

Where to find the inputs

Good bottom-up work doesn't need exotic data. It needs disciplined sourcing.

Useful inputs often come from:

• Your CRM for actual win rates, sales cycles, and deal sizes

• Proposal history to see which offers convert and which stall

• Public pricing signals from adjacent consultancies and implementation firms

• Vertical tools and marketplaces that reveal merchant or vendor populations

• Operational datasets tied to the niche you serve

If you work with e-commerce clients, for example, marketplace and operations data can sharpen your segmentation. Teams doing commerce-related targeting may find value in piping Amazon Seller Central data in Google Sheets to support faster account classification and opportunity mapping.

A strong sizing model also improves adjacent planning work like sales forecasting techniques, because it forces pipeline assumptions to reflect a defined market instead of an abstract growth target.

Common Market Sizing Pitfalls to Avoid

Most bad market size estimates fail for predictable reasons. The spreadsheet looks polished. The logic doesn't survive questions.

The biggest trap in AI services is using a standard customer-count formula without adjusting for the kind of value you sell.

Businesses need a way to translate current operational costs and inefficiencies into a market size estimate that justifies AI investment.

Trap one, confusing TAM with target market

A team finds a huge market category and starts speaking as if that entire demand pool is in play.

The fix is simple. Keep TAM in the model, but don't confuse it with sales reality. Your operating target should be a tightly defined subset that matches your current offer and reach.

Trap two, treating all buyers as identical

This happens constantly in consulting and AI services. Teams use one average contract value across startups, mid-market firms, and enterprises.

That usually hides important differences in scope, procurement friction, and implementation needs. Separate the segments. If necessary, use fewer segments, but make them real.

Trap three, using optimistic penetration with no evidence

A neat obtainable share can make the model look attractive. It can also wreck credibility if there's no logic behind it.

Good penetration assumptions should reflect your actual go-to-market motion. Consider channel access, proof points, delivery capacity, and how much buyer education the sale requires.

If a buyer needs to change process, budget, and internal ownership before they can buy, your obtainable market is smaller than your spreadsheet wants it to be.

Trap four, ignoring value-based economics

This is the issue that matters most for AI automation and process improvement work. Buyers often don't purchase because they want “AI.” They purchase because they want lower manual effort, fewer errors, faster throughput, or better decisions.

If your pricing is tied to efficiency or outcomes, market sizing should also reflect that logic. Start from the operational pain. Estimate where waste, delay, or repetitive labor exists. Then translate that into what buyers might justify spending to reduce it.

That approach won't always yield a neat industry-wide number. It will often produce a far more believable one.

Future-Proofing Your Estimates with AI and Analytics

A market size model for AI services can go stale quickly. New capabilities appear, buyer expectations shift, and categories blur together. A static spreadsheet built once a year won't keep up.

That's why I treat market sizing as a living model. It needs periodic updates, scenario ranges, and signals from the field.

Build scenarios, not a single answer

One of the clearest gaps in conventional guidance is how little it says about unstable categories. As noted in Pear VC's market sizing guide, traditional long-range projections are often flawed in fast-moving AI markets because definitions can shift within months, making earlier data outdated by later execution periods. The better approach is scenario-based sizing that accounts for compressed technology windows.

That means keeping at least a conservative case, an expected case, and a more ambitious case in view. It also means revisiting assumptions when tooling, regulation, or buyer readiness changes.

Use analytics as an updating mechanism

AI and analytics help most when they improve refresh speed.

That can include:

• Tracking competitor packaging and messaging to spot category shifts

• Monitoring your own pipeline by segment to identify where demand is strengthening or softening

• Reviewing pilot and proposal outcomes so your obtainable market reflects current evidence, not last quarter's story

The strategic value is simple. You stop treating market size as a slide for approval and start using it as an operating instrument. That's especially important for firms building practical, business-centric AI, where the commercial opportunity depends on real workflow adoption, not just technical possibility.

---

At NILG.AI, we help companies turn ideas like these into practical, measurable results with AI and data. If you want to explore how this applies to your business, get in touch with our team.