Executive Premise. The CEO’s question is not simply, “Can we grow?” It is, “Can the next dollar of revenue travel through the business at an attractive incremental margin without consuming disproportionate cash?”

The growth paradox

Revenue growth is usually interpreted as evidence that the strategy is working. In middle-market manufacturing and distribution, it can also be the event that exposes every weakness in the operating model. Volume rises faster than capacity. Product and customer complexity expand faster than management routines. Inventory grows to protect service, while service still deteriorates. Overtime, premium freight, rework and concessions become the unofficial capacity plan.

The financial pattern is familiar: sales are up, but gross margin is flat or down; EBITDA dollars increase less than expected, while EBITDA margin contracts; working capital absorbs cash; and the leadership team explains the variance as a temporary consequence of growth. Sometimes it is temporary. More often, it is a structural signal that the commercial engine and the operating system are no longer synchronized.

That distinction matters because the wrong response compounds the problem. Adding people, inventory, warehouse space or equipment may increase nominal capacity while preserving the underlying losses. The business becomes larger, but not stronger. The better response is to identify where growth is destroying economics, restore control at the constraint, and redesign the decisions that connect demand, capacity, service and cash.

Four ways attractive growth becomes economically dilutive

1. The constraint is invisible until demand reaches it

Most companies plan capacity at the department or facility level. Customers experience a system, however, and system output is governed by a small number of constraints: a machine family, engineering approval, skilled labor pool, receiving dock, pick face, quality gate or transportation lane. Growth loads the constraint first. Local utilization can look healthy while orders queue, lead times lengthen and promised dates slip.

The economic consequence is nonlinear. A modest increase in volume can trigger a much larger increase in schedule changes, expediting and overtime once the constraint loses protective capacity. The last unit sold is then materially less profitable than the average unit reported in the income statement.

2. Complexity rises faster than revenue

Growth often arrives with new customers, lower-volume SKUs, custom specifications, shorter lead times and more exceptions. Each may look attractive in isolation. Together they multiply setups, planning decisions, inventory positions, quality requirements and service rules. Bain describes complexity as a natural consequence of success and argues that unmanaged complexity can suppress growth, cost and customer outcomes. The practical lesson is that revenue should not be treated as economically equivalent across customers and products.

A high-revenue account can be value dilutive if it consumes scarce capacity, requires frequent overrides, carries unfavorable terms or creates obsolete inventory. Conversely, a smaller account can be highly attractive when its demand is predictable, its mix fits the network and its service requirements match the operating model.

3. Working capital becomes the hidden growth tax

Growing companies buy materials before they invoice customers and collect cash after they ship. If inventory days and receivable days remain constant, growth still requires incremental funding. If service problems add safety stock, disputed invoices or late collections, the cash requirement accelerates. McKinsey notes that many companies have opportunities to improve net working capital by 10–30 percent versus baseline—an indication of how much cash can be trapped in operating decisions rather than financing policy.

The CEO-level implication is clear: working capital is not a finance project. It is the cumulative result of decisions about assortment, forecasts, minimum order quantities, production sequencing, customer promises, invoice accuracy, credit and accountability.

4. Management bandwidth becomes the scarce resource

At smaller scale, experienced leaders compensate for weak processes through personal intervention. They know which customer must ship, which supplier needs a call and which production number cannot be trusted. Growth breaks this informal control system. Decision volume rises, but authority, data quality and management routines do not. More issues escalate to the executive team, slowing decisions precisely when speed and consistency matter most.

The symptom is a leadership team consumed by daily recovery. The cause is usually not insufficient effort. It is an operating model that has not defined how priorities are set, where tradeoffs are made, which data governs the decision and who owns the result.

Look beyond the monthly P&L

The income statement confirms what happened; it rarely reveals whether the growth model is creating value soon enough to change course. CEOs need a compact set of enterprise indicators that connect commercial ambition to operating readiness, incremental economics and cash.

Supporting operating diagnostics—including contribution per constrained hour, backlog age and promise-date changes—help management locate the mechanism of value leakage. They should inform the CEO discussion, not define it.

A CEO agenda for profitable growth

