For a long time, I’ve been obsessed with how we actually move the needle. I’ve lived the methodologies and tested every task manager on the market. But eventually, I hit a wall: most tools are either an empty bucket that requires too much maintenance or a rigid box that doesn’t adapt to a non-linear workday.

I realised I didn’t need another place to store a “To-Do” list. I needed a system that understood the friction between a high-level project and the ground-level reality of a busy afternoon.

That’s why I stopped searching for the perfect tool and started building it.

I call it Momentum.

The Problem with Productivity

We are currently living through a “complexity crisis.” Our work is fragmented across different roles, platforms, and mental spaces. Most apps solve for storage—they give you a place to park your tasks. Very few solve for flow—helping you decide what to do next based on your current context and available energy.

When I sat down to design the schema for Momentum, I focused on three core pillars:

• Contextual Logic: Eg., a task I can only do at a laptop shouldn’t be cluttering my view when I’m on the move.
• GTD®-Inspired DNA: Eg., I’ve integrated the core logic of the Getting Things Done® methodology—capturing ideas and clarifying next actions—but stripped away the manual overhead that usually leads to system fatigue.
• Vibe Coding & Agility: Eg., leveraging no-code architecture to build a multi-user system that can evolve as fast as my requirements do.

Building in the Open

This isn’t just about launching an app; it’s about a philosophy of work. I’ve been deep in the logic and architecture of this project for months, and it’s reached a point where it’s ready to step out of the lab.

As I move forward, I’ll be sharing more about the technical hurdles of building a multi-user architecture and the specific loops that make Momentum different.

What’s Next?

Building Momentum has reminded me that the best way to predict the future of your workflow is to build it yourself. This is the start of a new chapter in how I approach software and strategic intelligence, and I’m excited to share the progress.

Stay tuned—the build is just getting started, and in the meantime, here’s a short read with my baseline philosophy on creating a productive day.