Procurement Process Steps, and What They Mean for Sellers
The procurement process is the sequence a company follows to buy something: identify the need, request approval, evaluate suppliers, negotiate, sign, receive, pay, and manage the relationship afterward. ASCM lays it out in seven stages, and CIPS stretches it to thirteen for complex buys. If you sell software, those steps are not abstract. They are the exact path your deal walks after your champion says “I love it.”
This guide covers the steps the way a buyer sees them, then the way a seller experiences them. I’ll flag where software deals actually stall, because that’s where most forecasts quietly die.
TL;DR
- A standard procurement process has seven stages (ASCM): identify the need, submit a request, evaluate and select, negotiate, finalize the contract, implement, and manage the supplier. Larger organizations split these into as many as 13 steps.
- The number of steps matters less than who gets involved and when. Cross-functional stakeholders pulled in at the “identify the need” stage create less pushback later.
- For software, legal and security review is usually the bottleneck. Practitioners report it can run 6 to 12 weeks when documentation is incomplete.
- Sellers win procurement by preparing for it early: security documents, editable contracts, and something your champion can forward to people who never attended the call.
Table of Contents
- The procurement process in seven steps
- Why you’ll see 5, 7, 9, 10 or 13 steps
- The procurement process flow, in plain terms
- What changes for software purchases
- Where deals die inside the process
- How to sell through procurement
- Our perspective: procurement is a memory problem
- Where TrailerCast fits in the process
- A quick checklist for your next deal
- FAQ
- Sources
The procurement process in seven steps
Frameworks differ in how many steps they count, but they describe the same journey. Here is the seven-stage version from ASCM, with what each stage looks like in practice.
1. Identify the need
Somebody feels a pain: a team is drowning in manual work, a tool is being retired, an audit found a gap. The business defines what it needs, why, and roughly what it’s worth. This is where requirements, budget range, and the list of affected teams get set.
For sellers, this is the cheapest moment to influence the deal. Requirements written now become the scorecard used later.
2. Create and submit a purchase request
The requester files a formal request, often called a requisition. It states what is needed, the estimated cost, and the justification. In many companies, even small software and SaaS purchases go through review regardless of cost, as one college’s published policy shows. Don’t assume a $59 seat escapes the process.
3. Evaluate and select suppliers
Procurement compares options on price, capability, risk, and reputation. Formal buys use an RFI, RFP, or RFQ. Informal ones use a shortlist and a few demos. This is the stage most sales teams think of as “the deal.”
4. Negotiate terms
Price is only one lever. Payment terms, term length, renewal caps, liability limits, data-handling language, and service levels all get negotiated. Procurement teams increasingly look beyond the lowest price. ASCM describes a shift toward total value contribution, which asks what the purchase does for the customer, not just what it costs.
5. Finalize the contract
Legal, security, finance, and the business owner all sign off. The document gets signed. This is where deals slip from “this quarter” to “next quarter.”
6. Implement the contract
The purchase order is issued, the goods or service is delivered, and the invoice is matched against what was ordered and received before payment. In software, this is onboarding and provisioning.
7. Manage the supplier
Procurement tracks performance, handles renewals, and watches spend. It’s the stage buyers wish they’d planned for earlier, and the one sellers forget exists until a renewal goes sideways.
Why you’ll see 5, 7, 9, 10 or 13 steps
Search this topic and you’ll find lists of five, nine, ten, and thirteen steps. They aren’t contradicting each other. They are cutting the same process at different resolutions.
| Framework | Steps | What changes |
|---|---|---|
| ASCM | 7 | Compact: need, request, evaluate, negotiate, contract, implement, manage |
| Many vendor guides | 9 to 10 | Splits requisition review, purchase order, receiving, and invoice payment into their own steps |
| CIPS | 13 | Starts at specification and tender and ends at asset management |
ASCM notes that frameworks vary from 7 to 13 steps depending on organization size, maturity, and complexity. A 40-person startup buying a note-taking tool may do four of these in an afternoon. A regulated enterprise buying a platform may do all thirteen over a quarter.
The practical takeaway: ask your buyer which version they run. “What does your approval path look like after the demo?” is the single most useful question in a software deal, and it takes ten seconds.
The procurement process flow, in plain terms
If you’d rather see the flow than the list, think of three phases:
- Sourcing: identify the need, get approval, find and evaluate suppliers.
- Purchasing: negotiate, contract, and issue the order.
- Payment and management: receive, verify, pay, and track the relationship through renewal.
Most approvals are gates between those phases. A request gets approved or sent back. A contract passes legal or returns with comments. An invoice matches the order or it doesn’t. Every gate is a place where a deal can wait, and every wait is a place where your champion has to speak for you when you aren’t there.
What changes for software purchases
Buying software is different from buying office chairs. There’s no physical receipt, the risk lives in data and access, and the contract can renew itself.
Security and legal review is the long pole
Practitioners describe legal and security reviews as the main bottleneck in B2B SaaS procurement, often taking 6 to 12 weeks. The same source says delays are commonly caused by contracts that can’t be redlined and by incomplete documentation. Procurement teams often view SaaS through a risk lens, using frameworks such as SOC 2, NIST 800-53, or FedRAMP, and a vendor without standard security documents raises a red flag.
One independent benchmark paints a similar picture for renewals: redlines take 3 to 5 business days per round, and security review can add 2 to 4 weeks. Timelines vary by deal size, but the pattern holds. Paperwork, not enthusiasm, sets your close date.
If you’re selling into government or federal-adjacent buyers, the process gets more formal. The FedRAMP Agency Authorization Playbook has a pre-authorization phase where the agency and the cloud provider agree to partner and plan the authorization together.
Procurement wants to be early, not late
Forrester analysts, as summarized in a software procurement guide, argue procurement should be involved before vendor selection and should bring benchmarking data on what comparable companies pay for similar software. If you hear about procurement for the first time after verbal approval, you’re already behind.
Contracts renew themselves
The same guide reports that 69% of software contracts contain auto-renewal clauses, with cancellation windows typically of 30 to 90 days. Buyers who track renewals in a spreadsheet miss them. Sellers who forget the buyer’s renewal calendar miss the expansion conversation.
Where deals die inside the process
The calls were never the problem. The space between them was.
Here’s a scene you’ve lived. Your demo goes great. The champion is excited. Then she walks back to a CFO who wasn’t on the call, a security lead who needs answers buried in a recording nobody will rewatch, and a requisition form asking her to justify the spend from memory. The deal dies in an internal meeting you weren’t part of.
Map that to the steps:
| Procurement step | Who shows up who wasn’t on your calls | What usually goes wrong |
|---|---|---|
| Purchase request | Budget owner, finance | Champion can’t articulate the business case in their words |
| Evaluate suppliers | Procurement, IT | Your pricing and scope get compared to a one-line summary |
| Negotiate | Procurement, legal | Concessions are asked for without context on value |
| Security review | CISO, security analyst | Incomplete questionnaire, slow responses |
| Contract | Legal | Locked PDF, no redlining, version confusion |
| Manage supplier | Ops, finance | No owner for renewal and adoption |
None of those are product problems. They’re coordination problems, and they’re the reason multi-threading matters. One champion is a single point of failure. Every additional stakeholder who has seen the right slice of your story is insurance.
How to sell through procurement
You can’t skip the steps, but you can make each one faster. These are the habits we’d put in place before the first demo.
- Ask about the path early. In discovery, ask who signs, who reviews security, and who handles legal. Write the answers down and keep them attached to the deal.
- Get the security packet ready before anyone asks. Keep current certifications, a pre-filled questionnaire, and a data processing agreement on hand. Our guides on answering security questionnaires and vendor DPA requirements cover what reviewers look for.
- Send contracts in an editable format. The reported delay from locked documents is avoidable. See our notes on contract redlining best practices and shared document versioning.
- Give each stakeholder their own version of the story. A CFO cares about cost and payback. A CISO cares about data handling. Don’t make your champion translate.
- Propose a pilot. Practitioners recommend starting with a smaller pilot to confirm value before a full rollout, since it reduces internal friction and procurement pushback.
- Talk value, not just price. If procurement is thinking in terms of total value, bring numbers that show it. Strategic decision criteria for procurement tooling are also explored in this piece on procure-to-pay automation, which is useful if you want to understand how buyers’ own systems evaluate spend.
- Track engagement. If the CFO opened your pricing page and nobody else did, you know where to focus. Our write-up on content engagement tracking shows what signals to watch.
Our perspective: procurement is a memory problem
We built TrailerCast around one observation: the stages of a B2B deal aren’t really separated by process, they’re separated by people forgetting things. The procurement steps above are an organized way for a company to remember what it needs, what it was promised, and what it signed.
The seller’s version of that problem is the same. The notes from call one live in one tool. The demo recording lives in another. The deal room is a folder. The contract is a PDF in an inbox. By the time legal asks a question about something your rep said in discovery, nobody can find it.
Our view is that a deal should have one memory. That means the calls are transcribed and summarized, the demo is cut down to the 8 to 15 minutes that mattered, stakeholder-specific trailers go to the people who weren’t on the call, and the signature and handoff are part of the same workspace. When a champion has to re-sell your product from memory to a procurement committee, you’ve asked her to do your job without your materials.
We also think procurement is not the enemy. Procurement teams are doing risk management on money and data. The sellers who treat them as a stakeholder to equip, rather than a hurdle to dodge, close faster and renew more often.
— Daniel
Where TrailerCast fits in the process
If you sell to multi-stakeholder buyers, TrailerCast covers the stretch from the first call to the post-close handoff in one workspace: call notes and a running Deal Brief, AI-edited demo trailers, buyer-facing deal rooms, embedded eSignature, and a handoff brief for customer success. There is one plan with every feature, from $59 per month per seat. You can see how the stages connect on the features page.
A quick checklist for your next deal
Before you leave the next discovery call, make sure you know:
- Who owns the budget, and who will file the purchase request.
- Whether procurement or security review is part of the process, and when it starts.
- Which security and compliance documents the buyer expects.
- Whether the contract will be negotiated in an editable format.
- What the auto-renewal and cancellation terms will look like.
- Who will own the relationship after signature.
That list is short on purpose. Six answers, captured early, remove most surprises from the back half of the deal.
FAQ
What are the 7 steps of the procurement process?
ASCM’s seven stages are: identify the need, create and submit a purchase request, evaluate and select suppliers, negotiate terms, finalize the contract, implement the contract, and manage the supplier. Other frameworks add steps such as requisition review, purchase orders, and invoice matching, but they cover the same ground.
What are the 5 R’s of procurement?
The five rights are right quality, right quantity, right price, right time, and right place, as recognized by bodies like ASCM. They describe the goals a purchase should meet, not the steps to get there.
How is software procurement different from general procurement?
The risk sits in data, access, and contract terms rather than in physical goods. That means more weight on security and legal review, SOC 2 or similar documentation, and auto-renewal clauses. Reported review timelines for B2B SaaS run from several weeks to as long as 12.
How can a seller speed up a buyer’s procurement process?
Learn the approval path in discovery, have security documents and a data processing agreement ready, and send contracts in an editable format. Give every stakeholder material written for their concerns, and offer a small pilot if the buyer is wary of a full rollout.
Sources
- ASCM: What is procurement?
- ASCM: Prioritize Value Over Cost for Procurement Success
- CIPS: The thirteen steps of the procurement process
- CIPS: Procurement Supply Cycle
- Software Procurement Guide: Process & Best Practices
- Hennepin Technical College: Software Purchase Requests
- How Long Does a SaaS Renewal Actually Take?
- FedRAMP Agency Authorization Playbook