Project tools store work. They don’t make anyone do it.

There is nothing for them to learn. The accountability layer asks your team for exactly one thing: reply when they get a message. No timesheets, no status forms, no weekly self-assessment, nothing extra typed in, because the numbers compute from tasks, due dates and completions that already exist. Everyone gets a home screen with their own numbers on it, the same numbers their manager sees, on the same day. Setup includes a live training session and a written team manual.

No. It reads what is already true: a task moved, a due date passed, a piece shipped. There are no screenshots, no keystroke logging, no location tracking, no idle timers and no timesheets. Nobody fills in a form about themselves. Everyone sees their own numbers on their own home screen, the same numbers their manager sees. The work it does is stopping your reliable people from carrying the quiet ones invisibly, which is how you lose the reliable ones. Nothing on the system messages your team on its own, either. Every check-in is drafted, read by a person, and sent by a person, under their name.

The stack is yours structurally, not contractually. It runs on your server, you hold the environment file, the volumes and the nightly database dumps, and restoring from them is a documented procedure that has been run for real. The agreement puts it past argument: if the monthly service stops for 90 days, the source code is released to you under a perpetual internal use licence.

In your own Postgres database, in your own Docker volume, on the machine you choose: Nairobi, Europe, your own office. Nightly compressed dumps, 14 kept on a rolling window. No other company is in your database, so there is nothing to share and nothing to leak sideways. AI calls leave your server when you switch them on, and the key stays server-side, never in a browser.

No. Flat per instance within your tier's team size. Hiring your fifteenth or fortieth person changes nothing on the invoice, and every price is printed on this page.

Then you already know the shape of the problem. A board stores the work and shows you what exists. It has no opinion about who is delivering, it never tells you that a designer has gone quiet, and it never chases anybody, so the chasing is still you, twice a week, from memory. That missing layer is what this is: the colour computed from real delivery, the per-person record nobody typed, one shared list of what is on fire, and a chase that takes one click and stays on the record.

So did the agency this was built for, and it moved in one pass: 1,415 tasks, 1,494 comments, 97 custom fields and the docs. Re-runs gap-fill and never overwrite: on a live instance, 30 values the team had typed by hand came through a full re-import untouched, 30 before and 30 after. Migration is included on Standard, and it is verified with you before anyone switches over.

No. A client portal is scoped to the lists you put in it, so your client sees their own calendar and their own comments, and no spaces, no other clients, nothing internal. Their view also translates your internal pipeline into plain language, so a status named UPDATE REQUIRED reads as In review on their screen. They watch their own work land, which is most of why they stop emailing you for updates.

Count the hours you spent last week asking people where things were, and the meetings that existed to produce a status. Multiply by what an hour of your time is worth. You are already paying for this, in the wrong currency, and the invoice is a week of your attention rather than a line in the accounts. The prices are printed above, flat per instance, and hiring a person never raises them.

You could. The software is the small part. What takes the time is deciding what counts as behind, and making it hold on real data without insulting anyone: half or more of a person’s open work overdue, or more late than on-time deliveries in the last fourteen days, and grey when there is nothing to judge, so no claim is made about someone who has had a quiet fortnight. Every release round is gated on automated checks, with 37 test suites in the repository that run against a running stack before anything reaches a client. What you are buying is the rules and the record, not a login.

It installs as a real app on iPhone and Android, with genuine push notifications, a five-tab mobile layout and a calendar built for small screens. Laptops install the same way from Chrome or Edge.

No. AI features switch on per instance, calls go out when someone uses them, and nothing in your workspace trains a model. Leave the key blank and the whole workspace runs without it.