Every sprint has a line.
Jira can't see it.
Capaline puts capacity, money and hours on one board — before you promise the date, not after you miss it. Two-way with Jira. Your clients read it for free.
Pays, connects, runs — on the same stack as the products you already pay for.
Tickets fit. People don't.
Jira counts tickets. Capaline counts the three things a tracker never does — and shows them on the same row as the task.
Who is carrying twice their plan — by person, by role, by project. Before the sprint starts.
Cost at your own rates, live. Estimated, burned and closed on one line — not in the invoice.
Hours logged by a person who was never put on the task. Capaline finds them and adds her.
One board. Every question a delivery lead gets asked.
Sprints
Scope, risk, progress, money and hours by role — in one strip above the table. Tasks won't fit? You see it as a number, not as a surprise.
What does your next sprint cost?
Four numbers you already know. The margin is not a drawing — it is the same model that runs the board.
The hours nobody planned are still hours you pay for.
Every person on a task carries two numbers: what you planned and what they logged. When they drift apart, the row tells you — and when somebody works on a task they were never put on, Capaline finds them.
- 0Planned zero, logged twenty. Owen was on the task with no hours. The chip turns amber.
- +Never assigned, still worked. Ruby was not on the task at all. Her Jira worklog brought 20 h — she appears in italics, dashed, marked “found”.
- €Estimated vs burned, per project. 285 h planned, 283 h logged. €19 347 expected, €19 211 spent.
Pay for the people who plan.
Start with one real sprint.
Connect Jira, pick a sprint, set your rates. Sixty seconds later you know what it costs and who will not make it.
Start free — 14 days