CNSL

The tracker holds the tasks and runs a timer on one or many of them — one click, on the task itself. While it runs, the PWA on my phone carries a badge, which is what I kept forgetting in Toggl.

The calendar puts tasks on dates. The scheduler turns a repeated sequence into timed steps. The noder chains tasks through an LLM. The note pad became my micro publisher, and the chat works inside projects.

A note can be given its own public URL. A project can be shared with editor, viewer or contributor roles, or opened for submissions from people without an account.

1. Organisational pain
2. Big Vision into Claude
3. MVP
4. On every device
5. Add tools
6. dog-fooding

Dogfooding became the main driver for development. The more the app was capable of, the more I used it for my own planning. Opportunities and breaking points became apparent fast. With agentic building they were relatively easy to build or fix.

Later the board seeded itself from CNSL’s own roadmap on first load. The app tracks its own development, so every missing feature is visible while you use it.

The first version kept everything in the browser. Tasks lived in local storage — no server, no account. That ruled out sharing and a second device.

I chose those limits. The shape of the product changed every week. With nothing in a database there was nothing to migrate when a view changed; with no data on a server there was nothing that could leak. The backend came once the shape had settled.