1. Define the incremental economics. Translate the growth plan into required EBITDA, cash and service outcomes—not revenue alone. For each additional dollar of revenue, make the expected contribution, operating cost and working-capital requirement explicit.
2. Segment growth by value and operational fit. Analyze customers, products and channels using margin after cost-to-serve, demand variability, strategic value and consumption of constrained capacity. Reprice, redesign the service promise or decline demand that cannot earn an adequate return.
3. Find and stabilize the enterprise constraint. Identify the resource or decision that governs end-to-end throughput. Protect it from avoidable starvation, blockage, downtime, low-value work and schedule churn before judging whether capacity is insufficient.
4. Integrate the growth equation. Connect the sales forecast, S&OP, labor plan, inventory policy, capacity plan and cash forecast in one decision process. Execution and executive reviews should use the same demand and constraint assumptions.
5. Release existing capacity before adding fixed cost. Improve flow, scheduling, reliability, data, staffing and inventory parameters; then verify that throughput, service and cash moved. Existing assets and management capacity should be used deliberately before overhead or capital is added.
6. Scale the management system. Clarify decision rights, escalation thresholds, standard work and frontline routines. Assign operational owners to the root causes behind trapped cash and recurring recovery cost.
7. Gate cost and capital against evidence. Once the process is stable and the constraint is understood, size people, automation, space or equipment against demonstrated demand, residual capacity risk and a clean economic baseline.

An outcome-gated path to profitable growth

What the board should expect

A credible growth plan should explain not only where revenue will come from, but how the operating system will absorb it. The board should be able to see the limiting resources, the required investments, the expected incremental margin, the cash conversion profile and the service risk. Capital requests should be tested against a prior question: how much capacity and cash can be released through better flow, reliability, mix and decision discipline before new capital is committed?

This is not an argument for slowing growth. It is an argument for governing growth as an enterprise transformation rather than a sales outcome. Companies that align commercial ambition with operational economics can scale with improving service, stronger cash generation and expanding EBITDA. Those that do not may hit the revenue target while quietly reducing the quality and value of the business.

Sagamore Perspective. Bill Lenihan helps CEOs connect commercial strategy to capacity, service, cost-to-serve and working capital—so growth converts into margin, cash and enterprise value.

Executive Premise. A high OTIF score can coexist with shortages, substitutions, damaged product, incorrect paperwork, invoice disputes and avoidable customer effort. If the metric stops at the dock, it stops too soon.

The metric can be right while the customer experience is wrong

OTIF has earned its place on executive dashboards because it is intuitive and economically relevant. A customer asked for a quantity by a date; did the company deliver? The problem is not the metric itself. The problem is allowing it to become a proxy for the entire order experience.

Consider an order that arrives on time and in full but contains a picking error, damaged packaging or an invoice that does not match the purchase order. Operations may record success. The customer records disruption. Someone must investigate, receive a replacement, correct documentation, process a credit and reconcile payment. Revenue remains on the books, but the transaction has consumed margin and trust.

Accenture’s buyer research found that sellers significantly underestimated the importance buyers placed on consistent, on-time delivery. The broader message is even more important: customers want the fundamentals executed correctly the first time. Visibility and tracking have value, but they do not compensate for an unreliable order.

Why OTIF often overstates performance

The promise date moves

If the denominator uses the latest internal promise rather than the customer’s original requested date—or an explicitly renegotiated commitment—performance can improve on paper without improving for the customer. Re-promising may be necessary, but it should remain visible as a service failure or a separate measure of promise reliability.

The unit of measure favors the company

A shipment-level metric can hide failed lines. A line-level metric can make one order appear largely successful even when the missing line stops the customer’s production. A monthly average can hide chronic failures for a strategic account. Without a clear hierarchy—order, line, unit, customer and channel—the number becomes negotiable.

Availability disappears from the calculation

OTIF usually begins after the company accepts the order. It may not capture the demand that was backordered, substituted, canceled or never placed because inventory was unavailable. For a distributor, fill rate and lost sales can matter as much as delivery execution. For a manufacturer, reliable available-to-promise logic is critical to setting a commitment that the system can actually keep.

Quality and transaction accuracy sit in other functions

Damage, labeling errors, incorrect certificates, quantity discrepancies, returns, pricing errors and invoice disputes are often tracked in separate systems. This fragments accountability. The customer experiences one order; the company reports multiple functional metrics, each of which can look acceptable while the end-to-end outcome fails.

Measure the perfect order

APQC defines perfect-order performance as the percentage of orders handled without flaw, calculated from four components: on-time delivery, complete delivery, damage-free delivery and accurate documentation. Its cross-industry benchmark page reports a median of 88 percent across a sample of 1,818 companies. Multiplying component rates can provide an executive approximation, but the strongest operating method is order-level: an order is perfect only when every required condition passes. That preserves accountability and exposes failures that occur together on the same transaction.

