Engineering consultancies are built on expertise. But the honest question facing every managing partner in 2025 is this: which of the services your firm charges for today will clients still pay for in three years — and which will they expect an AI agent to handle for free?
The Defensible Revenue Audit answers that question before your clients do. It is a three-week, fixed-price engagement that maps every significant billing category in your practice against its automation probability over a 36-month horizon. The output is not a technology assessment. It is a commercial risk document.
Here is what the audit covers:
- Revenue mapping: Every active billing line is categorised by service type, client segment, and fee structure — working from actual invoicing data, not assumptions.
- Automation scoring: Each category is assessed against a defined displacement model: task structure, client price sensitivity, and how easily a competitor — human or AI-native — could substitute it within 12 to 36 months.
- Defensibility report: Delivered as a board-ready document identifying which revenue is safe, which is at risk, what the exposure is in monetary terms, and three specific repositioning options ranked by feasibility.
The audit takes three weeks, involves two dedicated people, and requires no organisational change to proceed. The output belongs entirely to your firm.
What the Audit Consistently Finds
Across the firms we have reviewed, three findings appear with enough regularity that they can be stated as near-certainties. Every firm gets at least one.
- The first is a service line with low automation risk that is being underpriced. Domain expertise and judgment-intensive work — the kind clients cannot easily replicate or delegate — is routinely priced like commodity delivery. The audit identifies where margins should be higher and builds the commercial case to move them.
- The second is a high-margin category that is six to eighteen months from commoditisation. Usually a standardised deliverable type or a reporting function. Clients are beginning to notice. Naming the timeline converts a vague anxiety into a specific action item.
- The third is a client relationship where the consultancy’s value is invisible, and therefore vulnerable. The client pays invoices but cannot articulate what they are buying beyond hours. These are the relationships that AI-native competitors will approach first. The audit surfaces them before they leave.
Why Mapping the Exposure Matters More Than Adopting AI Tools
The consultancies that will lose revenue to AI disruption are not the ones who failed to adopt AI tools. They are the ones who never mapped the exposure and therefore could not reposition.
The distinction is important. Technology adoption is a supply-side decision: it concerns how you deliver work. Revenue defensibility is a demand-side question: it concerns what clients will continue to pay for. Firms that invest in AI tooling without first answering the demand-side question risk automating services that were already becoming commoditised — and doing so faster.
The audit addresses the demand-side question directly:
- Which billing categories depend on judgment, relationships, or contextual knowledge that AI cannot yet replicate?
- Which depend on task execution that is already within the capability of current AI systems?
- Where are clients already forming expectations that will suppress what they are willing to pay?
- Where is your firm’s value genuinely differentiated — and is that differentiation visible to the client?
Answering these questions with data, rather than instinct, is what allows a firm to reposition upstream rather than defend ground it is already losing.
The Process
The engagement runs over three weeks and is structured to minimise disruption to ongoing operations.
- In the first week, we conduct a structured review of all active billing categories in collaboration with a designated internal contact. The goal is an accurate revenue map: what the firm actually charges for, at what margins, and for which client types.
- In the second week, each category is scored against the automation displacement model. This combines assessment of task structure — how routine or judgment-dependent the work is — with competitive analysis of what AI-native or lower-cost providers are already offering, and client-side signals around price sensitivity and expectations.
- In the third week, the findings are consolidated into the Defensibility Report. The report identifies safe revenue, exposed revenue, and the size of the exposure in monetary terms. It presents three repositioning options — typically a pricing adjustment, a service restructuring, and a new offering — ranked by how quickly each can be implemented and what it requires internally.
The report is delivered in a format suitable for partner meetings, board sessions, or client strategy discussions. It contains no recommendations to purchase further services. It is an analysis, not a proposal.
What the Engagement Is Not
The Defensible Revenue Audit is not an AI adoption programme. It does not recommend tools, platforms, or vendors. It does not require your firm to change how it operates in order to generate its findings.
It is also not a transformation engagement. The firms best positioned to act on the findings are those that have done the mapping first — not those that committed to a 12-month programme before understanding what they were defending.
The audit is deliberately narrow in scope because scope is what makes it actionable. A managing partner can commission it without a committee decision.
What Comes Next
The three findings the audit generates each point naturally toward a second conversation. A service line being underpriced suggests a repricing and repositioning exercise. A category approaching commoditisation suggests either a differentiation strategy or an orderly wind-down, depending on margin profile. A vulnerable client relationship suggests a value visibility programme.
None of these conversations require the audit to recommend them. The findings make them obvious. The client initiates them.
This sequencing — audit first, transformation second, chosen by the client based on what was found — is the difference between a vendor pitch and a peer analysis. The audit is the latter.
Find out how we can help — contact us for further information.