Market Sizing For Niche SaaS

Reviewed by Fallon Han· Updated 2026-06-01 06:05:33.032

This conversation was generated using Cook'd AI's career assistant and reviewed by Fallon Han from our editorial team for accuracy.

I want a worked example for market sizing a niche SaaS segment, but with the kind of layered thinking I can defend in a consulting interview. Can you walk me through how to break it down and what assumptions I should be ready to justify if the interviewer pushes back?

Absolutely. Let us use a specific example: a SaaS tool for invoice reconciliation sold to mid-sized e-commerce companies in India. The clean way to size it is to break it into layers: 1. Define the customer segment clearly 2. Estimate how many such companies exist 3. Estimate what share would buy the product 4. Estimate annual spend per customer 5. Multiply and sanity-check A simple structure could look like this: TAM = number of target firms x adoption rate x annual software spend per firm For example: - Mid-sized e-commerce firms in India: maybe 10,000 - Share with enough complexity to need this tool: 30 percent - Likely buyers in the next few years: 20 percent - Annual spend per firm: Rs 3 lakh That gives 10,000 x 0.3 x 0.2 x 3,00,000 = Rs 180 crore. The key is not the exact number. It is showing that each layer is logically defensible. If pushed, you should be able to explain why you excluded very small firms, why not every eligible firm adopts, and why the pricing is tied to the value created, like reduced errors and time saved.

That makes sense, but if the interviewer asks how I got to 10,000 firms, I do not want it to sound made up. How do I defend the market definition and avoid sounding like I am just guessing from the top down?

Good instinct. You want to show that the 10,000 is a reasoned estimate, not a random guess. A strong answer is to define the market from the bottom up using observable proxies: - Start with all e-commerce businesses in India - Filter to mid-sized ones with enough transaction volume to need reconciliation software - Exclude very small sellers who can use spreadsheets - Exclude very large enterprises if the product is not built for them You can say something like: "I would estimate the market by starting with the total number of e-commerce businesses, then narrowing by size and complexity. For example, if there are roughly 50,000 e-commerce firms overall, and about 20 percent are mid-sized enough to have recurring reconciliation pain, that gives 10,000." If challenged, be ready to explain the proxy behind each filter: - Revenue threshold - Monthly order volume - Number of payment channels - Need for accounting integration This sounds much stronger than saying, "I think there are 10,000 companies." In consulting, the interviewer usually cares more about whether your segmentation logic is clean than whether your base data is perfect.

Okay, but how do I choose the adoption rate and annual spend without overcomplicating it? I worry I will either understate it or use too many assumptions and lose the plot.

Keep both assumptions simple and tied to business logic. For adoption rate, think in layers: - Not every eligible firm is aware of the product - Not every aware firm has budget or urgency - Not every willing firm will convert in the relevant time frame So instead of one big uncertain number, you can frame it as a funnel. For example: - 60 percent are aware - 50 percent of aware firms feel enough pain - 70 percent of those actually buy That implies about 21 percent adoption, which you can round to 20 percent. For annual spend, anchor it to the value delivered or comparable software costs. - If the product saves one operations analyst per month, that may be worth Rs 1 lakh to Rs 2 lakh annually - If it also reduces errors and improves cash flow visibility, maybe the value is higher - A price of Rs 3 lakh a year is plausible if the software is mission-critical The interviewer may ask why not Rs 50,000 or Rs 10 lakh. Your defense should be value-based: - Below Rs 50,000, the product may be too cheap to fund support and integration - At Rs 10 lakh, many mid-sized firms may not see enough ROI unless the product is deeply embedded So choose a range, then land on a midpoint. That shows judgment rather than false precision.

Can you show me how to sanity-check the final estimate so I do not just multiply a bunch of assumptions and end up with a number that feels arbitrary?

Yes. Sanity-checking is what makes the estimate credible. Use three checks: 1. Compare to market logic If your estimate implies that each customer pays more than a large enterprise software budget, it may be too high for this segment. 2. Compare to operational reality Ask whether the number of customers times spend implies a sales motion the market can actually support. For example, Rs 180 crore across 2,000 customers means about Rs 9 lakh total per customer if you are only selling to a tiny subset, which may be too rich for mid-sized firms. 3. Compare to adjacent products If accounting or workflow SaaS in the same segment sells for Rs 1 lakh to Rs 5 lakh annually, then Rs 3 lakh is plausible. A neat way to present this in an interview is: "My estimate is Rs 180 crore, but I would sanity-check it against customer willingness to pay and comparable SaaS pricing. If the number looks too high, I would revisit either the adoption assumption or the spend per customer before changing the market definition." That last part matters. It shows you know which assumption to stress first, rather than randomly tweaking everything.

What if the interviewer challenges my assumption stack and says I am being too generous on both adoption and pricing? How do I respond without getting defensive?

Respond by showing trade-offs, not defensiveness. You can say: "That is fair. If I lower adoption, I may need to justify a higher spend per customer because only the firms with the strongest pain would buy. If I lower pricing too much, the product may not be economically viable. So I would treat these as linked assumptions and test them together." Then offer a downside case: - Adoption drops from 20 percent to 10 percent - Annual spend drops from Rs 3 lakh to Rs 2 lakh - Market size falls from Rs 180 crore to Rs 60 crore That tells the interviewer you are not attached to one answer. You are showing a range and explaining what drives the range. A strong consulting-style move is to say: "If you want, I can also test an optimistic and conservative case to show whether the segment is attractive even under pressure." That keeps the conversation collaborative and makes you sound structured under pushback.