For many middle-market companies, the APQC definition is the right foundation but not the entire architecture. The scorecard should begin before shipment and end after the transaction is financially clean. That means adding availability, order-entry accuracy and first-pass invoice acceptance where those are material to the customer promise.

Measurement Rule. Perfect-order rate = orders that pass every required condition ÷ total eligible orders × 100. Use component measures and reason codes to diagnose the result; do not let them replace the end-to-end outcome.

One enterprise metric, two management views

The CEO and board need a single end-to-end outcome: the percentage of customer orders completed without any material failure. The operating organization needs the decomposition behind it. A composite score without a loss tree creates awareness but not action; a collection of functional measures without a composite score creates activity but not accountability.

• Executive view: perfect-order rate, trend, economic cost of failures and performance for strategic customer segments.
• Operating view: the same result decomposed by failure point, cause, customer, SKU, site, carrier and order profile.
• Financial view: credits, concessions, premium freight, returns, write-offs, dispute aging and customer-service effort associated with imperfect orders.

Make the economics visible

Imperfect orders create failure demand: work that exists only because the first execution was wrong. It rarely appears as one clean line on the P&L; its cost is distributed across customer-service labor, freight, scrap, rework, returns, credits, excess inventory, deductions and lost future demand. The result is systematic underestimation. Assign direct recovery costs to each failed order and estimate the capacity consumed by investigation and correction. The intent is not perfect cost accounting; it is to make the magnitude and concentration of failure visible enough to prioritize action.

The analysis often changes commercial conversations. A customer that appears low margin may be suffering from preventable execution failures. A high-growth channel may require packaging, labeling or cut-off capabilities the operating model was never designed to provide. A portfolio decision that appears to be about product profitability may actually be about service-model complexity.

A CEO agenda for perfect-order performance

1. Define the promise. Agree on the customer-requested date, the committed date, the acceptable delivery window and the rules for renegotiation. Do not allow silent promise-date resets.
2. Define the unit. Report order-level perfection as the enterprise outcome, supported by line-level diagnostics. Treat any critical-line failure as an order failure where the customer’s use case warrants it.
3. Create one failure taxonomy. Assign each imperfect order one primary reason at the first point of failure, with secondary tags where they improve diagnosis. Build a Pareto by value and customer impact; avoid “other,” “customer issue” and similar categories that absorb accountability.
4. Connect service to economics. Track the cost of recovery and the commercial risk associated with each failure family. Prioritize on value and customer impact, not frequency alone.
5. Segment the promise. Different customers and products can warrant different service models. Make those choices explicit and price exceptions rather than letting them enter through daily escalation.
6. Govern end to end. Assign one executive owner for the order journey and establish a cross-functional review of the largest failure modes and corrective actions.

An outcome-gated path to perfect-order performance

The standard is not a better score—it is a better experience

A demanding perfect-order metric may initially fall when components are measured honestly; that is improved visibility, not deterioration. OTIF is essential, but it belongs inside a reliability view spanning availability, promise integrity, correct delivery and documentation without preventable customer effort. The objective is fewer failures that erode trust, margin and growth—not a negotiated score.

Sagamore Perspective. Bill Lenihan helps leadership teams build one customer execution system with a shared definition, loss tree, visible economics and accountable action. The result is fewer failures, lower recovery cost, stronger customer trust and more reliable growth.

Executive Premise. How will Operations enable the company's revenue growth and EBITDA plan while delivering the quality, service, productivity and cash performance required to sustain it?

The capacity gap is an enterprise signal

That question leads to the central issue: where is the operating model unable to support the plan, and should leadership respond through better decisions, stronger capabilities, different operating policies or additional capital? Installed capacity is the output implied by equipment, labor and operating assumptions. Demonstrated capacity is what the enterprise can repeatedly convert into saleable product at the customer-required mix and service level. The CEO's task is not to claim the entire difference. It is to determine what portion is structural, what reflects an economic choice and what is genuinely recoverable.

Armand Feigenbaum's original conception of the hidden factory was broader than machine efficiency: it encompassed organizational capacity consumed by failure work. In manufacturing, that work appears as downtime and rework, but also as expediting, repeated reviews, documentation correction, schedule churn and informal workarounds. It rarely belongs to one function. Reliability, quality and changeovers matter, but so do product complexity, commercial promises, planning rules, supplier performance, workforce capability and the way leaders resolve tradeoffs. The strategic issue is an operating system that is failing to convert resources into the performance the business requires.

