Find where the work is stuck.
A goal map that shows at a glance what the whole plan is waiting on — and who owns it. Not a task list but a picture that makes it obvious what depends on what. The work in it is done by people and by AI agents. Your data stays yours — download all of it any time.
Company or team
See where it is stuck — before the meeting does
- A goal map instead of a task list: at a glance, what holds the whole project and who owns it.
- The Organization overview across projects: what is overdue, what is not moving, who has the biggest backlog.
- Work is done by people and by AI agents (MCP); recurring steps are handled by rules.
- The Monday report in one click — Markdown or CSV, the same numbers as on screen.
Family and friends
One shared plan — and it is clear who promised what
- Moving house, building, a holiday, a party: one map everyone sees the same way.
- Who promised what and by when — without nagging in the group chat.
- A simple phone view: what's on today, what's burning, what I promised to whom.
- A starter map for families, no corporate jargon.
Just for yourself
My Day: a plan, not a list of reproaches
- You write down when you want to deal with it — the plan is respected, the deadline is never hidden.
- My Day: today, tomorrow, this week, overdue — on the computer and on the phone.
- Ideas go to the stash, goals to the map; the AI helps break a goal into steps.
- No list that shouts at you in the morning: first what you planned yourself.
The same product for everyone, nothing locked. 30 days free, no card, then the smallest plan — or self-host killBottleneck on your own server for free, with everything included.
Where the bottleneck usually is
Recognise any of these? Then it isn't that your team works too little.
Everything waits on one person
Approvals, budgets and small details all have to pass through the founder or the team lead. The rest of the team has capacity to spare and sits idle waiting for a verdict.
Information gets stuck between departments
Sales doesn't pass on what was promised. Marketing doesn't know what's being sold. Engineering finds out too late. Time then goes into meetings and into fixing mistakes that only came from a bad brief.
“Everything is priority one”
The team jumps between tasks and reacts to whatever is loudest right now. Work in progress piles up, nothing gets finished, and the strategic work never moves at all.
One specialist holds the whole process
Only one person understands that system, that customer, that procedure. The moment they're ill or away, the process stops and nobody knows where to pick it up.
Manual routine instead of real work
Hours of copying data between spreadsheets and pushing paperwork. The capacity that was meant to grow the business drowns in mechanical work.
None of these announces itself as “here is the bottleneck”. It shows up as deadlines slipping while nobody can say exactly why. A goal map turns that into a place you can point at — what is being waited on, how long it has been waiting, and it's visible to the team, not just in your head.
How it feels to use
Add a sub-goal in one click and name it right there
Every node carries an Add sub-goal button — the new step appears exactly where it belongs and joins the tree straight away. In the dialog you add a description, a status, a deadline, an owner, and whether the step is done by a person or an automation.
A status change shows up in the map at once: the node changes colour and progress rolls all the way up to the top-level goal.
The map is not a picture you draw once and then keep updating in your head. Nodes are dragged, branches collapse, and the bottleneck moves to wherever it actually is. When a node waits for its whole subtree, the map knows — you do not have to remember that "there is no point starting this until that is finished".
What you see in a map
Not a task list. A map that shows the cause.
A tree of goals, not a flat list
The goal on top, the steps below it, and their steps below them. A node can wait for its whole subtree, so you can see what actually blocks the deadline — and what is only noise.
"My day" and time tracking
A clickable overview of overdue / today / next 7 days / blocking others, computed live from your data. Timers are in the base product — on tasks and on map nodes, with entries you can assign afterwards and summaries per project and per client.
Tasks for people and for agents
A REST API and an MCP server mean Claude Desktop or Claude Code can read and edit your maps. The agent writes its own status back into the node — you just decide.
Day to day
"My day" instead of working out what to work on
Four tiles — overdue, today, next 7 days, open — computed live from your data rather than from a list somebody maintains by hand. Each task shows which project it belongs to and whether something else is waiting on it ("blocks: Publication").
The whole panel exports as a portrait image for a phone, including an anonymous variant with the titles blacked out, for when you want to show the load and not the content.
Time tracking that stays out of the way
Start the timer blank and assign the project and client afterwards — even retroactively, on an entry that is already finished. Totals come per day, per week and per project.
Tracking does not change a task's status. It is supplementary information, not another thing to keep up. A timer left running stops itself after twelve hours.
The map has its own layout for phones
The Landscape / Portrait switch refers to the screen, not to the tree. On a monitor the tree grows downwards with siblings side by side; on a phone it flips — the main axis runs to the right and nodes stack, so you can read it with a thumb and scroll one way.
Same map, same data, laid out differently.
On a phone, only what today needs
On a narrow screen the app switches to a simplified view: one column, large rows, one tap to tick a task off, and three tabs at the bottom. No shrunken maps you cannot hit anything in.
Your skin applies here too, so the phone looks like the app on your desktop. It can be added to the home screen as an app and read without a signal.
Appearance
Eleven skins. Light, dark, and a green terminal.
A skin covers both light and dark mode and is stored with the account, so everyone on the team picks their own. Your own skin can be imported and exported again.
Switching takes one click
Indigo, High contrast, Terminal, Paper, Ocean, Forest, Midnight, Plum, Peach, Graphite, Ruby and Rose. High contrast is there for legibility, not for show.
Skins are plain data — a company that wants its own colours simply imports them.
Why not just another task tracker
Four differences you notice in the first month
Time tracking is in the base product
Not in a higher tier. Timers, manual entries and summaries are there even in the free version you run yourself.
No seat minimums
You do not buy seats in packs of five, and you do not pay for colleagues who sign in once a quarter.
The data stays with you
Either literally on your server, or — when we host it — on machines in Germany. Your maps are not shipped off to somebody else's model in the background.
The AI can be switched off
And off is the default. Everything that matters works without it; if you want it, plug in your own model or use our service.
Open code, described honestly
The source is available. You may modify it, run it yourself, use it inside your company for free — and offer your own services around it. You may not host it as a paid service, white-label it, or resell it.
This is not open source in the strict (OSI) sense — it is fair-code. We say it that precisely on purpose: calling source-available code "open source" annoys exactly the people who care most about licensing, and they are right to be annoyed.
Run it yourself, or have it built for you?
Installing it yourself is free and carries no commitment. If you have neither a machine nor the appetite, we will set it up for you.