The Claude Cowork Playbook for Procurement Teams — Molecule One
Practical Playbook · 2026 Edition
The Claude Cowork Playbook for Procurement Teams
A practical guide for procurement leaders who are past the "what is this?" stage and ready to build something that actually works inside their function.
By Molecule One
15 Sections · ~16,000 words
No developer skills required
How to use this document set
📘
You are here
The Claude Cowork Playbook for Procurement Teams
The strategic reference. Covers the full picture: what Cowork is, the complete skill library, connector notes, credit management, governance, team rollout, and the 30/60/90 roadmap. Read it to understand why and what. Return to it when you need depth on a specific topic.
1
New to Cowork? Start with Section 2 (Getting Set Up) and Section 3 (Your First 48 Hours). Then use Section 13 (the 30/60/90 Roadmap) as your spine for deeper strategy and team rollout guidance.
2
Already using Cowork? Use the sidebar navigation to jump directly to the section you need: skills, connectors, scheduling, credit management, or the 90-day roadmap.
3
Rolling out to a team? Start with Section 11 (Governance) and Section 13 (the 30/60/90 Roadmap). Share the Playbook with each team member and point them to the prompt guides in Section 14.
✦
Introduction
Why this playbook exists and what makes Cowork different
If you have been in procurement for more than five years, you have seen a wave of technology promises before. Most of them delivered partial value at significant cost and change management effort. Spend analytics platforms that required 18 months of data cleansing before producing anything useful. Contract management systems that the team adopted for six months and then stopped using. E-procurement tools that added process rigor but did not actually make sourcing faster.
Cowork is not asking you to change your workflow to fit a system. It is asking you to describe your workflow in plain language and then doing the repetitive parts of it for you. That difference sounds small, but in practice it is the difference between a tool that gets abandoned and a tool that becomes part of how your team works.
— The Molecule One team, after 60 days of real procurement use
We spent 60 days running real procurement work through Cowork before writing our field report. We spent another two months building and refining the skills, automations, and integrations described in this playbook. Everything in here is something we have actually done, not something we theorized about.
This playbook is not a complete picture. Cowork is a research preview product and it is changing quickly. Some of the specific steps here will be outdated within a few months as the product develops. What will not be outdated is the approach: start with the highest-value recurring tasks, build skills that encode your team's judgment, automate the monitoring and reporting work that consumes analyst time without requiring analyst judgment, and keep humans in the decision chain for anything that matters.
A procurement team that adopts this approach in 2026 will not just be more efficient. It will be structurally better positioned: more data-informed, more responsive, and more capable of doing the strategic work that justifies procurement's seat at the table.
This playbook is your starting point. What you build with it is yours.
1
Who This Playbook Is For and How to Use It
Audience, prerequisites, and reading paths
This playbook is written for procurement leaders and their teams at enterprise companies who are past the "what is this?" stage with AI and are ready to build something that actually works inside their function.
If you have not yet read our field report, "I've lived inside Claude Cowork for 60 days. Procurement teams should pay attention," start there. It covers what Cowork is, how it compares to other Claude products, the pricing model, and where the product is heading. This playbook picks up where that article ends. We are not going to re-explain what Cowork is. We are going to tell you exactly what to do with it.
👤
Primary audience
A director, senior manager, or VP of procurement who makes or influences decisions about tools and workflows. A category manager or procurement operations lead who is close enough to the day-to-day work to know where the friction is. Someone preparing to roll Cowork out to a team of five or more people.
🚫
What this playbook is not
Not a developer guide. You do not need to write code, manage infrastructure, or understand APIs. Every step is written for someone whose expertise is in procurement, not software.
Choose your reading path
Brand new to Cowork
Start with foundations
Read Sections 2 and 3 first, then Section 4. Use Section 13 as your spine and return to relevant sections as you hit each milestone.
Already using Cowork individually
Level up
Skip to Section 5 (skill library) and Section 6 (automation). Read Section 11 when you are ready to bring your team on.
Evaluating for team deployment
Start with rollout
Read Sections 10, 11, and 12. Those cover credit management, team rollout, and honest limitations.
2
Getting Set Up
Plan, hardware, connectors, workspace folder, and security
Getting Cowork working properly for procurement is a one-time setup effort. Do it right and you will barely think about it again. Rush it and you will spend weeks wondering why things are not quite clicking.
The plan you need
Claude Pro
$20/mo
Experimentation only. You will hit usage limits quickly with agent tasks, browser automation, or large document processing.
Recommended for individuals
Max 5x
$100/mo
Five times Pro capacity per session. The practical minimum for daily procurement use. Skills, scheduling, and browser automation all work reliably here.
Max 20x
$200/mo
Twenty times Pro capacity. For power users running multiple Cowork sessions daily, batch contract processing, or heavy browser automation.
Recommended for teams
Team
$25-125/seat/mo
Standard seats ($25/mo) for lighter users, Premium seats ($125/mo, 6.25x Pro capacity) for power users. Minimum 5 members. Admin controls, SSO, shared plugins, enterprise search.
Enterprise
Custom
Seat fees plus API-rate usage billing. Full admin controls, plugin marketplace curation, domain capture, spend controls. No model training on your data.
💡
Simple upgrade rule
If you are going to use Cowork as a daily working tool rather than an occasional curiosity, Max 5x pays for itself in the first week of real use. For teams, start with Standard seats for everyone and upgrade individual power users to Premium as usage patterns become clear.
Platform support
Cowork runs on Claude Desktop for both macOS and Windows. Download the latest version from claude.com/download. You need an active internet connection throughout every session, and the desktop app must remain open while tasks are running.
Your workspace folder
When you open Cowork for the first time, you will be prompted to select a folder on your computer. This becomes your workspace folder. Everything Cowork saves, generates, or downloads for you ends up here. Think of it as the shared table between you and the agent.
Good options: a folder inside your OneDrive or SharePoint sync path, or a dedicated "Cowork" folder in your documents. Avoid your Desktop or Downloads folder, as files will accumulate quickly.
Set up your global instructions
Global instructions are standing directions that apply to every Cowork session automatically. Open Claude Desktop, go to Customize, and add instructions that set your default context: your role, your company, your preferred output format, any standing rules. For a procurement team, good global instructions include your organization name, your standard document formatting preferences, your category taxonomy if you have one, and a reminder to save outputs as .docx or .xlsx rather than markdown.
Projects: persistent workspaces
Projects let you group related tasks into self-contained workspaces with their own files, instructions, scheduled tasks, and memory. Instead of starting every session from scratch, a project remembers what you have done before and carries that context forward. Create a project for each major workstream: one for your logistics category, one for the office supplies RFP, one for monthly reporting. Each project can have its own folder, its own instructions, and its own scheduled tasks.
Memory within a project means Cowork learns your preferences and context over time. Ask it to remember your category taxonomy, your supplier naming conventions, your preferred report format, and it will carry those forward into future tasks within that project. Memory does not transfer between projects, which keeps your workstreams cleanly separated.
Connectors to set up on day one
Cowork connects to external tools via integrations called MCP connectors. Setting them up takes two to five minutes each, done through the Claude desktop app settings. Here is the priority order for a procurement team:
Microsoft 365
Priority 1 · Official
Outlook + SharePoint + OneDrive + Teams + Calendar in one connector. One-click setup via Microsoft OAuth. Read-only by default: Cowork reads your files and emails, drafts but does not send.
Web Search
Priority 1 · Official
Often already enabled. Allows live research, supplier lookups, market news. Verify it is active before your first session.
DocuSign
Priority 2 · Official (Beta)
Official Anthropic connector. Create and send agreements, search expiring contracts, track signing status, extract clause data. Built specifically for procurement workflows involving digital agreements.
Granola
Priority 2 · 3rd Party
Connect if your team uses Granola for meeting transcripts. Enables post-negotiation summaries, action item extraction, and meeting-to-brief workflows.
SAP Ariba / Concur
Priority 3 · Needs IT
Available via CData MCP Server. Connects Cowork to Ariba sourcing and Concur T&E spend data. Requires IT setup, read-only in standard configuration. Raise with your SAP admin.
ServiceNow / Dynamics 365
Priority 3 · Needs IT
ServiceNow via community MCP server (purchase requisitions, approval queues). Microsoft Dynamics 365 via Microsoft's own MCP server (PO history, vendor master, approval workflows). Both require IT engagement to configure.
Claude in Chrome — Browser Automation
Fallback · No IT Needed
The universal fallback for any web-based procurement system without a dedicated MCP connector: Coupa, Jaggaer, Ivalua, legacy supplier portals, trade finance portals. Cowork navigates the browser interface exactly as a human would. Best for data extraction and read tasks, not for write actions in production systems.
🔒
Security note
Cowork runs in a sandboxed environment. It can only access the folder you have designated. External tool connections use standard OAuth flows. On Teams and Enterprise plans, your conversation data is not used for model training, which matters for teams handling sensitive supplier and contract data.
Your first 30 minutes
Once your workspace folder is set up and Microsoft 365 is connected, run these five tasks to see what Cowork can do before you read another page. Each produces a real deliverable you can use immediately.
⚡
Five deliverables in twenty minutes
Pick a real supplier, a real contract, and a real spend file from your current workload. Placeholder examples teach you nothing. Real examples teach you whether this tool belongs in your workflow.
⚡ Try these now
1
Research a supplier you are meeting next week (3 min, no files needed). Paste: "Act as a procurement analyst. Research [Supplier Name] in the [category] category for a [renewal / new engagement] decision. Deliver a brief with: financial health snapshot, recent news and industry position, risk signals, and three suggested questions for the meeting. Save as a Word document."
2
Extract terms from a contract on your desk (3 min, drop a PDF into your workspace). Paste: "Act as a contracts analyst. Extract key commercial terms from [filename]: payment terms, termination rights, auto-renewal clauses, liability caps, SLA commitments, and price adjustment mechanisms. Flag anything unusual or risky. Present as a table in Word."
3
Turn messy meeting notes into structured minutes (2 min, copy-paste notes). Paste: "Act as a meeting scribe. Convert these notes into formal minutes: [paste notes]. Structure as: attendees and date, key discussion points, decisions made, and an action tracker table with owner and due date. Save as Word."
4
Analyze a spend file you already have (5 min, drop an xlsx or csv into workspace). Paste: "Act as a spend analyst. Analyze [filename] and deliver: transaction categorization by supplier and category, top 10 suppliers by spend, categories with 15%+ YoY increase flagged for review, consolidation opportunities, and data quality issues. Present in a Word report with tables."
5
Build a negotiation strategy for a live deal (5 min, no files needed). Paste: "Act as a negotiation strategist. For [Supplier Name] ($[value] annual spend, expires [timeframe]), build a negotiation brief: opening position, target outcome, walk-away threshold, three concessions ranked by cost/value, and recommended talking points. Show reasoning for each number."
Five real deliverables. Everything from Section 3 onward explains how to make this a daily habit, package workflows as reusable skills, and extend them across your team.
2 of 14 sections
Continue reading, it's free
Enter your work email to unlock the remaining 12 sections: the mental model, skill building, automation, team rollout, governance, the 90-day plan, and the prompt guide library.
✓ Access granted, unlocking the rest of the playbook…
3
The Mental Model
How Cowork fits alongside Chat, Excel, and PowerPoint
The biggest mistake procurement teams make when adopting Claude is treating all of it as one thing. It is not. Each surface in the Claude product family does something different, and using the wrong surface for a task is like using a fork to drink soup. You can do it, but you will be slower and more frustrated than you need to be.
Surface
What it is
Best for
Not for
Claude Chat claude.ai
Conversation interface with optional project context. Good memory within projects, but no local file access or tool connections.
Fast drafts, quick analysis of pasted text, brainstorming, contract clause questions, negotiation strategy sounding board.
Anything requiring your actual files, multi-step workflows, or external system access.
Claude Cowork Desktop app
Autonomous agent. Accesses local files, connects to tools via MCP, runs skills, schedules tasks, organizes work in persistent projects with memory. Can control your desktop directly on Pro/Max plans.
Multi-step deliverables, skills, automation, connecting to Outlook/SharePoint/DocuSign, operating inside web apps, controlling desktop applications, scheduled recurring tasks.
Quick conversational questions that do not need file access. Use Chat instead to save credits.
Claude in Excel Excel add-in
AI analyst inside your open spreadsheet. Shares full conversation context and supports skills. Works on data currently in the file.
Spend analysis, supplier scorecards, contract data tables, price variance analysis, when data is already in Excel.
Multi-source tasks, combining a spreadsheet with document or web research. Use Cowork for that.
Claude in PowerPoint PPT add-in
AI collaborator inside your open presentation. Shares full conversation context and supports skills. Builds slides from source material you provide.
Replacing the strategic judgment about what the audience needs to hear. AI builds structure; you own the narrative.
🧭
The day-to-day flow for procurement teams
Use Chat for quick thinking. Use Cowork for structured deliverables and workflows. Use Excel and PowerPoint integrations when you are already in those applications and want in-context help. On Pro or Max plans, enable Computer Use when you need Cowork to interact with desktop applications that do not have connectors. These tools are complementary, not competing.
4
Building Your First Skill
Step-by-step using the Supplier Research Brief as the starter case
A skill in Cowork is a saved, reusable workflow. Instead of re-explaining a complex task from scratch every time, you package the instructions, context, and tool connections once, give it a name, and invoke it with a single command. For a procurement team, skills are what separate occasional AI use from something that actually changes how you work day to day.
💡
Start with pre-built skills
Before building custom skills, look for existing skill packages that cover your use case. Pre-built skills work out of the box and are a useful reference for building your own.
📋
The starter use case: Supplier Research Brief
Takes a supplier name and optional category. Researches the company using web search and your Microsoft 365 connector, and produces a structured two-page brief covering company overview, financial health, market positioning, risk indicators, recent news, and recommended first-meeting questions. Before this skill: 60-90 minutes of analyst time. After: 3-5 minutes, every time.
The six-step skill-building process
1
Define the task before you touch Cowork
Spend ten minutes with a blank document answering: What is the task in one sentence? What inputs does it require? What does the output look like? Who will use it? What should it always include or avoid? Doing this upfront saves three iterations later.
2
Write a draft prompt in plain language and run it
Open Cowork and run the task manually first. Do not aim for a perfect prompt on the first try. Run it and review the output; a first run tells you more than an hour of planning.
"Research [Supplier Name] for a procurement meeting. They are a supplier in the [Category] space. I need a structured brief covering: company overview, scale and financial health, known major clients and market positioning, any risk indicators, relevant news from the last 90 days, and five questions I should ask in an initial sourcing meeting. Save the brief as a Word document in my workspace folder."
3
Refine based on what you see
Add specificity about output length and format. Add context about your buyer position. Add instructions for handling data gaps ("if financial data is not publicly available, note it explicitly rather than inferring"). Iterate two or three times until you would share the output with a colleague. Then save that prompt.
4
Package it as a skill file
Create a short markdown file with the skill name, trigger description (what Cowork reads to know when to invoke it), and detailed instructions. Save it in a Skills/ subfolder in your workspace.
## Supplier Research Brief
**Trigger:** Use this skill when asked to research a supplier,
vendor, or potential partner for a procurement context.
**Instructions:**
Research the company the user specifies. Produce a structured
brief with: Company Overview, Financial Health (public signals),
Market Positioning, Risk Indicators, Recent News (90 days),
and 5-7 Recommended First-Meeting Questions.
Keep to two pages. If data is unavailable, say so. Do not
speculate. Save as "[Supplier] Research Brief [Date].docx"
in the workspace folder.
**Inputs:** Supplier name. Optional: category, risk concerns.
5
Test it on a second supplier
Run the skill on a different supplier than the one you used in development. This is the real test. Does it produce a clean output without additional guidance? Find edge cases (limited public info, common company names, international suppliers) and update the skill file accordingly. The best skills go through four or five revisions before they are production-ready.
6
Share it with your team
On Teams or Enterprise plans, package the skill as part of a team plugin and push it to colleagues. Anyone who installs the plugin can invoke it with the same output quality. One good skill multiplied across a five-person team is worth five times the investment.
5
The Procurement Skill Library
6 skills available today, more coming soon
Six skills are available today covering the highest-value use cases across the sourcing and category management cycle. Additional skills are in development and will be released soon.
01
✓ In plugin
RFP Generator
Takes a Statement of Work or scope description and produces a complete, structured RFP ready to issue, with evaluation criteria, pricing table, and supplier instructions.
"Generate an RFP for logistics services across our EU distribution network. Priorities: on-time delivery reliability and track-and-trace visibility."
02
✓ In plugin
RFP Analyser
Scores supplier RFP responses section by section against your stated evaluation criteria. Produces a weighted comparison matrix and a ranked recommendation with supporting evidence.
"Score the three responses to our IT managed services RFP. Weightings: technical capability 35%, pricing 30%, implementation plan 20%, references 15%."
03
✓ In plugin
Negotiation Playbook
Builds a structured pre-negotiation brief: opening position, target outcome, walk-away point, BATNA, concession ladder, anticipated supplier tactics, and non-negotiable red lines.
"Build a negotiation playbook for our logistics contract renewal. Goal: 6-8% reduction. We have two competitive bids in hand and a 60-day notice window."
04
✓ In plugin
Category Strategy
Produces a complete category strategy document: spend profile, Kraljic matrix positioning, supply market analysis, risk assessment, savings opportunities, and a phased action plan.
"Build a category strategy for our indirect IT spend: $4.2M across 18 suppliers. We're fragmented and need a consolidation plan for the next 12 months."
05
✓ In plugin
Spend Analysis
Takes a spend export and produces a structured analysis: category breakdown, top suppliers, concentration risk, year-over-year variance, and prioritized consolidation opportunities.
"Analyse our Q1 indirect spend from this export. Identify our top 10 suppliers, any category over 40% concentration, and the three best consolidation opportunities."
06
✓ In plugin
Supplier Scorecard
Takes KPI data and produces a formatted scorecard with RAG ratings per dimension, weighted overall score, trend vs. prior period, and a QBR-ready summary paragraph.
"Build a scorecard for TechSource Inc. OTD: 91%, defect rate: 0.3%, invoice accuracy: 98%, satisfaction survey: 3.6/5. Weight delivery and quality highest."
07
Coming soon
Supplier Research Brief
Researches any supplier and produces a structured brief: financial health, market positioning, risk indicators, recent news, and recommended meeting questions.
"Run a supplier research brief on Grainger for our indirect MRO category renewal."
08
Coming soon
Contract Clause Extractor
Reads an uploaded contract and extracts key commercial terms into a structured table: payment, termination, auto-renewal, liability caps, SLA, and escalation clauses.
"Extract payment terms, termination clauses, auto-renewal provisions, and liability caps from this supplier agreement."
09
Coming soon
Negotiation Debrief
Takes call notes or a transcript and produces: agreed items, open items, supplier positions, prioritized action list with owners, and a ready-to-send follow-up email.
"I just finished a negotiation call with Acme Logistics. Here are my notes: extract what we agreed, what's open, and draft the follow-up email."
10
Coming soon
Contract Renewal Tracker
Reads your contract register and produces a weekly alert listing expiries in the next 30, 60, and 90 days with recommended action for each. Designed to run on a schedule.
"Check the contract register and flag everything expiring in the next 90 days. Highlight anything over $200K as needing a sourcing decision."
11
Coming soon
Vendor Risk Assessment
First-pass risk filter covering financial stability, geographic exposure, ESG signals, and business continuity. Flags items for your risk committee with confidence levels.
"Run a vendor risk assessment on our sole-source packaging supplier, Flexipack GmbH in Germany. Flag anything for our risk committee."
12
Coming soon
Savings Opportunity Identifier
Reviews spend or contract data and flags savings levers: consolidation opportunities, payment term gaps, volume rebate misses, expiry windows, and underutilized commitments.
"Review this travel spend file and identify the top three savings opportunities to prioritize for next quarter."
13
Coming soon
Meeting Prep Brief
Pulls context from your calendar invite, recent emails, existing supplier research, and open action items into a one-page prep doc readable in under five minutes.
"Prep me for my QBR with Siemens tomorrow at 10am. Pull from our recent email thread and flag any open action items from last quarter."
14
Coming soon
Procurement Status Report
Takes team updates, project trackers, and savings data and produces a formatted weekly status report written for the CPO or CFO audience.
"Generate this week's procurement status report for the CPO. Here are the team updates and savings tracker. Flag the logistics renewal as the priority risk item."
15
Coming soon
Policy Compliance Checker
Checks a purchase request or contract against your procurement policy and flags exceptions, required approvals, and competitive bid thresholds. Upload your policy once as reference.
"Check this $180,000 software renewal against our procurement policy. What approvals does it need and does it require a competitive bid?"
6
Scheduling and Automation
What to automate vs. what to keep human-in-the-loop
The scheduling feature in Cowork is one of the most underused capabilities in the product. For procurement teams with recurring reporting requirements, contract monitoring, and market intelligence duties, scheduling is where Cowork starts to feel less like a tool and more like a team member.
You describe a task and tell Cowork when to run it: hourly, daily, weekly, on weekdays, or on demand. When the time arrives, Cowork runs the task automatically, saves the output, and waits for your review. Create scheduled tasks using the /schedule command in any Cowork session, or from the Scheduled Tasks page in the sidebar. Scheduled tasks can live inside Projects, which means your contract renewal tracker can sit alongside the category's other files, instructions, and memory.
One important limitation: scheduled tasks only run while your computer is awake and the Claude Desktop app is open. If your laptop is closed when a task was scheduled to fire, Cowork will run it automatically when the app reopens and notify you. For mission-critical Monday morning alerts, leave your machine running or open the app first thing.
✅ Safe to automate
📅
Contract renewal alerts. Run every Monday. A report showing what expires in the next 30, 60, and 90 days. Never miss a renewal decision again.
📰
Supplier news digests. Weekly digest for your top 20 critical suppliers, filtered for procurement-relevant signals: financial news, leadership changes, operational disruptions.
📊
Spend variance reports. If your P2P can export to a shared folder, schedule a weekly summary comparing it to prior period and budget. First-pass signal before your Monday meeting.
📋
Meeting prep briefs. Run every Sunday evening. Prep briefs for all supplier meetings on your calendar for the coming week, pulled from email, existing research, and open action items.
💰
Savings pipeline status. Weekly summary of active savings projects from your tracker spreadsheet, formatted as a one-page update for the CPO.
⚠️ Keep human in the loop
🤝
Supplier selection decisions. Cowork can research, compare, and summarize. It should not make the award call. The commercial and relationship consequences belong to a human.
✍️
Contract approval. Cowork can draft and flag exceptions. It is not the final check before execution. Legal review and commercial sign-off are human steps for good reasons.
🧠
Negotiation strategy. Research and market intel can be automated. What to concede, what to hold, how to read the counterparty: that is judgment work that cannot be delegated.
💬
Relationship-sensitive communications. Cowork is excellent at drafting. For communications where the relationship is fragile or the stakes are high, review carefully before sending.
🏗️
Anything touching live production systems. Read access is generally safe to automate. Write access, record creation, and approval actions must require explicit human confirmation.
⚖️
The rule of thumb
Anything you would want to be able to explain to your CFO or CPO if it went wrong should have a human review step. Automation that saves three minutes but costs three months is not a good trade.
Your first scheduled task: Contract Renewal Tracker
The best place to start with scheduling is a contract renewal alert. It is low-risk, immediately valuable, and teaches you the full skill-to-schedule workflow in under ten minutes. Here is the skill file you can copy directly into your Skills/ folder:
## Contract Renewal Tracker
**Trigger:** Use when asked to check contracts expiring soon
or to run the contract renewal tracker.
**Instructions:**
Read the contract register at Reference Data/Contract Register.xlsx.
Identify all contracts expiring within 30, 60, and 90 days from today.
For each expiring contract, note: supplier name, contract value,
expiry date, current owner, and a recommended action:
- Over $200K: "Initiate competitive tender or renegotiation review"
- $50K to $200K: "Review and confirm renewal strategy with owner"
- Under $50K: "Standard renewal, confirm with owner"
Save the output as a Word document titled
"Contract Renewal Alert [Date].docx" in Outputs/Reports/.
Also provide a brief summary in the chat window.
**Inputs required:** None. Reads from the register automatically.
Test it once manually by typing "Run the Contract Renewal Tracker." Check the output against your register. Then schedule it to run every Monday at 7:00 AM. From that point forward, a report appears in your Outputs/Reports/ folder every week showing exactly what is expiring and what action to take. You will never again find out about an auto-renewal because nobody was watching the calendar.
💡
Review your scheduled tasks monthly
Scheduled tasks consume credits automatically. Once a month, check your task list and retire anything that is no longer useful. A weekly report that nobody reads is still burning credits and cluttering your workspace folder.
7
Connecting Your Tools
Practical integration notes: Microsoft 365, DocuSign, SAP connectors, browser automation
Microsoft 365
The Microsoft 365 connector is a single OAuth flow that covers Outlook, SharePoint, OneDrive, Teams, and Calendar. It is the most important connector for enterprise procurement teams. Once connected, Cowork can search your inbox for supplier threads, read files from SharePoint document libraries, and reference OneDrive-stored contracts and templates directly in any workflow.
📁
Folder organization tip
Create a dedicated folder structure: Procurement / Cowork Outputs / [Year] / [Category or Supplier] in OneDrive. When asking Cowork to save files, point it to the right folder explicitly, otherwise outputs accumulate at the root level. Use .docx and .xlsx formats; native SharePoint document types can be inconsistent.
🔧
Setup: connecting Microsoft 365
Open the Claude desktop app and go to Settings, then Connectors. Find Microsoft 365 and click Connect. You will be redirected to a standard Microsoft OAuth screen where you grant read and write permissions. Once authorized, Cowork can access your Outlook, OneDrive, SharePoint, Teams, and Calendar immediately. If your organization uses Conditional Access policies or domain restrictions, you may need your IT admin to approve the OAuth grant before it completes. Test the connection by typing: "Find the three most recent emails I received from any supplier or vendor. Summarize each in one sentence." If results come back, you are connected.
Outlook
The Outlook integration (included in Microsoft 365) lets Cowork search, read, and draft emails. Most valuable for: summarizing supplier email threads before a meeting, drafting outreach emails placed in your Drafts folder for review, and monitoring for specific supplier communications in scheduled workflows.
✉️
Cowork creates drafts, it does not send autonomously
When you ask Cowork to draft an email, it lands in your Outlook Drafts. You review, edit, and send. Keep this as your default behavior. The three-second review step is a meaningful control.
Outlook Calendar
Calendar access enables the automated meeting prep workflows in Section 6. Cowork can also create calendar events when you ask it to. For example, after a negotiation debrief: "Schedule a follow-up with the supplier in 30 days and add the agreed action items to the invite body."
Limitation: Cowork manages your own calendar, not other attendees'. It cannot update or delete existing entries from others' calendars.
DocuSign
DocuSign has an official Anthropic connector (currently in beta) built specifically for procurement workflows. This is a material upgrade from browser-based workarounds. The connector supports: creating and sending agreements from Cowork, searching for contracts expiring within a given timeframe, tracking signing status across open agreements, and extracting clause text for review. For any procurement team managing a significant volume of supplier agreements, this connector materially reduces the manual overhead of contract administration.
📝
Example workflow: Contract expiry monitoring
Ask Cowork: "Search DocuSign for any supplier agreements expiring in the next 90 days and give me a list sorted by contract value." This runs against your live DocuSign account and returns structured output you can act on immediately, with no manual log-in, no exporting, and no spreadsheet maintenance.
SAP Ariba and SAP Concur
Both SAP systems are available via CData MCP Server, a third-party connector layer that requires IT setup but does not need a custom integration. Ariba provides sourcing, supplier master, and contract data. Concur provides T&E spend data. In standard configuration, both are read-only, which is appropriate for procurement intelligence workflows. Raise these with your SAP admin; setup is typically two to four hours of IT effort, not a project.
ServiceNow and Microsoft Dynamics 365
If your organisation routes purchase requisitions or procurement approvals through ServiceNow, a community MCP server is available that connects Cowork to requisition queues and approval workflows. If Dynamics 365 is your ERP or P2P system of record, Microsoft publishes its own MCP server that exposes PO history, vendor master data, and approval state. Both require IT to configure and approve, but once connected they give Cowork direct access to your operational procurement data without any browser automation.
Computer Use: direct desktop control
Computer Use is a research preview capability that lets Cowork interact directly with your desktop: opening files, clicking through applications, typing into forms, and navigating any software on your machine. It works as a three-tier approach. Cowork tries connectors first (fastest and most reliable), then browser navigation, then direct screen interaction. For procurement teams, this means Cowork can pull data from applications that have no connector and no web interface, such as locally installed ERP clients or legacy desktop tools.
⚠️
Computer Use availability and limitations
Currently available on Pro and Max plans only. Not yet available on Team or Enterprise plans. Computer Use operates outside Cowork's normal sandbox, running on your actual desktop, so close sensitive applications before enabling it. Do not grant access to banking, healthcare, or financial trading applications. Start with simple, low-risk tasks and build from there.
Browser automation via Claude in Chrome
Claude in Chrome opens a Chrome browser window and navigates web applications for you, reading information and taking actions through the interface exactly as a human would. For procurement teams, this remains the right approach for Coupa, Jaggaer, Ivalua, and any web-based system that does not yet have a dedicated MCP connector. Claude in Chrome gives Cowork a way into those systems without any IT integration work. On Team and Enterprise plans where Computer Use is not yet available, browser automation is the primary fallback for unsupported systems.
✅ Good browser automation use cases
🔍 Extracting supplier lists, PO status, open requisitions from your P2P system
📄 Checking invoice status in supplier portals
📈 Pulling benchmark data from industry portals requiring login
🌐 Any procurement platform without a dedicated MCP connector: Coupa, Jaggaer, Ivalua
⚠️ Proceed carefully
🔐 Systems requiring MFA on every action, as browser automation becomes fragmented
✏️ Form submissions, approvals, PO creation, which require explicit confirmation at each step
🏭 Production procurement systems, where you should use extraction only, not workflow execution
Claude in Excel is the right tool whenever your primary material is a spreadsheet and you want to do something analytical with it. It meets you where the data already is, which for most procurement teams is exactly where you need it.
Use Case
What to say
Time saved
Spend analysis from raw ERP export
"Clean this data. Consolidate duplicate supplier names. Summarize spend by L1 category and top 20 suppliers. Identify the three categories with highest supplier count relative to spend. Show results in a new sheet."
~3 hrs → 40 sec
Supplier scorecard population
"Add a new row for Q1, calculate period-over-period trends, and flag in red any metric that declined more than 10% versus last quarter. Write a two-sentence performance summary for each supplier."
~1 hr → 5 min
Contract register maintenance
"Merge this clause extraction output into our contract register. Calculate days to expiry for every contract. Add a traffic-light column: red if under 60 days, amber if under 90, green otherwise. Sort by urgency."
~45 min → 5 min
Price variance analysis
"Identify which line items have increased above 8% over the past 12 months, which suppliers have the highest quote variance, and whether there is any seasonal pattern to the price movements."
~2 hrs → 10 min
🏷️
One trick that makes spend analysis significantly better
Before running analysis, paste your category taxonomy into a separate tab and say: "Use the taxonomy on the Categories tab as the classification reference. Recode any items in 'Unclassified' or 'Other' using the most logical match from this list." This single step dramatically improves output quality.
🤔
Claude in Excel vs. Cowork for data tasks
One question decides it: is the data already in a spreadsheet and am I already in Excel? If yes, use Claude in Excel. If the task requires pulling from multiple sources, combining a spreadsheet with a document or web research, or saving a finished analysis to a specific location, use Cowork.
9
Claude in PowerPoint
QBR decks, category strategy, savings summaries for finance
Procurement leaders spend a disproportionate amount of time building slide decks for audiences who have three minutes to absorb them. Claude in PowerPoint does not eliminate the work of building a deck, but it compresses it significantly and removes the blank-slide paralysis that slows most people down.
🎯
The key insight about AI-assisted decks
Treat the first draft as structure, not polish. The AI gets the logic and flow right. Your job is editing for accuracy, adding specific numbers and evidence, and applying your judgment about what this particular audience needs to hear.
Quarterly business review decks
Run the Supplier Scorecard Builder skill in Cowork first. Then open PowerPoint with your QBR template and say: "Build a QBR deck for our Q1 review with TechSource Inc. Use our standard template. The performance data is in the notes I've pasted. The open issue to highlight is invoice accuracy below our 98% threshold. For strategic priorities: we're increasing spend with them in H2 and expect them to expand their dedicated team."
The draft will be 70-80% of the way there. Total time: 20-30 minutes instead of two hours.
Category strategy presentations
Generate your source material first using the Spend Category Summary and Price Benchmark Research skills. Then bring that material into PowerPoint with audience context explicitly in the prompt. A deck for a CPO who knows the category is very different from a deck for a CFO who needs the category explained from first principles. Tell Claude in PowerPoint who is in the room.
Savings summary slides for finance
Finance audiences want three things: what did we commit to, what did we deliver, and why did anything fall short. Keep a running savings tracker in Excel. At the end of each period: "Build a two-slide savings summary for the CFO. Slide one: committed vs. delivered with gap explanation. Slide two: pipeline for next quarter with top three initiatives. I'll paste the tracker data." Two slides, twenty minutes.
🎨
Use your template automatically
Store your organization's PowerPoint template in your workspace folder and reference it by name in your prompts. One line, "use the Q1 2026 template", makes every deck use your fonts, colors, and layouts without additional formatting work.
10
Managing Credits Wisely
How to avoid burning your usage pool on the wrong tasks
Credits in Cowork are not all created equal. A simple drafting task uses a fraction of the credits that a browser automation session or large document processing task consumes.
Task
Credit intensity
Relative cost
Drafting an email from information you provide
Very low
Extracting clauses from a short contract (<20 pages)
Use Chat for things Chat can do. If you are drafting an email and do not need Cowork to pull from your files or connected tools, write it in Chat. Simpler tasks like quick drafts and questions consume fewer credits than full Cowork agentic tasks.
Batch similar tasks. Run the Contract Clause Extractor on 15 contracts as a single batch task, not 15 individual sessions. Starting a new task session repeatedly is less efficient.
Set scope limits in prompts. "Search no more than five sources then compile your findings" produces a faster, cheaper result than an open-ended research instruction that triggers ten rounds of search.
Keep files tidy. Trim spend exports to the columns and rows you actually need. Remove appendices and schedules from contracts if they are not relevant to the extraction.
Review scheduled tasks monthly. Scheduled tasks run automatically and consume credits automatically. Retire any that are no longer useful. A weekly report that nobody reads is still burning credits.
🎯
Team heuristic that captures 90% of right-sizing
If the task requires connecting to a tool, working with a file, or running a skill: use Cowork. If it is a question or draft you can answer from what is in your head: use Chat.
11
Rolling This Out to a Team
Plugins, governance, shared workspace, and change management
Moving from individual Cowork use to team-wide adoption is a different kind of challenge from setting it up for yourself. The technical work is simpler than most people expect. The human work is where most rollouts either succeed or stall.
Plugin marketplace and admin controls
On Team and Enterprise plans, organization owners curate which plugins are available to members. Three installation modes exist: auto-install (pushed to everyone automatically), available (self-service), and not available (hidden entirely). This gives procurement leadership control over which skills and connectors the team can access.
🔴
Critical enterprise limitation: no audit logging
Cowork stores conversation history locally on each user's computer. This data is not captured in your organization's Audit Logs, Compliance API, or Data Exports; this applies across all plan tiers, including Team and Enterprise. For regulated procurement workloads that require full audit trails, document your Cowork outputs through your existing P2P system of record. On Team and Enterprise plans, Anthropic provides generally available OpenTelemetry (OTel) support for streaming usage, cost, and tool activity data to your own observability infrastructure. This covers prompts, tool invocations, file access, and human approval events, but is not a substitute for compliance audit logging.
The most common mistake in AI tool training is spending the session teaching people how to write prompts. Most people will not walk away from a two-hour session able to write a good prompt from scratch. Instead, train people on the skills that already exist. Show them: here is how you invoke the Supplier Research Brief, here is what the output looks like, here is how you refine it if the first output is not quite right.
When people succeed at a skill they already have access to, two things happen: they become more confident using Cowork, and they start identifying new tasks that could benefit from the same treatment. Skills are the entry point. Prompt fluency comes with real use.
The three real barriers to adoption
Fear of headcount reduction
Address this directly and honestly. Teams that get the most from Cowork reinvest time savings in higher-value work: more strategic sourcing, deeper supplier relationships, better data-backed negotiations. That is the actual opportunity.
Data security concerns
Take this seriously. On Teams and Enterprise plans, conversation data is not used for model training. Get the specifics from your IT and legal teams before deployment, not after.
Skepticism about output accuracy
Do not argue with it. Show people the outputs. Build in a review habit: every AI-generated output going to a stakeholder or supplier gets a human eye before it leaves. The goal is to replace routine production, not judgment.
💡 The pilot approach
Start with four to eight people: one senior champion, two to three category managers with complex recurring work, one to two analysts who will stress-test it. Run four to six weeks. Document every finding. This becomes your internal rollout playbook.
Honest guardrails given current product limitations
Every honest evaluation of a technology tool includes the things it should not do yet. These are not failures of the product. They are the current edges of what works reliably, and understanding them protects you from building workflows that will disappoint you.
⚖️ Legal-binding decisions and contract execution
Contract summaries should be reviewed by a lawyer before reliance. RFPs drafted by Cowork need legal and commercial review. The agent has no liability, no professional obligations, and no context about your jurisdiction's specific requirements.
🔐 Systems requiring MFA at every step
Browser automation works well when you authenticate once and the session stays live. If your P2P systems require MFA confirmation on every action, automation becomes fragmented. Test this early before building workflows around it.
⚡ Real-time data that changes by the minute
Cowork works on data as a snapshot. It is not designed for real-time monitoring. If you need to track a live bid auction or price feed, use purpose-built tools for those tasks.
🗂️ Tasks requiring full audit trail in a system of record
Approvals and sourcing events need to be documented in your P2P system for compliance. Cowork does not write back to your P2P. The documentation step still happens through the proper channel.
🏭 ERP write-back and transactions
Creating POs, approving invoices, updating vendor master data: these are not operations to route through Cowork today. ERP systems have validation requirements and audit logging not compatible with agent-driven data entry.
🏢 Organization-specific knowledge you have not provided
Cowork knows general procurement well. It does not know your specific categories, supplier relationships, or internal terminology unless you build it into your skills and project instructions. Until you do, outputs for highly organization-specific tasks need more review.
🖥️ Computer Use on Team and Enterprise plans
Direct desktop control (Computer Use) is currently available on Pro and Max plans only. If your team is on a Team or Enterprise plan, browser automation via Claude in Chrome is the right approach for applications without MCP connectors. Plan your workflows accordingly and monitor Anthropic's release notes for when Computer Use extends to organizational plans.
🔒
Confidential information note
Any data you bring into a Cowork session becomes part of that session's context. On Teams and Enterprise plans, Anthropic's privacy protections are clear, but apply your own judgment about what is appropriate to share with any third-party tool. Financial data not yet public, M&A-related sourcing activity, and personal data about individuals should be treated with the same care you would apply to any cloud tool.
Data governance for procurement teams
Procurement data is commercially sensitive. Contract values, supplier pricing, negotiation strategies, and internal cost models are all things your competitors, your suppliers, and the market should not see. Before you roll Cowork out to a team, everyone needs to understand what is safe to share with Claude, what requires caution, and what should never go in.
The good news is that on Anthropic's Team and Enterprise plans, your conversations and files are not used to train Claude's models. Your data stays within your organization's instance. But "not used for training" is not the same as "no risk at all." You still need clear guidelines so your team operates with confidence.
✅ Safe to use freely
📊
Publicly available supplier information, market research, general category descriptions, published pricing, internal process documentation, policy templates, and general procurement best practices.
✅ Safe with standard care
📋
Your own spend data (anonymized or aggregated), contract clause templates without specific pricing, RFP templates and evaluation frameworks, supplier scorecard structures, and internal process workflows.
⚠️ Use with caution
🔒
Live contract terms and pricing with specific suppliers, negotiation strategies for active deals, supplier-specific performance data, detailed should-cost models, and competitive bid comparisons during an active RFP. Fine to use in Cowork (not used for training), but limit who on your team accesses these conversations.
🚫 Do not put in Cowork
⛔
Personal data of supplier employees (national IDs, bank details), trade secrets or proprietary formulas shared under NDA, legal hold or litigation documents, classified government procurement data, and anything marked as restricted under your information security policy.
💡
The practical test
Before pasting any document into Cowork, ask yourself: "Would I be comfortable sending this as an email attachment to an external consultant under NDA?" If yes, it is almost certainly fine for Cowork. If no, think carefully about whether it belongs there.
Governance principles
Human reviews everything. Claude drafts, you decide. No contract clause, supplier communication, or commercial commitment should go out without a human reviewing the output. This is non-negotiable, regardless of how good the output looks.
Confidentiality by default. Treat every Cowork session as confidential. Do not share session links or output files outside your procurement team without checking who needs access. Use your company's standard file sharing policies for output documents.
Audit trail matters. Save important outputs to a shared drive or document management system. Cowork sessions are not permanent records. On Team and Enterprise plans, Cowork stores conversation history locally on each user's machine, and this data is not captured in your organization's Audit Logs, Compliance API, or Data Exports. For regulated workloads, document Cowork outputs through your P2P system of record.
Supplier fairness. Using AI to research suppliers is fine. Using AI to generate misleading communications, fabricate performance data, or create fake competitive pressure is not. The tool should make you more efficient, not less ethical.
Train before you scale. Before giving team-wide access, run a 30-minute session showing what Cowork can and cannot do. Cover the data classification above. People who understand the boundaries use the tool with confidence rather than anxiety.
Common questions from procurement leaders
"Can our suppliers see what we put into Claude?" No. Your conversations and files are private to your organization. On Team and Enterprise plans, your data is not shared with other users, not used to train models, and not accessible to Anthropic employees except in narrow safety review scenarios.
"What if Claude gives us wrong information about a supplier?" Treat Claude's web research the way you would treat a junior analyst's first draft: useful structure, good starting point, but always verify critical facts (financial data, legal proceedings, ownership changes) against primary sources before acting on them.
"Can we use Claude for contracts under NDA?" You can use Cowork to analyze contracts received under NDA, provided your NDA does not specifically prohibit processing through cloud-based tools. Most standard commercial NDAs do not restrict this, but for highly sensitive agreements (M&A, government, defence), check with your legal team first.
"Should we tell suppliers we are using AI?" There is no legal obligation to disclose your internal tools. However, if a supplier asks whether AI was used to generate a document, be honest. The reputational risk of being caught in a lie far outweighs any perceived advantage of secrecy.
"How do we handle this with InfoSec and Legal?" Start the conversation early. Share Anthropic's security documentation (available at anthropic.com/security) with your InfoSec team. The key points they will care about: SOC 2 Type II compliance, data encryption in transit and at rest, no model training on customer data (Team and Enterprise), and configurable data retention policies.
13
A 30/60/90 Day Adoption Roadmap
A week-by-week plan for a procurement team starting today
This roadmap is for a procurement leader starting from scratch or near-scratch: you have access to Cowork, you have a team of five or more people, and you want to move from individual curiosity to functional capability within a quarter.
The roadmap is deliberately conservative. The goal in 90 days is a small number of skills your team uses every day, a few well-designed automations, and a clear governance model. That is a meaningful, defensible outcome. The more advanced capabilities follow naturally from that foundation.
30
Days 1-30
Setup · First skills · Individual use
Week 1
Foundation
Install app, set workspace folder, connect Microsoft 365 and web search. Run a Supplier Research Brief on a real supplier. Take the output to a real meeting.
Week 2
Build first custom skill
Pick your most repetitive high-value task. Follow the Section 4 process. Aim for 80% useful first drafts, not perfection.
Week 3
Connect your data
Get a spend export into your workspace folder. Run the Spend Category Summary skill. Use the top three findings as the basis for a real team discussion.
Week 4
First automation
Set up the Contract Renewal Tracker as a scheduled Monday morning task. End the week with a working automation already running.
Day 30 target
Using Cowork 3-4x/week · 2-3 reliable skills · 1 running automation
60
Days 31-60
Team pilots · Tool connections · Automation
Weeks 5-6
The pilot group
Identify 4-6 colleagues. Run two 2-hour onboarding sessions a week apart. Document every skill request that comes out; you are building a backlog.
Weeks 7-8
Expand the skill library
Build 3-5 skills from the pilot backlog. Prioritize tasks that at least 2-3 people do regularly. One skill used by five people daily is worth more than five skills used by one person each week.
Throughout
Connect additional tools
Connect DocuSign if your team manages agreements digitally; it pays for itself in contract visibility alone. Connect Granola if the team runs meeting debriefs there. Raise SAP Ariba or ServiceNow with IT if pilot users flagged those systems. Only add what the pilot group identified as important.
Day 60 target
Active pilot group · 8-12 skills · 2-3 automations running
90
Days 61-90
Full rollout · Governance · Measurement
Weeks 9-10
Full rollout
Roll your skill library out to the full team via the admin console. Have pilot participants share their own experience; real examples are more credible than prepared demos.
Weeks 11-12
Governance and measurement
Assign skill ownership. Set quarterly review date. Measure two things: adoption (who used it and for what) and value (three best examples of Cowork saving significant time or improving output quality).
Day 90 output
Your Q2 roadmap
The clear list of skills you wish you had, integrations not yet working, and deferred use cases. This list is your next quarter's plan.
Day 90 target
Full team on Cowork · Governance in place · Data for the CPO conversation
🎯
What "done" looks like at day 90
A functioning skill library. A governance model. A handful of running automations. Enough real data to have an informed conversation about what to build next. You will also have a clear list of the gaps: the skills you wish you had, the integrations that are not yet working, the use cases you deferred. That list is your Q2 roadmap.
If you want help building custom skills or accelerating your roadmap, get in touch →
What a typical week looks like
Here is what using all of these capabilities together looks like in practice: a realistic procurement week from first alert to finished deliverable, showing every Claude surface working together on a single deal.
📋
Scenario: Preparing for a major contract renegotiation
Your $1.2M logistics contract with Acme is expiring in 58 days. Here is how the week unfolds.
Your scheduled task fires. It reads the contract register and drops an alert into Outputs/Reports/: Acme Logistics, $1.2M, expiring in 58 days, recommended action "Initiate competitive tender or renegotiation review." You see it when you sit down.
💬
Monday morning: Think through the approach in Claude Chat
Before doing any research, you open Claude Chat (not Cowork, this is a thinking task, not a doing task) and talk through the negotiation. "We have a $1.2M logistics contract expiring in 58 days. We are generally happy but want a 5 to 8% cost reduction. What are our strongest negotiating points?" Chat helps you think through strategy, risk, and BATNA. No files needed, no agentic tools running.
🤖
Monday afternoon: Run the Supplier Research Brief on Acme Logistics
In Cowork, the Supplier Research Brief skill fires: web search runs, recent news is pulled, your Outlook emails and SharePoint files are cross-referenced for internal context. Output: a structured brief with financial health signals, risk flags, and five opening questions, saved in your workspace.
🤖
Monday afternoon: Extract commercial terms from the existing contract
Drop the current Acme contract into the workspace folder and run the Contract Clause Extractor. Output: a clean summary table of payment terms, termination rights, auto-renewal clauses, liability caps, and SLA commitments. You now know exactly what you are renegotiating from.
📊
Tuesday: Price variance analysis in Claude in Excel
Export two years of Acme invoice data. Open it in Excel. Use the Claude pane: "Identify line items that have increased in price over 24 months. Calculate the cumulative increase and flag anything above 5%." This gives you data-backed talking points: specific numbers you can reference in the negotiation room.
📑
Wednesday: Build the CPO brief in Claude in PowerPoint
Open PowerPoint with your company template. Use the Claude pane to build an internal negotiation brief for the CPO: $1.2M contract, recommending direct renegotiation over competitive tender, target 6% reduction, three negotiating points. Paste the research brief and price analysis as source material. Output: a branded deck ready for review. Twenty minutes instead of three hours.
✅
Post-meeting: Negotiation Debrief skill in Cowork
After the call with Acme, paste your notes into Cowork and run the Negotiation Debrief skill. Output: a structured summary of what was agreed, what is open, Acme's stated positions, a prioritized action list with owners and deadlines, and a draft follow-up email in your Outlook Drafts ready to review and send.
📊
The outcome
Approximately 45 minutes of active AI-assisted work across the week. Six Claude surfaces and capabilities used: scheduled automation, Chat, Cowork skills, Excel, PowerPoint, and connectors. Five substantial deliverables produced. Roughly eight hours of equivalent manual analyst effort replaced and reinvested in strategy and the negotiation itself.
14
Role Prompt Guides
Full prompt guides by role: 15 prompts each, with copy-paste text and usage context
Each prompt guide contains 15 copy-paste prompts written for a specific procurement role. Download the guide that matches your work and use it as your day-to-day reference alongside this playbook. Every prompt can be used immediately, with no configuration required beyond having the relevant files in your workspace folder.
📊
Procurement Analyst
Data, spend analysis & reporting
15 copy-paste prompts covering spend categorisation, tail spend, price variance, contract extraction, compliance monitoring, and data quality.
15 copy-paste prompts covering the full sourcing cycle: RFI drafting, RFP construction, supplier evaluation, should-cost modelling, negotiation strategy, debrief, and transition planning.
RFP First Draft
RFP Evaluation Scorecard
Negotiation Strategy Builder
Should-Cost Model
Negotiation Debrief
+ 10 more prompts
🎯
Procurement Director / CPO
Governance, reporting & strategic oversight
Executive briefing covering what Cowork is, deployment plan, pricing tiers, security & compliance overview, and 4 prompts for CPO-level reporting, risk escalation, and governance.
15 copy-paste prompts for day-to-day buying: PO emails, quote comparisons, price benchmarking, delivery escalations, invoice queries, approval packs, and spend summaries.
Three-Quote Comparison
Price Benchmark Check
Delivery Delay Escalation
Invoice Query to Supplier
Approval Pack for Manager
+ 10 more prompts
🤲
Supplier Relationship Manager
Strategic relationships, performance & development
15 copy-paste prompts for managing strategic suppliers: QBR packs, performance scorecards, corrective action plans, escalation briefs, annual reviews, and joint business plans.
QBR Preparation Pack
Supplier Performance Scorecard
Corrective Action Plan Request
Issue Escalation Brief
Annual Supplier Review
+ 10 more prompts
💡
One guide, one role
Each guide is a complete prompt reference for a specific procurement role: 15 prompts, each with full copy-paste text and context for when to use it. Keep it open in a browser tab or save the PDF alongside this playbook. The prompts work in any order; start with whichever is most relevant to your work right now. In smaller teams where one person covers multiple roles, download more than one.