When demand presses against demonstrated capacity, the organization often frames the answer as a capital request: a new line, an additional shift, more warehouse space or outsourced production. Some investments are essential. But capital added before the enterprise understands the constraint can reproduce the same weaknesses at a higher fixed-cost base. It can also solve the wrong problem—for example, adding equipment when the real limitation is product mix, material availability, planning discipline or decision latency. Recovered capacity creates value only when it releases the governing constraint and enables the business to convert demand into profitable, saleable output.

Why hidden capacity is strategically important

It tests whether strategy and the operating model are aligned

A growth strategy is credible only if the operating model can support the promised volume, mix, lead time and service economics. A recurring capacity shortfall may indicate an asset limitation, but it may also reveal that commercial priorities, supply-chain choices and operating capabilities are working against one another. The hidden factory gives the CEO a fact base for separating those issues.

It changes the economics of the capital decision

Capacity recovered at the true enterprise constraint can generate additional contribution with limited incremental fixed cost. Its value is not an hourly labor saving; it is the combination of saleable throughput, more reliable service, lower recovery cost, improved cash conversion and capital deferred or avoided. This enterprise value—not a narrow efficiency measure—should anchor the comparison among operating improvement, flexible capacity and permanent investment.

It reveals where leadership attention has the greatest leverage

Unstable flow often produces more inventory, more schedule changes, more expediting and less reliable customer commitments. Those symptoms cut across Operations, Sales, Supply Chain, Finance and Human Resources. By framing the constraint end to end, the CEO can focus the leadership team on the few cross-functional decisions that materially improve service, margin and cash. The right answer may still be new equipment—but with clearer scope, specifications, risk and return.

Find the constraint, not the noisiest asset

The enterprise constraint is the condition that governs the business's ability to meet its customer and financial commitments. It may be a machine, but it may also be supplier reliability, workforce capability, a planning rule, portfolio complexity, engineering throughput or a slow cross-functional decision. Improving the loudest local problem can raise a departmental metric while leaving enterprise performance unchanged—or create more inventory and congestion elsewhere.

Operations, Engineering, Maintenance, Quality and continuous-improvement leaders should validate the technical causes and design the countermeasures. The executive team defines the business requirement, insists on a shared fact base, resolves cross-functional tradeoffs, assigns accountable leaders and connects the result to service, margin, cash and capital. This combination preserves technical rigor while keeping the work anchored to enterprise strategy and value.

Informal workarounds should be treated as evidence about the operating system, not merely as employee noncompliance. When surfacing a problem produces blame, delay or more bureaucracy, people learn to work around it and the loss remains invisible. Leadership must create the conditions in which operating realities can be surfaced, tested and resolved with the people closest to the work.

Translate operating evidence into executive choices

Measures such as overall equipment effectiveness are useful to operating and technical teams, but they are not an enterprise capacity strategy. A plant-wide average can hide the governing constraint, mask product-mix effects and reward local optimization. CEOs should expect technical measures to reconcile to the outcomes that matter: reliable customer commitments, good throughput, contribution margin, cash conversion and capital risk.

Evidence that small losses can carry large economics

A NIST Manufacturing Extension Partnership case illustrates the leverage. A manufacturer focused total productive maintenance on a CNC lathe that was constraining throughput. The company reported roughly 22 percent productivity improvement, an OEE increase from 39 to 45 percent and $250,000 of avoided investment. The executive lesson is to direct specialist effort at the enterprise constraint and translate the operating result into economic value before capital is approved.

BCG has likewise reported that clients using advanced production scheduling achieved more than a three-percentage-point OEE uplift through changeover reduction and asset-capacity improvement. Technology can improve visibility and accelerate the result, but it should follow a clearly framed management question. Digitizing weak operating rules can institutionalize loss or accelerate the wrong work. Enterprise value comes from better decisions about demand, sequence, constraints and tradeoffs—not from software or a technical metric alone.

A CEO agenda for capacity and capital

