Building a business operating system from scratch

For a long time I ran my business the same way most people do. Notion for notes and tasks. Google Sheets for tracking. A CRM for client and pipeline management. A separate invoicing tool. A Kanban board somewhere in between. Everything connected to everything else only loosely, and only when I remembered to update it.

It worked, up to a point. The problem was not any single tool. The problem was that none of them knew about each other. Every morning started with a small tax. Open five tabs, scan five different places, try to hold the full picture of what was actually happening across four active workstreams in your head. That context-switching has a cost, and it compounds.

I run Trailhead Holdings across a few genuinely different areas. NGP and FMCG consulting. An e-commerce operation through Momentum Commercial. MVP Cricket, a SaaS product for grassroots cricket clubs. A job search workstream. Each one has its own rhythm, its own pipeline, its own set of things that need tracking. No off-the-shelf tool was built with that shape of business in mind.

So I built one.

Trailhead OS runs at app.trailheadholdings.uk and is built on Next.js, TypeScript, Tailwind, and Supabase. It has a command centre dashboard that gives me a single view across everything. A Kanban board for each workstream. A CRM. Invoicing with PDF generation. An AI-powered quoting module. Web push notifications. A client discovery form that feeds directly into the pipeline.

It took time to get right. Building your own tooling means every decision is yours, which is a benefit and a burden simultaneously. There were weeks where I was spending more time building the system than using it. That is the honest version.

But the shift when it came together was significant. The morning context-switching is gone. Everything that matters about each workstream lives in one place, and that place understands the structure of how I actually work. The CRM knows which workstream a contact belongs to. The Kanban boards are shaped around how each business operates, not around how some product team in San Francisco thought a generic user might work. The invoicing pulls from the same client data rather than requiring me to re-enter it somewhere else.

The broader point is not that everyone should build their own tools. Most people should not. The point is that the quality of your operating infrastructure has a direct effect on how well you can think and make decisions. If you are spending mental energy bridging the gaps between disconnected tools, that energy is not going into the work itself.

I am still building it out. Gmail integration, Google Calendar sync, and a Stripe layer are in the pipeline. But even at this stage it has changed how the business runs. One system. Full picture. Every morning.