A founder who spent fifteen years in commercial real estate says their target market is "real estate." That's a $1.1 trillion industry. It's also not a market — it's an aspiration with too many sub-problems inside it to build a focused product. The same problem shows up with "insurance," "healthcare," "construction," "legal." These are industries, not markets. And the distinction matters for everything that comes after the first pitch meeting.
The operator founder advantage is deep domain expertise in a specific vertical. But that expertise is only useful if it points to a specific enough problem that you can build one product, sell it to a specific buyer, and be the obvious choice for that buyer over anything else that exists. An operator who narrows to the right slice converts their knowledge into a company. An operator who stays broad converts their knowledge into another failed pitch.
Why smaller is actually safer
The counterintuitive truth about market size at the early stage is that a smaller, more specific market is almost always safer than a large, diffuse one. Not because larger markets are bad — they're not — but because large markets attract large competitors, and large competitors win on distribution long before they win on product.
A focused market has the opposite dynamic. Buyers in a tightly defined niche are connected — word travels fast in a specific community, and a product that solves the actual problem compounds through referral in a way no paid channel can match. The first ten customers tell the next twenty because they know each other. The churn rate is low because the product is built for the exact workflow, not a generic approximation of it. Competitors who need to serve a larger surface area to justify their overhead can't profitably serve a market that specific.
The operator founder who narrows their market is not limiting potential. They're choosing to be the obvious best answer to one specific question first, with the distribution and the data to earn the adjacent questions later.
The signal that you've found the right slice
Most operators who come from a large industry describe their target market in industry terms: "HVAC contractors," "regional banks," "specialty subcontractors." These are categories, not markets.
The right slice is defined by workflow, not industry. "HVAC contractors" is a category. "Residential HVAC contractors with 5 to 15 trucks who schedule service calls without a dedicated dispatcher" is a market. The difference is that the second description implies a specific decision-maker, a specific workflow problem, a specific competitive set, and a specific path to the first ten customers.
The test is whether your product description changes based on who in that market you're talking to. If a 3-truck HVAC contractor and a 25-truck HVAC contractor would need different versions of your product to get value, they're not the same market. Pick one. Build for them first. The other one is version two.
Three questions that force specificity
If you've been describing your market in industry terms, three questions usually produce the right level of specificity.
First: who is the specific person who feels the pain of the problem you're solving? Not the company — the individual. What's their job title, and what's the decision they make every day that your product makes better or faster? If the answer is "the owner" at one company and "the operations manager" at another, you don't have a consistent buyer yet, and your product-market fit will be harder to establish.
Second: what does a bad week look like for that person because your product doesn't exist? If you can't describe a bad week in two minutes — the specific missed deadline, the wrong data in the report, the process that broke down on Thursday because of the thing that always breaks down on Thursday — you don't know the problem well enough to build the product yet.
Third: which three companies in your target segment would you call tomorrow if you had a working prototype? If you can name three without thinking about it, the market is specific enough. If you have to think about it for more than ten seconds, the market isn't specific enough yet.
The specificity forces clarity about what the product has to do on day one. A product for "HVAC contractors" has to do everything for everyone in that category. A product for "residential HVAC contractors with 5 to 15 trucks who schedule without a dispatcher" has one job: make it possible for the owner to schedule jobs without needing to hire a full-time dispatcher. That's a product you can build in one quarter and sell in two calls.
The confidence problem
Most operators who start too broad aren't confused about the problem — they're managing risk. If "real estate" is the market, the market never fully rejects the idea. Staying broad is a hedge against being told the specific problem you know isn't big enough to build a company around.
The hedge doesn't work. A broad market means you can't get the first ten customers, because the product doesn't solve anything specific enough for them to prefer it over what they already have. You can't raise a pre-seed round, because investors can't evaluate a product with no defined wedge. You can't hire early team members, because nobody knows what they're building toward or who specifically they're building it for.
Committing to the right slice is the move that actually reduces risk. The specific market either responds or it doesn't — and you find out in month two instead of month fourteen. If the specific slice validates, you have a real company. If it doesn't, you've learned something specific you can act on, rather than spending a year in ambiguity.
The founders who build large companies from vertical software rarely started with the whole market in mind. They started with the clearest, most specific version of the problem they understood, got good enough at that version to be the obvious answer, and earned the right to expand from there. That's the sequence. Start with the slice you know cold.