Professional Services
The enquiry is in one system, the project is in another, the time is in a third and the invoice is in a fourth. We put the engagement on one record, then let the system do the drafting and the comparing that nobody has time for.
What it costs today
Every one of these is a place where two facts about the same engagement live in two places and nothing brings them together while there is still time to act. Six patterns turn up in almost every firm we map.
It arrives by email, by referral, through the website and through a partner nobody told. Whether it becomes an opportunity depends on how busy that person was on the day it came in.
A pipeline that describes who is organised rather than what is real.The firm has delivered the same shape of work a dozen times and none of that reaches the next scope. Somebody rebuilds the phases, guesses the effort and prices it from memory of the last one.
Two days of senior time per proposal, and a scope nobody can check.The project was quoted at 240 hours and took 290. Both numbers exist, in two systems, and nothing brings them together while there is still time to do anything about it.
SPI Research put average project overrun at 10.7 percent in 2025.Consultants fill timesheets on Friday for a week they half remember, which is the point at which the short tasks stop existing and the long ones get rounded.
Billable utilization fell to 66.4 percent in 2025, the lowest SPI has recorded in nineteen years.The bid went in, the client went quiet, and the reason lives in a conversation somebody had on a call. SPI put the average bid-win rate at 48.1 percent, so roughly half of all that effort produces nothing anyone learns from.
The same losing bid, submitted again next quarter.Who is available, from when, and at what utilization is a question the firm answers by asking around. On-time delivery sat at 73.8 percent in 2025 against a five-year average of 76.
Work promised on capacity the firm did not have.The four benchmark figures above are from SPI Research's Professional Services Maturity Benchmark, which surveys more than 500 firms. They are here to say that these are industry conditions rather than a problem with your firm. What they cannot tell you is which of them is costing you the most, and that is what the mapping is for.
The operating pattern
Controlled delegation is the whole design, and everything below this band is an application of it. Repeatable work goes to the system. What the client pays, what the firm commits to and what the client is told goes to a person.
An enquiry, a scoping call, a proposal, a project set up from that proposal, a timesheet and an invoice. The same six shapes, on every engagement, assembled by hand each time.
Reading an enquiry, matching it to a company you already have, scoring it against your own rules, pulling the engagements it resembles, drafting a scope and setting up the project from what was agreed. None of it is judgment.
The fee, the commercial terms, whether to bid at all and what the client is told are decisions with risk and relationship in them. They reach a person with the work already assembled.
See it run
The enquiry gets matched to the CRM, checked against the work the firm has already done, qualified against the firm rules and scoped from the service catalogue. The fee is left for a partner.
Connected systems
Enquiry Halcyon Utilities Operating model review
Result
Completed automatically
Requires a person
The fee, and whether the firm wants this work.
Engagement partner
Connected systems
Enquiry Unmatched sender Three-line email, no organization
Result
Completed automatically
Requires a person
Whether this enquiry is worth chasing at all.
Business development
Connected systems
Enquiry Ardent Logistics Systems selection, fixed fee requested
Result
Completed automatically
Requires a person
Whether to decline, or to counter with a different shape.
Engagement partner
This demo uses fictional data. The workflow gets configured around your systems. Build a workflow like this
The work
The order matters more here than in most sectors. The record comes before the reporting, because a system cannot compare an estimate to an actual until both are attached to the same engagement.
The first draft written from work you have already delivered
Reads the enquiry, matches it to the company already on record, scores the fit against your own written rules, pulls the engagements that resemble it with their actual hours rather than their quoted ones, and drafts a scope with the assumptions stated as assumptions. The fee field stays empty.
Data: enquiries, your CRM and your delivered engagements. Human: a partner prices it and approves the scope.
The four systems that hold one engagement, joined up
The enquiry, the opportunity, the project, the time and the invoice on one record with one reference. This is the unglamorous half of the work and it is the half that decides whether any of the rest is possible, because a workflow can only compare an estimate to an actual if the two are on the same object.
Data: your CRM, project system and accounting. Human: project leads own the scope and the change.
The status report as a by-product of the work
Progress, hours, budget position and open risks assembled from the systems the project already runs in, drafted into the format the client expects and the format the partner expects. Two audiences, one set of facts, neither of them retyped.
Data: project, time and budget records. Human: the project lead approves anything the client sees.
Margin, win rate and overrun, by the thing that causes them
What the firm actually makes by service line, by client type and by who sold it. Which enquiries convert and which ones the firm should stop bidding for. This one comes last because it stands on the record the second workflow builds, and it is worthless before that exists.
Data: your own delivery and financial records. Human: partners decide what the firm stops selling.
Most firms want the fourth one and have to buy the second one first. Margin by service line is the report every partnership asks for, and it cannot be produced honestly until the estimate, the actual, the change and the write-off are on the same record. A dashboard built before that is a picture of four systems disagreeing.
The decisions
These get agreed with the partners and whoever owns IT before a build starts, and between them they decide what the workflow is allowed to be. Two of them are about your clients rather than about you.
What counts as working. Accepted output against your own baseline is the proof. The baseline gets taken before the build exists, and afterwards the same work is measured against it with the review burden counted openly, because a system that produces plenty and has to be checked twice has saved nothing. How we measure AI work sets out the method.
How it starts
This sector is the one where the order is worth stating plainly, because the thing most firms want to buy sits on top of the thing most firms have not built.
Proof
The approach on this page comes out of these engagements. One is a professional firm mapped end to end, and three are the design patterns the workflows above are built on.
A professional services firm running on standalone databases that did not talk to each other, with document handling done by hand. We audited the operation, mapped the gaps and built a four-pillar roadmap the firm could take to any implementer.
An intake questionnaire becomes a profile, a classification and a recommendation document, with the scoring on fixed rules and every output waiting in an approval queue. The same design as the proposal workflow above: drafted by a system, released by a person.
Territory research a team used to do by hand now lands every morning without anyone triggering it. The pattern behind the enquiry workflow: gathering a person would do badly at nine in the evening, done before the day starts.
A phased program that put capability ahead of deployment: role-based training first, then pilots in research, client engagement and reporting, then the roadmap to scale it. A professional firm learning to supervise the work rather than just run the tool.
Begine Fusion is a Zoho Authorized Partner working across Canada, the United States, the United Kingdom and Nigeria, with a team on the ground in Nigeria since 2013. Every engagement is published in full, including what was measured and what was a design target. The full set is on our work.
Fit
The work pays back when the firm is big enough that nobody holds the whole picture in their head any more. If that is not where you are, the right column says what to do instead.
Where to start
The same five offers every other client buys, scoped to a firm that sells time and has to know what it cost. Find the line that sounds like yours.
No price is quoted on this page. A sector is not an offer and does not have a price of its own. What a firm here pays follows which of those six lines is the real one and how much of the record already exists. Working out which line is yours is what the first call is for.
Questions
The seven that decide whether a build is worth starting, answered before the proposal rather than inside it.
No, and it is built so that it cannot. A comparable engagement tells you what work of that shape actually took. It says nothing about what this client should pay, because that is a judgment about risk, relationship, appetite and what else is in the pipeline. The fee field on a drafted proposal is empty and stays empty until a person fills it in.
Usually not. The common problem is that the two hold different versions of the same engagement and nothing reconciles them, which is a connection problem rather than a software problem. If the mapping finds a system that genuinely cannot carry the work, we will say so and give you the reasoning rather than a recommendation.
Some of your client contracts already decide what tooling may touch their material, and those terms win. Which engagements are in scope, which are excluded and what stays masked are settled before the build, written down, and shown to a client who asks. We would rather scope a smaller workflow than one you cannot describe to your largest client.
It reduces the problem rather than solving it. Time captured against a record that already knows what the person was working on is a correction rather than a reconstruction, and that is a different task on a Friday afternoon. What it will not do is make people record work they have decided not to record, and any partner who has run a firm knows the difference.
It can show you realised margin by service line and by client type, after write-offs rather than before them, and win rate by where the work came from. Most firms find at least one service line that looks profitable at the quote and is not at the invoice. What to do about that is a partnership decision, and it usually involves more than the numbers.
A baseline is taken before the build exists: current time to a proposal, review effort, rework, and the gap between estimate and actual on the work in question. Afterwards the same work is measured against it with the review burden counted openly, because a system that produces plenty and needs checking twice has saved nothing.
The record usually comes first and runs five to nineteen weeks depending on how many systems come into scope, sequenced so something is live well before the end. A workflow on top of it is four to six weeks. Ahead of both sits the mapping, which is two to three weeks and produces a decision you can act on whether or not we do the build.
Thirty minutes with a partner, whoever runs delivery and whoever owns the numbers is enough to name the first workflow, the record it needs underneath it, and the baseline it gets measured against.
