
Why Big 4 Consultancies Can't Solve Operational Workflows
Strategy consultants excel at organisational design but struggle with operational systems that turn data into action. Most mid-market distributors need faster pricing decisions, not transformation roadmaps.
Why Big 4 Consultancies Can't Solve Operational Workflows
Introduction: The £2M Strategy That Changed Nothing
A £75M building materials distributor paid Deloitte £2.3M for a digital transformation roadmap. Eighteen months later, they still price concrete mix in Excel. The 147-page strategy document sits in a SharePoint folder that nobody opens.
This isn't a failure of execution. It's a structural mismatch between what consultancies sell and what operational teams need. Strategy consultants excel at organisational design, but struggle with the daily decisions that determine margin, efficiency, and customer experience.
Operational workflows need systems that turn data into action. Pricing algorithms, fulfilment routing logic, inventory allocation rules. These systems must integrate with existing platforms, work with real data, and improve measurable outcomes. Consultancy deliverables - frameworks, roadmaps, governance structures - don't make decisions faster or more accurate.
The consultancy model profits from perpetual engagement, not finished platforms. This creates incentives to recommend complex, multi-year programmes rather than focused operational improvements that clients can own and operate independently.
Why Strategy Consultants Don't Build Operating Systems
Big 4 consultancies approach technology selection through vendor relationships, not operational requirements. PwC has partnerships with Salesforce and Adobe. Accenture promotes Microsoft and SAP solutions. These relationships generate significant revenue streams - implementation fees, ongoing support contracts, and vendor referral commissions.
This creates a fundamental bias problem. When a distributor needs faster pricing decisions, the consultant recommends a £500K Salesforce Commerce implementation plus 18 months of change management. The operational reality - a pricing decision that currently takes three days could be automated in six weeks with a focused application - gets lost in transformation rhetoric.
Strategy consultants understand business process in theory but lack depth in specific operational contexts. They can map out quote-to-cash workflows on whiteboards but haven't spent hours debugging why trade pricing matrices break when customers order mixed pallets. Operational workflows require domain knowledge that comes from building and maintaining systems that process real orders, not designing them on slides.
The breadth vs depth problem compounds over time. Consultants rotate between projects and industries. A pricing specialist at Deloitte works on insurance algorithms, then retail markdown optimisation, then B2B distribution. Each project involves learning enough to create recommendations, not enough to build production systems that handle edge cases and scale with business growth.
When we implement Dynamic Pricing Intelligence, the first question is always about existing pricing cycles - approval workflows, update frequency, margin protection rules. These operational details determine system design. Strategy consultants focus on high-level transformation opportunities but miss the implementation complexity that determines success or failure.
The Implementation Reality: Years vs Quarters
The typical Big 4 timeline follows a predictable pattern: six months for strategy development, another twelve months for vendor selection and contracting, then 24-36 months for implementation and change management. Total project duration: three to four years from initial engagement to measurable outcomes.
Focused operational applications work on a different timeline. A fulfilment routing optimization - the kind that reduced delivery costs by 18% for a building materials distributor - went live in eight weeks. The pilot covered one product category and two depots. Full deployment across seven locations took another twelve weeks.
The difference isn't project management efficiency. It's scope and ownership. Big 4 projects attempt comprehensive transformation across multiple business functions. ERP upgrades, process reengineering, organisational restructuring, and cultural change management. Each component introduces dependencies, approval cycles, and integration complexity.
Operational decision applications solve specific problems with focused capabilities. Pricing decisions. Route optimization. Inventory allocation. These applications connect to existing systems without requiring wholesale replacement. A demand forecasting model doesn't need new ERP software - it needs clean transaction data and clear rules for when predictions override manual judgement.
Implementation speed directly affects business impact. The Yorkshire logistics network that saved £180K annually through route optimization started seeing results in week three of the pilot. By month six, the system had processed 40,000 deliveries and optimised routes for seasonal demand patterns. A multi-year transformation programme would still be in the vendor selection phase.
Our clients typically see measurable improvements within 90 days of deployment. Pricing accuracy, fulfilment efficiency, inventory turns. These metrics improve because the systems are focused on specific decisions, not comprehensive business transformation. You can optimise pricing algorithms without restructuring sales teams or implementing new CRM systems.
Cost Analysis: £500K in Slides vs £50K in Software
The true cost of Big 4 engagements extends far beyond professional services fees. A typical digital transformation programme includes strategy development (£200K-£400K), vendor selection advisory (£100K-£200K), implementation support (£300K-£800K), and ongoing change management (£150K annually). Total cost over three years: £1.2M-£2M excluding software licensing and internal resource allocation.
Platform costs add another layer. Salesforce Commerce Cloud starts at £120K annually for mid-market implementations. Adobe Commerce Enterprise begins at £180K. SAP Commerce is £200K+ for distributors processing significant B2B volume. These platforms require ongoing customisation, integration work, and specialist development resources that consultancies provide at premium rates.
Internal resource allocation multiplies these costs. Big 4 projects consume senior management time for steering committee meetings, milestone reviews, and change management initiatives. A £60M distributor typically dedicates 20-30% of their operations director's time to transformation programmes. That's £40K-£60K annually in opportunity cost for a single resource.
Compare this with focused workflow support platforms. Custom AI Development projects typically range from £40K-£80K for pilot implementations, scaling to £120K-£200K for full deployment. These applications integrate with existing systems, so no ERP replacement or data migration required. Internal resource requirement: one week of subject matter expert time for requirements gathering, plus ongoing feedback during pilot phases.
The ROI difference is significant. Our clients achieve 3-8% margin improvement within six months of deployment. For a £50M distributor, that's £1.5M-£4M annual impact from systems costing £100K-£200K to implement. Big 4 programmes deliver broader organisational benefits but struggle to demonstrate specific operational improvements that justify multi-million pound investments.
Hidden costs matter in both approaches. Consultancy projects include change management, training development, and process documentation that operational platforms don't require. But operational platforms need ongoing refinement, performance monitoring, and capability expansion as business requirements evolve. The difference is ownership: you control platform evolution rather than depending on consultant availability and vendor roadmaps.
The Platform Ownership Problem
Consultancy implementations create long-term dependencies that undermine operational flexibility. When your pricing logic sits inside Salesforce Commerce Cloud, you need Salesforce-certified developers to modify rules. When demand forecasting runs on Adobe's algorithms, you can't tune models based on local market conditions without vendor involvement.
Platform ownership means controlling your everyday work logic. If trade pricing needs adjustment for seasonal suppliers, you modify rules directly rather than raising change requests with external developers. If fulfilment routing algorithms need refinement for new delivery constraints, you update parameters based on operational feedback, not vendor best practices.
The data mesh approach exemplifies this ownership principle. Bytebard Data Mesh connects existing systems - ERP, commerce platform, WMS, CRM - without forcing migration to consultant-preferred vendors. Your transaction data, customer information, and inventory records remain in current systems while AI-powered decision tools access clean, standardised data feeds.
Big 4 consultancies promote vendor consolidation as operational simplification. Single platform for commerce, CRM, inventory management, and financial reporting. This creates surface-level integration but deep vendor lock-in. When business requirements change, you're constrained by vendor capabilities rather than operational needs.
Operational workflows require continuous refinement based on business data, market conditions, and performance feedback. Generic best practices - the foundation of consultancy recommendations - don't account for local market dynamics, customer behaviour patterns, or supplier relationships that affect day-to-day operations. Your pricing algorithms need to reflect your cost structure, competitive position, and customer mix, not industry benchmarks.
Platform ownership also enables gradual capability expansion. Start with pricing decisions, add fulfilment optimization, then integrate demand forecasting as confidence builds. Consultancy programmes attempt comprehensive transformation from day one, creating complexity that obscures which improvements actually drive business value.
When You Actually Need Consultants (And When You Don't)
Big 4 consultancies excel at problems requiring organisational expertise: merger integration, regulatory compliance, market entry strategy, and capital allocation frameworks. These challenges need breadth of experience across industries, deep understanding of governance structures, and ability to manage complex stakeholder environments.
Operational workflows fall into a different category. Pricing cycles, fulfilment routing, inventory allocation, and customer segmentation are domain-specific problems that benefit from deep technical capability rather than broad strategic perspective. You need systems that integrate with existing platforms and improve measurable outcomes, not frameworks that require cultural transformation.
The build vs buy decision depends on internal capability and timeline requirements. Building operational artificial intelligence internally makes sense for organisations with strong development teams and 12-18 month implementation timelines. Buying focused platforms works when you need measurable improvements within quarters, not years.
But there's a third option that consultancies rarely mention: rent-and-customise approaches that combine platform capabilities with operational control. Workflow Mapping identifies which decisions need automation, which need human oversight, and which can be eliminated entirely. This creates a focused roadmap for operational improvement without comprehensive business transformation.
Consultants add value when operational improvements require organisational change: new roles, revised incentive structures, or governance models that span multiple departments. But most operational workflows can be improved through better systems without reorganising teams or redefining responsibilities.
The key distinction is between transformation and optimisation. Transformation changes how businesses operate. Optimisation makes existing operations more effective. Most mid-market distributors need optimisation - faster decisions, better accuracy, lower costs - not fundamental business model changes that require multi-year transformation programmes.
Strategy consulting works for strategic problems. Operational workflows need operational systems. The fundamental mismatch isn't capability or experience - it's business model and timeline alignment.
Consultancies profit from ongoing engagements, complex implementations, and vendor relationships. Clients need focused improvements, measurable outcomes, and platform ownership. These incentives create different approaches to technology adoption and operational improvement.
The evidence supports focused operational applications over comprehensive transformation programmes. Faster implementation, lower cost, measurable ROI, and platform ownership that enables continuous improvement based on business requirements rather than consultant availability.
Learn more about Workflow Mapping & Architecture.
Common questions
Why do Big 4 consultancies struggle with operational workflows, and what kind of solutions do they typically offer?
Big 4 consultancies struggle because they excel at organizational design but lack depth in specific operational contexts, often recommending complex, multi-year programs. They typically offer frameworks, roadmaps, and governance structures, which don't directly make decisions faster or more accurate, as seen with the £2.3M Deloitte strategy that left a distributor pricing concrete mix in Excel.
What is the typical timeline and scope for Big 4 consultancy projects compared to focused operational applications?
Big 4 projects typically have a three to four-year timeline, including six months for strategy, twelve months for vendor selection, and 24-36 months for implementation, aiming for comprehensive transformation. In contrast, focused operational applications, like a fulfilment routing optimization that reduced delivery costs by 18%, can go live in eight weeks and achieve full deployment in another twelve weeks.
How do vendor relationships influence the technology recommendations made by Big 4 consultancies?
Vendor relationships create a fundamental bias, as consultancies like PwC (Salesforce, Adobe) and Accenture (Microsoft, SAP) have partnerships that generate significant revenue. This leads them to recommend expensive, comprehensive solutions, such as a £500K Salesforce Commerce implementation, even when a focused application could automate a pricing decision in six weeks.
What is the cost difference between Big 4 consultancy engagements and focused operational software solutions?
Big 4 engagements can cost £1.2M-£2M over three years for strategy, vendor selection, implementation support, and change management, excluding software. In contrast, focused operational applications like Dynamic Pricing Intelligence can deliver measurable improvements within 90 days, with clients typically seeing results from software solutions that are significantly less costly than multi-million-pound transformation programs.
Themes
Neil Boughton
Co-founder & Technical Director
Neil is a co-founder of WithPraxis. With more than 30 years in technical architecture and systems delivery, he sets the engineering direction for every WithPraxis platform and implementation. He specialises in the unglamorous but critical work, data pipelines, system integration, and making AI models perform reliably in production environments rather than just in demos.
Connect on LinkedInMore in this cluster
Continue exploring this topic

Commerce operations insights and applications
Agentic AI Observability: Detecting When Your Autonomous Systems Are Operating on Bad Data
Agentic systems fail quietly. A pricing agent drifts 2% below target margin over eight weeks, processing 4,200 decisions before anyone notices. Margin leakage: £87,000. The agent didn't crash or throw errors—it just made slightly wrong decisions, consistently, for two months. Gartner predicts 40% of agentic AI projects will be cancelled by 2027, primarily due to silent degradation that compounds into operational disasters.

Operational workflow improvement
Why Fortune 500 Supply Chain AI Fails at Mid-Market: The Complexity Mismatch Problem
Fifty-seven percent of supply chain leaders cite data quality as the primary barrier to AI adoption. Not model accuracy. Not cost. Data quality. Most mid-market distributors have data spread across five to seven systems with no single source of truth. You cannot train an AI model on conflicting data. The unglamorous work of master data management, integration, and governance must come first.

Operational workflow improvement
Inventory Decisions Under Uncertainty: When AI Forecasts Conflict With Safety Stock Rules
Deploying demand sensing AI without retiring legacy safety stock policies creates a hidden cost: dual everyday work. Inventory planners second-guess AI recommendations, override autonomous reorder points, and maintain manual guardrails 'just in case.' This article quantifies the cost of running both systems, explains why most deployments fail at the governance layer, and outlines the workflow clarity required to let one system own inventory decisions.
Related Articles

Operational workflow improvement
Why Fortune 500 Supply Chain AI Fails at Mid-Market: The Complexity Mismatch Problem
Fifty-seven percent of supply chain leaders cite data quality as the primary barrier to AI adoption. Not model accuracy. Not cost. Data quality. Most mid-market distributors have data spread across five to seven systems with no single source of truth. You cannot train an AI model on conflicting data. The unglamorous work of master data management, integration, and governance must come first.

Operational workflow improvement
Inventory Decisions Under Uncertainty: When AI Forecasts Conflict With Safety Stock Rules
Deploying demand sensing AI without retiring legacy safety stock policies creates a hidden cost: dual everyday work. Inventory planners second-guess AI recommendations, override autonomous reorder points, and maintain manual guardrails 'just in case.' This article quantifies the cost of running both systems, explains why most deployments fail at the governance layer, and outlines the workflow clarity required to let one system own inventory decisions.
Was this article useful?
