the playbook

Everyone budgets for the event. Almost nobody budgets for the sixty days after it, which is where every outcome I've ever been credited with actually happened.

ARlink demoed one-click permaweb deploys at the end of Hacker House 2. The room went quiet, people clapped, and everyone flew home. The $2.5M seed closed three months later: after intros, debriefs, and a Launchpad that existed purely to keep the thread alive. If we'd treated Demo Day as the finish line, that round wouldn't have happened.

So I stopped thinking of follow-up as goodwill and started treating it as infrastructure: staffed, scheduled, owned by someone with a name. An ecosystem's real throughput is measured in the gap between applause and outcome, and that gap is a product you have to build.

A 48-hour hackathon optimises for caffeine and demo polish. Two weeks of co-living optimises for something else entirely: the thing that happens at 1 am near coffee corner when two strangers realise they're solving the same problem from opposite ends.

Across five houses, thirty builders each, twenty devs and ten designers, the pattern held every single time. The projects that survived weren't the ones with the best demo. They were the ones whose teams had already argued, cooked, lost a football match and made up before they ever wrote a line together.

The residency is expensive and slow and logistically miserable, and I'd run it that way again. You can't schedule trust into a weekend.

1,500 applications came in from across the houses. We took about thirty a time. For a long stretch, I thought the curation was overhead, admin standing between us and the real work.

It was the work. A room's character is set entirely by the last person you let in, and every weak yes costs you three strong builders who quietly decide the bar isn't real. The cohorts that produced BetterIDEa, 0rbit, LiteSeed and ARlink weren't lucky draws; they were the chosen ones from a lot of uncomfortable rejections.

Community people are trained to be welcoming, and it makes us bad at this. Open is not the same as good. The most generous thing you can do for the people in the room is be ruthless about who else is in it.

Every ecosystem team says it supports builders and means technical support: office hours, credits, a mentor slot. That's the easy half. The part that actually compounds is treating the person, not the project, as the thing you're investing in.

We ran quality over quantity in every activation, but the moments people still bring up years later aren't the sessions. It's helping someone get their first passport. Someone's first flight. Making sure every single interaction left a person feeling heard rather than processed. None of that shows up in a recap thread, and all of it is why they come back and bring three friends.

Real connection isn't a soft skill you sprinkle on a programme, it's the retention engine. Pave the way for their success in and beyond your event, and the ecosystem will grow on its own.