Studio notesPodcast

The week nothing shipped.

A VentureOS week that produced no code and answered the question anyway. Recorded on the Friday, before we had tidied up the story.

Episode 14 · The week nothing shipped
14:0241:18

Founders ask us how many customer conversations are enough. It is a reasonable question and the honest answer is unsatisfying: somewhere around ten, and after that you are usually buying comfort rather than evidence.

The number matters less than what comes back. Ten people describing the same problem in their own unprompted words is a signal you can act on this week. Forty people politely agreeing that your idea sounds useful is not a stronger version of that signal — it is a different thing entirely, and it is worth nothing.

What we look for instead

Three things, in order. Each one is harder to fake than the last.

  1. The same words. Not the same agreement — the same specific phrase, used by people who have never met.
  2. Something already paid for. A spreadsheet, an intern, a workaround. Money already leaving for this problem beats any stated intention.
  3. An action after the call. A forwarded email, a colleague pulled in, a date offered. Enthusiasm that survives the call ending.

The stall has a recognisable shape. Conversation twenty-two is scheduled, the deck gets another pass, and the week produces no new evidence. It feels like diligence from the inside. From the outside it looks like a founder who has decided not to find out.

Ten is a sample. Forty is a stall.

So we cap it. Ten conversations, then a written answer, then a decision about what to build. If the answer is thin after ten, that is itself the finding — and it is a cheaper finding at ten than at forty.1

1 The ten-conversation cap is not a research method, it is a decision deadline. We have broken it twice, both times in regulated markets where the buyer and the user were different people. ↩

Chapters

  1. 00:00Why we stopped the week
  2. 06:40The assumption we were testing
  3. 15:12What the week actually produced
  4. 24:35Telling the founder
  5. 33:08What we would do differently

Transcript

Lightly edited for readability. Timestamps jump the player.

00:00Stephan. We should say at the start that this episode is about a week that did not produce a product. That is not a framing device — nothing shipped.
00:34Michael. And the founder had paid for it. So the question we were sitting with on the Friday was whether we had wasted a week of somebody’s money.
06:40Stephan. On the Monday we wrote down the assumption the week was testing, and what evidence would settle it. In this case it was whether any of the twelve operators we spoke to had ever paid anybody to solve this.
07:22Michael. Nine of twelve had a workaround. None of them had bought anything. Two had tried and stopped. That is a clear answer and it arrived on the Thursday.
15:12Stephan. So what the week produced was a decision, plus a written record of why. Which is worth more than a prototype nobody would have used, though it does not feel that way on the Friday.
24:35Michael. Telling the founder was the part I got wrong. I led with the reasoning instead of the conclusion, which meant he spent four minutes waiting for bad news he could already see coming.

The newsletter

One note a month, usually about something that went wrong.

No digest, no round-up. One thing we learned, written up while it is still uncomfortable.

About 900 founders and operators. Unsubscribe in one click.