The Procurement Playbook: Transforming Your Purchasing Process with Ramp

Mystery invoices are showing up in AP, large purchases are surfacing on expense reports a month after the fact, and three teams are paying for three variations of the same tool that you only find out about at renewal. The procurement process you set up 2 years ago has hit its limit, and tightening the rules is making employee adoption worse, not better.

Chris Sumida leads go-to-market for Ramp's procurement products, while TK Kong is a product lead who has been at Ramp for over 5 years. Together they walk through 5 warning signs that your procurement process is broken, plus a live demo of the intake-to-pay workflow they recommend instead.

If you're dealing with maverick spend, software sprawl, or a fragmented approval process, keep reading.

Top 5 takeaways from the session

1. Indirect spend is the silent killer

Ramp's own transaction data shows SaaS alone grew 24% year over year last year. If you don't have an intake form capturing requests before money moves, you've already lost your chance to negotiate, consolidate, or say no. When mystery invoices keep showing up in your AP queue, that's a system problem, not an employee problem.

2. Most bypassers don't know procurement exists

As Chris put it, "Not every employee at your business is being malicious. They may simply not even know there's an approval process to begin with, which is an entirely separate problem."

That changes the fix, because the answer isn't stricter enforcement but making the intake process faster and clearer than whatever workaround employees are already using. When the path of least resistance is also the compliant path, adoption follows.

3. Transparency is the operating principle

Ramp's own procurement lead has a phrase the team uses internally: "time to operate in the open." When requesters, managers, legal, IT, and finance can all see where a request stands and the rationale behind every decision, procurement moves faster and earns the trust that drives adoption. When employees can't see what's happening with their request, they find workarounds.

4. Parallel approval paths compress cycle time

The most important design choice in the demo is a canvas-based workflow where legal and IT or security review happen at the same time instead of one after the other. Add conditional routing so requests over $25K go one way, contracts trigger an Ironclad workflow, and sensitive data triggers a security questionnaire.

Your approvers handle more requests without adding days to the timeline. Some Ramp customers run their full procurement cycle 80% faster than before adopting the platform.

5. Price intelligence at the moment of approval

When a Datadog request hits the queue, the procurement admin sees a benchmark of what other companies pay for the same SKU. That data is anonymized, normalized by payment frequency, and surfaced right inside the approval workflow.

The goal is:

"Helping you provide those insights at the time of request so that approvers, procurement folks, and professionals have all this visibility in one place without having to have ten different tabs open."

That data comes from Ramp's network of 30,000 customers (at the time of the webinar) and lands exactly where negotiation decisions get made.

Why does stricter procurement policy stop working?

Stricter procurement policies stop working because the problem was never insufficient rules. Most finance and procurement leaders, when they feel their process slipping, reach for more policy: tighter thresholds, more mandatory approvers, and a sternly worded email about the procurement portal. None of that works.

The problem is that procurement was built to control spending, not to help people buy what they need. As Chris framed it:

"[Procurement] was primarily viewed as very transactional and has led to procurement departments being seen as these gatekeepers controlling spend through a strict set of rules rather than as a strategic partner."

That produced systems that are rigid, opaque, and unpopular with the employees who are supposed to use them. When you layer stricter rules onto a system employees already resent, you just generate more workarounds.

The shift Chris and TK describe is structural: design the process around the people using it, make everything visible, and make the right path easier than the workaround. Do those three things and you'll start seeing spend earlier, consolidating vendors, and negotiating better contracts.

One intake form with conditional routing handles every purchase request

The whole system runs on one intake form. It captures what every approver needs to know, then routes the request to the right people based on the answers.

Here's how it works in practice.

1. One entry point for every request: Not email for one team, Slack for another, and Jira for a third. One form, the same form, for every purchase request
2. AI populates the request from a quote or screenshot: An employee drops in a vendor quote, contract, or shopping cart screenshot. Ramp's AI fills in vendor name, amount, contract term, and custom fields automatically
3. Conditional questions surface dynamically: If an employee answers yes to "do you have a contract," a follow-up appears asking them to upload it. If they indicate sensitive data will be shared, security questions surface automatically. Approvers get the context they need without requesters guessing what's relevant
4. Routing rules match the request to the right approver: Routing can depend on deal size, department, vendor type, GL category, whether the vendor is new, or whether there's a contract. Each condition routes to the right approver or triggers an integration like an Ironclad workflow
5. Parallel paths run simultaneously: Legal and IT review at the same time rather than in sequence

