You are three weeks into the engagement. Your operations lead is in their fourth two-hour workshop. Your IT contractor is on a third call about data export. Your PA has rescheduled three client calls so the founders can attend an all-day strategy day. Nobody put a number on any of it when you signed the proposal.
This is the staff time tax, and it sits across nearly every AI engagement at SME scale. The consultant invoiced for their hours. Your team’s hours are part of the project too. They are just not on a piece of paper anyone signed.
Why does your team’s time never appear on the invoice?
The consulting proposal scopes the consultant’s time, the consultant’s deliverables, and the consultant’s success criteria. It does not scope yours. Your team’s hours are treated as a free input the engagement happens to need, not a budget line that someone has to fund. That treatment is the source of nearly every “we ran out of capacity” complaint after sign-off, and the reason engagements stall in week four when a senior person disappears into back-to-back workshops.
The number is bigger than buyers expect. A typical strategy engagement absorbs 100 to 150 hours of your team’s time, and that is before any implementation has started.
The five places staff time goes
Five activity categories absorb staff time in any AI strategy engagement. Stakeholder interviews. Data access coordination. Internal validation of consultant findings. IT integration prep. Change management workshops. Each one has a typical hour band, and together they add up to a working week or more across the leadership team.
Stakeholder interviews are the largest single category. A consultant doing a credible diagnostic will speak to 8 to 12 people across the business, usually in one-hour sessions, plus follow-ups. That is 20 to 50 hours of senior time over a four-week window, and it includes the founders, the operations lead, the customer-facing leads, and finance.
Data access coordination is the second. Someone has to find, export, format, and supply the data the consultant needs for the diagnostic. In an SME without dedicated IT, that is usually one person with admin access to several systems, working through 10 to 30 hours of export and integrity-check work.
Internal validation is the third. The consultant will produce findings, recommendations, and a draft roadmap. Someone on your side has to read it carefully, sense-check it against the realities of your business, and feed comments back. That is 10 to 40 hours, weighted toward whoever knows the operations best.
IT integration prep is the fourth. If the engagement leads to any pilot or implementation, the IT layer has to be ready: access controls, data residency, audit logging, vendor security review. Even at pilot scale this is 20 to 60 hours, and it usually falls on a contractor or one capable in-house person.
Change management workshops are the fifth. Your team needs context on what is being introduced, why, and how it affects their day-to-day. Workshops, runbooks, and Q&A sessions absorb 20 to 100 hours depending on team size and the depth of the change.
What 100 hours of staff time actually costs
A typical SME senior person costs £50 to £95 an hour fully loaded, depending on role and seniority. The IPSE 2024 survey of UK freelance day rates puts management consultants at £763 a day, IT project managers at £634, and software developers at £575, and internal team rates land in similar bands once on-costs are included. The maths is straightforward.
A 100-hour engagement at £50 an hour is £5,000 of capacity. At £75 an hour it is £7,500. At £95 an hour, £9,500. A 150-hour engagement at the same rates is £7,500 to £14,250. None of this is on the consultant’s invoice. All of it is real spend.
The hidden line in this is that the people whose time is most absorbed are usually the ones whose time is most expensive. The operations lead is usually the deepest into the engagement. The IT contractor is the second deepest. The founders sit in for the strategic conversations. The cost concentrates on the highest-paid, highest-leverage roles in the business, and it pulls them off the work the business hired them to do.
How a good consultant reduces the load
Some consultants design the engagement to minimise staff time, and the difference is visible at proposal stage if you know what to look for. Three things separate the consultant treating your team’s time as cheap from the one treating it as a real resource.
First, structured asynchronous interviews instead of two-hour live sessions. A good consultant offers a written questionnaire with follow-up calls for the non-obvious answers, which can compress a 50-hour interview phase into 20 hours of senior time.
Second, an agreed data access protocol up front. The consultant names the data they need, the format, the export method, and the access roles before the engagement starts. That moves the data work from a discovery surprise to a planned task, and shrinks it by half in most cases.
Third, change management as a partnered workstream rather than a client deliverable. A consultant who treats change management as your problem will hand you a runbook and walk away. A consultant who treats it as part of the engagement will run the workshops, write the comms, and stay in the room when the team has questions.
How to build the time tax into proposal review
You can put the staff time tax into the proposal review without making the conversation adversarial. Two questions surface the answer, and both are reasonable to ask on the first call. Neither requires the consultant to commit to a number; both require them to think about your team’s time as a real cost rather than an assumed input.
Ask which of your roles the engagement will need time from, and how much. A good consultant will name the roles (operations lead, IT, finance, founders), give an hour band per role, and break it down by week. A less good consultant will say “minimal involvement” or “as needed”, which usually translates to half the leadership team’s calendars for two months.
Ask how the consultant has reduced the time burden in similar engagements. A consultant with a good answer will describe the asynchronous interview pattern, the data access protocol, the workshop format. A consultant without a good answer has not thought about your team’s time as a real cost. That answer is the signal you are looking for.
The staff time tax is unavoidable. Budgeting for it explicitly turns it from a hidden surprise into a planned line. Your team’s time is real money, and the engagement either accounts for it openly or charges you for it quietly.
If you would like to talk about how to scope an AI engagement that respects your team’s capacity, book a conversation.
