The performance problem

Every accelerator cohort ends the same way: twelve startups on a stage, eight minutes each, a room full of investors who've already decided where to park their cheques. The startups that perform well get funded. The ones that don't, often don't.

That's a selection process optimised for presentation skill, not product quality. And it creates a perverse incentive — spend the final weeks of your programme polishing a pitch instead of polishing the product.

We don't do demo days because we're not an accelerator. We're a studio. The distinction matters more than most people think.

Studios build differently

An accelerator takes external founders, adds resources, and hopes for the best. The hit rate is low by design — the model works because a tiny percentage of bets pay for all the losses.

A studio builds companies from the inside. The team that identifies the opportunity is the team that builds the product. There's no handoff, no pitch, no "are you coachable?" gut check. The intellectual honesty is baked in because you're accountable to yourself.

This changes the economics. Instead of betting on 50 teams and hoping 2 survive, you build 5 things with high conviction and expect 3 to work. The cost per experiment is lower. The signal-to-noise ratio is higher. The failure mode is "we killed it early" rather than "they ran out of runway."

Some sidequests are quick experiments. Others become the whole story. We won't know which until we build them.

What we do instead

Instead of demo days, we have kill decisions. Every venture in the studio gets a clear set of conditions that would cause us to shut it down: no product-market fit signal by week 8, customer acquisition cost above a threshold, retention curve that flattens in the wrong place.

This is the opposite of a pitch. A pitch is designed to make something sound inevitable. A kill decision is designed to find the cracks before you've poured concrete.

When a venture survives the kill decisions and starts generating revenue, it doesn't need a demo day. It needs an operating team, a cap table, and a plan. That's when we raise — with data, not decks.

The AI advantage

AI has compressed the cost of building software by an order of magnitude. What used to take a team of twelve engineers six months can now be done by two people in six weeks. This is the structural shift that makes the studio model work.

When building is cheap, experimentation is cheap. When experimentation is cheap, you can afford to be honest about what isn't working. You don't need to cling to a narrative because you've sunk $2M into it. You can just... stop. And start the next one.

Demo days are built for a world where starting a company is expensive and irreversible. We live in a world where it's cheap and iterative. The ceremony doesn't fit the reality.

Building in the dark

There's a line we use internally: "build in the dark until it works." It's not about stealth mode or secrecy. It's about focus. When you're performing for an audience, you optimise for applause. When you're building for customers, you optimise for retention.

We'll share what we're doing when there's something worth sharing. Not a prototype. Not a landing page. A business. With customers, revenue, and a thesis that's been tested against reality.

That's not a demo day. That's just Tuesday.