Building a Personal Project Command Centre

I usually have a lot on the go at once. Client work, internal products, half-formed ideas, and concepts that are not ready yet but still feel worth keeping close. Some are active, others are parked. Some only matter because they connect to something else that has not quite crystallised yet.

For a while, Notion held most of this together. In some ways, it still does, but it has always felt slightly disconnected from the way I actually think. Pages of notes is useful, but it rarely provides the bigger picture of what’s spinning around in my head! It can store the information, but I could never really feel the shape of everything.

I wanted one interface where I could see everything at once and make sense of it.

So I built a personal Project Command Centre.

Why one place matters

The problem was never that I had nowhere to write things down. The problem was that my ideas lived in too many separate mental spaces.

A client project might sit in one place. A future product idea somewhere else entirely. A blog concept buried in a chat window. A business opportunity discussed with AI, interesting at the time, then never properly followed up.

That created low-level friction where the information existed, but was not easy to compare, prioritise or revisit. Things slip, not because they were forgotten exactly, but because there was nowhere obvious to hold them in context with everything else.

The Project Command Centre helps fix all that. Each project becomes a card with its own status, type, priority, tags, score and next action. At a glance, I can see what is active, what is worth pursuing, and what probably needs to stay parked.

The useful part is not really the dashboard itself. It is that the dashboard helps me ask better questions.

From notes to something I can think with

A list of ideas, however well-intentioned, can easily become another place where things quietly disappear.

A visual interface changes the relationship I have with my own work. The cards make each project feel assessable rather than simply recorded. The filters separate client work from internal products, and concepts from active priorities. The scoring system gives me a rough way to weigh value, fit, effort and risk without turning it into spreadsheet theatre.

It does not have to be perfect, it just needed to help answer the questions that matter.

What deserves attention now? What has real commercial potential? What needs more research or validation? What is high value but high effort? What am I holding onto because it feels interesting, rather than genuinely useful?

That is where a small, focused internal tool becomes much more valuable than yet another set of notes.

Adding AI without making it the whole point

The next layer is AI support, summaries, risk flags, suggested next actions, that sort of thing.

That does not mean handing over decisions. It means using AI to reduce the mental sorting that has to happen before a decision can be made. If a project has notes, tags and recent activity, the system can help surface what matters, flag blockers and suggest the next sensible move.

That is the kind of AI I find genuinely useful in a business tool. Quiet, contextual and in the background. Not a chatbot bolted onto a dashboard, and not a gimmick.

Making it more enjoyable to use

I also added theme switching.

Not for any serious reason, just because this is my own personal platform and I am bored of internal tools that all look like the same polite SaaS dashboard, muted colours, rounded cards, and the same safe interface patterns you have seen a thousand times before.

There is nothing wrong with clean SaaS design. It works, it is familiar, and it scales. But when a tool is only for you, it does not have to be neutral.

So the Command Centre can shift between themes, darker cyber-style layouts, stronger accent colours, HUD-style panels, and a more playful operating-system feel. It still has to be legible, and the information still has to do its job. But personal software is allowed to have a bit of character.

Why this matters beyond the interface

Most small businesses end up adapting themselves around whatever tools they already use. They squeeze their processes into Notion, Trello, spreadsheets, CRMs and shared folders, then accept the gaps between them as normal.

Sometimes that is fine, but oftentimes the better answer is a small, purpose-built tool that fits the business rather than the other way round. It does not need to replace everything, it just needs to solve one specific problem clearly and well.

For me, that problem was visibility. I wanted to see my ideas, products and client work together in one place, so I could make better decisions about what to pursue next.

The result is a personal command centre that feels genuinely useful, reasonably structured, and deliberately a little over the top.

Which, for something only I ever have to use, feels exactly right.