Tools
Services
WorkKompendioAbout
ende
Octinex Flow

Flow knows on Monday, and keeps knowing all week, without anyone having to keep a board up to date.

  • In a pilot at a large MVZ in Berlin
  • German and English
  • Self-hosted

A personal project, built in my own time.

Why most boards die

Keeping a board up to date becomes one more job.

  1. Monday

    A new board. Tidy, colourful, and everyone keeps it up to date.

  2. Wednesday

    Updating it is now a task on top of the work. Some cards are already behind.

  3. A week later

    The board says one thing. The real plan lives in someone’s head again.

Flow turns it round: the work keeps the plan current.

Requests, hours and progress reach the plan from the work itself. Keeping it up to date isn’t a second job.

How Flow works, step by step

  1. 01 · A request arrives

    Requests come through a form, not your inbox.

    Anyone can ask through a public form. The request lands on the board as a card by itself, with what was asked and by when.

    Gone copying requests from emails into a board

  2. 02 · The work gets drafted

    Claude drafts the steps and the hours.

    A person checks the draft and changes it before it counts. Without AI, templates per category do the same job.

    Gone guessing hours into an empty field

  3. 03 · The week answers

    Every promise gets a colour.

    Each card is planned day by day against the focus hours people really have. Green: can be made. Yellow: tight. Red: not without giving something up. Flow suggests what to move.

    Gone finding out on Friday

  4. 04 · Today is ready

    Each morning starts with a plan.

    “Today” is built from the hours left and what’s due. Whatever must start today says so.

    Gone writing a to-do list every morning

  5. 05 · One tap

    The clock is the timesheet.

    One tap starts work on a card, another switches. Forget to stop it, and Flow asks whether it’s still running and suggests when it ended.

    Gone filling in a timesheet on Friday afternoon

  6. 06 · The asker sees it too

    Requesters follow their request themselves.

    A status page shows where a request stands. When the team is full, it says so, and until when.

    Gone answering “any news on my request?”

  7. 07 · Friday looks back

    The weekly review writes itself.

    Every estimate is set against the hours the card really took, and what slipped is listed: all from the week’s clocks.

    Gone putting a weekly report together

Flow drafts, rates and reminds. People decide.

That’s what being in control means here: knowing on Monday what Friday will look like, without keeping a board alive by hand.

Try it

Add requests and watch the week answer.

Requests waiting

  • Booking form shows the wrong date

    3 h · due Tue · firm

  • Flyer for the open day

    6 h · due Wed

  • New blog layout

    8 h · due Thu

This week can be made

12 h planned of 25 h

  • Opening hours on the website: 2 h, due Tue, can be made
  • Photos for a new team profile: 4 h, due Thu, can be made
  • Newsletter for October: 6 h, due Fri, firm, can be made
  • can be made
  • tight: over 80 % full until then
  • not without giving something up
  • ◆ firm promise

Runs in your browser on made-up data, with a simplified form of the rule Flow’s week timeline uses.

Who it’s for

One plan, seen from four sides.

  • Team leads

    See every promise rated, and what to move so the week fits.

  • The team

    A day already planned, one-tap clocks, and break reminders in a Chrome side panel.

  • People who ask

    A form to ask, and a page to follow the answer, without chasing anyone.

  • Call teams

    Tap counters for calls that keep counting offline and catch up later.

How it’s built

For the people who’ll ask how.

  • 534commits since July 2026
  • 1,100+automated tests
  • 4stress-test reports since September
  • 2interface languages, German and English

Figures as of 12 October 2026.

  • TypeScript
  • React 19
  • Vite
  • Tailwind CSS
  • Express
  • SQLite
  • zod
  • JWT
  • Anthropic API
  • installable web app
  • Chrome extension
  1. Web app, side panel, wall screenReact 19, one codebase, installable
  2. ServerExpress · every input checked (zod) · JWT sessions · one organisation each
  3. SQLiteon the organisation’s own server

Claude, optionaldrafts estimates · templates stand in without it

  • Tests check that no organisation can see another’s data.
  • In production the server refuses to start with a missing or default secret.
Where it stands

From first commit to pilot.

  1. July 2026First commit
  2. Sept – Oct 2026Four stress-test rounds
  3. NowIn a pilot at a large MVZ in Berlin
Write to me

Want to talk about Flow?

Whether you’re hiring, have a team that needs it, or want to back it: one message reaches me.

I use what you send here only to answer you. Privacy policy

The other tools