Here is the number that should bother you: senior consultants at professional services firms spend roughly 30% of project time on formatting, boilerplate, and deliverable assembly work that a well-structured system could handle in minutes. That is not a small inefficiency. On a 10-person team where senior staff bill at $200 to $300 per hour, that percentage represents hundreds of thousands of dollars per year in margin that gets absorbed by work that produces zero client value.
The problem is not that your consultants are slow. The problem is that your firm is asking expensive, experienced people to do the same low-leverage work, from scratch, over and over again, on every engagement.
This post covers what the data actually says about why this happens, what firms that have fixed it did differently, and what a realistic path forward looks like for an operations lead who is tired of watching the same problem repeat itself.
The Professional Services Problem
Most consulting firms have some version of the same structural issue. Work product exists, but it exists in the wrong places. Past proposals live in someone’s email. Frameworks from a successful engagement are buried in a folder nobody remembers. The methodology deck from two years ago was updated once and then siloed on the partner’s laptop.
When a new engagement starts, the default move is to open a blank document and start over. Not because the team wants to recreate everything from scratch. Because finding, evaluating, and adapting prior work takes almost as long as building fresh, especially when nobody is sure which version is current or whether the client context still applies.
This is what the hidden cost of productivity leaks in consulting actually looks like in practice. It is not one obvious drain. It is a coordination tax spread across every project: document hunting, context switching, rework, and the slow bleed of senior attention toward junior tasks.
The result is a firm where deliverable quality varies based on who has the most time that week, where clients get different output quality depending on which team they draw, and where institutional knowledge walks out the door whenever a senior person leaves.
What Industry Professionals Are Actually Saying
Community discussions among consultants and professional services operators consistently surface the same frustrations. The biggest time drains are not the client work itself. They are the coordination overhead wrapped around the work.
Forums and professional communities consistently call out administrative overhead (expense reports, timesheets, manual reporting), meetings that generate no decisions, email and scheduling loops, and the specific pain of searching across email, shared drives, and Slack to find documents that should be instantly accessible.
One pattern that comes up repeatedly is what you might call the anticipation tax: time lost waiting on replies from partners, clients, and colleagues, then absorbing last-minute direction changes that force rework on deliverables that were nearly complete. According to Reddit’s consulting community, this waiting and rework cycle is one of the most significant hidden costs in the day-to-day reality of consulting work.
The other recurring theme is the gap between what exists in theory (templates, playbooks, shared repositories) and what people actually use in practice. Repositories that require manual searching, lack context about when and how past materials were used, and are not integrated into the workflow where work actually happens get ignored. People default to starting fresh because the overhead of reuse feels too high.
This is not a technology problem. It is a workflow design problem. The technology is only useful if it is embedded in the moment when someone is about to open a blank document.
By The Numbers: Industry Benchmarks
The data behind these community observations is consistent across multiple sources.
| Metric | Finding | Source |
|---|---|---|
| Firms citing knowledge reuse as top challenge | 72% | Industry research cited in consulting AI assessments |
| Proposal prep time reduction from codified knowledge | ~50% | Consulting AI assessment data |
| Senior consultant time on non-billable formatting | ~30% of project time | Community and operations research |
| Top-performing firms that systematically harvest project artifacts | Identified as key differentiator | SPI Research Professional Services Maturity Benchmark |
| Firms automating status reporting and workflow steps | Correlated with quality consistency | AI-in-professional-services industry summary |
SPI Research’s Professional Services Maturity Benchmark identifies deliberate, consistent harvesting and sharing of project assets, artifacts, best practices, tools, templates, and lessons learned as a measurable differentiator between high-performing and average professional services organizations. The firms that do this consistently show better profitability and higher client satisfaction scores.
The benchmark also notes that quality consistency depends on governance, not just repositories. Having a shared drive full of past proposals does not produce consistent deliverables. Mandatory search requirements during planning, reuse requirements in proposal development, and quality gates that verify teams considered prior work do.
For operations leads, the takeaway is clear: the infrastructure problem is solvable, but it requires process change, not just a new tool.
Strategy 1: Recover Senior Consultant Time from Formatting and Boilerplate
The 30% figure is not inevitable. It is a symptom of a specific workflow design choice: asking the most expensive people on the engagement to handle deliverable assembly because there is no alternative.
The fix starts with separating the thinking work from the production work. Senior consultants should be reviewing, refining, and adding insight to deliverables. They should not be building slide structures, formatting tables, or hunting for the right logo placement.
Practically, this means three things.
First, map where senior time actually goes during deliverable creation. Most firms that do this exercise find that 40 to 60% of the time attributed to deliverable work is actually formatting, version management, and document assembly rather than strategic content creation.
Second, build production workflows that generate a complete first draft before a senior person touches the document. This can be as simple as a structured intake process that a junior team member completes, triggering a template that produces a formatted draft. Or it can be more sophisticated: an AI system that pulls from past projects, applies your firm’s templates, and produces a first draft that senior consultants review rather than create.
Third, set explicit role expectations. If your senior consultants believe their job includes formatting deliverables, they will keep doing it. Formalizing the review-not-build model requires explicit direction from leadership.
RunFrame builds AI-powered deliverable generators that handle this production layer: pulling from past project archives, applying firm templates, and outputting structured first drafts. The senior consultant’s job becomes editing and elevating rather than building from nothing. This is one approach. The core principle applies regardless of the specific tool you choose.
Strategy 2: Standardize Deliverable Quality Across the Firm
Quality variance is one of the most consistent complaints from operations leads at consulting firms, and it is also one of the most damaging to client relationships. When a client compares deliverables across two engagements and notices that one looks like a $50,000 project and one looks like a $200,000 project, it creates questions that are hard to answer.
The root cause is almost always the same: deliverable quality is currently a function of who created it and how much time they had, not a function of firm standards.
Fixing this requires three components working together.
Defined quality standards: What does a complete, high-quality deliverable look like for each major deliverable type your firm produces? This needs to be documented in enough detail that someone creating a deliverable for the first time can hit the standard without guessing.
Templates that enforce structure: Templates are not just formatting tools. They are quality enforcement mechanisms. A well-built template makes it harder to produce a bad deliverable than a good one, because the structure guides the creator toward completeness.
Review gates before client delivery: Quality governance means nothing without a checkpoint where someone with authority over quality standards reviews deliverables before they go out. This does not have to be a senior partner review of every document. It can be a checklist-based peer review that takes 15 minutes and catches the most common quality gaps.
SPI Research’s maturity benchmark data supports this approach directly: high-performing professional services organizations combine standardized processes with ongoing measurement and governance around adherence. The firms that measure quality consistency are the firms that maintain it.
For more on how top firms operationalize this, see what top professional services companies do differently with AI.
Strategy 3: Build a Knowledge Reuse System That People Actually Use
The 72% figure on knowledge reuse as a top operational challenge reflects a specific failure mode: most firms have tried to solve this with a repository, and repositories do not work well enough on their own.
Academic research on consulting knowledge reuse confirms what practitioners already know from experience. Senior staff create generalizations from past experience that are useful, but junior consultants often cannot apply those generalizations without context. A slide deck from a past engagement without the narrative context of why decisions were made is often less useful than it looks.
The same research shows that knowledge reuse works best when users can contact the original author and share a common perspective. The repository is a starting point, not the endpoint. Person-to-person support complements the artifact.
This suggests a reuse model built around three layers.
Layer 1: Structured capture at project close. Every engagement closes with a brief structured debrief that documents key decisions, what worked, what did not, and which deliverables are worth reusing. This takes 30 to 60 minutes and is done while the context is fresh. Without this step, artifacts accumulate without the context that makes them reusable.
Layer 2: Retrieval embedded in the workflow. The search for prior work needs to happen before the blank document opens, not after. This means a mandatory check-in step at project kick-off where the team identifies the three most relevant prior engagements and pulls the applicable artifacts. Making this a required process step, rather than an optional good practice, is what separates firms that reuse from firms that intend to.
Layer 3: Expert access alongside artifacts. When someone retrieves a prior deliverable, they should be able to identify who created it and ask questions. A knowledge system that routes artifact access to include the original author’s contact creates the person-to-person support that research identifies as critical for successful reuse.
The biggest time wasters for consultants consistently include document hunting and knowledge fragmentation. A well-designed reuse system eliminates the search problem by making prior work findable, contextual, and connected to the people who can explain it.
Implementation Roadmap
For an operations lead ready to move on this, here is a sequenced approach that does not require a large technology investment upfront.
Weeks 1 to 4: Audit and baseline. Map where senior consultant time actually goes during deliverable creation. Interview three to five senior consultants and shadow one engagement kick-off. Identify your top five most frequently created deliverable types. Document what a complete, high-quality version of each looks like.
Weeks 5 to 8: Template and governance build. Create enforced templates for each high-frequency deliverable type. Define the review gate process. Assign quality review ownership. Establish the project close debrief protocol.
Weeks 9 to 12: Reuse system activation. Catalogue the last 12 to 18 months of project artifacts using the debrief format you defined. Tag them by engagement type, industry, and deliverable type. Add a mandatory prior work review step to your project kick-off checklist.
Weeks 13 to 20: Automation layer. Evaluate whether an AI-assisted first draft tool makes sense for your volume and deliverable types. Pilot on one deliverable type, measure time savings and quality consistency, and expand based on results.
This sequence works because it builds the process infrastructure before adding automation. Automating a broken process produces bad outputs faster. Fixing the process first means that when you add automation, it runs on solid ground.
If you want to know where your firm sits before starting, the AI Readiness Scorecard at RunFrame is a 10-minute assessment that maps your current state across the dimensions that matter most for professional services operations.
How RunFrame Approaches This
RunFrame’s work with professional services firms starts from the same audit-first principle described above. Before any automation is built, the team maps existing workflows, identifies the highest-leverage deliverable types, and catalogues available knowledge assets.
The deployable system that results combines three components: a deliverable generator that pulls from past project archives and applies firm templates to produce structured first drafts, a knowledge retrieval layer that surfaces relevant prior work at the moment it is needed in the workflow, and a governance layer that tracks which templates are being used, which artifacts are being reused, and where quality gaps appear.
This is not a generic AI tool dropped into your existing chaos. It is a configured system built around how your firm actually operates, deployed on the AI operating system model that RunFrame uses across professional services clients.
For firms that want ongoing management rather than a one-time build, fractional AI operations keeps the system current as your templates evolve, new project types emerge, and your knowledge base grows.
The goal is not to replace senior consultant judgment. It is to make sure that judgment is applied to the work that actually requires it, rather than absorbed by the production work that a well-built system can handle.
The Operational Case for Moving Now
The firms that will have a structural advantage in professional services by 2026 are not the ones with the most talented consultants. Talent is roughly distributed across the market. The advantage goes to the firms that have figured out how to systematize knowledge reuse, standardize deliverable quality, and recover senior time from low-leverage work.
That is an operations problem, not a talent problem. And it is solvable with the right combination of process discipline and targeted automation.
If your senior consultants are still spending 30% of their project time building deliverables from scratch, your firm is funding your competitors’ efficiency advantage. The data on what fixes this is clear. The implementation path is well-defined. The remaining variable is whether your firm decides to act on it.
Start by understanding where you actually stand. Take the AI Readiness Scorecard to get a clear picture of your current state across knowledge management, deliverable workflows, and automation readiness. Or if you would rather talk through your specific situation first, book a discovery call and we can work through what makes sense for your firm’s scale and deliverable mix.
You can also see how the deployment process works end to end on the how it works page, or review the full picture of what RunFrame builds for professional services firms.
The 50th time your team recreates the same deliverable does not have to happen.
