From Hackathons to Venture Building
Hackathons taught me how to ship. Venture building taught me what shipping is actually for. The gap between those two lessons took longer than I expected.
What Hackathons Actually Teach
I've won a few hackathons. The skill being tested isn't what most people think.
It's not product instinct — 48 hours isn't enough to develop that. It's not technical depth — judges can't evaluate that either. What hackathons select for is the ability to synthesise a narrative around a half-finished thing, and ship that narrative convincingly.
That skill is genuinely useful. It's also genuinely different from building a company.
The Translation Problem
The hardest part of moving from hackathon thinking to venture building was unlearning the demo instinct.
In a hackathon, the demo is the product. Polish the demo, win the hackathon. In a company, the demo is a promise. Polish the demo at the expense of the underlying system, and you've just made a promise you can't keep.
I made this mistake early. I got very good at making things look ready before they were. The feedback I was getting — interest, enthusiasm, early commitments — felt like validation when it was actually just evidence that I was a good storyteller.
What Changed
The shift happened when I stopped optimising for the reaction in the room and started optimising for the outcome six months later.
That means different questions: not "does this demo well?" but "does this hold up when someone actually uses it?" Not "are people excited?" but "are they coming back?"
It's a slower feedback loop. It's less immediately gratifying. It's also a much more honest signal.
Where I Am Now
Hackathons are still worth doing — they compress learning in ways that matter. But I go into them now with a different objective: not to win, but to find the one genuine insight that might be worth carrying forward.
That reframe changes what you build, what questions you ask, and what you take seriously when the weekend is over.