Industry · Professional services

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.

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 change it to yours.

Where it goes wrong

What usually breaks first.

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.

Timesheets arrive late and get guessed

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

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.

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.

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 & integrations

Microsoft 365Power AppsPower AutomateSharePointAzure AD SSOReact + TypeScriptNode.jsPostgreSQL
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 is a design problem, not a training problem. 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?

A written scope agreed before we start, a working build in your hands by week two, demos every Friday so you steer it, and source code plus infrastructure handed over at the end.

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).