Startups don't die of bad ideas. They die of latency.

Cycle time is the whole game

Give two teams the same eighteen months of runway. One learns something real every week; the other every six weeks. The first gets roughly seventy attempts at being right, the second gets twelve. No amount of founder brilliance closes a gap that wide. Everything we push on inside the incubator is, ultimately, an attack on cycle time.

We have tracked this across nine portfolio companies over three years. The single strongest correlate of who raised a follow on round was not team pedigree, market size, or even revenue at month twelve. It was the number of distinct, falsifiable things the team had learned about their customer by month six. Teams above the median on that count raised at twice the rate of teams below it.

Founders resist this framing at first because it sounds like it is asking them to move faster and sloppier. It is not. It is asking them to shrink the unit of work until feedback can attach to it. A three month build has one shot at being right. Four three week builds have four shots, with the same total time spent, and each one teaches the next.

Where the weeks disappear

• Waiting for a decision that has no named owner.
• Building for three months before showing anyone, because showing is uncomfortable.
• Infrastructure choices that make deployment an event instead of a habit.
• Hiring for a role the company has not yet proved it needs.
• Fundraising conversations that consume the founder for a quarter with no term sheet in sight.

The commodity argument applies here more sharply than anywhere. Every hour an early team spends assembling infrastructure that ten thousand other companies also need is an hour not spent on the two or three things that are genuinely theirs. Buy the boring layer. Always. The cost of a managed service is trivial next to the cost of a week.

We once watched a two person technical team spend five weeks building an internal admin panel and a bespoke deployment pipeline before writing a single line of the product a customer would see. By the time they shipped anything, a competitor with no engineers, using off the shelf tools, had already run six pricing experiments. The five weeks were not wasted on a bad idea, they were wasted on infrastructure nobody was going to pay for.

The operating rhythm we install

Most cited post mortems still put 'no market need' at the top of the list of why startups fail. That is not a strategy failure, it is a feedback failure, the market was telling them something the whole time and the loop was too slow to hear it.

The 48 hour rule is the one founders push back on hardest and thank us for latest. Any decision sitting unresolved past two days gets escalated automatically to whoever can break the tie, even if the answer is a guess. A wrong decision made on Tuesday can be corrected by Friday. A right decision made three weeks late is functionally indistinguishable from a wrong one.

What we look for before we back anyone

We look for teams who already shipped something ugly that worked, because that proves the loop exists before the money arrives. Capital is the easy part of this business. Senior operating attention, someone who has already made the expensive mistake you are about to make, is the part that is genuinely scarce.

In diligence we ask founders to walk us through their last three product decisions end to end: what triggered it, how long from question to answer, what evidence closed it. Teams that struggle to answer usually have not built the loop yet, no matter how polished the deck is. Teams that answer in ninety seconds, with dates attached, tend to be the ones still operating three years later.

The counterintuitive part: slow down to speed up

There is a failure mode on the other side too. Teams that ship weekly but never sit still long enough to interpret what they shipped end up with a fast loop that teaches them nothing, because nobody closes the loop with an actual conclusion. Speed without a written down learning is just motion. We require every portfolio team to keep a one paragraph log entry per week: what we tried, what happened, what we now believe. It takes ten minutes and it is the single highest leverage habit we have found.