Given how much topic annoys me, it’s surprising that I haven’t written about it before.
As managing director of Dreamit UrbanTech, I see well over a thousand (if not 2000) pitch decks a year. Now that we work with more mature, pre-Series A round startups, most of our applicants have already raised a seed round and may have even gone through other accelerators, so it’s more than a little bit surprising to me that somewhere between 10-20% of those applicants still have unnecessarily complicated Market Size slides.
Here’s an example of what I mean:
Yeah, you’ve seen it before too. Looks kind of impressive, doesn’t it?
Unfortunately, here’s what I see:
Let me break this down for you you:
Total US Construction – The startup sells software. Why do I care about money spent on concrete, labor, etc.? That’s no more relevant to this startup than Dim Sum sales in Moscow.
Contractor Software Spend – They sell software to subcontractors. If a general contractor is spending $50K or $100K a year on Procore, why does that matter? Those GCs have no use for this startup’s product, will never use it, and will certainly not be spending any of their money on it. Might as well toss in revenue from video game sales for all that has to do with this market.
Subcontractor Software Spend – Right type of product, right customers – now we’re getting somewhere. Probably still a top-down estimate but at least this is less obviously wrong.
Top down is for convertibles, not pitch decks
Let me let let you in on a secret: top-down market size estimates are almost always incorrect and generally useless to an investor.
Why are they almost always incorrect? Because they typically capture a lot of related spending on different types of tools. In the example above, the figure includes spending on other construction related software, not to mention more general purpose software like Microsoft Office and Quickbooks. Furthermore, the top-down approach ignores pricing. Let’s say, hypothetically, that you make software that replaces absolutely everything the subcontractor might possibly buy but do it at a tenth of the price. By definition, your market is 90% smaller than the top down estimate suggests. Alternatively, say you provide a solution that’s much more functional and valuable than anything on the market and expect to price at a premium to existing software. In that case, the top down market size estimate understates your potential.
The more accurate and useful way to estimate your market is bottoms-up. It’s really not that complicated. At the end of the day, it is simple third-grade math: Total number of potential customers times what you plan to charge. Really, it’s that simple.
So that’s what an appendix is for…
I called top-down estimates “generally useless” instead of simply “useless” for a reason. They occasionally are a useful appendix slide as a sanity check. If you are creating a completely new product category and your bottoms-up market size estimates are large, it’s good to know the size of the total budget you are competing for. For instance, if your bottoms-up estimate comes to $100B and the software spend for the entire construction industry is $130B, you are essentially arguing that your customers will either stop buying 77% of all the software they currently use to buy yours or that they will manage to steal budget from other departments. Not entirely impossible, but extraordinary claims require extraordinary proofs. Needless to say, you’ll get a lot less pushback if your bottoms-up estimate came to ‘just’ $10B out of $130B.
Who’s on first?
As simple as the above TAM equation is, it still has two variables: number of customers and price. So if you haven’t told me what you charge, the equation isn’t going to make much sense. You need to define the price variable before adding the number of customers into the mix. That’s why your Revenue Model slide should almost always immediately precede the Market Size slide.
In some cases your Revenue Model may be a bit complicated. Your price may increase based on usage (e.g., number of seats or concurrent users), frequency (e.g., API calls, reports or searches per month), or value received (e.g., which modules they subscribe to). Your Revenue Model slide should include this detail at a high level but should also clearly show what you believe the average spend will be across all your customers. Assuming the reader thinks that estimate is plausible, he or she can seamlessly plug it into the market size equation on the next slide.
Maybe we can meet in the middle?
Typically, when you see the infamous 3 circles the only number that matters is the bottom circle but, alas, not always. Sometimes the Total Addressable Market is actually the middle circle. For example:
Now we have to actually think about it (dammit!). If the startup is pitching software for roofing subcontractors, the bottom circle is the relevant one (and I can stop reading right there because that market size is way way way too small). But if a founder is making software for all subcontractors and they’ve identified roofing subs as the first subsegment they are targeting as they go-to-market, then the middle circle is the one that matters when it comes to TAM.
Bear in mind that the bottom circle is not wrong. It’s even interesting and relevant information as far as an investor is concerned. It is simply in the wrong place. “TAM” means “Total Addressable Market”: if everybody who could use your software uses it, how big is the market? If you choose to sell to some types of customers before others, that information belongs on your Go To Market slide.
At first glance, this looks like a $200M market. That’s a nice size for a self-funded company, but it is generally not considered large enough for venture funding. But take a look at footnote 3. This company is assuming that they ultimately get only 25% of the total market. This may very well be true but they are selling themselves short. Investors think in terms of total market size; all our rules of thumb implicitly assume that the startup will only capture some of that total. In theory, we should be able to correct for that but, psychologically speaking, the low number sticks in our mind. Plus that assumes we caught this in the first place. As I mentioned before, we don’t particularly like it when you make us think.
When top-down and bottom up are the same
Before I get more than the normal volume of hate mail and ‘gotcha’ email, there is one legit exception to this rule. Under certain revenue models, the top-down estimate is actually what drives your bottom up number. For instance, if this software was used for purchasing construction material and had a revenue model where the software was free but they got a commission on all sales of, for instance, 4% of contract value then the top down figure of everything spent on construction supplies is actually the entirely relevant input to the “third-grade math” equation for market size: Total purchases x 4% = TAM.
You would still have to be very careful to exclude the types of construction supplies that are not on their platform (e.g., if you can’t sell cement, you have to pull that spend out) but in this case, the top-down data is not only valid but necessary.
Making it concrete
With the above in mind (and apologies for the awful pun), here’s a quick recap of what you can do to make your Market Size slide as effective as possible. I call them, “The TAM Commandments”:
Thy TAM shall be a single figure. Thou shalt not have three figures and expect Me to figure out which two to ignore.
Thou shalt use bottoms-up estimates. Top-down estimates are an abomination. (Except when they aren’t)
Honor thy Revenue Model slide and keep it before your Market Size slide
Thou shalt not kill your Market Size by reducing by your expected market penetration
Thou shalt not covet the Go To Market slide. Leave GTM strategy off the Market Size slide.
Thanks for reading and please share this with all your friends… because I’m sick and tired of bad Market Size slides.
Note:This example is loosely based on Dreamit UrbanTech alumn Knowify. Their Market Size slide looked nothing like this and, for those of you who actually read the footnotes on the charts, the $800M TAM is 800K subcontractors in the US x an average software subscription price of $1000 per sub. So in other words, Knowify did it right. 🙂