The first 90 days: why new CFOs discover procurement has no outreach engine

Day 47.

The new CFO has already finished the budget review, met every department head, sat through the forecasting discussions, and signed off on the close. Most of the onboarding process has been strangely reassuring. Revenue visibility looks decent. Headcount planning seems under control. Finance has dashboards. Procurement has software. Operations has process owners. Everybody describes the environment as disciplined.

Then she asks for the vendor file.

What arrives is technically organized. There is a procurement export. A contract folder. Several spreadsheets. Historical sourcing comparisons. Archived RFQs. Somebody from procurement joins the call to help explain category ownership because the naming conventions stopped making sense after the company crossed two hundred employees.

Within an hour, several uncomfortable things become obvious.

Nobody agrees on how many active suppliers the company actually has.

Finance believes the count is around 180.

Procurement says it depends how vendors are categorized.

Operations points out that regional teams still source independently in certain categories.

A sourcing manager quietly mentions that several inactive suppliers are still technically live inside the system because cleaning vendor records has never been prioritized.

Then someone notices the same supplier appears under three slightly different names.

The room goes quiet for a second.

This is usually the moment new CFOs begin discovering how procurement actually functions inside growing companies.

Not in theory.

Operationally.

The interesting part is that none of this happens inside obviously dysfunctional businesses. Most companies experiencing this already invested heavily in procurement modernization. They implemented Coupa, Ramp, Zip, SAP Ariba, or some combination of spend management, approvals, procurement workflows, and finance visibility tooling. Purchase requests route correctly. Payments are controlled. Approvals exist. Contracts have owners.

From far enough away, the system looks mature.

The friction only becomes visible when the organization needs to source vendors quickly.

A supplier raises pricing unexpectedly. A manufacturing category suddenly needs alternatives outside China. A portfolio company acquisition creates vendor overlap. Leadership asks procurement to test the market before the next operating review.

Then the company discovers how much sourcing still depends on spreadsheets, inboxes, institutional memory, and whoever happens to remember the last RFQ process.

Most new CFOs end up running some version of the same hidden audit during their first ninety days.

The vendor count is usually the first surprise.

Leadership thinks the company works with perhaps 150 suppliers. The actual number is often three to five times higher once agencies, contractors, regional purchasing, software vendors, logistics providers, facilities suppliers, inherited relationships, and one-off sourcing decisions are included. Nobody intentionally created the sprawl. Growth created it naturally. Teams optimized locally. Procurement inherited the complexity afterward.

Spend distribution reveals another pattern.

A relatively small percentage of suppliers controls most spend while hundreds of lower-visibility vendors continue operating quietly in the background. Those vendors rarely receive strategic attention because procurement teams are already overloaded maintaining operational continuity across the rest of the environment.

The contract repository usually tells its own story.

Despite years of procurement tooling investment, critical sourcing context still lives across Google Drive folders, shared inboxes, local spreadsheets, Slack threads, procurement exports, and documents nobody updated after employees left the company. Historical quote data technically exists, but retrieving it in a usable format often takes longer than rebuilding the sourcing process from scratch.

That realization changes the tone of the onboarding process very quickly.

Because the problem stops looking like procurement visibility and starts looking more like missing sourcing infrastructure.

Most procurement modernization projects focus heavily on spend management. The company buys systems for approvals, compliance, invoice workflows, vendor governance, payment controls, procurement requests, budget visibility, and renewals. Those systems solve real operational problems.

But they quietly assume something important.

The supplier already exists.

That assumption shaped the architecture of the category.

The downstream layer became sophisticated. The upstream layer remained surprisingly manual.

This becomes obvious around months two through four of a CFO transition because that is often when vendor change starts accelerating. Underperforming suppliers need replacement. Procurement teams get pressure to diversify sourcing. Acquisitions create duplicate vendors. Manufacturing teams request alternatives because pricing shifted or lead times became unstable.

The organization suddenly needs to identify, evaluate, and compare suppliers quickly.

That is where sourcing starts feeling older than the rest of the stack.

A sourcing manager manually searches supplier directories.

Someone forwards old RFQs trying to remember who handled the category last year.

Procurement reaches out through generic website forms because nobody can identify the correct operational contact.

Quotes arrive across PDFs, spreadsheets, email bodies, screenshots, and calls.

Finance asks for a side-by-side comparison before Friday.

Now somebody has to manually normalize fragmented information before leadership can even discuss the decision itself.

Sales organizations solved versions of this operational problem years ago.

Nobody expects revenue teams to manually search websites, organize outreach through spreadsheets, lose pipeline context every quarter, and rebuild prospect history repeatedly from memory. Modern outbound infrastructure evolved because customer acquisition became too operationally expensive without systems.

