Podcast Summary 5 min read

Procurement is sales without the quota — Reba Cox on the function of functions

How the gatekeeper posture decays the procurement chair, why the first deal sets every renewal, and what a fruit-basket cloud negotiation looks like.

Reba Cox started in base-metals futures trading on a New York trading floor in February 2008, where she was the only woman in the room and learned to stop saying "dang it" because the traders wouldn't take her seriously. She moved to base-metals procurement at Philips Lighting — same market, other side — and discovered that knowing how 80% of a stamped-steel hinge's cost is just the underlying steel price gives you a different kind of negotiation. The factory-floor years took her to China, Mexico, the US. Six years ago she joined MongoDB to build the procurement function from scratch. She now runs sourcing, contracting, and vendor management for every dollar MongoDB spends that isn't payroll.

The spine is that procurement is sales without the quota — and that everything the function gets right or wrong flows from whether the rest of the company treats it as a partner or a blocker. Reba’s posture is unambiguous: gatekeeping is a failure mode, not a job description. The bedrock practices she runs — zero-dollar touch, first-deal-baseline discipline, the refusal to haggle on price — all serve the same posture. The function lives or dies on the relationship.

The function of functions

Procurement at MongoDB is twelve people sitting across legal, security, internal audit, finance, marketing, product, engineering, real estate, and HR. The role is to represent every other function’s voice in a vendor conversation in a way they can’t themselves — and to do it without becoming the team people work around.

Procurement, by nature, is a function of functions.

The discipline Reba ran from week two at MongoDB was a motto: be the friendliest, most helpful, most can-do team you work with at this company. The point is mechanical — disarm the gatekeeper perception before it forms. The result, six years in, is procurement as a sought-after partner in the conversations that matter. The engineer who told her in week three he’d never work with her took two years to flip; he’s now Slacking her regularly. The procurement leader who muscles their way into a policy before earning the relationship loses both. The one who builds the relationship first earns the right to set the policy.

The first deal is the rest of the deals

The cleanest worked example is software contracting. Most companies — buyers and sellers — don’t realise the first commercial agreement sets the trajectory the vendor’s sales rep will model every renewal against. The annualised run rate becomes the comp-plan baseline. The pricing tier becomes the discount floor. The omission of a price cap becomes a problem that surfaces at renewal three.

The first deal you do sets your baseline for all renewals. A lot of people — especially in a software deal — don't understand that.

Reba’s discipline: never sign a new vendor for more than one year. The trial year tells you whether the product, the relationship, and the terms are real; year two onward is when you commit. Price caps go in from day one — MongoDB now runs 99.5% of contracts with them, which Reba says materially helps both sides because the sales rep can forecast within a known band. Auto-renews are refused. Consumption-based pricing gets split into two buckets: hard limits where internal inefficiency could spike spend, and uncapped paths where customer-driven usage is the whole point. The demand-planning model — borrowed from manufacturing, applied to seat-based software — annoyed sales reps for the first year until they understood the procurement team would rather pay for 60 today and add to it monthly than pay for 100 and waste 40.

Haggling means you didn’t do the work

The negotiation masterclass closes on the line that reframes the whole function.

If you're haggling on price, you've done a bad job. That means you have zero business case if it's just a haggle.

Price is the last 5% of the conversation. The first 95% is demand planning, scope definition, comparison shopping, security vetting, SLA design, and understanding the vendor’s margin structure well enough to know what they can actually move. Reba’s preferred negotiation is one where she helps the vendor reduce their own cost of product so the price she needs becomes achievable for both sides — she’s done this with consumption-based vendors where their cloud contract was the limiting factor. The frame is mutually-beneficial, not adversarial. If a negotiation has been escalated to a procurement leader, somebody has already failed to fight with facts. The fruit-basket frame for cloud contracts captures the same discipline — 60 to 80% of cloud spend is on instances (the apples); the bananas and pineapples are noise until the apples are right.

When to hire — and where it sits

