KyroTask
Language
SOFTWARE & PRODUCT AGENCIES

Work like a sprint team, bill like an agency

Sprints, story points, dependencies and velocity on one side; a client portal, billable hours and an invoice on the other — both on the same task.

Sprints and the API are on the free plan
The sprint tool and the client report are two products
The same task is in your backlog and in your client’s portal. Nothing is copied between them.
See how it works
Blocking work is noticed late
You link dependencies between tasks; an attempt to create a cycle is refused, and blocked work carries its own signal on the board.
Estimates are given without looking back
Velocity and burndown, plus cycle time and estimation accuracy — commit from your own history.
See how it works
Nothing connects a task to its PR
Paste the pull request, branch or commit URL onto the task; the type is read from the address and it sits beside the work.
It does not talk to your own tools
Scoped API keys, signed webhooks and an MCP server — your AI agent can open tasks and write comments.
See how it works
Fixed-price work loses money quietly
Hours, rate cards and budgets, with cost frozen at close and a profitability report on top.
See how it works

From sprint planning to paid invoice

  1. 01

    You plan the sprint from your backlog with story points, dependencies, and issue types. What was committed is locked as the sprint starts.

  2. 02

    The team works and logs billable hours; a published task moves in the client portal at the same time, with its PR link sitting beside the work.

  3. 03

    The sprint closes, velocity and burndown are plotted from real data, and the period’s billable hours convert directly into an invoice.

Why the numbers hold

Most velocity charts draw every sprint at 100%, because closing a sprint moves unfinished work out and only the finished work is left to count. Not here:

What was committed is stamped up front
The points and task count committed at the start are recorded. What was delivered is stamped separately at close; they are two different numbers.
An unmeasured sprint is a gap, not a zero
A sprint that ran before this stamp has no commitment record, and the chart leaves it empty — filling it with what was delivered is exactly the lie being avoided.
Cycle time separates the queue from the work
Lead time counts from when the task was opened, cycle time from its first move. A task that never moved is left out of the cycle average rather than folded into it.
Done is kept as a moment
A task is stamped when it enters a done column, and the stamp is removed if it comes back out. The report reads when work finished, not where the card sits now.

What we do not do

These are the things most often assumed on the engineering side. Here they are before you sign up, not after:

  • There is no GitHub or GitLab integration. Dev links are URLs you paste by hand: no app to install, nothing syncs by itself, and PR status is not read back.
  • CI, code review and deployment are not here. This tracks the work; it does not replace your own toolchain.
  • There is no ready-made import from another tracker. You can script a migration against the public API.
  • API keys on the free plan: 1, read-only; a write scope needs Pro.
  • Cycle time, estimation accuracy and time series are on Pro. Sprints, story points, dependencies and velocity/burndown work on the free plan.

Frequently asked questions

Could we use this instead of our issue tracker?

Sprints, backlog, story points, issue types, dependencies, velocity and burndown are all here. We wrote the comparison — including the part where the other tool wins — on its own page, and we would rather you read that.

Can a client see inside our sprint?

Only the tasks you publish to them. The portal is a separate authentication scheme; internal comments, hours, rates and costs stay behind the wall.

Can our AI agent connect to it?

Yes. The product exposes an MCP server, and with a scoped API key your agent can list projects and tasks, create tasks and write comments. The OpenAPI document is public and needs no account.

Can we see the margin on fixed-price work?

The profitability report (revenue − cost) is on Business, and cost rates can be entered on every plan; the hours every report reads come from time tracking, which is Pro. Cost is frozen when a log closes, so a later raise does not rewrite a past margin.

Set up your next sprint here

No credit card. 14 days of full Pro, then it drops to the free plan.