What do investors ask about your competitors?
Six diligence questions that sound like they're about the market, and what a credible answer actually requires.
Diligence questions about competitors are rarely about the competitors. Six questions investors actually ask, and what a good answer sounds like.
The competitive slide is the one founders rehearse least and get interrupted on most. It usually holds a four-quadrant chart, three logos, and a sentence about being the only platform that does both. Nobody asks about the chart. They ask something sideways — about a company you didn't put on it, or about a price change from March — and the answer either lands or it doesn't.
What's being tested is not your market knowledge. It's whether you look at the market on purpose or only when something surprises you.
"Who do you lose deals to?"
The trap here is answering with your positioning instead of your pipeline. Founders name the competitor they'd like to be compared to. Investors want the name that shows up in closed-lost, which is frequently a cheaper tool, an internal spreadsheet, or nothing at all — the deal just didn't happen.
A good answer is specific and slightly unflattering: two named competitors, roughly what share of lost deals each accounts for, and one sentence on the pattern. "We lose to them on procurement, not product" is a real answer. "We rarely lose head to head" is a signal you aren't tracking it.
"What changed at your competitors in the last six months?"
This is the question that separates people who watch from people who remember. A vague answer — "they've been pushing upmarket" — is a conclusion without evidence behind it. A strong answer is three or four dated facts: a pricing page that dropped its lowest tier in April, a SOC 2 badge that appeared in June, a run of enterprise AE postings starting in July.
Dates matter more than the facts do. A change with a date is something you observed; a change without one is something you absorbed from a podcast. If you can say when you noticed, you're implicitly saying you were looking. Timestamping every competitor change is unglamorous work that pays off in exactly this moment.
"Why hasn't the incumbent just built this?"
Expect it in almost every first meeting, and expect the honest answer to be uncomfortable: often they could, and they haven't gotten to it. Investors have heard "they're too slow" enough times to discount it entirely.
The credible version cites structure rather than speed. Their pricing model doesn't accommodate your use case without cannibalizing a bigger line. Their integration surface points at a different buyer. Their docs and API reveal an architecture that makes your feature a rewrite rather than an addition. Those are claims you can support from public material, which is why they survive follow-up questions.
"What happens if they drop their price to zero?"
A hypothetical, but not an idle one — they're checking whether you've thought about the shape of your moat when price stops being part of it. The bad answer is a flat "they won't." The better answer explains what their pricing is load-bearing for, and what breaks on their side if they give your category away.
If you've read their tiers carefully, you usually know: free tiers exist to feed a sales motion, and the seat or usage limits show what they're protecting. A competitor whose entire expansion story runs through a metered add-on can't zero it out without a revenue story to replace it.
"How do you know any of this is still true?"
The quietest question, and the one that decides how much of the rest of your answer gets believed. Competitive knowledge decays. The deck you built in January is describing a company that has since changed its onboarding, its integration list, and possibly its ICP.
The honest answer names a mechanism. For some teams it's a person and a recurring calendar block. For others it's tooling: Seeto watches the public surfaces — pricing, changelogs, docs, careers, integrations — and surfaces the differences as dated change events, so "what moved since our last raise" is a list rather than a memory exercise. It doesn't read the market for you or tell you what a change means; that judgment stays yours. But it does remove the excuse that nobody noticed. Either way, say what the mechanism is. "We check regularly" is not one.
"Who else is going to enter this market?"
Most founders answer with the two obvious adjacent platforms. That's table stakes. The interesting answer includes someone the investor hasn't considered — a vertical tool adding horizontal features, an open-source project starting to sell hosting, a services firm productizing its methodology.
The evidence for entry is public and early: job postings for roles outside their stated scope, docs for an API that has no product attached yet, a conference sponsorship in a category they don't serve. Entry signals show up in hiring and documentation months before they show up in marketing. And the flip side belongs in the same answer — competitors who have quietly stopped competing with you should come off the list, because a roster you never prune reads as a roster you never look at.
None of these questions reward encyclopedic knowledge. They reward a habit — evidence with dates on it, a named mechanism for staying current, and the willingness to say what you don't track and why. Build the running record during the quarters when nobody's asking, and diligence becomes a retrieval problem instead of a research sprint.