The Procurement OS: Seven Claude AI Skills for the Full Source-to-Contract Lifecycle

The Molecule One Procurement OS is a free Claude AI plugin that gives procurement teams six production-ready skills covering source-to-contract, from spend analysis to negotiation, with a seventh (Contract Management) in internal testing and coming very soon. Until now, we used these skills exclusively with our consulting clients. They are what we build and deploy when we work with CPOs to implement AI across procurement functions. We have now decided to make them public, in the interest of the larger procurement community.

Over the past few months, every engagement we ran across manufacturing, financial services, retail, and professional services started with the same six workflows: categorise spend, build a category strategy, write the RFP, evaluate responses, score suppliers, prepare for the negotiation. We kept rebuilding these skills from scratch for each client. Eventually we packaged them into a single Claude plugin that any procurement team can install and run in minutes, on Claude Code or Claude Cowork. No developer skills required.

This article covers what each skill does, how they chain together into a coherent procurement workflow, and how to install and run them. If you have already read The Claude Cowork Playbook for Procurement Teams, you can think of this as the working operating system that the playbook described in the abstract. If you want to understand how to implement AI in procurement more broadly, start there.

The rest of this document is structured for two reading paths. If you want the why, read sections 1 through 3. If you want the how, jump to sections 4 through 12 and use the sidebar to navigate to whichever skill you need today. If you just want to install it, section 13 has the download link.

Most procurement teams using AI today are using it the way you would use a calculator: pull it out for a discrete task, get the answer, put it away. McKinsey research consistently shows that the procurement functions delivering the most value from AI are the ones treating it as infrastructure, not as a tool. Someone uses ChatGPT to summarise a contract. Someone else uses Claude to draft an RFP cover letter. The category lead has a private prompt library for spend questions that nobody else knows exists. None of it is connected. None of it is repeatable. Each prompt starts from zero.

This is not nothing. It is faster than not using AI at all. But it is structurally limited in three ways:

The result is what we have been calling the procurement-AI fragmentation problem. Teams have access to capable AI, but the work product they get out of it is uneven, inconsistent, and difficult to defend. The technology is doing well. The operating model around it is doing badly.

When we started building AI workflows for procurement clients, we quickly learned that the right unit of procurement AI is not the prompt. It is the skill. A skill is a structured, reusable workflow with its own configuration, its own templates, its own guardrails, and its own outputs. You install it once and use it forever. The next person on your team uses the same one. The methodology is shared, the memory is persistent, and the outputs are consistent.

The Procurement OS is seven of those skills, designed and tested as a set, packaged as a single plugin. We built these skills originally for client engagements. We are releasing them publicly because the procurement community deserves access to the same methodology we use with our consulting clients.

What an OS gives you that a stack of prompts doesn't

This is the same shift you would make if you were going from spreadsheets-as-data-pipelines to a real ETL tool. The work is the same. The infrastructure around the work changes. And once that infrastructure exists, you stop spending energy on the parts of the workflow that don't deserve any.

The seven skills cover the Source-to-Contract lifecycle in the order you would normally run it: from understanding spend, through category planning and sourcing, to supplier management and live negotiation.

Each skill is built to stand alone. You can run the Spend Analyzer on its own without ever touching the others. You can use the Negotiation Playbook Generator the night before a renewal call without ever having run a single line of spend through the Spend Analyzer. They are independently useful.

But the design intent is that you also run them in sequence when the work calls for it. The output of Spend Analyzer becomes the input of Category Strategy Builder. The category strategy informs the RFP. The RFP defines the criteria the Response Evaluator scores against. The selected supplier feeds the Scorecard Engine. The supplier's performance, plus the original commercial terms, feed the Negotiation Playbook for the renewal. End to end.

At a glance

What about Contract Management?

You will have noticed that the seven skills listed above cover Source-to-Contract but stop short of the contract itself. That is deliberate. The Contract Management skill is in internal testing right now, but it needs more work before it is ready for a general audience. Contract review, clause extraction, obligation tracking, and renewal alerting all behave differently across industries and jurisdictions, and we want to get this right rather than ship something half-finished. It is coming very soon.

