Inside the Implementation: Codifying Procurement’s Central Nervous System with Shashi Kamath

When you speak with Shashi Kamath about procurement, he doesn’t start with forms, fields, or approvals. Instead, he starts with the ‘central nervous system’ that makes sense of it all. For him, a successful implementation isn’t just about getting workflows live; it’s about codifying how procurement thinks; its policies, categories, exceptions, and relationships, in a way that both humans and AI can understand and use.

With an engineering background, Shashi brings a rare combination of deep procurement expertise and platform-building knowledge to the role, having spent years working at Ariba leading procure-to-pay and catalog engineering before joining ORO. This vantage point has shaped a distinct view: procurement transformations succeed when you treat policies and ontology as product, not paperwork.

From Fragmented Rules to a Central Policy Brain

One of the clearest examples of this mindset comes from experiences with a large life sciences customer, where multiple teams joined early workshops with their own distinct lists of requirements. IT had one set of rules, procurement a second, sourcing a third, and strategic contracting yet another. Each group had legitimate needs, but they were spread across different systems, processes, and spreadsheets.

“Very quickly, we realized that all of this shouldn’t live in separate corners,” Shashi recalls. “These were really just expressions of a single procurement policy.”

Instead of scattering configuration across dozens of workflows, he and the team created a centralized procurement policy layer for the customer. He thinks of this as codifying the organization’s procurement brain:

• Which categories qualify for fast-path purchase orders vs. complex review
• Which supplier types require onboarding approvals vs. auto-approvals
• What thresholds trigger sourcing, contracting, or extra risk checks

All of those rules moved into a single, structured policy file. Changing how procurement behaves no longer meant opening an implementation project; it became updating the organization's ‘central nervous system’ and letting the orchestrated flows respond automatically.

Rapid Prototyping the Art of the Possible

That central policy layer can’t exist in a vacuum, but emerges from a very hands-on, iterative implementation style. Customers frequently arrive asking to “see the art of the possible,” and Shashi’s answer is working software, not slideware.

For one customer with a contracting system, Ariba for buying, and a separate risk management tool, the initial ask was simple: show us how all of this could work together. Within two weeks, ORO had those disparate systems talking to each other and driving a unified view of data and status.

“Seeing everything integrated that quickly is a turning point,” Shashi says. “It helps customers believe their vision is achievable, not just aspirational.”

Those rapid prototypes surface the real patterns: where policies conflict, where hand-offs stall, and where teams duplicate work. That’s when it becomes obvious that codifying a shared policy layer will simplify both implementation and ongoing change.

Orchestrating the Invisible 90% of Procurement Work

Shashi is blunt about the limits of traditional procurement tools: most of them, he argues, only touch a thin slice of the overall journey.

“By the time an order shows up in a typical system, 90% of the procurement work has already happened in email,” he explains. “Sourcing decisions, contract checks, budget conversations - they’re all invisible.”

With a recent customer, ORO used that reality as a design constraint rather than a complaint. Rather than automating a single step, the team focused on orchestrating an entire IT procurement function end-to-end:

• Intake starting from the initial request
• Determining whether sourcing is required
• Checking or creating new contracts
• Managing negotiation and approvals
• Pushing the final, enriched data into the customer’s sourcing, contracting, and ordering systems

The impact was twofold. First, business stakeholders finally had a single, coherent experience instead of a manual email maze. Second, the procurement team saw, in some cases for the first time, what their stakeholders actually go through in order to get something done.

“When everything is orchestrated, procurement can see their own value more clearly,” Shashi notes. “They’re not just processing a purchase order; they’re enabling the full decision process that leads up to it.”

Freeing Procurement From Compliance Firefighting

That visibility is particularly powerful in industries including the pharmaceutical and life sciences, where compliance is non-negotiable and the stakes are high. Historically, procurement teams in those environments have spent a disproportionate amount of time policing documentation and chasing details, often at the expense of partnering with the business.

Shashi’s view is that modern orchestration platforms should absorb most of that burden. By encoding compliance rules directly into the central policy layer, and ensuring every step of the process flows through ORO, teams move from manual firefighting to automated guardrails.

