A plan that knows who’s free, and checks itself every week.

Stint turns the estimate your client approved into a plan for the people who’ll do the work, around their time off and public holidays. Then a short weekly follow-up checks that the plan still holds, and the hours go straight to Jira.

Stint project overview with phases, a plan by role and a time-off requestStint estimate in days per role, with version 3 approved and earlier versions lockedStint weekly follow-up showing what changed, blockers, decisions and tasksStint week of hours with drafts and a confirmation that hours were saved to Jira

What your team gets.

Everything from the first estimate to the last hour logged, in one place.

Estimates with versions

Days per role for every requirement, exported to PDF or Excel. Approve a new version, and the old one locks.

A plan from the estimate

Phases, people and dependencies come straight from what was approved. Drag a bar, and everything after it moves.

Time off already in it

People ask, team leads approve, and the plan works around public holidays and days off on its own.

A follow-up that ends on time

Each week, a queue of projects showing only what changed, with blockers, decisions and owners kept beside the plan.

Hours straight to Jira

Everyone logs time by week or by month, and nothing reaches Jira until they press save.

Your roles, your steps

Software, events, construction, marketing or consulting. Your roles become the estimate’s columns.

Built for your clients’ data.

Estimates, rates and people’s time off are sensitive, so Stint treats them that way.

Access is by invitation only, with separate roles for admins, managers and members.
Passwords are checked against known breaches, and an account locks after repeated failed attempts.
You can see every signed-in session and end any of them, and an audit log records every sensitive action.
Each space’s data is kept apart from every other space.
No tracking pixels, and data is only kept for as long as its retention period says.
On your own servers, the backups go where you decide and updates go in when you choose.

Questions teams ask.

Do I need UnflowHub™ to use it?

No. Stint works on its own.

Is it only for software teams?

No. Any team that estimates work and schedules people against it can use it. Events, construction, marketing and consulting teams plan the same way, and you set your own roles and project steps.

Can we run it on our own servers?

Yes. It comes as one Docker image with a Postgres database and runs inside your network. You decide where the backups go and when updates are installed.

Does it work with Jira?

Yes. Each person connects their own Jira account and logs hours by week or by month. Nothing reaches Jira until they press save.

What happens when the estimate changes?

You approve a new version and the plan follows it. The previous version is locked, so you can always see what was agreed and when.

How does it handle time off?

People ask for time off in Stint, their team lead approves it, and the balance updates. Company days off and public holidays are already in the plan, so nobody gets scheduled on a day they’re not working.

Is our data kept apart from other companies’?

Yes. Each space has its own data, access is by invitation only, and there are no tracking pixels.

What’s coming next?

Sharing clients, roles and public holidays across all of an organization’s spaces, exporting all your data in one go, a time-off calendar people can check without an account, and an assistant that turns a written request into a first draft of the plan. Tell us what your team needs. Requests from teams using Stint go first.

Want software that looks this good?

Tell us how your business really runs. The team behind this will build yours to the same standard.