Beyond that, we are preparing the launch of the full Source-to-Pay Procurement OS within the next month or so. That release will add contract lifecycle management, invoice matching, payment optimisation, and compliance monitoring to the existing skills, covering the complete procurement cycle from spend analysis through to payment.

Spend Analyzer is usually the first skill teams reach for, because spend visibility is usually the first thing a procurement function lacks. Most organisations have spend data sitting somewhere, like an ERP export, a P-card report, or an invoice register, but the data is messy, the category structure is informal, and pulling a clean "where are we spending" picture out of it takes a week of analyst time.

The Spend Analyzer skill takes whatever export you have, parses it, normalises supplier names, applies a category taxonomy (yours if you have one, a sensible default if you don't), flags maverick and tail spend, and surfaces ranked savings opportunities. The output is a categorised spend cube in Excel and an executive summary in Word.

Category strategy is the work that procurement leaders consistently say they don't have time for. It's the deliberate, deliberate planning of how a category will be sourced, segmented, and managed over a horizon of 12-24 months. Most organisations skip it. The ones that do it well usually do it with the help of an external consultant, at significant cost.

The Category Strategy Builder skill brings that work in-house. Give it a category name, a one-line objective, and any spend data you have for the category (an export, a contract list, a supplier roster, whatever is to hand). It returns a Kraljic-segmented view, supply market intelligence, three to five savings levers ranked by effort and impact, and a sourcing roadmap. The more spend data you feed in, the more the recommendations are grounded in what your organisation is actually buying instead of generic category benchmarks. You can iterate the output, push back on the recommendations, and ship a defensible category plan in an afternoon.

Writing an RFP from a blank page is one of the most over-engineered tasks in procurement. Most teams have a template that's three years old, written by someone who's left the company, that nobody fully understands. The RFP that actually goes out the door is a Frankenstein of that template, copy-pasted clauses from the last three RFPs, and whatever the requesting business unit wrote in an email.

The RFP Generator skill replaces that with a structured pipeline: feed it your source material (SOW, contract, brief, meeting notes, or just a description) and it returns an issuable RFP, RFI, or RFQ with all the standard sections, plus a supplier cover letter, plus an evaluation scoring template aligned to what you're asking. You decide the type (RFP / RFI / RFQ); the skill handles the structure.

Once the RFP is back in, the work that follows is the work nobody wants to do. Twenty pages per supplier, multiplied by three to five suppliers, in different document formats, with answers in different orders, scattered across attachments. Comparing them line by line is the kind of work that takes a senior analyst three days and still produces a comparison everyone disagrees with.

The RFP Response Evaluator skill compresses that to a few hours. Drop the supplier responses into a folder, give the skill the original RFP, and it produces section-by-section scoring, a side-by-side comparison highlighting strengths and gaps, a ranked recommendation, and an Excel scoring grid with RAG colours. You can override weightings, ask follow-up questions about specific responses, and generate a recommendation memo that survives stakeholder scrutiny.

Once a supplier is on the books, performance management is supposed to be the disciplined backbone of supplier relationships. In practice, it tends to be ad hoc: a quarterly review meeting where everyone shows up with their own numbers, no shared scorecard, and an action list that gets forgotten by the next quarter.

The Supplier Scorecard Engine skill builds the scorecard, runs it, and reports on it. You give it your SLA and KPI data (or describe it verbally if your data is informal) and it produces a scorecard with RAG ratings, trend analysis if historical data is provided, an improvement plan with owners and milestones, and a benchmark comparison against peers in the same category. The skill is designed to be run quarterly so that performance management stops being something everyone improvises in the meeting.

Negotiation is the highest-leverage hour of work in procurement. It is also the most under-prepared. The pattern most teams fall into: you do the spend analysis, build the strategy, run the RFP, evaluate responses, run the scorecard… and then walk into the renewal meeting with a one-page summary the analyst threw together the night before. The leverage you built up in the prior six months evaporates because nobody had time to convert it into a structured playbook.

The Negotiation Playbook Generator skill exists to close that gap. You feed it the supplier proposal, your target position, the contract terms, and any market intel you have. It returns a structured playbook: a quantified BATNA, a sequenced set of negotiation levers ordered by impact, pre-drafted counter-proposal language for the contentious clauses, and a one-page briefing card you can take into the meeting itself. Used well, the skill changes the meeting itself: instead of reacting to what the supplier puts on the table, you walk in with the levers, the numbers, and the language already prepared, and you run the conversation.

To show how the skills chain together, here is one scenario we have worked through in the field. Your AWS contract is up for renewal in six months. The CFO wants 15% off. You have a year of cloud invoices and a draft renewal proposal from AWS sitting on your desk.

If you have already read The Claude Cowork Playbook for Procurement Teams, the Procurement OS will feel like the natural next step. The playbook makes the case that procurement teams should build skills, automate analyst-time work, and govern AI use carefully. The Procurement OS is seven of those skills, pre-built, ready to install.

If you haven't read the playbook, you can still use the Procurement OS perfectly well, since it stands on its own. But the playbook gives you the wider context: how Cowork works as a platform, how to manage credits, how to roll Cowork out across a team, how to build governance around it, and how to plan a 30/60/90-day adoption arc. The two documents are designed to be read together.

The simplest way to use them together: read the Cowork Playbook to understand the operating model and the platform; install the Procurement OS to put the operating model into practice on day one.

The Procurement OS ships as a single bundle file: m1-procurement-os-v1.0.0.skill. You install it once. After that, the seven skills appear in any conversation in Claude Code or in the Project where you uploaded them.

In Claude Code

1. Open Claude Code (terminal or desktop app).
2. Run /install-plugin or go to Settings, then Plugins, then Install from file.
3. Select the bundle file: m1-procurement-os-v1.0.0.skill.
4. Restart Claude Code (or open a new chat).
5. Type /. The seven skills should appear in the autocomplete.

In Claude Cowork

1. Open Claude Cowork and select the workspace where you want the skills available.
2. Go to Customize, then Plugins, then Browse and Install.
3. Upload the bundle file m1-procurement-os-v1.0.0.skill.
4. All seven skills load into the workspace automatically.

Detailed step-by-step instructions are in the official Anthropic documentation: Claude Code plugin install guide and Claude Cowork skills guide.

First run setup

The first time you use any skill, Claude will ask a few short setup questions: your organisation name, your primary currency, your ERP system, your financial year start month, and your spend taxonomy if you have one. Answers are saved to config.json inside the skill folder and reused on every future run. If anything changes, just tell Claude in conversation: "Update my settings, we've moved to NetSuite." No file editing required.

The full user guide

The bundle ships with a 7-page user guide PDF that covers installation, every skill in detail, an end-to-end example, and a troubleshooting section. The guide and the bundle are both in the download below.

The Procurement OS v1.0 is available now. The download includes the user guide PDF and the installable plugin bundle. Drop your work email below to access both.

What happens next

1. You install it. Five minutes in Claude Code, two minutes in Claude Cowork.
2. You run your first skill. Not sure where to start? Take our AI Readiness Assessment first. Otherwise, we recommend starting with /spend-analyzer if you have spend data on hand, or /negotiation-playbook-generator if you have a renewal coming up. Both produce a usable artifact in under an hour.
3. You tell us what worked. We are continuously improving the skills based on real procurement use. Email hello@moleculeone.ai with what worked, what didn't, and what you wish was there.

Need help with rollout?

If you want help installing, configuring, or rolling the Procurement OS out across a procurement team, our AI procurement consulting team offers implementation support: installation, custom skill development, and governance setup. We also run AI training for procurement teams: hands-on workshops that get your analysts productive with the OS in days, not weeks. Email hello@moleculeone.ai or visit moleculeone.ai/contact.