TeamKazi

Is this project still making money?

Project management for firms that bill for their people’s time. Every project carries a live profit and loss — so you find out you are losing money in week three, not at handover.

Built for professional services firms who bill for time and live or die by margin.

Week three, not handover

Watch the margin move

Labour, expenses, contract value and earned value reconcile to the same numbers as the work happens. When the margin drifts from the approved baseline, the variance is on the screen — while there is still time to do something about it.

Look at the last row. Rather than forecasting a number it cannot stand behind, TeamKazi says which two timesheets it is waiting on. No flattering defaults.

A demonstration of TeamKazi's project financials: across four weeks the project margin falls from 22.4% to 8.6%, with a cost variance of −8.2% against baseline attributed to a labour overrun. The forecast at completion is withheld, because two timesheets are still awaiting approval. Figures are illustrative.

The problem

Milestones are not margin

Most project tools tell you what is late. Very few tell you what late has just cost you, and fewer still tell you in time to act on it.

  • Late is visible. Costly is not.

    Every project tool will tell you a task has slipped. Almost none will tell you what that slip has just done to your margin.

  • The plan takes days to build

    A signed scope document gets turned into a work breakdown by hand, task by task, before any actual work starts.

  • Numbers that will not survive a client meeting

    Figures that disagree between modules, and a zero on screen where the honest answer was "not yet calculable".

How it works

Built around the money, not the checklist

Three things TeamKazi does that a task list cannot: price the plan, build the plan, and defend the numbers afterwards.

01

Know your margin, not just your milestones

A live P&L on every project

Labour cost, expenses, contract value and earned value — reconciled to the same numbers, updated as the work happens.

  • Live profit and loss per project, not a month-end reconstruction
  • Fixed-price and time-and-materials billing models
  • Contract value and cost budget kept separate, so revenue and spend never get confused
  • Earned Value Management: CPI and SPI, cost variance and schedule variance
  • Expenses tracked against the project alongside labour
  • Lock the approved plan as a baseline — variance is measured against what was signed off, not against a target someone quietly edited
A practice principal at a sunlit desk looking up from a printed report with quiet satisfaction, rolled drawings, a scale rule and a marked-up schedule in front of him.
02

Let the AI do the setup

Start from a document, not a blank page

Hand it a requirements document and get a structured work breakdown back in minutes rather than days — then edit it before anything is committed.

  • Upload an SRS or scope document and get a draft breakdown of phases, tasks and subtasks
  • You review and edit the draft before it becomes the plan
  • Daily brief: what needs your attention today, across every project
  • Project analysis — a plain-English reading of where a project actually stands
  • Portfolio insight — the patterns running across all projects at once
  • Meeting notes turned into assigned work
Two colleagues either side of a large printed plan marked up with coloured notes, one annotating it with a pen, both pleased with how it is coming together.
03

Numbers you can take to a client meeting

No flattering defaults

When TeamKazi cannot calculate something honestly, it says so and explains why — instead of showing you a zero and letting you find out later.

  • Portfolio-wide KPIs, burn, health distribution and profitability on one screen
  • Project cards ranked by what actually needs attention
  • Health status shown together with the reasoning behind it
  • Drill from portfolio to project to task without losing your place
  • Cross-project AI insight over the whole portfolio
Two colleagues at a meeting table going through a figure together on a tablet, an open notebook and papers in front of them.

Dependencies

Which tasks actually decide your finish date

Link the tasks that must happen in order and TeamKazi works out the critical path for you. Everything else has float — room to slip without moving the completion date.

Circular dependencies are blocked before they can be saved, weekends are excluded from the calculation, and every task shows what it is blocked by and what it blocks.

A Gantt chart of a 70-day project schedule. 5 of the 7 tasks sit on the critical path and decide the finish date: Survey & site handover, Structural drawings, Approvals, Fit-out, Snagging & handover. The remaining tasks carry float and can slip without moving the completion date.
  1. 1.0 Survey & site handover
  2. 1.1 Structural drawings
  3. 1.2 Services layout 4d float
  4. 2.0 Approvals
  5. 2.1 Procurement 6d float
  6. 3.0 Fit-out
  7. 3.1 Snagging & handover
Decides the finish date 5 tasks · 70 days

On the critical path Has float

Under the hood

Everything underneath

A complete project management system in its own right — the part the financials sit on top of.

Projects and the Control Centre

Everything about a project, on one screen.

  • Seven views per project: Overview, Tasks, Schedule, Team, Documents, Meetings and Financials
  • Health status at a glance, with the reasoning behind it
  • Phases, milestones and a full risk register
  • One place instead of five tools

Tasks that reflect how work really runs

Structured like a project plan. Fast like a to-do list.

  • Board and list views, drag and drop, group by anything
  • Work Breakdown Structure numbering (1, 1.1, 1.1.1) applied automatically
  • Nested subtasks with two-way roll-up — finish the children and the parent moves; complete the parent and the children follow
  • Task detail drawer with assignees, hours, notes, attachments and rich text
  • An analytics bar that filters the board when clicked: at risk, overdue, unassigned, by person

Dependencies and the critical path

Know which five tasks decide whether you finish on time.

  • Link tasks that must happen in order, with circular dependencies blocked before they can be saved
  • Automatic critical path calculation
  • Gantt chart with dependency arrows, float bars and weekends excluded
  • “Blocked by” and “Blocks” shown on every task
  • Automatic slip detection, with the downstream impact

Timesheets and approvals

Approve time knowing exactly what it costs you.

  • Week calendar with drag-to-fill time entry
  • Auto-suggested entries from task activity, so people log time they would otherwise forget
  • Submit by date range or rolling week
  • Manager approval showing person, hours and cost together
  • Rich notes and file evidence attached to entries

Team, workload and capacity

See who’s drowning before they tell you.

  • Per-project team roster with hours and cost contribution
  • Workload view across people — who is overloaded and who has room
  • AI assignee suggestions based on current load and history

Obligations, documents and milestones

The things that aren’t projects, but still can’t be missed.

  • Personal to-dos, plus delegation with notification
  • Recurring items for regular obligations — “file VAT by the 15th” generates itself and keeps nagging until it is done
  • Per-project document library, with attachments on tasks and time entries
  • Milestone tracking against the plan, and an invoice raised from a completed milestone

If you bill for time

Approve the hours with the cost in view

Most approval screens show a name and a number of hours. TeamKazi shows the person, the hours and what those hours cost — so the approval is a financial decision made with the financial consequence on the same screen.

Entries can be dragged into a week calendar, are auto-suggested from task activity so people log time they would otherwise forget, and carry notes and file evidence. It works in any browser, including your phone.

A desk at the end of the working week in low evening light: an open notebook of handwritten entries, a pen, a cooling mug and a closed laptop.

Proof

Honest by design

TeamKazi's credibility rests on being the tool that does not flatter you. That is a design decision with consequences you can check.

  • Seven project views, all functional — no “coming soon” tabs
  • Critical path verified against a hand-computed textbook schedule before release
  • Financial figures reconciled across three modules — Team, Earned Value and P&L agree to the shilling
  • Where a number cannot be calculated, TeamKazi reports why instead of showing zero

Security

  • Every organisation’s data isolated at the database level, enforced by the database itself — not by application code that could have a bug in it
  • Modern authentication with session security and idle timeout
  • Role-based access

Bring a project that went wrong

We would rather walk through a real job of yours than send a brochure. Bring one that lost money and we will show you the week the numbers would have told you.

Request a Demo
Back to top