What should intake and orchestration change in your organisation?
Intake is where a need first reaches procurement. Orchestration moves it through the lifecycle from there. Procurement Code helps you decide what both should change and gets the organisation ready for it, independent of every platform vendor.
The business
Anyone can ask. Most have never used a procurement system.
We need an agency for the spring launch
Marketing manager
Can we renew our design software?
Creative lead
I need laptops for twelve new starters
HR business partner
Our cleaning contract ends in March
Facilities manager
Intake
Understands each request
The requester
Who is asking, and for which part of the business
Funding
Whether there's a budget, and whose it is
Governance
Which policies and checks apply
Intent
What they're really trying to buy, and why
You decide what each request must tell you, and which answers change the route.
Orchestration
Routes it the right way
A purchase order
In policy, with a contracted supplier
A buying channel
Catalogue, marketplace, card or a self-serve quote
The procurement team
A sourcing event, a negotiation or a contract
A specialist platform
Risk and compliance, contract management or another system that owns the work
You decide which requests go straight through, the channel or system for each kind of spend and when the team steps in.
Brought in along the way
- Finance
- Legal
- Information security
- Data privacy
- Risk
- Budget holder
Some platforms do both. Others put intake in front of the tools you already have. Either way, each one needs its own decisions.
What the platform runs, and what you decide
An orchestration platform runs the workflows across the lifecycle. Each one needs decisions from your side before it can run, and a demo won't show you those.
Engage and plan
The platform runs
Intake, with every request routed to the right approvers
You decide
Which buying channel each request goes to, and the thresholds that decide it
Source, negotiate and contract
The platform runs
Sourcing requests, contract review and approval routing
You decide
Which spend needs a tender, and who can sign at each level
Onboard
The platform runs
Supplier onboarding with risk, security, privacy and bank checks built in
You decide
Risk tiers, so a low-risk supplier isn't held up as long as a high-risk one
Purchase and pay
The platform runs
Purchase orders, approvals and invoice processing
You decide
When a purchase order is needed, and what happens when one is raised late
Manage, perform and exit
The platform runs
Renewals, supplier records and offboarding
You decide
Who owns each supplier relationship, and when it ends
Agents will take on more of this work over time. They act on the same rules, so the rules need writing down first.
What changes around the workflows
The workflows are the visible part. The bigger decisions are about the operating model around them.
How do your policies change?
Policy written for people to remember becomes rules a workflow can run, with thresholds and risk tiers set by category, value and risk.
How do your processes get redesigned?
Not the old process on a new platform. Each route is redesigned around what the platform and its agents can now do.
How do procurement's services change?
Which services procurement offers, and who delivers each one, whether that's self-service, the team, an outside provider or the platform.
Who runs it afterwards?
Where agents take on the routine work, and the team that runs orchestration as a platform once the build is over.
How the work fits around your vendor
Your vendor runs the platform work. Procurement Code works on your side, on the decisions the platform can't make for you.
With Procurement Code
Your vendor
What you have
Where to start
One session · At no cost
The diagnostic session
Your leadership team rates the lifecycle and the governance controls across it, and chooses the first use case.
Before you commit
4 to 6 weeks
Readiness Review
Policies, controls, data, integrations and sponsors checked against what the platform will need, and the business case built with finance.
Alongside the review, or on its own
Proof of concept
Procurement Code runs your side of it. Success criteria are agreed first, then real users test the workflows.
During the build
As your design authority
Blueprint
The policies and decision rights the workflows and agents run on, the buying channels and each role redefined.
After go-live
Until your team runs it
Adoption and the next phase
The old routes closed, adoption measured against the baselines, your team set up to run the platform, and the next use case scoped.
Each piece of work stands on its own. Start wherever your project is today.
Why work with Procurement Code on intake and orchestration
01
Experience as the client
I've led an orchestration rollout from the client side and configured the platform myself, so the advice comes from running it in live operations, not from a demo. Supplier onboarding came down from weeks to days.
02
Strategy and technology together
The orchestration decisions sit inside the procurement strategy and operating model, so nothing gets lost between the people who set the direction and the people who build it.
03
Independent of every vendor
Procurement Code doesn't resell software and takes no commission or referral fee. You engage it directly, and the advice starts from how your business works.
Weighing up intake or orchestration?
Tell me where you are with it, from the first demo to a build that has stalled, and we can work out where to start.
Talk it through
Send a short note about the decision in front of you. I reply personally within a working day.
Get in touch