Why procurement breaks as companies scale (and fix it)

Procurement doesn’t break because teams stop following process—it breaks because growth outpaces it.

For CFOs, it shows up as something else first: unexpected spend, delayed approvals, duplicate tools, and reporting that’s always one step behind reality. You don’t lose control overnight—you lose visibility gradually, until finance is reacting instead of orchestrating.

This is how it typically shows up:

• unexpected spend
• procurement delays and a slow procurement process
• duplicate tools
• reporting that’s always one step behind reality

What worked at 50–100 employees—informal approvals, direct supplier relationships, and ad-hoc purchasing—starts to fail at 300–1,000. Not because the team changed, but because complexity did.

In mid-market companies, procurement rarely gets formally designed. It evolves organically. Early on, that flexibility is a strength. But as headcount grows, requests multiply, stakeholders increase, and processes fragment across email, spreadsheets, ERPs, and cards, creating procurement process inefficiencies.

What changes in procurement when a company scales?

In a recent talk at Payhawk, Rapha Bautz, PMM for Procurement at Payhawk, sat down with Kiril Kavardzhikov, Procurement Manager at Payhawk, to explore how growing companies gradually lose control of spend, and how they can regain it.

As Kiril explains:

“For small companies… everybody knows what you’re buying… But as the headcount grows, you start to lose that shared awareness.”

At the same time, teams become more autonomous. They move faster—but outside of a shared process.

As Kiril adds: “More and more teams become more autonomous. They decide to purchase something on their own. So nobody has the full picture anymore.”

This is the inflection point most finance teams miss: procurement isn’t failing because of policy—it’s failing because there’s no system orchestrating how decisions happen end-to-end.

Approvals become inconsistent. Supplier and tool sprawl accelerates. Spend visibility disappears. Policies exist on paper, but not in practice, leading to a procurement process breakdown.

As Kiril notes: “This is when it becomes clear that it needs to be centralised and not decentralised…”

The insight is simple but critical: finance doesn’t need more controls—it needs orchestration. A way to connect requests, approvals, vendors, and payments into a single, visible workflow that scales without adding complexity.

In the next sections, we’ll break down exactly where procurement starts to fail—and how to fix it with a practical, scalable procurement process improvement framework.

Procurement transformation doesn’t start with a new system—it starts when scale exposes the limits of how things used to work.

As companies grow, request volume doesn’t just increase—it multiplies across teams, regions, and budgets. What was once a simple approval between a manager and finance now involves multiple stakeholders, unclear thresholds, and inconsistent decision-making, increasing pressure on the procurement cycle.

Approvals become layered, but not necessarily structured. Some requests move quickly, others stall, and many get pushed through informal channels to avoid delays, creating procurement bottlenecks.

At the same time, supplier and tool sprawl accelerates. Different teams choose their own vendors, often solving similar problems in parallel. Without central oversight, duplication becomes inevitable—and costly.

To keep things moving, teams start working around the process. Requests happen in email, Slack, or meetings. Approvals get buried in threads. Finance and procurement teams spend more time chasing information than making decisions, reinforcing procurement inefficiencies.

In practice, scaling introduces:

• more stakeholders and approval layers
• inconsistent decision-making
• supplier and tool sprawl
• workarounds via email, Slack, and meetings

What looks like a procurement inefficiency is actually something deeper: the process hasn’t scaled with the business.

The 5 ways procurement breaks as you grow

As companies scale, procurement bottlenecks don’t appear as one big failure—they emerge as a series of connected breakdowns. Each one seems manageable on its own, but together they create a system that’s slow, fragmented, and hard to control, with growing procurement process inefficiencies.

Approvals turn into bottlenecks (cycle time explodes)

The first sign is usually approvals. What used to be quick decisions become slow, inconsistent, and hard to track. More stakeholders are involved, but approval thresholds aren’t clearly defined, and requests are scattered across email, Slack, and meetings.

The result is predictable: cycle times increase, procurement delays grow, teams start chasing approvals, and “urgent exceptions” become routine. Eventually, business users bypass the process altogether—because waiting is no longer an option.

Visibility disappears (no “full picture”)

At the same time, visibility starts to break down. As teams become more autonomous, they make purchasing decisions independently, without a shared system connecting requests, approvals, and payments.

Nobody has the full picture anymore. Finance can’t see committed spend early enough, procurement lacks end-to-end context, and reporting becomes reactive instead of proactive. What looks like a reporting issue is actually a structural spend visibility gap.

Tool and supplier sprawl accelerates

As growth continues, supplier and tool sprawl accelerates. Different teams adopt their own solutions, often solving similar problems in parallel. Over time, this leads to duplicate tools, overlapping contracts, and subscriptions that continue long after the original owner has left the company.

Accounts payable processes the invoices as they come in—but without the context to question whether the spend is still necessary. Costs compound quietly, without clear ownership or control.

Policy exists on paper, fails in practice

Most companies already have procurement policies in place. The problem is that, at scale, those policies stop working in practice.

