Commit, then track
Pull tasks into a fixed-length sprint and KanBit tracks the remaining work day by day — no separate spreadsheet, no manual tallying.
Project planning · The core of KanBit
Backlog to roadmap without switching tabs.
Boards, sprints, epics, and milestones live in one workspace — the whole planning stack, not three tools stitched together. Group tasks into epics, tie them to milestones, and watch a burndown that tells the truth.
One sprint, its burndown, and the epics rolling up to a milestone
Sprints
Sprints with a chart that tells the truth.
Run fixed-length sprints, commit a set of tasks, and track them against a burndown that plots ideal versus actual — no massaging the numbers to look on schedule.
Ideal vs actual
The burndown plots both lines, so a slipping sprint looks like a slipping sprint. The chart is there to inform the standup, not to flatter it.
Points or task count
Chart by estimate points or by number of tasks — whichever unit your team actually plans in. Switch without re-entering anything.
Structure
Tasks roll into epics. Epics roll into milestones.
Structure emerges from the work instead of a separate planning tool. Group tasks into an epic, point epics at a dated milestone, and attach key results so everyone knows what 'done' actually means.
Task
The unit of work
One thing to do, with an owner, a state, an estimate, and a due date.
Epic
A body of work
Group related tasks into a feature or workstream and track it as one.
Milestone
A dated target
Point one or more epics at a date, attach key results, and place it on the roadmap.
Milestones carry key results and land on a roadmap you can share, so the plan reads the same to the person doing the task and the person asking when it ships.
Filtering
Filters that actually filter.
The advanced filter bar composes conditions the way you think: any of, not any of, or all of. Save the view. Share the view.
Filter across every field that matters:
- Owner
- State
- Type
- Priority
- Label
- Epic
- Sprint
- Milestone
Build a view once — "my team's unfinished work this sprint, minus anything labelled blocked" — then save it and share it, so the whole team is looking at the same board.
Planning shouldn't need a second tool.
Start freeMake it yours
Bend the tool to your process.
KanBit adapts to how your team already works instead of forcing one canonical process on you.
Custom workflow states
Rename, reorder, add, and remove the columns on a board so they match how your team actually moves work — not a fixed To-do / Doing / Done.
Custom fields
Add the fields your process needs — a client, an estimate, a stage — and filter and group by them like any built-in field.
Labels
Colour-coded labels cut across projects, so "needs design" or "blocked" reads at a glance and drops straight into the filter bar.
Teams
Group members into teams, assign work to a team, and filter a board down to what one team owns.
Docs & wiki
Docs and a wiki that live next to the work.
Write specs, briefs, and runbooks in the same workspace as the tasks they describe — no context-switch to a separate documentation app.
Folders
Organise specs, briefs, and runbooks into folders that sit in the same workspace as the tasks they describe.
Versioning
Docs keep their history as they change, so you can see what a spec said before the scope moved.
Sharing
Share a doc with the people who need it and keep the rest of the workspace sealed off.
An honest limitation
There is no Gantt chart.
If your process lives and dies by cascading dependency bars, KanBit isn't your tool today — we'd rather tell you now than after the demo.
What you get instead
01 — A roadmap
Milestones laid out over time, so anyone can see what ships next quarter without opening a single board.
02 — Dated milestones
Real target dates with key results attached — a shared definition of what "done" means and by when.
03 — Sprints with burndown
Short cycles with an honest chart. Enough structure to stay on track, without pretending every task blocks the next.
The rest of KanBit
Planning is one module of three.
The CRM and time tracking share the same workspace as your planning — same data, same permissions, no integrations to wire up.
Straight answers
Project planning, questioned honestly.
The things teams ask before they move their planning to KanBit.
No. KanBit doesn't draw cascading dependency bars or a critical path — you plan with sprints, epics, milestones, and a roadmap instead. If your process lives on a Gantt chart, KanBit isn't the right fit today, and we'd rather say so before the demo than after it.
You can import tasks from a CSV today. One-click importers for Jira, Linear, and Shortcut are on the roadmap but not shipped yet, so for now the path in is a CSV export from your old tool and a CSV import into KanBit.
Yes. Sprints, epics, milestones, and roadmaps are Pro features. The Free plan covers kanban boards, tasks, and the full CRM — upgrade to Pro when you need the planning stack on top.
An epic groups related tasks into one larger body of work, like a feature or a workstream. A milestone is a dated target that one or more epics roll up to. Epics answer what; milestones answer by when. Both can carry key results.
Give one client a workspace. See where it goes.
Takes a minute to sign up. Free plan is genuinely free. No card required, no drip campaign, no gotchas.