Procurement sourcing never fully went through the same transition.

There is still no true equivalent of Salesforce for vendor outreach inside most procurement environments.

The consequences accumulate quietly.

Time-to-quote expands dramatically because sourcing teams spend weeks discovering suppliers, locating the right contacts, clarifying missing information, and reconstructing sourcing context manually. A process that should take one week turns into four.

Response rates stay lower than expected because outreach frequently lands in generic inboxes instead of reaching the correct operational contacts. Procurement teams waste time chasing replies rather than evaluating suppliers.

Historical quote data disappears constantly because sourcing events operate like isolated projects instead of persistent intelligence systems. The same RFQ gets recreated every twelve or eighteen months because nobody can retrieve prior comparisons cleanly.

Eventually comparison quality itself begins degrading.

Vendor evaluation drifts toward intuition because information arrives inconsistently and sourcing teams are forced to rebuild context manually under time pressure. Procurement leaders know categories should be re-sourced more aggressively, but the operational burden attached to running a clean sourcing process becomes difficult to justify continuously.

One procurement operator at a manufacturing company described it bluntly during a sourcing review.

“We know some categories are overpriced. We just don’t have the bandwidth to reopen them properly every year.”

That sentence explains a surprising amount of procurement behavior inside mid-market companies.

The organizations adapting fastest are beginning to treat sourcing differently.

Less like administrative coordination.

More like infrastructure.

The shift usually starts with defining what a qualified supplier actually looks like before urgent sourcing begins. Procurement teams identify the categories carrying the highest operational risk, then build structured vendor profiles around geography, certifications, production capacity, lead times, logistics capabilities, responsiveness, pricing structure, and compliance requirements.

Supplier discovery becomes more systematic after that.

Instead of relying on scattered searching and institutional memory, procurement teams begin identifying candidate vendors against explicit sourcing criteria. Outreach happens through identified contacts instead of generic forms. RFQs become structured enough that quote comparison can happen consistently. Historical sourcing data survives long enough to become operationally useful later.

The interesting change is what starts compounding once sourcing information accumulates structurally.

Procurement teams recognize supplier response patterns across categories.

Finance gains historical pricing context instead of isolated snapshots.

Leadership can reopen sourcing conversations faster because prior vendor intelligence still exists in usable form.

A sourcing intelligence layer gradually emerges where previously there was mostly fragmented operational memory.

This is the infrastructure category beginning to appear between spend management systems and procurement operations.

Tools operating in this layer, including Glidely, focus less on controlling purchasing activity and more on helping companies discover suppliers, coordinate outreach, centralize quote comparison, and retain sourcing intelligence over time.

For most new CFOs, the first ninety days after recognizing the gap become less about buying another procurement platform and more about understanding how sourcing currently operates inside the company.

The first thirty days usually focus on inventory. Which vendors are actually active, which categories carry concentration risk, where sourcing ownership lives, and how much supplier knowledge depends on specific employees rather than systems.

The following thirty days tend to revolve around defining supplier criteria more rigorously. Procurement and finance identify categories where pricing volatility, operational dependency, supplier concentration, or geopolitical exposure create the highest sourcing risk.

The final stage involves running at least one structured sourcing workflow end-to-end. Supplier discovery becomes systematic. Outreach becomes centralized. Quote comparison becomes standardized enough that leadership can review vendors inside a shared framework instead of scattered spreadsheets.

At that point, the operational problem usually becomes much easier to describe.

The organization did not merely lack procurement visibility.

It lacked sourcing infrastructure.

And once finance leaders recognize that distinction, they start noticing versions of the same gap almost everywhere inside the business.

Frequently asked questions

Should a new CFO buy procurement software during the first 90 days?

Most companies already have substantial spend management infrastructure in place. The more useful question is whether sourcing workflows themselves remain fragmented.

How can companies tell whether they have an outreach problem or a spend management problem?

If supplier discovery, outreach, RFQ coordination, quote comparison, and historical sourcing retrieval still depend heavily on inboxes and spreadsheets, the sourcing layer is likely underbuilt.

Why do procurement teams still rely so heavily on email?

Because most procurement tooling categories evolved around governance, approvals, and spend visibility while supplier acquisition workflows remained comparatively manual.

What is the difference between Coupa, Ramp, Zip, and a vendor outreach engine?

Spend management systems govern purchasing activity after suppliers enter the environment. Vendor outreach infrastructure focuses more heavily on supplier discovery, outreach coordination, quote comparison, and sourcing intelligence retention.

Do companies need a CPO before improving sourcing infrastructure?

No. Many mid-market companies begin improving sourcing workflows long before building large procurement organizations because operational sourcing pressure appears earlier than formal procurement maturity.