The energy after the bookshop project — a small idea, a rejection, a yes, and a genuinely great result — clarified something I'd been circling for a while: I didn't want to keep chasing individual projects one at a time. I wanted a team built to do something meaningful, repeatedly.
What Changes When You Think in Teams, Not Projects
A single project has a start and an end. A team has momentum that outlasts any one deliverable. Every team I'd led up to that point — the five-person group at 15, the remote collaborations, the bookshop crew — taught me something about how people work together under real constraints. That accumulated knowledge is wasted if it resets to zero every time a project ends.
Meaningful, Not Just Profitable
The bookshop trade wasn't the highest-paying project I'd done — it might have been the lowest, in strict cash terms. But it was the one that felt best, because the outcome mattered to real people beyond a transaction. That's the bar I decided to hold future work to: not just "will this pay," but "will this matter to someone."
Where That Decision Has Led
Everything since — including building Form24, a real SaaS product solving a real problem in a market I understand — traces back to that decision. I stopped asking "what's the next project" and started asking "who's the team, and what should we be building together." That's still the question I'm working from.