1. Frame the business requirement. Translate strategy and customer commitments into the volume, mix, service, margin and resilience the operating model must support. Capacity has meaning only in relation to those outcomes.
2. Establish one enterprise fact base. Test the definitions and integrity of the operating data, then reconcile demand, installed and demonstrated capacity, service performance, cost-to-serve and cash implications across Commercial, Operations, Supply Chain and Finance.
3. Identify the governing constraint. Determine which asset, capability, policy or decision truly limits enterprise performance. Have the appropriate functional experts validate causes and distinguish structural limits from recoverable losses.
4. Value the strategic alternatives. Treat safety, quality and compliance as decision gates. Then compare operating improvement, portfolio or service-policy changes, flexible capacity and permanent capital using contribution, customer risk, cash, resilience and execution risk—not departmental efficiency alone.
5. Mobilize the right owners and specialists. Assign technical countermeasures to the leaders equipped to deliver them, while the executive team removes cross-functional barriers and maintains alignment to the enterprise objective.
6. Verify enterprise outcomes. Confirm that the response improves reliable throughput, service, margin or cash under normal operating conditions. Update decision rights and management routines so the gain is sustained.
7. Make the capital decision from evidence. Commit capital where verified demand and residual capacity risk justify it, with a clearer definition of the asset, its economics and the operating conditions required to earn the return.

An outcome-gated path from constraint to decision

Questions to test every capacity request

• Which strategic objective and customer commitments is this capacity request intended to support?
• Where is the enterprise actually constrained, and what evidence validates that conclusion?
• How much of the gap is structural, how much reflects an economic choice and how much is genuinely recoverable?
• What failure work or informal workaround has become normalized because the formal operating system cannot meet the requirement?
• Which operating, commercial or flexible-capacity alternatives should be considered with permanent investment?
• How will each option affect service, contribution margin, cash, resilience, safety, quality, compliance and execution risk?
• How will the operating model ensure that a new asset does not inherit today's constraints?

Capacity is an enterprise decision before it becomes a capital project

The strongest CEOs create the conditions for plant leaders and technical specialists to solve the right problem: a clear business requirement, a shared view of the constraint, explicit economic choices, accountable ownership and decisions that work across functional boundaries. The goal is for capital to follow strategic clarity and operating evidence—funding strategic growth rather than carrying forward unresolved operating loss.

Sagamore Perspective. Bill Lenihan works alongside CEOs to translate strategic priorities into operating performance and better capital decisions. His end-to-end perspective helps leadership teams identify what truly constrains enterprise results, align functional leaders and specialists around the highest-value response, and convert operating improvement into more reliable service, stronger margins, cash generation and enterprise value.

For years, robotics, artificial intelligence and advanced analytics appeared to be technologies reserved for Amazon, Walmart and the largest global distributors.

That is no longer true.

Cloud software, subscription pricing, autonomous mobile robots, embedded AI and lower-cost sensors have made advanced capabilities accessible to middle-market distributors. The question is no longer whether the technology is available.

The real question is whether management can convert it into measurable operating and financial value—without overinvesting, disrupting the business or creating an expensive collection of disconnected tools.

The market is moving—but implementation is lagging

In MHI and Deloitte’s 2025 supply-chain research, 28% of respondents reported using AI, while another 54% expected to adopt it within five years. Expected five-year adoption reached 92% for inventory and network optimization, 83% for robotics and automation and 88% for sensors and automatic identification. MHI and Deloitte ↗

Distributors clearly recognize the opportunity. McKinsey found that approximately 95% of distributors surveyed were exploring AI use cases. Yet only about 30% believed they had sufficient internal talent to scale AI, and fewer than 10% had developed and prioritized an AI roadmap. McKinsey & Company ↗

That is the central challenge facing the middle market: enthusiasm is widespread, but disciplined execution is not.

Start with the operating constraint—not the technology

For a distributor, that constraint may be:

• Excess inventory and poor demand forecasting
• Picker travel time and warehouse congestion
• Inaccurate inventory records
• Chronic overtime
• Low fill rates
• Purchasing leakage
• Inefficient truck routing
• Manual order entry
• Pricing inconsistency
• Returns, credits and claims
• Customer-service response time

Technology should be selected only after the constraint has been quantified.

A distributor losing margin through inventory obsolescence probably needs better forecasting, segmentation and replenishment logic before it needs a robot. A warehouse where selectors spend much of the shift walking may have a legitimate case for autonomous mobile robots. A company processing hundreds of emailed purchase orders may create more immediate value through document automation and AI-assisted order entry.

The objective is not to become a “high-tech distributor.” It is to improve EBITDA, working capital, service and capacity.

Fix the operating system first

Technology does not repair an undisciplined process. It accelerates whatever process already exists—including a bad one.

Before automating a workflow, management should establish:

• A clearly defined process
• One accountable process owner
• Accurate master and transactional data
• Standard work and exception rules
• Baseline performance measures
• A realistic integration plan
• Workforce training and adoption responsibilities

