Why does a 3-month consulting project take 3 months?
It is not because the analysis requires 3 months of thinking.
A typical strategy engagement — market assessment, competitive analysis, financial modeling, strategic recommendations — contains perhaps 40-60 hours of actual analytical work. The kind of deep thinking that requires senior expertise and cannot be rushed.
The other 700+ hours are coordination.
Meetings to align the team. Approval chains to review drafts. Onboarding new team members mid-project. Reformatting slides to match the template. Waiting for the engagement manager to be available for a checkpoint. Scheduling with stakeholders across three time zones.
60% of total consulting project time goes to coordination, not analysis.
This article explains why traditional consulting timelines are long, how AI changes the equation, and what realistic timeline compression actually looks like.
The coordination tax
Research from Asana shows that knowledge workers spend 60% of their day on coordination activities, leaving only 13% for strategic planning and 27% for skill-based work.
In consulting, the coordination overhead is even worse. A typical 8-person consulting team spends time on:
Team coordination: Daily standups, weekly team meetings, bi-weekly checkpoint reviews, draft review sessions, formatting alignment meetings
Client coordination: Weekly steering committee meetings, stakeholder interviews, interim presentations, feedback incorporation sessions, final presentation rehearsals
Internal approvals: Engagement manager reviews, partner reviews, quality assurance reviews, legal reviews (for certain deliverables), compliance checks
Knowledge transfer: Onboarding new team members, offboarding departing team members, documenting decisions for continuity, transitioning work between project phases
Administrative overhead: Timekeeping, expense reports, status updates to firm leadership, staffing requests, resource allocation discussions
The work that actually advances the project — research, analysis, synthesis, drafting — happens in the gaps between these coordination activities.
40% of time in meetings is wasted. 67% of meetings are rated as failures by executives. Unproductive meetings waste over $37 billion per year.
But the real problem is not that meetings waste time. It is that large teams require exponentially more coordination.
Brooks' Law and the communication explosion
Fred Brooks, in his classic 1975 book The Mythical Man-Month, formulated what is now known as Brooks' Law:
"Adding manpower to a late software project makes it later."
The reason is mathematical. Communication paths scale as N(N-1)/2* where N is team size.
| Team Size | Communication Paths |
|---|---|
| 2 people | 1 path |
| 3 people | 3 paths |
| 5 people | 10 paths |
| 8 people | 28 paths |
| 10 people | 45 paths |
| 15 people | 105 paths |
A 10-person consulting team has 45 communication channels that must be managed, aligned, and kept in sync. A 2-person team has 1 communication channel.
Every communication path is an opportunity for:
- Misalignment on assumptions
- Lost context in handoffs
- Delayed decisions waiting for alignment
- Rework due to conflicting interpretations
- Meetings to reconcile different approaches
Brooks' Law has been validated repeatedly in studies spanning 7,200 software projects. Adding personnel yields declining marginal benefits and increases negative impacts on quality.
The #1 predictor of whether work takes longer than expected is amount of cross-team coordination.
In consulting, the dynamic is identical. A partner, two engagement managers, and five analysts working on a strategy project spend more time coordinating with each other than they spend doing analytical work.
The small team advantage
Amazon's Two-Pizza Team Rule states that no team should be larger than can be fed by two pizzas (typically 5-10 people).
But even that might be too large. Research shows that 2-person teams completed a task in 36 minutes while 4-person teams took 52 minutes — 44% longer for the same task.
Why are small teams faster?
Minimal communication lines: A 2-person team has 1 communication channel. Decisions happen in a 5-minute conversation, not a 60-minute meeting with 8 people.
No approval chains: In a large team, work flows from analyst → consultant → engagement manager → partner. Each layer adds review time. In a 2-person team (or a solo practitioner), the person doing the work is the person making the decisions.
No onboarding tax: Large teams experience turnover mid-project. A new analyst joins in Week 3. Someone gets pulled to a higher-priority engagement in Week 5. Each change requires knowledge transfer. Small teams avoid this.
Direct accountability: In a large team, responsibilities fragment. The analyst who built the model is not the person presenting to the client. The engagement manager who scoped the project is not the person doing the research. In a small team, accountability is clear and direct.
The combination of small team size + clear goals + autonomy produces dramatically faster outcomes.
What AI replaces
The traditional consulting model used large teams because certain types of work require parallel effort:
Parallel research: To benchmark 30 companies, you need 3 analysts working simultaneously. One person doing it sequentially would take 3x longer.
Simultaneous workstreams: To build a financial model, research regulatory constraints, and interview stakeholders, you need multiple people working at the same time.
Volume work: To synthesize 50 industry reports and extract key themes, you need several people reading in parallel.
First-draft generation: To draft a 100-slide deck, you need multiple people creating content simultaneously.
AI eliminates the need for large teams by handling the parallel work that used to require multiple people.
AI can research 30 companies simultaneously. A senior partner directs the AI to extract competitive positioning, financial performance, and strategic initiatives from 30 companies. The AI processes them in parallel. The partner synthesizes the findings. What used to take 3 analysts 1 week now takes 1 partner with AI 4-6 hours.
AI can run multiple workstreams simultaneously. The same AI infrastructure can build financial model scenarios, scan regulatory documents for constraints, and draft interview guides at the same time. The partner reviews and refines each workstream. What used to require coordinating 3 people now requires 1 person directing AI.
AI can process volume at scale. Synthesizing 50 industry reports used to require 2 analysts reading for a week. AI can extract themes, identify patterns, and flag outliers in a few hours. The partner applies strategic judgment to the synthesis.
AI can generate first drafts. The 100-slide deck that used to require 3 people formatting and drafting for 2 weeks can be prototyped by AI in hours. The partner refines the narrative, strategic logic, and key exhibits.
The work that used to justify an 8-person team for 12 weeks can now be performed by 1-2 senior practitioners with AI infrastructure in 4-5 weeks.
Realistic timeline compression
Let us be honest about what compresses and what does not.
A typical 12-week consulting engagement breaks down as:
| Activity | Traditional Time | With AI |
|---|---|---|
| Scoping and kickoff | 1 week | 1 week |
| Stakeholder interviews | 2 weeks | 2 weeks |
| Research and benchmarking | 3 weeks | 1 week |
| Analysis and modeling | 2 weeks | 1 week |
| Synthesis and drafting | 2 weeks | 0.5 weeks |
| Internal review and iteration | 1 week | 0.5 weeks |
| Final presentation and handoff | 1 week | 1 week |
| Total | 12 weeks | 7 weeks |
What compresses:
- Research and benchmarking: AI handles parallel scans of industry data, competitive intelligence, and prior work
- Analysis and modeling: AI prototypes models, runs scenarios, and generates exhibits
- Synthesis and drafting: AI generates first drafts of narratives, slide structure, and key messages
- Internal review: Fewer review cycles because the senior partner is doing the work directly, not reviewing junior output
What does NOT compress:
- Scoping: Understanding the client's actual problem requires judgment and conversation
- Stakeholder interviews: People need time to think, provide feedback, and align internally
- Final presentation: Clients need time to absorb recommendations, ask questions, and make decisions
What disappears entirely:
- Coordination overhead: No daily standups for an 8-person team
- Onboarding new team members mid-project
- Approval chains and multi-layer reviews
- Reformatting work to align with team standards
The realistic compression is 12 weeks → 7 weeks for a typical strategy engagement. That is 42% faster, driven by AI eliminating parallel work and small teams eliminating coordination overhead.
Could it be faster? If the client is decisive and stakeholder alignment is tight, perhaps 5 weeks. But 5 weeks is not the norm.
The honest pitch is not "instant strategy" — it is "half the time, with no waste."
What happens to the consultants?
Accenture laid off 22,000 employees in 2025 as part of an $865 million AI-driven restructuring. At the same time, Accenture grew its AI/data workforce from 40,000 (2023) to 77,000 (2025).
The consulting industry is not shrinking. It is restructuring.
Firms are shedding junior analysts whose primary function was volume work — data extraction, slide formatting, first-draft writing — and hiring AI-savvy senior practitioners who can use AI infrastructure to deliver what used to require teams.
"AI tools can now perform tasks that previously required armies of junior consultants — data analysis, code generation, process mapping, and even strategy formulation. What once took teams of analysts weeks can now be accomplished in hours or days."
The pyramid is collapsing. The question is whether firms will replace it with "senior partner + AI" or try to preserve the leverage model with "junior analysts + AI".
Early evidence suggests the former. The best consulting outcomes come from pairing AI with deep domain expertise, not from augmenting junior labor.
The bottom line
Consulting projects are slow because large teams create coordination overhead that dominates schedules.
60% of time goes to coordination, not analysis. Brooks' Law proves that adding people makes projects slower, not faster. 2-person teams complete work 44% faster than 4-person teams.
AI eliminates the work that previously required large teams — parallel research, simultaneous workstreams, volume synthesis, first-draft generation.
The result: 12-week engagements compress to 7 weeks. The compression comes from two sources: AI handling parallel work and small teams eliminating coordination waste.
Speed does not mean cutting corners. It means cutting waste.
At Pertama Partners, we operate on this model: 1-2 senior practitioners with AI infrastructure. No 8-person teams. No coordination overhead. No approval chains.
The work that used to take 12 weeks now takes 5-7 weeks. Not because we skip steps. Because we eliminate the time spent coordinating people who should not have been on the project in the first place.
Weeks, not months. Without the waste.