MY OWN TOOL · USED EVERY DAY

Project Flow: the tool I run my days from

My own tool · Runs my businesses and my client projects

Problem

Four parallel commitments needed one honest view of my promises and my time.

Built

A personal cockpit on my own machine for promises, delivery and real capacity.

Result

21 database updates and 16 helper scripts, with the data, the connections and the workflows all tested.

project-flow
Illustrative interface visual

Stack

React 18TypeScriptSupabase (local Docker Postgres)dnd-kitrecharts

The problem

I run a community business, a consulting practice, a software build and a day job. That needs one honest view of my promises and my time, not four to-do apps.

What I built

A personal cockpit that runs on my own machine.

  • check_circle

    Every week I log what I promised and what I delivered, so I can see my say-do ratio. Promises made in meetings come in automatically.

  • check_circle

    An honest capacity view: work needed against time available, shown in red, amber and green, plus what-if scenarios.

  • check_circle

    When a deal is won, it turns into a delivery project by itself.

  • check_circle

    The data lives on my own machine. Each area is walled off, everything is tested, and there is a written export so the whole thing can move anywhere.

Proof

21
database updates
16
small helper scripts
6
outside tools used, on purpose

The plumbing is treated like a product: the data, the connections and the workflows are all tested.

Illustrative interface visual
Illustrative interface visual
arrow_back Previous One screen to run every client rollout
Next arrow_forward Documenting the undocumented