This is particularly important with AI. Forecasting algorithms trained on inaccurate item, customer, lead-time or inventory data will produce faster answers—not necessarily better ones.

Deloitte’s research reinforces the relationship between advanced technologies and their foundations. In its 2025 technology-value survey, 47% of AI investors were also investing in ERP, compared with only 21% of non-AI investors. Deloitte characterized ERP as a backbone for integrating AI into operations. Deloitte ↗

For many middle-market distributors, getting more value from the existing ERP and WMS is the first advanced-technology initiative.

Use an affordable technology ladder

Middle-market companies should not jump directly from spreadsheets and tribal knowledge to a fully automated distribution center. A staged technology ladder is less risky and usually produces a better return.

Pilot narrowly and scale on evidence

The best pilots are not demonstrations. They are controlled business tests.

A credible pilot should define:

• The baseline performance
• The targeted improvement
• The affected process and volume
• Total implementation and operating cost
• Integration requirements
• Workforce and training implications
• Service and accuracy guardrails
• A time-limited testing period
• The conditions for scaling, changing or stopping

Useful measures include cases per labor hour, labor cost per case, order-cycle time, inventory accuracy, fill rate, perfect-order rate, overtime, cost per delivery, space utilization and working-capital reduction.

A pilot that improves productivity but increases errors, congestion or support costs has not succeeded.

McKinsey recommends beginning with one or two low-risk, high-value use cases that can be delivered within three to four months, followed by a one- to two-year value-based roadmap. It also recommends reinvesting early returns to make the transformation self-funding. McKinsey & Company ↗

Build the business case around cash—not headcount promises

Many technology proposals overstate labor savings.

If a system theoretically saves the equivalent of five employees but payroll, overtime and outside labor do not decline—and additional volume is not processed—then the savings have not reached the income statement.

The business case should distinguish among:

• Hard-dollar cost reduction
• Avoided future hiring
• Additional throughput
• Inventory and working-capital release
• Reduced errors, returns and claims
• Avoided facility expansion
• Revenue retained through better service
• Risk reduction
• Costs merely shifted to software, maintenance or consultants

It should also include implementation labor, integration, infrastructure, cybersecurity, training, process redesign, support and expected downtime—not just the vendor’s subscription or equipment price.

In my own work, process redesign combined with practical technology has enabled a produce distributor to support approximately 20% growth without warehouse expansion while reducing overtime by 65%. At an industrial distributor, the combination of operating discipline, better systems and performance management helped increase inventory accuracy from below 80% to above 98%, reduce overtime by more than 60% and improve on-time, in-full service from below 30% to above 95%.

The lesson is not that technology alone produced those results. It is that technology amplified a better operating model.

Do not ignore governance and cybersecurity

Connected equipment, cloud applications and AI tools expand the attack surface and create new data, privacy and operational risks.

At a minimum, distributors should establish:

• Approved AI applications and use policies
• Role-based access
• Multifactor authentication
• Data backup and recovery
• Vendor-security requirements
• Restrictions on entering confidential data into public AI tools
• Human approval for consequential AI actions
• Logging and monitoring
• Incident-response responsibilities

NIST’s Cybersecurity Framework 2.0 emphasizes governance and supply-chain risk and includes a quick-start guide designed specifically for smaller organizations with limited cybersecurity resources. NIST CSF 2.0 Small Business Guide ↗

Governance is not theoretical. Gartner predicted that more than 40% of agentic-AI projects would be canceled by the end of 2027 because of escalating costs, unclear business value or inadequate risk controls. Gartner ↗

The middle market may have an advantage

Large corporations have more money. They also tend to have more systems, organizational layers, approval cycles and legacy complexity.

A well-managed middle-market distributor can move faster.

It can identify a constraint, establish a baseline, pilot a solution and make a scaling decision without creating a three-year transformation program. It can involve frontline employees directly and adjust operating processes quickly.

But that advantage exists only when leadership remains disciplined:

• Fix the process before automating it.
• Start with measurable business value.
• Use existing systems before buying more software.
• Pilot one constraint at a time.
• Keep humans accountable for material decisions.
• Scale only after the economics are demonstrated.
• Reinvest verified savings into the next initiative.

Advanced technology is now within reach of middle-market distributors.

What remains scarce is not capital or software. It is the management discipline to turn technology into sustained operating performance.

That—not the size of the technology budget—will separate the winners from the rest of the market.