The most common excuse I hear from people who want to build things is that they don't have enough time. They need a weekend. They need a week off. They need to quit their job and go full-time on their idea. They need the stars to align before they can start. I'd argue they need the opposite. They need less time, not more. Three hours is enough to ship a product. I know because I've done it repeatedly.
This isn't a productivity hack or a motivational platitude. It's an observation from having shipped over twenty-four products, almost all of them built in sessions of three hours or fewer. The constraint doesn't limit the output. It defines it. And in most cases, it improves it.
Why short sessions produce better work
In advertising, I spent entire days on single presentation decks. Tweaking slides. Adjusting copy. Reworking the narrative arc for the third time because someone in the room had a feeling about page seven. Fifteen years of that. Entire weeks disappearing into the process of explaining ideas rather than making them.
Now I build in sessions that rarely exceed three hours, and the products are better than most of those decks ever were. The reason is simple: when time is scarce, you can't afford to faff about. You can't spend forty-five minutes choosing a colour palette. You can't research seven different navigation patterns. You can't read three blog posts about best practices before writing a single line. The constraint strips away everything that isn't essential and forces you to make decisions.
This is Parkinson's Law applied to product development. Work expands to fill the time available. Give a team a month and the work takes a month. Give yourself three hours and the work takes three hours, because it has to. The interesting discovery is that the three-hour version is often sharper, more focused, and more honest about what actually matters.
Single-session ships
I built Oishii London, a curated guide to Japanese restaurants in London, in a single session. Three hours. The idea hit me during the day, I sat down that evening, and by the end of the session it was live. Not because it was simple, but because the deadline forced me to focus on what actually mattered: the restaurants, the design, the feel of it. Everything else got cut.
First Out started the same way. One session, one core feature: which Tube exit should I use? The Forest Quiz was a single evening. London Pub Guide, same story. Each of these exists because the time pressure forced a specific kind of clarity: build the core thing, ship it, iterate later.
Single-session products have a particular quality. They're tight. There's no feature creep because there was no time for features to creep. They do one thing, they do it clearly, and they're done. The time pressure creates a specific kind of decision-making where you learn to trust your instincts. Is this layout good enough? Ship it. Does this feature matter or is it nice-to-have? Skip it. Pick one font, move on.
Why constraints beat resources
The startup world glorifies resources. More funding, more engineers, more runway. But resources often produce the opposite of what you'd expect. More time means more deliberation. More people means more consensus-seeking. More budget means more options, which means more paralysis.
Constraints produce the opposite: clarity, speed, decisiveness. Designers have understood this for decades. A blank canvas is harder than a brief with parameters. The brief gives you something to push against, and the pushing is where the interesting work happens.
The AI tooling makes this even more powerful. With Claude Code, the gap between idea and working product has compressed from weeks to hours. That compression is perfectly suited to short sessions because the feedback loop is immediate. Describe what you want, see it materialise, adjust, ship. The whole cycle fits inside a window that most people would consider too short to accomplish anything meaningful.
The compound effect
One three-hour session produces one product. That's useful. But the real power is in compounding. Twenty-four products later, each one has taught me something about building, about taste, about what works and what doesn't. The speed of iteration means the learning curve is steep, in a good way. I'm making better decisions in session twenty-four than I was in session one, not because I've studied more but because I've shipped more.
I've also developed a sense for what can be built in a single session versus what needs multiple sessions. Modern Retro took a week of sessions. CultureTerminal evolved over many iterations. Knowing the difference between a one-session idea and a multi-session idea is itself a skill that only comes from doing it repeatedly under tight constraints.
The products are the proof. And the fact that they were built in short, focused sessions under real constraints isn't a weakness. It's the entire methodology. Three hours is all you need, not because three hours is a lot of time, but because it's exactly enough to strip away everything except the work itself.
