Professional Services
In a services business the numbers that matter — utilisation, margin, recoverability — are assembled from time, scope and billing. When those live in separate systems the numbers arrive late and get argued with. We join them.
What this covers
Pipeline to engagement
A won opportunity that becomes a resourced engagement without re-keying.
Time and expense
Capture people will actually complete, on the device they have.
Resourcing
Who is available, who is committed, and what that does to margin.
Project delivery
Scope, milestones and change requests tracked against the commercial agreement.
Billing
Fixed price, time and materials and retainers, invoiced from what was recorded.
Practice reporting
Utilisation and recoverability available before the month closes.
Who this is for
Consultancies
Where utilisation and quality are in constant tension.
Agencies
Retainers and projects running side by side against the same people.
Legal and accounting
Recorded time, matter economics and strict billing rules.
Engineering practices
Long projects with staged commercial terms.
How we work
People who have done it before
Teams that have worked in this setting, not a generic squad reading the brief for the first time.
One team, start to finish
The people who design it are the people who build it and the people who answer for it afterwards.
Working software early
Something running in weeks, so the direction is judged against a real thing rather than a document.
Sector experience, not sector slides
What we bring to the first meeting
We have worked in this sector, so the first conversation is about your constraints rather than an introduction to the domain. Where we have not done something before, we say so.
Talk to us
What we promise
- A named team you can reach, not an account manager relaying questions
- A working version early, and every fortnight after that
- Written estimates with the assumptions and the risks stated
- Your code, your data and your accounts, yours throughout
- A direct answer when something is late or will not work
How it runs
Understand
Two weeks with the people doing the work, mapping what actually happens rather than what the process document says.
Prove
One narrow slice built and put in front of real users, to test the approach before it is expensive to change.
Build
Delivery in fortnightly increments, each one usable, each one reviewed with you.
Run
Support, monitoring and improvement — or a handover to your team, documented.
Common questions
No. The system should follow your commercial model, including the awkward parts of it.
More of them will if it takes seconds and reflects the work they actually did. Compliance is a design problem before it is a management one.
Yes, and the rate policy is agreed explicitly rather than assumed.
Time capture and billing first, in weeks. Resourcing and reporting build on the data those produce.
Is this the right fit?
Tell us what you are trying to do. If we are not the right people for it, we will say so.
Get in touch