How a 140-Person IT Services Firm Lifted Billable Utilisation From 64% to 72%
Customer Overview
The client is a mid-sized IT services and systems integration firm operating across the UAE and India, with approximately 140 delivery staff and around 40 concurrent client projects at any given time. Revenue sits in the AED 50–60 million range, generated almost entirely from time-and-materials and fixed-price professional services engagements.
Like most services businesses of this size, the firm had grown by hiring. Delivery ran on a combination of spreadsheets, a legacy project tool, and the institutional memory of four delivery managers. It worked until it didn’t.
The Challenge
The leadership team knew something was wrong with delivery economics but could not locate it. Revenue was growing. Margin was not. The three underlying problems turned out to be structural rather than behavioural.
1. Utilisation was invisible until it was too late to act
Timesheets were submitted late and inconsistently — roughly 58% arrived within the required week. Because bench time only became visible during month-end close, a consultant who sat unallocated for three weeks was discovered in the fourth. By then the cost was sunk and the sales pipeline had already moved on.
This is not a small problem. Industry benchmarking by SPI Research found billable utilisation across professional services firms fell to 66.4% in 2025 — the lowest level in the history of their annual survey, against a typical target of around 75%. Every percentage point of unrecovered bench time is pure margin loss.
2. Sales pipeline and delivery capacity were disconnected
Resource allocation lived in a shared spreadsheet maintained by whoever had edited it last. Two project managers could — and regularly did — commit the same senior consultant to overlapping engagements. Meanwhile, deals were being signed with no view of whether the people to deliver them actually existed.
The result was a whipsaw pattern familiar to any services leader: periods of heavy subcontracting at negative margin, immediately followed by periods of unbilled bench.
3. Project margin was only known at closure
Cost-to-complete was estimated informally. Scope creep was absorbed silently by delivery teams who wanted to protect the client relationship, and unbilled overtime was rarely converted into a change request. Projects that ran 15% over budget looked healthy right up until the final invoice.
A fourth pressure was emerging underneath all of this. As generative AI tools absorbed routine analysis, documentation and first-draft code, the junior billable hours that historically filled utilisation began to disappear — compressing exactly the work that used to keep the bench productive.
The Solution
Techvaria implemented a connected delivery and capacity layer on the Zoho platform. The design principle throughout was that utilisation is a data timeliness problem before it is a management problem — if the number arrives three weeks late, no amount of accountability fixes it.
1. Zoho Projects as the single delivery system of record
All active engagements were migrated into Zoho Projects with a consistent work breakdown structure, milestone definitions, and budget baselines at task level. Project templates were built per engagement type so that a new project inherits its structure rather than being assembled by hand.
Critically, every project carries both a sold value and a planned cost, so variance is computed rather than estimated.
2. A timesheet compliance loop that actually closes
Zoho People was configured with automated submission reminders, escalation to the reporting manager after 48 hours, and an approval gate that blocks project closure while timesheets are outstanding. Mobile submission was enabled so that consultants on client site were not dependent on a laptop.
The change here was not the reminder — it was making timesheet completion a blocking dependency for something the delivery manager wanted.
3. A capacity planning layer blending pipeline with commitment
Zoho Analytics was used to blend three previously separate datasets: committed allocations from Zoho Projects, weighted opportunity data from Zoho CRM, and leave and availability from Zoho People. The output is a rolling twelve-week capacity view showing, per skill group, committed hours against available hours against weighted pipeline demand.
This single report replaced the allocation spreadsheet and ended double-booking, because allocation now happens against a live availability number rather than a remembered one.
4. Weekly margin and cost-to-complete reporting
Project profitability moved from a month-end accounting exercise to a Monday-morning delivery review. Each project surfaces actual cost to date, remaining budget, forecast cost-to-complete, and unbilled time flagged for change-request conversion.
The Impact
Measured over two quarters following go-live:
An eight percentage point improvement, moving the firm from below the industry benchmark to comfortably above it.
Within-week submission, which is what makes every other number in this list trustworthy.
Previously unbilled time now identified weekly and converted into change requests before the client relationship made it awkward.
Cost-to-complete variance surfaced while there was still time to act on it.
Unallocated capacity now visible in the current week rather than in the following month’s close.
Driven by the combination of higher utilisation, recovered unbilled time, and reduced emergency subcontracting.
Why This Worked
Nothing in this implementation was technically exotic. The platform capability existed; what was missing was the connection between three systems that each held part of the answer.
Two design decisions did most of the work. First, making timesheet submission block something delivery managers cared about, rather than relying on reminders. Second, building the capacity view against weighted pipeline rather than signed work, so that resourcing decisions could be made before a deal closed rather than after.
It is worth being honest about one limitation. Zoho Projects handles tasks, timesheets, budgets and Gantt scheduling well, but multi-project resource capacity forecasting is not a native strength — it required Zoho People and Zoho Analytics alongside it. Any partner claiming Projects alone solves capacity planning is overselling. The combination works; the single module does not.
Conclusion
Professional services firms are facing a genuine structural squeeze. Utilisation is at a historic low across the industry, while AI tooling is quietly removing the junior billable hours that used to absorb bench capacity. Firms protecting margin through rate increases alone are treating a symptom.
The firms that hold margin over the next few years will be the ones that can see utilisation in the current week rather than the previous month — and act on it while the bench is still fillable.
This case study is representative of a typical mid-market professional services engagement. Client details are anonymised and figures are illustrative of outcomes achievable in comparable deployments. Industry utilisation benchmarks are sourced from the SPI Research 2026 Professional Services Maturity Benchmark.
