Written by the AgileFever editorial team. Facts checked on November 5, 2026 against the official pages of the organizations named in this post. AgileFever sells training for some of the topics covered here, and we say so wherever it applies.
A startup rarely loses a kanban tool war on features. It loses on habits: a board with twenty cards in “Doing”, no sense of which card has sat for nine days, and a year of history trapped in a tool nobody can leave. This post gives you a way to choose a free kanban board for startups by what the board must make visible, not by what a comparison page lists. It names no tools and compares no plans or prices, because those change often and your needs differ.
If you are still deciding how to lay out columns, start with our kanban board examples. If you want a ready starting layout, the kanban board template post covers that. This post answers the earlier question: which board, and how to test it.
What a free kanban board for startups needs on day one
Five capabilities cover a team’s first six months. Everything else is optional.
- Columns you can rename and reorder. Your workflow is not “To do, Doing, Done” for long. You will add a review or a waiting column within weeks.
- A WIP limit on each column. A limit caps how many cards a column may hold. The board should show the count against the limit, for example 4/5, so a breach is visible without anyone doing arithmetic.
- Card age. Each card needs a start date, and the board should show days since start. Age is the earliest warning you get that something is stuck.
- A blocked flag. A card that waits on a customer, a vendor or another team must look different from a card being worked. Otherwise it passes for progress.
- Simple flow numbers. You need items finished per week, current WIP and cycle time. A chart is nice. A table you can read is enough. Our kanban metrics guide defines each one.
Add a sixth item that most founders overlook: export. We return to it below, because it decides how painful your first tool change will be.
What the Kanban Guide says a board must show
The Kanban Guide from Kanban University (version 2025.5, updated May 1, 2025) defines a Kanban board as the visualization of a team’s workflow definition. It calls it essential to make at least the minimum elements of that definition visible on the board. Those elements are the states work passes through, explicit policies for how work moves from started to finished, and control over how many items are in progress.
Three points from the Guide shape a tool choice:
- WIP is controlled, and the board may show it any way the team chooses. The Guide does not require a particular widget. A number printed in the column header satisfies it. So does a count in a spreadsheet cell.
- Policies must be explicit. A policy is a written rule such as “a card enters Review only with a link to the change”. If your tool has no place to write column rules, put them in a pinned card or the board description.
- Four flow metrics are the minimum. The Guide names WIP, throughput, work item age and cycle time, and expects the team to collect and analyze them. It leaves the chart styling to you. A tool that cannot produce all four, even through a file you can open in a spreadsheet, will not support the practice.
The Guide sets no required look, so a plain board that shows the right things beats a polished one that hides age and blocks. See what kanban cards should contain.
Feature checklist: must have, nice to have, ignore for now
Use this table when you compare any free kanban board for startups. Mark each row yes or no after you have tried it, not after you have read about it.
| Feature | Priority | Why |
|---|---|---|
| Rename and reorder columns | Must have | Your workflow will change in the first month. A fixed layout forces workarounds. |
| WIP limit per column, with the count shown | Must have | The Guide expects explicit WIP control. A limit with no visible count gets ignored. |
| Start date and days-open on each card | Must have | Age is the cheapest early warning. Without start dates you cannot compute cycle time later. |
| Blocked flag or marker | Must have | Waiting work looks like progress unless the board says otherwise. |
| Export of cards with dates and column history | Must have | Without it, every future switch loses your flow data. Test this on day one. |
| Free plan limits you can live with | Must have | Check how many users, boards and history days the free plan allows against your next six months of hiring, not today’s headcount. |
| Swimlanes for work types | Nice to have | Helps once you mix feature work, bugs and urgent items on one board. A team of three can use card colors. |
| Automation rules | Ignore for now | Automating a process you have not stabilized hides problems. Add rules after a month of stable columns. |
How the answer changes from 3 people to 15
The same five capabilities hold for a free kanban board for startups at every size. What changes is how much structure you add around them. The sizes below are assumptions to make the pattern concrete, not rules.
| 3-person team | 15-person team | |
|---|---|---|
| Boards | One board for everything. | One board per team of about 5 to 9, plus a light shared view if work crosses teams. |
| Columns | 3 to 5: Backlog, Doing, Review or Waiting, Done. | 5 to 7, with a separate waiting column where handoffs happen. |
| WIP limits | About one card per person in Doing, so 3 for the team. | Limits per team and per stage. One per person plus 1 or 2 for review or wait columns. |
| Card age | Visible in a glance at the board; a daily 10-minute check works. | Needs an aging view or filter, since nobody can scan every card. |
| Blocked work | Flag and talk about it the same day. | Flag, owner and a named reason, so patterns show up. |
| Metrics | Finished per week and card age. | Add cycle time distribution and a service level expectation, such as 85% of items done within a stated number of days. |
Growth is where “free” costs money. A free plan that works for 3 people may cap users, boards or history before you reach 15. Read the limits for each as a question about your hiring plan, then decide whether you accept a forced move at that point. A paid tier later is a normal outcome. A tool you cannot export from is the real risk. A kanban board for small teams should never trap its own data.
The flow arithmetic that justifies WIP limits
A WIP limit is not a mood. It follows from Little’s Law, a result proved by John Little in 1961 for stable systems: average WIP equals average throughput times average time in the system. Rearranged: average time in the system equals average WIP divided by average throughput.
The numbers below are illustrative. Suppose a startup team finishes 6 items a week and that rate stays steady. Only the number of items in progress changes.
Illustrative numbers. Time in system (weeks) = items in progress divided by 6.
The chart makes the case for a board that shows WIP against a limit. With 24 items open, a customer request waits about four weeks on average even though the team is just as busy. Starting fewer things is the cheapest way to deliver sooner. Real throughput varies, so use this to set a first limit, then adjust from your own data.
You can use the same arithmetic to set a first limit. If the team finishes 6 items a week and you want a typical wait of about 2 weeks, total WIP of about 12 is the starting point. Spread it across columns, with a smaller share in the stages where work waits. Our kanban cycle time guide shows how to measure the result.
What it costs to switch tools later
Most startups change their work tool at least once. The cost is mostly the data, not the new setup. These are the items to confirm before you commit to a free board.
- Dates per card. The export should include created, started and finished dates. Without them you lose cycle time for everything finished so far.
- Column history. Some exports list only the current column. You want the date each card entered each column, because that is what shows where work waited.
- File format. A plain table you can open in a spreadsheet is the safest format. A format only the tool itself reads is not an export.
Run the check on day one: create five test cards, move them across columns, flag one as blocked, then export. Open the file. If you cannot rebuild the story of those five cards from it, you will not be able to rebuild a year of real work either. If the export fails, add a spreadsheet and copy each finished card into it weekly. That small habit protects your history in any tool.
A one-week trial plan
Run the trial with real work, one team, one board. A week is long enough to see a block and a finished card, and short enough to abandon.
Create 4 or 5 columns, write one policy per column, and set provisional WIP limits from the arithmetic above. Run the 5-card export test.
Add the current in-progress items with true start dates. Do not tidy; the first honest picture is the useful one.
Start new work only when a column is under its limit. Write down any moment the limit felt painful.
Mark every card that waits on someone outside the team. Note how long each stays flagged.
Sort open cards by days open. Talk about the oldest two before starting anything new.
Export the week’s cards and open the file in a spreadsheet. Compute finished count and average age.
Review the numbers below, then keep, change or drop the tool.
Measure these at the end of the week:
| Measure | How to get it | What it tells you |
|---|---|---|
| Items finished | Count cards that reached Done | Your first throughput figure, the baseline for later weeks. |
| Median age of open cards | Today minus start date, middle value | Whether work is moving or sitting. |
| Oldest open card | Largest days-open value | The first thing to discuss at the next check-in. |
| Days blocked | Total days cards stayed flagged | How much waiting hides behind outside dependencies. |
| Export result | Can you rebuild the five test cards from the file? | Whether switching later is safe. |
No software: a whiteboard or a spreadsheet board
A free kanban board for startups can be a wall or a sheet. A startup that cannot decide between tools can run on a whiteboard or a shared spreadsheet for a month, then pick a tool once it knows what it uses. The Guide asks for visible workflow, explicit policies and WIP control, none of which needs an application.
Whiteboard
- Draw 4 or 5 columns with a limit written in each header, such as Doing 3.
- Use one sticky note per item. Write the start date in the corner.
- Write column policies on the board’s edge in one line each.
- Each Friday, photograph the board and record finished items and open ages in a notebook or a spreadsheet.
Spreadsheet board
One sheet, one row per item. Use these columns:
| Column | Content | Formula or rule |
|---|---|---|
| A: Item | Short title starting with a verb | Text |
| B: Started | Date work began | Entered once, never overwritten |
| C: Stage | Backlog, Doing, Waiting, Done | Drop-down list |
| D: Blocked | Yes or empty, plus reason in E | Drop-down list |
| F: Finished | Date it reached Done | Entered once |
| G: Age | Days open | =IF(F2=””,TODAY()-B2,””) |
| H: Cycle time | Days from start to finish | =IF(F2=””,””,F2-B2+1) |
To see WIP, count rows where Stage is Doing or Waiting. To see throughput, count rows with a Finished date in the last seven days. Add a note cell above the table that reads Doing limit: 3, and color it red with conditional formatting when the count exceeds the limit. Filter by Stage to see the board view, or add a second sheet with one column per stage and move titles by hand if you prefer cards.
Because the sheet is already a table, the export problem disappears. When you move to a tool later, you import the rows and keep every date. For how the same ideas look on a board with swimlanes and policies, see our kanban board explainer.
When training helps
If your startup is adopting kanban for the first time, a structured course can shorten the trial period. AgileFever sells the Team Kanban Practitioner (TKP) course, a one-day live online course whose certification comes from Kanban University. The program page says it covers Kanban principles, practices and how to apply them. As listed on November 5, 2026, it costs $550 in the US store and Rs 14,000 in India before 18% GST at checkout, with one-day batches on November 20, December 4 and December 18, 2026.
Additional discounts are available. Contact us to know more.
The one-week trial costs nothing and works with or without a course. Skip the course if the week already answers your questions.
Questions people ask
Is there a free kanban board for startups that is good enough?
Yes, if it passes five tests: renamable columns, a WIP limit per column, visible card age, a blocked flag and a working export. Try it for one week with real work. If any test fails, a spreadsheet board is a better free option than a weak tool.
What features should I look for in a free kanban tool for startups?
Must-haves are editable columns, WIP limits with visible counts, start dates and card age, a blocked marker and a data export. Comments, swimlanes and built-in charts are nice to have. Automation, time tracking and long integration lists can wait.
Can a startup run kanban without any software?
Yes. The Kanban Guide asks for visible workflow, explicit policies and WIP control, none of which needs software. A whiteboard with sticky notes works for a small co-located team, and a spreadsheet with start and finish dates works for a remote one.
How many WIP limits should a small team set?
Start with one limit per column where work sits. A common start is one card per person in the doing column, plus a small allowance for review and waiting columns. Adjust after a week using your own throughput and card age.
When should a startup move from a free board to a paid one?
Move when a free-plan limit blocks real work: users, boards, history, permissions or reporting. Check the limits before you hit them. If your data exports with dates intact, the move is a routine decision, not a rescue.
What does Little’s Law have to do with choosing a board?
It links WIP, throughput and time per item: average time equals WIP divided by throughput. If you finish 6 items a week with 12 in progress, items take about 2 weeks. A board that shows WIP against a limit helps you hold that number down.
