Capital procurement is flying blind

In most industries, indirect procurement is where enterprise software starts. It's low-risk, high-volume, and the ROI story writes itself. Manufacturing, life sciences, CPG, and industrials work differently. The real money moves through capital procurement.

That's also where procurement teams have the least visibility of anywhere in the business. Let’s go deeper.

Why capital spend escapes procurement visibility

Capital expenditure in asset-heavy industries runs on a different scale. These are projects worth tens of millions of dollars, sometimes hundreds: new plant equipment, production line expansions, facility buildouts, EPC (engineering, procurement, and construction) contracts. The stakes are enormous, the approval chains are long, and the supplier relationships are complex. The process governing all of it is often a patchwork of emails, spreadsheets, and manual handoffs that somehow made it into 2026.

Here's what that looks like in practice.

A plant engineer identifies a critical equipment need. They reach out directly to a preferred vendor they've worked with for years. A purchase order eventually surfaces in the ERP, weeks after the decision was already made. Finance finds out when the invoice lands, and through it all procurement was never in the loop.

That's an ordinary day at most industrial companies, and the pattern extends well beyond capex.

In Zip's State of AI in Spend report, a survey of 1,050 procurement, finance, IT, and operations leaders, 36% said non-procurement functions increased their direct purchasing of technology or services without procurement involvement over the past 12 months. If that's happening in the categories procurement was built to govern, it's happening with capital equipment too.

The planning environment is making the timing problem worse. Capital projects run on multi-year timelines, but only 15% of those leaders said they can plan with confidence beyond two years, and a quarter said their planning horizon shortened over the past year under pressure from inflation (cited by 54%) and supply chain disruption (39%). Asset-heavy companies commit eight- and nine-figure budgets on visibility that runs out well before the project does.

The result is cost overruns, suppliers nobody vetted, compliance problems that surface at audit, and a procurement team that's perpetually reactive. Capital budgets get consumed without visibility as risk accumulates without controls, and the people accountable for spend governance are the last to know anything.

Why capital procurement is so hard to fix

The complexity of capital procurement goes beyond the dollar amounts. It comes from the nature of the spend itself.

Unlike indirect categories like software or professional services, capital projects involve cross-functional stakeholders with strong opinions and legitimate authority. Engineering owns the spec, operations owns the timeline, finance owns the budget, and legal owns the contract. Each one has a different system, a different workflow, and a different definition of "approved."

Add multi-ERP environments (common after M&A), procurement lead times that span budget cycles, supplier qualification requirements driven by safety and regulatory standards, and sourcing events where technical evaluations and commercial negotiations run in parallel.

The process is inherently cross-functional. The tools are siloed. That's the problem, and practitioners know it. When asked which aspect of procurement most needs fundamental redesign rather than incremental improvement, the top answer in the State of AI in Spend report was how procurement collaborates with other functions: finance, legal, IT, and the business. It beat sourcing, contracts, and data flows.

Every capital decision crosses at least three of those functions. That's why every timing problem in the plant engineer story above keeps repeating: by the time anyone with governance responsibility can see the spend, the decisions that mattered have already been made.

How to get procurement upstream of capital spend

Adding controls to the back of the process only slows decisions down or reverses them, and both options make procurement "the department of no." (Have you heard that one before?)

That reputation carries a real cost. The same survey found that inflexible or slow processes are the single biggest factor limiting procurement's influence, named by 32% of leaders, ahead of underinvestment in talent or technology and every other option. It topped the list last year too. Speed is procurement's most persistent liability, and more back-end controls make it worse.

The fix is getting visibility before decisions are made, which requires changing how capital requests enter the organization in the first place. In practice, this comes down to five moves.

1. Give every capital request one front door

Engineers bypass procurement because the official channel is harder than calling a vendor they trust. So make the official channel the easy one: a single intake point that captures the business case, project classification, budget code, and risk tier upfront, without requiring the requester to know which ERP to use or who their third-level approver is. When intake is easier than the workaround, the workaround stops. And procurement sees the spend at the moment of intent instead of the moment of invoice.

