Software for firms that sell time and cannot see where it goes.

Utilisation, timesheets, project profitability, retainer burn, and approvals. The operational layer spreadsheets stop supporting somewhere around the twentieth person.

Professional services

Every professional services firm hits the same wall. Up to about twenty people, a partner holds the whole picture in their head and a spreadsheet fills the gaps. Past that, the picture stops being accurate and nobody notices for two quarters, usually until a project that felt profitable turns out not to have been.

The closest system we have shipped is a full ERP for a multi-office law firm: time capture, project and matter economics, a four-step invoice approval, document control, and partner reporting. The mechanics are the same for a consultancy, an agency, an accounting practice, or an architecture studio. Only the vocabulary changes, and we learn yours in the requirement study before anything is built.

Where it goes wrong

What usually breaks first.

  1. 01

    Nobody knows which projects are actually profitable

    Revenue is tracked, cost of delivery is estimated, and the two never meet in the same report until year end.

  2. 02

    Timesheets arrive late and get guessed

    Friday afternoon reconstruction from calendar entries. The data is technically complete and practically fiction.

  3. 03

    Retainer burn is invisible until the client complains

    Nobody sees that a fixed-fee engagement crossed its budget in week three, because the number is only assembled at month end.

  4. 04

    Approvals bounce around email

    Scope changes, invoices, and hiring approvals live in threads. There is no queue, no escalation, and no record of the decision.

  5. 05

    Reporting is a monthly manual rebuild

    Someone senior spends two days a month assembling a deck from four exports. That is the most expensive spreadsheet in the business.

Typical stack and integrations
  • Microsoft 365
  • Power Apps
  • Power Automate
  • SharePoint
  • Azure AD SSO
  • React + TypeScript
  • Node.js
  • PostgreSQL
Questions we get

Straight answers.

We already pay for Microsoft 365. Can you build on that?
Usually yes, and it is often the right answer. Power Apps and Power Automate cover a lot of internal tooling well. We will tell you honestly when a workflow has outgrown low-code and needs a real application behind it.
How is this different from buying a PSA tool?
A packaged PSA tool assumes a delivery model. If yours matches, buy it, and we will say so. Firms come to us when their model does not match: unusual retainer structures, mixed fixed-fee and time-and-materials, or approval chains a vendor will not configure.
Will our team use it?
Adoption comes down to design. We build the two or three actions people perform daily to be faster than the workaround they use now. Everything else follows from that.
What does the engagement look like?
It starts with a requirement study. We sit with your team, document how time, projects, and approvals are handled today, and agree the scope and timeline in writing. Then we design and build, test it with your people, train them, go live, and stay on for support after launch.
Book a discovery call

Tell us what's slowing your professional services team down.

A 30-minute discovery call. We map the process, point out the easy wins, and outline a clear plan (no obligation).