The procurement function should not be optional past a certain stage. Reba’s read: a 600-to-1,000-employee pre-IPO company can start with a hungry manager-level hire from a high-growth environment. Any public company without procurement has missed the mark; SOX controls, security vetting, FedRAMP or HIPAA work all require it. The reporting line depends on the spend mix. Tech (mostly indirect) belongs under the CFO once mature, FP&A as the right launching point for the first hire. Manufacturing (mostly direct) belongs under the COO, because plant managers need a leader who weighs production continuity against margin gains rather than just optimising the financial decision.

You do not want to be a procurement team that's seen as a hindrance. You want to be seen as the people that get stuff done — and represent your stakeholder's voice in a way they cannot.

The argument running underneath every structural recommendation is the same. Procurement that sits in the wrong reporting line, or hired too late, or treated as a gatekeeper, decays into the version that gets routed around. Procurement built deliberately, sitting in the right line, with the relationship discipline to earn the seat, becomes the function that quietly does the work nobody else can.

What to listen for

The full episode runs the only-female-on-the-trading-floor years, the Philips Lighting transition into procurement, the contrast between manufacturing (5–8% YoY savings is rock-star) and tech (security is the headline), the AI-as-new-category scramble that rewrote the intake process mid-year, and the pivot Reba is making out of procurement into sales operations as the broadening move toward an eventual CEO chair — anchored on Apple’s Tim Cook. Her three-word descriptor is Hello Kitty Maximalism. Listen at /podcast/ep-022-reba-cox; for the other procurement essays in the SoF catalogue, see Murali Sundararajan and Michiel de Bruijn, or /topics/procurement-spend.

Related questions

Why does Reba Cox call procurement "sales without the quota"?
Because the procurement leader and the sales rep on the other side of the table want the same outcome — close the deal as fast as possible — but the procurement role is to do it on terms that protect the buying company. Reba's framing rejects the adversarial model: the friction in most deals is communication, not incentive alignment. The line also signals to her team that procurement is not a passive paperwork function. It requires the same relationship discipline, deal hygiene, demand planning, and timing instinct that a quota-carrying seller brings. The difference is the quota; the muscle is the same.
What does Reba Cox mean by the first deal setting the renewal baseline?
Every commercial term agreed in the first contract — pricing tier, discount structure, volume assumption, price-cap mechanics — becomes the starting point the vendor models all future renewals against. A weak first deal compounds into overpayment for years, because vendors anchor their growth forecasts to your annualised run-rate and their sales reps build comp plans around it. Reba's discipline: never sign a new vendor for more than one year, set price caps from day one (MongoDB now has them on 99.5% of contracts), do not accept auto-renews, and treat the first negotiation as setting a five-year trajectory. The negotiation that matters most happens before anyone has used the product.
How should procurement be structured and where should it report?
In tech (mostly indirect spend), procurement belongs under the CFO once the function matures, with FP&A as the right launching point for the first hire. In manufacturing (mostly direct spend), procurement belongs under the COO, because plant managers care about whether margin gains break production lines — a CFO will optimise for the financial decision and a COO will weigh both sides. Reba's call on timing: pre-IPO companies of 600 to 1,000 employees can start with a hungry manager-level hire from a high-growth environment; any public company without a procurement function has missed the mark. The reporting line matters less than ensuring the leader has been through the trenches of large-scale operations.
What is the "fruit basket" approach to cloud-contract negotiation?
Reba's shorthand for prioritising what to negotiate inside a cloud contract: the basket has apples, bananas, and pineapples; the apples are your instances and they account for 60 to 80% of the spend. Almost every win in a cloud negotiation comes from understanding instance pricing, savings plans, and committed-use mechanics. The bananas and pineapples — peripheral services, data egress, support tiers — matter, but they don't move the contract enough to start there. Without instance-level fluency, procurement leaders overpay materially on the apples while haggling over the smaller fruit. The frame is a discipline about where the leverage lives.

Updates

  1. Editorial pass under the v2 podcast-summary guideline.