2. Build approval paths that match how capex is actually governed

A capital request doesn't route like a $500 software subscription. It may need executive sign-off above a threshold, capital committee review, legal and environmental approval, and finance validation, all in sequence. Most organizations run this through email chains and standing meetings, which is why approvals stall and nobody can say where a request sits. Map the real governance path into a workflow that routes automatically, and make it changeable without an IT project, because capital approval processes change more often than anyone admits.

3. Qualify suppliers as fast as projects introduce them

Capital projects pull in new suppliers constantly: fabricators, specialty contractors, EPC firms. Each one needs vetting for financial health, safety certifications, and insurance before they touch the work, and that qualification can't live in someone's inbox as a shadow approved-vendor list. It needs to be a single pipeline the whole organization can see, and it can't end at onboarding. A supplier that was healthy at qualification can be in financial distress by the time the project peaks, so monitoring has to continue for the life of the engagement.

4. Run capital sourcing in one workspace

Capital RFPs carry far more weight than commodity bids: technical specifications, multi-round negotiations, and weighted scoring across commercial and technical criteria, with evaluators from engineering, procurement, and finance who all need to participate. Running that by email means version confusion, lost context, and weeks of back-and-forth. Centralizing the event (the RFP itself, supplier communication, scoring, and the award decision) turns weeks into days and leaves a record of why the winner won.

5. Keep one thread from commitment to invoice

In most capital projects, committed spend, ordered spend, and invoiced spend are tracked in different places or not at all, which is how overruns stay invisible until they're unfixable. The award should connect to the contract, the contract to the PO, and the PO to the invoice, with a three-way match at the end. When that thread is unbroken, finance can see what's committed, procurement can see what's at risk, and leadership can see what's actually happening across the capital portfolio.

Where Zip fits in capital procurement

This is the problem Zip's Procurement Orchestration platform is designed to solve. Every spend request comes through one front door, with routing that adapts to the complexity behind it.

Intake, approval workflows, supplier onboarding and risk monitoring, sourcing, contracts, and procure-to-pay run as connected steps in one thread rather than handoffs between siloed tools.

Just as important is what Zip doesn't require. Companies in these industries run SAP and Oracle systems customized over a decade, often several of them after acquisitions, with IT backlogs that make every new integration a six-month conversation.

Zip sits in front of those systems as the orchestration layer, reading from and writing back to the ERPs teams already use. Nothing gets ripped out, and the ERP investment works harder than it did before. For companies operating across multiple plants, geographies, and business units, each operating unit can run its own workflows and supplier rules while leadership keeps portfolio-level visibility at the top.

Start smaller than you think

Capital procurement transformation shouldn't happen all at once.

The companies that see the fastest results start with a focused scope: bring intake online for capital requests in one category or one facility, establish the approval workflow, and get procurement in the loop before purchase decisions are made. That alone surfaces what was hidden: the spend nobody could see, the suppliers nobody vetted, the approvals that were happening in email.

From there, extend downstream into how suppliers are qualified, how competitive bids are run, how contracts are executed, and how invoices are matched back to what was approved. Skip the big-bang transformation. The goal is making procurement visible in places it was invisible, and controlled in places it was out of control.

The case for orchestrating capital spend

Capital spend in manufacturing, life sciences, CPG, and industrial companies is too significant and too complex to manage through spreadsheets and email chains. The governance risk is real, the exposure to overruns is real, and so is the opportunity: getting procurement upstream of the biggest decisions a company makes.

Procurement leaders already know where the redesign has to start. In Zip's survey, cross-functional collaboration was the part of the function most in need of a rethink, and slow processes were the biggest drag on procurement's influence. Orchestrating spend answers both, wherever the decisions happen. In asset-heavy industries, that's capital procurement.