A reasonable place to start is one purchase category, the 5 to 7 questions every approver needs answered, and one form for it.

How the 5 warning signs show up in real companies

If 2 or more of these 5 signs are showing up at your company, your procurement process has hit its limit.

• Rapid growth with unmanaged purchasing: As headcount and vendor count scale, indirect spend balloons faster than anyone realizes. Ramp's SaaS data shows indirect spend growth 24% year over year. The symptoms are mystery invoices in AP and large purchases discovered on expense reports 30 days after the fact.
• Employees bypassing approvals: Sometimes intentional, mostly not, and the result is the same regardless—unnegotiated contracts, off-the-shelf pricing, budget overruns, and elevated fraud exposure
• Vendor overlap and software sprawl: Marketing is on Asana. Another team is on Monday.com. Three departments are paying for variations of the same tool. Nobody can see seat utilization, so you can't tell at renewal which contracts to consolidate or cut.
• Legal and IT flying blind. Procurement is inherently cross-functional. When your legal and security teams can't see what's being purchased, contracts get signed without review and sensitive data goes to vendors who haven't passed a security check.
• Vendors underperforming without accountability. You're not running regular supplier evaluations. You're not managing renewals proactively. You discover the problem when you're already locked into another 2-year term.

The AI intake form and conditional question logic

For the person making a purchase request, it starts with one form. An employee opens Ramp, clicks request funds, picks the relevant spend program, and either fills the form manually or drops in a quote.

“Employees can simply just drop in a quote, contract, or screenshot, and Ramp will fill out the request for them. It's super easy. There's pretty much no training required."

The build: Admins define the form questions in advance: amount, vendor, contract term, the problem being solved, whether a contract exists, whether sensitive data will be shared, and GL coding if required. Each question can be marked required or optional, and any question can trigger a conditional follow-up.

The guardrail TK demonstrated is a conditional question chaining: If a requester answers yes to "do you have a contract with this vendor," a second question appears asking them to upload the order form. If they answer yes to "will we be sharing confidential or sensitive business information," additional security-related questions surface. The requester only sees what's relevant to their specific request, and approvers get the full context without chasing follow-ups.

In the demo: TK filled out a $100,000 HubSpot services request live on the call, including conditional contract upload and tagged collaborators in the activity thread, in a fraction of the time the same request would take across email, separate legal tickets, and after-the-fact GL coding.

The canvas approval workflow with parallel paths

Once a request is submitted, it enters a visual approval canvas where multiple reviewers can work in parallel, cutting cycle time significantly. TK demoed the workflow builder live.

Each approval step is a node on a canvas, and admins can require approvals, send notifications, insert pauses, or trigger external integrations. Conditions fire on amount, department, role, location, entity, manager, vendor, request answers, or HR-integration fields, and multiple conditions can stack on a single branch.

"It's really customizable, and you can set these conditions or you can overlay multiple conditions."

The named guardrails:

• Parallel approval paths: Legal and IT review simultaneously, not sequentially, after manager approval
• Automated delegates: If an approver is out of office and didn't set one, an admin can skip the step and approve on their behalf, with full audit trail
• Version control: The canvas builder maintains version history so admins can reference and roll back workflow changes

TK walked through a software procurement workflow with manager approval, parallel legal-and-IT review, a triggered Ironclad workflow for contract review, and a final procurement admin sign-off, all visualized on a single canvas. Approvers can act from Slack, Teams, or email without logging into Ramp.

Price and seat intelligence at the point of decision

Price intelligence surfaced inside the approval workflow is the feature most likely to change how you negotiate renewals.