When the process is too slow or unclear, teams find workarounds. They purchase outside the system, skip steps, or retroactively justify spend. Over time, this behaviour becomes normalised. The policy still exists—but it’s no longer enforced by the way work actually happens, weakening procurement compliance.

Finance and procurement work in different systems

Underpinning all of this is a deeper structural issue: finance and procurement are often operating in completely separate systems.

Accounts payable and finance teams work in the ERP, while procurement workflows live elsewhere—across disconnected tools, spreadsheets, or inboxes. Data doesn’t flow between them, so information has to be re-entered, reconciled, and chased.

The result is fragmented context. No single view of the process from request to payment. And no reliable way for finance to stay ahead of spend.

These breakdowns don’t happen in isolation—they reinforce each other. And as they compound, procurement shifts from being a control function to a source of friction across the business.

The hidden costs of procurement breakdown

The real cost of procurement breakdown isn’t just inefficiency—it’s the loss of spend visibility and control at the finance level.

When teams start making decisions independently, the impact compounds quickly. As Kiril explains: “Whenever teams start [to] make decisions of their own, it usually leads to duplicating tools…” What looks like speed at the team level creates duplication, wasted budget, and fragmented ownership across the business.

Over time, this becomes harder to detect. As Kiril adds: “Somebody purchased something, but he or she is no longer in the company, but that software continues to run… and invoices continue to come and accounts payable are paying them without ever raising the question, ‘do we really need this?’”

For CFOs, this is where the problem becomes real.

The impact shows up in finance as:

• budget surprises because committed spend isn’t captured early
• no clear distinction between strategic and operational spend
• manual reconciliation and chasing across systems
• audit and procurement compliance risk

Budgets start to drift—not because of large, strategic decisions, but because committed spend isn’t captured early enough. By the time finance sees the invoice, the decision has already been made.

At the same time, there’s no clear distinction between high-value, strategic purchases and everyday operational spend. Both flow through fragmented processes, requiring manual oversight where it matters least—and not enough control where it matters most.

Finance teams are left reconciling data across systems, chasing approvals, and piecing together context from multiple tools. What should be a structured process becomes reactive work. In many cases, even when tools are in place, they act as little more than a coordination layer—digitising steps without removing the underlying manual effort.

And as visibility weakens, so does compliance. Audit trails are incomplete, policy enforcement is inconsistent, and risk increases—not because controls don’t exist, but because they’re not embedded in how procurement actually runs.

The hidden cost isn’t just wasted spend. It’s the shift from proactive financial control to reactive firefighting—and from structured, automated workflows to processes that still depend on constant human intervention.

True value only emerges when procurement workflows are designed to run with minimal manual involvement. Requests should be routed automatically, approvals should follow predefined thresholds, and matching and checks should happen in the background—reducing active participation rather than increasing it.

This is also where AI is beginning to play a role. It can support high-volume, low-judgment tasks like categorising spend, flagging anomalies, extracting invoice data, or suggesting next steps. But it doesn’t replace accountability—financial decisions still sit with humans.

Without this balance—automation handling operational load, and humans focusing on exceptions and strategic decisions—organisations don’t eliminate inefficiency, they simply move it around.

Step 0 — fix visibility before you fix process

Before any procurement process improvement, there’s a more fundamental step: restoring spend visibility.

As Kiril puts it: “When you say optimise, the first word that comes to my mind is visibility, because you cannot optimise something that you don’t know what exactly it is.”

This is where many teams go wrong. They try to redesign workflows, introduce new tools, or enforce policies—without first understanding what’s actually being bought, by whom, and why.

But procurement isn’t just about process—it’s about control. As Kiril notes: “The procurement role is to centralise and control the spend of a company. We are the ultimate gatekeepers…”

That control starts with clarity.

In practice, this means running a full spend and software audit. Not just looking at invoices, but identifying what you’re paying for, who owns each vendor or subscription, and whether it’s still needed. This is often where hidden duplication, unused tools, and unmanaged spend surface for the first time.

It also means mapping how spend flows today—across requests, approvals, vendors, and payments—so you can see where visibility is lost.

The goal isn’t immediate optimisation. It’s establishing a baseline.

Because once you have a clear, end-to-end view of spend, decisions become simpler. You can prioritise what to fix, where to standardise, and where procurement automation will actually make a difference.

Without that visibility, any process change is just guesswork.

How to fix procurement as you scale

Fixing procurement at scale isn’t about adding more control—it’s about applying the right procurement best practices in the right order. Once visibility is in place, the focus shifts to structuring how decisions happen and ensuring the process can scale without adding friction.

Standardise intake and approvals first

The first step is to bring consistency to how requests enter the system and how they get approved.

That means defining clear approval thresholds, roles, and responsibilities—so every request follows a structured path instead of being handled ad hoc. Just as importantly, you need defined exception paths, so urgent requests don’t bypass the system entirely.

Without this foundation, everything else breaks down. With it, cycle times become predictable, and decision-making becomes transparent.

Centralise decision-making without slowing the business

