A good fit when
- Work arrives continuously and you want a regular line drawn under it.
- "What did we ship last cycle?" is a question somebody actually asks.
- The team is roughly three to thirty people and nobody wants to administer a tool.
The board that grew
When a kanban board
stops being enough.
Nothing broke. The board still works exactly as it did on day one — that is the problem. Thirty cards was a plan. Three hundred is an archive nobody reads, and "what did we actually ship last month?" has no answer that does not involve scrolling.
Free for one workspace, 3 boards and 100 MB · £2.99 incl. VAT per seat per month beyond that · viewers are free
WHAT ACTUALLY BREAKS
Three failures,
all the same cause.
A board is a picture of right now. Once it also has to be the record of everything before now, it is doing two jobs and doing the second one badly.
The Done column becomes a landfill
Everything finished piles up in one place, so the column that should be the most satisfying to look at is the one nobody opens. Archiving hides the work; leaving it makes the board unusable. Neither is a record.
Nothing carries forward on purpose
Unfinished work stays where it is, mixed in with work that never started. The distinction between "we tried this and did not finish" and "we have never touched this" is the most useful one a team has, and a single long-lived board erases it.
Every status question needs a person
What is in flight, how much arrived this week, which stage everything is stuck at — all of it is visible on the board and none of it is countable. So someone counts, by hand, on a Friday.
WHAT LAVER DOES
The board ends,
and says what it did.
Not a bigger board. A board with an end date, which is a different object entirely.
A sprint closes itself
Turn a board into a repeating series — 7, 14 or 21 days, or anything from 1 to 90. When a sprint ends, Laver creates the next board with the same columns, groups and people, moves the unfinished tickets across, and leaves the finished ones behind.
The board you just closed becomes an honest record of what that cycle delivered. Nobody writes it; it is what is left.
SprintsThe new board starts as the remainder
Not a fresh guess — the honest leftovers, already in the columns they were in. The difference between "unfinished" and "never started" survives, because only one of them moved.
Boards and columnsThe counting is done for you
Every board has a stats view: how many tickets sit at each stage, including the stages nobody has reached, a breakdown by label, and how many arrived each week for the last twelve.
Narrower questions get filters — label, priority, assignee, due date, overdue — so the board in front of you answers what has slipped and what nobody owns.
Under those counts the same page measures how work has been moving: cycle time and the slowest 15% of it, how many tickets were delivered each week and by whom, how old the open work is and which column it is queueing in.
Measured, not forecast. All of it is read back from what the tickets actually did, so there is no velocity model here and no burndown chart pretending to predict next month.
HONEST FIT
Where this helps,
and where it will not.
If a bigger board is genuinely what you need, Laver is the wrong answer and we would rather you knew now.
Not what this is
- No swimlanes and no calendar. There is a timeline off the board header, whose bars you can drag to reschedule, but it can only draw the tickets that have dates on them. Groups exist; they are filters, not a second dimension.
- No estimates, so no points, no velocity and no burndown. The stats view reports what happened — counts, cycle time, throughput and queueing — and never what was planned.
- No epics. A board can define its own custom fields, tickets can be linked as blocking, related or duplicate, and automation rules can move and label them as the cycle runs — but none of those is a hierarchy.
- Every sprint adds a board, so a long-running series grows the sidebar.
READY WHEN YOU ARE
Draw a line under it.
Turn one board into a cycle, and let the closed ones be the record you keep meaning to write.
Create your workspaceKeep reading
- Project management for small teams — the whole product in one concrete week.
- Project management without the setup — if configuring the tool became the project.
- Sprints — exactly what moves when a cycle ends.