Ramp anonymizes and normalizes transaction data across its network of 30,000 customers (at the time of the webinar) to generate real-time pricing benchmarks at the SKU level.

“With Ramp's vast data that we have across 30,000 customers, we're able to anonymize data and provide insights called price intelligence."

When a Datadog request hits the queue, you see benchmarks for that specific SKU, sliced by payment frequency and contract length, directly inside the request view.

For customers who connect their Okta instance, Ramp pulls SaaS usage data showing actual seat utilization against contracted seats and ties it to the payment data already in the vendor record. You see what you're paying, what you contracted for, and how many seats are actually being used, all in one view.

TK showed the Datadog vendor record with full spend history, outstanding POs, card transactions, reimbursements, contracts, and the price intelligence benchmark all in a single view. You don't need to open 10 tabs across review sites and benchmarking tools, because the data is where the decision happens.

POs, three-way match, and AP in one platform

With Ramp, your POs, bills, card transactions, and payments all live in one platform, which is what separates it from standalone procurement tools.

"With Ramp, since it's under one platform, under one hood, you're able to connect the dots super easily."

Approved requests automatically generate purchase orders, and you can pay down POs by card transaction, vendor invoice, or both, against a single committed budget. When an invoice arrives, Ramp reads it, matches line items against the PO, and routes it to AP for payment. Three-way match (adding a receiving confirmation step) is available for teams that need it.

“Let's say you contracted for $3,000 for an implementation fee, but they bill you $5,000, Ramp will actually automatically flag that for you, and then you can design the approval process."

If a vendor invoices for a different rate, a higher quantity, or a line item the original PO didn't include, Ramp routes it to the approval process you've defined.

From a bill view, an AP manager can click directly back to the originating PO to see the full audit trail: the original request, all approvals, attached contracts, and every card transaction and invoice matched against the budget.

There's no reconciliation across disjointed systems, and POs sync natively into QuickBooks Online and NetSuite, with CSV export and API options for other ERPs.

Supplier onboarding and renewal management

Most procurement teams leave two things unfinished: vendor onboarding and renewal management. Ramp handles both.

Supplier onboarding

Traditional vendor onboarding (W-9 collection, payment details, security questionnaires, COIs) takes 2 to 4 weeks.

"We've removed a ton of friction because we know it's very painful today for procurement teams to do vendor onboarding, or it might take two to four weeks for suppliers to onboard."

Ramp sends a link to the vendor contact, who fills out a custom form designed by your procurement team and submits the information in one pass. The vendor record stays in draft status until the request is approved, and if the request is rejected, the record archives without polluting your vendor master.

Renewal management

Ramp reads and extracts contract metadata on upload, and reminders fire at 30, 60, or 90 days before renewal, routed to the vendor owner by default or to custom groups you define. Combined with price intelligence and seat intelligence, you walk into every renewal with data instead of scrambling to pull it together.

Final thoughts

Modern procurement isn't a tooling upgrade. It's a design shift: make the compliant path easier than the workaround, operate in the open, and put data where decisions happen. The 80% cycle-time improvement is a downstream effect of those choices, not the goal.

Start with one category and one form.

See how Ramp fits in

If unapproved purchases, duplicate software, or a messy approval process keep showing up in your AP queue, the fix starts with one intake-to-pay platform your employees will actually use. That’s what Ramp Procurement was made to fix.

FAQs

What's the difference between intake-to-pay and traditional procure-to-pay?

Traditional procure-to-pay starts at the PO. By the time a PO exists, someone has already negotiated the deal, reviewed the contract, and picked the vendor, usually over scattered emails and Slack threads. Intake-to-pay starts one step earlier, at the moment an employee decides they need to buy something, and that earlier capture is what gives finance, legal, and security a chance to weigh in before the dollar is committed, not after.

What does overbilling protection actually catch?

Ramp uses AI to read bill line items and match them to PO line items based on description, amount, quantity, and rate. If a vendor invoices for a different rate, a higher quantity, or a line item the original PO didn't include, Ramp flags it and routes it into the approval process you've defined. Three-way match adds a receiving confirmation step on top of that for teams that need it.