As complexity grows, decentralised purchasing creates fragmentation. But centralisation doesn’t mean adding bureaucracy—it means creating a single, orchestrated way decisions are made.
As highlighted earlier, as Kiril noted, “this is when it becomes clear that it needs to be centralised and not decentralised…”

The key is balance. Finance and procurement need control and visibility, while business teams need speed. The right approach centralises decision-making through a shared process—but keeps the experience simple and frictionless for end users.

Manage tail spend differently from strategic spend

Not all spend should be treated the same.

High-value, strategic purchases require tighter control, deeper review, and cross-functional input. But applying that same level of scrutiny to everyday operational spend creates unnecessary friction.

Instead, tail spend should be managed with simple guardrails, clear visibility, and guided buying.

Make the process truly end-to-end

Procurement isn’t just approvals—it’s the entire lifecycle from requisition to payment: request → approval → vendor → invoice → matching → accounts payable.

In many organisations, these steps exist—but across disconnected systems. Information has to be re-entered, context gets lost, and teams operate with partial visibility.

The goal is an end-to-end process where everything flows together.

As Kiril explains: “Everybody in that process can see exactly the same information… and we are all working in the same system, so there is no context that is missing throughout the process.”

When that happens, procurement stops being a series of handoffs—and becomes a single, coordinated system that scales with the business.

How to tell if a vendor is truly “end-to-end”

Not every procure to pay software solution is truly end-to-end—even if it looks like it on paper.

Many vendors position themselves as complete solutions, but in reality, they’re a collection of separate modules stitched together. And at scale, that distinction matters—because fragmented tools recreate the same problems you’re trying to solve.

As Kiril points out: “If they can just showcase all individual modules, this means that they don’t have that process… they’re just promoting individual features bundled together…”

The simplest way to evaluate this is through a practical “demo test.”

Ask the vendor to run a complete, real-world scenario from start to finish: from request to approval, to vendor selection, to invoice, to matching, to payment.

Don’t accept feature walkthroughs. Don’t jump between screens. Watch how the process actually flows.

Because that’s the real test. As Kiril explains: “They need to showcase the whole scenario from start to the end… make sure that all the information flows in every step, and there is no need for me to reenter any information…”

If data has to be re-entered, if context is lost between steps, or if different parts of the process live in separate systems, it’s not truly end-to-end—it’s just feature bundling.

This is where many mid-market companies make a costly mistake: adopting specialised procurement software that solves one part of the process, while leaving the rest fragmented across cards, expenses, travel, and payments.

On paper, it looks like optimisation. In practice, it creates a larger, more complex ecosystem to manage.

A more scalable approach is to consider whether a broader platform—one that connects procurement with payments, cards, travel, and integrations—can deliver better long-term value. Not by adding more tools, but by orchestrating the entire process in one place.

This is also where flexibility matters. As companies grow, their needs evolve. The right platform should scale with that growth—adapting to increasing complexity without forcing a complete system overhaul.

Because ultimately, choosing a vendor isn’t just about features. It’s about whether the system can support a truly connected process—without introducing new fragmentation as you scale.

A 30/60/90-day plan for mid-market teams

Procurement process improvement doesn’t happen all at once—it’s most effective when approached in structured phases that build on each other.

In the first 30 days, the focus should be on visibility: auditing spend, tools, and vendor ownership, while mapping how procurement workflows currently operate across requests, approvals, and payments.

By 60 days, the priority shifts to structure—standardising intake and approval processes, defining clear thresholds, and actively reducing vendor and tool sprawl to eliminate duplication.

By 90 days, teams can layer in automation and optimisation: automating approvals and invoice matching, introducing real-time dashboards for spend visibility, and tracking KPIs such as cycle time, compliance rates, and cost savings.

This phased approach ensures procurement process improvement is grounded in clarity first, then consistency, and finally scalability.

How to fix procurement bottlenecks and improve spend visibility at scale

Procurement doesn’t fail because teams stop following process—it fails because growth creates complexity faster than processes can keep up.

What worked at a smaller scale becomes fragmented under pressure: approvals slow down, visibility disappears, and workarounds become the default. The result is a system that feels busy—but lacks control.

The fix isn’t to add more rules. It’s to rebuild the foundation in the right order.

First, restore spend visibility so finance can see what’s happening before money is committed. Then, standardise intake and approvals to remove inconsistency. Finally, connect everything into an end-to-end workflow where information flows without re-entry.

Automation plays a role—but only when it reduces active human involvement, not when it adds another layer to manage.

The “aha” for most finance leaders is this: procurement doesn’t need more tools or tighter policies—it needs orchestration. In practice, that means one connected workflow for request, approval, vendor, invoice, and payment—so teams aren’t making decisions across separate systems with missing context.

If you’re exploring how to fix procurement bottlenecks and procurement process bottlenecks as you scale, the next step is understanding how modern platforms support structured intake, approvals, and real-time spend visibility.
You can book a demo to see how Payhawk helps finance teams manage company spending with greater visibility and control.