How can a candidate probe a startup's revenue path and competitive moat with its founder?

## Two questions, one purpose Runway tells you how much time the company has. Revenue path and moat tell you whether that time is being spent on something that can become a business. Both are founder territory: engineers rarely see the pricing conversations, and recruiters cannot speak to defensibility. ### Revenue path Ask it as a chain rather than a single fact: **who pays today, what exactly are they paying for, and who is expected to pay next?** The chain matters because early-stage companies often have revenue that does not generalise — a handful of customers paying for something close to consulting, which looks like traction on a chart and behaves like a service business in practice. Useful probes once the chain is on the table: - How long does it take from first conversation to first payment? - Does the second customer in a segment cost as much to serve as the first? - What has to be true for the current customers to spend more next year? ### Moat Ask it as a hostile hypothetical, politely: **if a well-funded competitor set out to copy this next quarter, what slows them down?** Founders answer this well or badly, and the difference is informative. Answers that describe something real usually name an asset that accumulates or a cost someone else must pay: | Shape | What it sounds like | |---|---| | Compounding data | Customer operational data flows in and makes the product measurably better with tenure | | Integration depth | The product sits inside workflows that took months to wire up | | Switching costs | Leaving means re-training staff or re-doing an integration | | Distribution | A channel or partnership that is expensive for a newcomer to reach | | Regulatory or procurement access | Approvals and certifications that take time regardless of engineering speed | Answers that describe a lead rather than a moat: 'we execute faster', 'we were first to see this', 'our design is better', 'our team is stronger'. All four may be true today and none of them survives a well-funded competitor's second year. A founder who says 'honestly, not much yet — our bet is that the data advantage compounds before anyone notices' is giving you a *better* answer than one who lists four moats, because it is falsifiable and it tells you what the company is racing toward. ## A worked example An early-stage company sells demand-forecasting models to operations teams. The co-founder describes revenue: a small number of customers pay an annual subscription, and each one needed several weeks of bespoke data plumbing before the first useful forecast. That single description answers both questions and sets up the next ones. On revenue: the sales cycle includes an integration project, so growth is gated by delivery capacity, not by demand alone. On moat: the integration depth is a real switching cost — once forecasts are wired into someone's ordering process, replacing them is expensive. But the same fact is also the drag on growth. So the question that earns its place next is: **is the plumbing getting cheaper per customer, or is each one still bespoke?** Whether that curve is bending is arguably the whole company, and a founder who has thought about the business will light up at the question. ## Keeping it a conversation Three cautions. First, do not deliver these as a list; ask one, listen, and let the answer choose the follow-up. Second, do not perform market analysis at the founder — a candidate who explains the competitive landscape back to the person who lives in it reads as arrogant, not prepared. Third, calibrate your expectations to the stage: at the earliest stages there may be no revenue and no moat yet, and the honest answer is a hypothesis with a test attached. What you are grading is not the presence of a fortress; it is whether the founder can tell the difference between what is proven and what is hoped. ## What to do with the answers Write them down after the conversation, in the founder's words. If you later hold more than one offer, the specificity of these answers is one of the few things that distinguishes early-stage companies from the outside, and it fades from memory faster than the numbers do.