Professional Services
You sell expertise. The system should sell it faster than you can.
A professional services firm rarely loses on capability. It loses on the week between the first conversation and the proposal, and on the hours nobody can account for afterwards.
How the business actually runs
Before any software is discussed.
Work arrives through referral and reputation. A partner has a conversation, promises a proposal, and writes it personally — usually from the last one that looked similar. Scope is agreed in email. Delivery happens across documents and calls. Utilisation is a feeling until the month closes, and by then the quarter is set.
- Consultancies
- agencies
- legal
- accounting
- architecture
- engineering practices
Where the money leaks
Four leaks we see in almost every one of these businesses.
Not generic inefficiency — the specific places where revenue, margin or time escapes a professional service business.
- 01
The proposal that took a partner a week
The most expensive person in the firm spends their most valuable hours reformatting a document. Speed and consistency both suffer, and so does the win rate.
- 02
Scope that grew without a record
Every unbilled extra started as a reasonable email. Without a change record attached to the engagement, the margin erodes invisibly.
- 03
Referrals with no system behind them
The firm knows referrals are its best channel and does nothing systematic about them — no tracking of who refers, no timely thank-you, no structured follow-up.
- 04
Utilisation visible only in hindsight
If you discover in week five that a consultant was at sixty per cent in week two, the revenue is already gone.
The system
One connected flow, end to end.
Each stage feeds the next, and every stage is measurable. This is the shape of what we would build — the detail is decided with you.
- 01 Enquiry
- 02 Qualification
- 03 Proposal
- 04 Engagement
- 05 Delivery record
- 06 Renewal
- CRM shaped around engagements, not sales targets
- Proposal generation from reusable components
- E-signature and deposit collection
- Time, scope and variation tracking
- Client portal for documents and status
- Utilisation and pipeline reporting
- Days from first conversation to proposal
- Proposal win rate by service line
- Realised margin against quoted margin
- Utilisation by consultant, in-month
A worked example
Illustrative, with the assumptions stated.
Assume
- Say a twelve-person firm issues 15 proposals a month
- Each takes a senior person four to six hours to produce
- Around one in five engagements runs over scope without a variation being billed
What changes
- Proposals assemble from approved components in under an hour, with the partner editing rather than drafting
- Scope changes are captured against the engagement when they happen, not reconstructed at invoicing
- Referral sources are recorded, so the firm can tell which relationships actually produce work
- Utilisation is visible weekly, while something can still be done about it
Assumptions for illustration. The real version uses your proposal log and timesheets — and it is often the scope leak, not the win rate, that turns out to be the bigger number.
Is this you?
Worth a conversation if any of these are true.
And worth saying plainly when they are not.
- Proposals depend on one or two people and take days
- You cannot say today which engagements are over scope
- Referrals are your best channel and nothing tracks them
- Utilisation is a month-end discovery
If you are turning work away and your people are at capacity, the opportunity is pricing and selection, not faster proposals. We will say so.
Further reading and other industries
Tell us how the business runs today.
We will map where the revenue leaks, show you the system that closes it, and say plainly if the numbers do not justify building anything.
Start a Project