Built agentic procurement workflows on real category desks — from commodity buying to global IT sourcing. Identified Pactum AI and Coupa before the category had a name for it. The same methodology — governance framework, model routing, capability tiers, board-level KPIs — is what the ProcureAI suite packages for any function serious about running AI as infrastructure, not piloting it.
The field notes — what held in production and what didn't — live under /insights.
Every SKILL.md, every template, every formula — fork it, fine-tune it, share it with the team. Override files (assets/playbook.yaml, references/internal-policies.md) make each skill yours. Internal use, modification and redistribution are free. Not for resale.
xRFP feeds xScore. xContracts feeds xRenew. xSpend feeds xSavings. Every skill writes to the next one's input contract, so the workflow connects — category strategy through bid scoring, contract obligations, renewal radar, all the way to the board readout. The signal is in the seams.
Skills run inside your own Claude Desktop, Claude Code or agent runtime — your data never touches a ProcureAI server. No training on your prompts. Frontier-model routing is yours to configure. Audit trail per invocation. The walkthrough deck is a public artefact — email me and I'll send it.
Want to talk about how to wire the suite into your category? Email [email protected] — I read every one.
Five pillars, two questions each. Step through them for an instant read on where your team is foundational versus ready to wire agents into the workflow. The full 42-question diagnostic — scored against a peer benchmark, with the specific 90-day moves per pillar — ships inside the free skills download.
Spend taxonomy, contract corpus, supplier master
Our spend is classified to a consistent L1–L4 taxonomy — not just raw GL codes.
Our contract corpus is searchable as text — an agent could retrieve a clause today.
Sourcing cycles, templates, repeatable steps
We've mapped which sourcing steps are rules-based versus genuine judgement calls.
We have reusable templates — RFP, scorecard, renewal scan — an agent could draft from.
Model cards, audit trail, residency, sign-off
We have a signed-off data-handling and residency position for AI tools.
Every AI-assisted output can be traced — who ran it, which model, what inputs.
Ownership, capacity, build-vs-buy
Someone owns configuring and maintaining AI skills — with real capacity, not goodwill.
We've made an explicit build-internally versus route-to-vendor call.
Platform deal vs frontier-routed orchestration
We've looked past a single platform pitch and understand frontier-model routing.
We can match the model to the task — reasoning, long-context, or cheap classification.
No email needed · answers are logged anonymously to sharpen the benchmark
Your five-pillar read
—
The full diagnostic scores every pillar against a peer benchmark and returns the specific skills and 90-day moves that close each gap — it ships inside the free skills download.
Get the full diagnostic + 90-day moves16 SKILL.md files · 5 working files · CC-BY-4.0 · no demo call
Feed in your spend under management, headcount, contract count and category mix. Every assumption is a named cell — finance can pressure-test it, override it, or rebuild it from scratch.
Five live savings drivers
Free · no email required · < 50 KB · bonus 38-row L1–L4 spend-taxonomy starter tab
Default scenario · $50M spend · 35 FTEs · 6 categories live
3-year cumulative
savings modelled
of 3-year spend
under management
first-draft RFP
cycle-time reduction
payback period
vs $250k Y1 invest
Numbers from the workbook's default inputs. Plug in your spend, headcount and category mix — the formulas update live.
Business case first — or jump straight to install, routing and fine-tuning.
playbook.yaml, internal policies) are in place. The readiness scorecard above tells you which pillar will slow you down.procureai.tech in any forked SKILL.md is appreciated but not required.~/.claude/skills/, the Claude Agent SDK via its skill loader, the Anthropic API as the system prompt of a tool-using agent, plus n8n / LangChain / CrewAI / OpenAI Assistants by pasting the body into the system prompt. Same files, every runtime.SKILL.md (or drag the whole skills/ folder). Claude reads the frontmatter and auto-activates the right skill based on what you ask — type "draft an RFP for managed cloud" and xRFP fires; "scan contracts for renewals" pulls in xRenew. No slash commands to memorise.skills/ tree into ~/.claude/skills/ (user-wide) or .claude/skills/ in your project (repo-scoped). Restart Claude Code and the skills load automatically — confirm with /skills. Same applies to the Claude Agent SDK's skill loader; point it at the folder, it indexes the frontmatter.description field doubles as the routing hint.assets/playbook.yaml (your negotiation playbook, scoring weights, sourcing rules), references/internal-policies.md (procurement policies, residency requirements, approval matrices), templates/ (your house RFP / contract templates). Edit those, leave the SKILL.md alone, and the skill becomes yours without forking it. Quarterly suite refreshes won't overwrite your overrides.Sixteen SKILL.md files — drop into Claude Code or any agent runtime and ship the work this quarter.
Download the skills