“With compliance handled by the system, procurement can shift their energy to the value they provide to stakeholders,” he says. “They’re not just the back-office function saying no; they’re the partner helping the business get to yes in the right way.”

This shift can be clearly seen in customers that implement orchestration across an entire function, such as IT, from end-to-end for their initial go-live. Rather than a narrow win around supplier onboarding, for example, they experience a transformation of how an entire part of the company can ask for, approve, and receive what it needs.

UX as the Full Interaction, Not Just the Interface

It’s tempting to equate “great user experience” with a clean interface and modern design, but Shashi’s definition is far broader.

“For us, UX isn’t just the screen,” he explains. “It’s the entire interaction a business user has with procurement, compliance, IT, and security. Everyone involved in getting their request fulfilled is part of the equation.”

That perspective shapes how ORO approaches early implementation phases. The goal is not only to make an intake form intuitive; it’s to ensure the whole journey feels coherent:

• Clear expectations when a request is submitted
• Smooth hand-offs between teams without repetition
• Visibility into transaction status and next steps

By bringing every relevant team into a single orchestration platform, ORO enables customers to redesign the end-to-end interaction pattern. The interface is just one expression of a deeper change in how people collaborate around procurement.

Feeding AI with Procurement’s Ontology

Underneath all of this sits what Shashi calls the ontology of procurement: a structured map of entities, policies, and relationships across systems. “When we say we know procurement, we don’t just mean we’ve seen a lot of flows,” he says. “We know how the domain is structured; the objects, rules, and dependencies, and that’s what we expose to AI so it can solve real problems.”

This tackles two chronic problems for procurement teams: fragmented data and fragmented policies. On the data side, the same supplier might appear as Vendor_ID: 99402 in the ERP and Contract_Party_ID: AC-77 in the contracting system. ORO’s ontology resolves those identities into a single master [Supplier: Acme], giving teams a 360-degree view of total spend and active contracts.

Policy fragmentation looks similar. A contract may specify Net 45 with a $50k cap while the ERP defaults to Net 15 and allows overspend. Attaching the right policies directly to the [Supplier: Acme] master concept, ORO centralizes logic enforcement so invoices that violate contract terms are automatically overridden or flagged.

As ORO also understands how suppliers, orders, and invoices are structured in ERPs like SAP, Oracle, and NetSuite, it can quickly interpret each customer’s setup and connect these objects in a way that reflects their reality. That is how in a rapid two-week “art of the possible” prototype, the team can go beyond basic API writing and stand up an integrated, ontology-driven view of suppliers, contracts, risk, and transactions that customers immediately recognize as their own.

This is where the ‘central nervous system’ metaphor really comes to life. The policy and ontology layer is the nervous system; AI agents are the reflexes and higher-order thinking that operate on top of it.

Implementation as the Moment the Nervous System Comes Together

For Shashi, implementation is where all of these threads converge. It is the moment when procurement’s scattered rules, data, and workflows are wired into a single central nervous system that both people and AI can rely on.

“In a way, the ontology and policy layer looks a lot like a brain,” he explains. “The grey matter is where we codify the data structures across systems, and the white matter and reflex paths are how we codify and enforce central policies.” In practice, that means supplier, contract, order, and invoice data from tools like SAP and Oracle are modeled consistently in ORO’s ontology, while policy logic determines how signals travel through that network, triggering the appropriate action.

When that nervous system is in place, teams move from tweaking individual workflows to updating how the brain itself thinks and reacts. Changing a policy or onboarding a new system becomes a matter of adjusting the central model, with every orchestrated flow and AI assistant responding automatically.

Want to learn about how ORO can transform procurement at your organization? Book a demo with one of our experts.

By Kate Jeter, Director of Global Field Marketing

Kate Jeter is a strategic B2B procurement tech marketing leader with 25+ years of experience specializing in field marketing, events, and demand generation for SaaS and enterprise platforms. Before ORO, she was the Head of Marketing, Community, and Growth at ProcureTech. She is an expert in aligning marketing and sales for revenue acceleration, pipeline growth, and global brand positioning.