1-Week AI Training for Procurement Teams: Day-by-Day Plan

We've run AI training for 10+ procurement teams now, across categories, across team sizes, across maturity levels. The single most consistent observation: the 1-week format works. The 1-day workshop doesn't (no time for skills to transfer). The 21-day program doesn't (loses momentum in week 2 and dies). Five days, run intensively, with the right structure, that's the format that gets procurement teams from AI-curious to AI-fluent and stays there.

This piece is the day-by-day plan we run with clients. It's also what we'd recommend any procurement leader use if they're building an internal program rather than bringing in a partner. We're not gatekeeping the curriculum because the curriculum isn't the moat, the facilitation and the 30/60/90 follow-through are. Take the plan. Use it. Adapt it.

If you're a CPO or head of procurement scoping AI training and trying to decide what "good" looks like, this is the structural answer. If you're an L&D leader being asked to spec a procurement-specific AI program, the day-by-day below is the starting brief. If you're an individual procurement professional whose team isn't ready for a formal program yet, scroll to the end for the self-led version of the same plan.

Why 1 week beats the alternatives

Before the day-by-day, the why. We've tried every format, 90-minute exec exposure sessions, half-day team intros, 1-day immersives, 21-day cohort programs. The 1-week intensive consistently outperforms all of them on the metric that actually matters: durable adoption at day 90.

Why the 90-minute exec session fails: It produces exec buy-in but no behavior change. The team needs to leave with something they used, not something they watched.

Why the half-day intro fails: Enough time to introduce the concepts. Not enough time to run any workflow end-to-end. Participants leave knowing what AI could do for their work without ever having done it.

Why the 1-day workshop fails (mostly): It's the most common format and the most disappointing. Day-of energy is high, the work feels productive, and by Friday the next week 80% of participants are back to their old workflows. There's no follow-through built in.

Why the 21-day cohort program fails: Loss of momentum is brutal. By day 14, the homework participation drops 40%+. By day 21, the only people still engaged are the ones who didn't need the training in the first place.

Why 1 week works: Long enough that every participant runs every major workflow end-to-end with their own real data, builds their share of the team's prompt library, and commits to a 30/60/90 plan. Short enough that the calendar protection holds, the exec presence is sustainable, and the energy stays high through the showcase on Friday afternoon. Five days is the sweet spot between enough time to actually build the muscle and short enough that everyone shows up every day.

It also matches how procurement leaders already think about work, in sprints. Sourcing events run in sprints. Category reviews run in sprints. Treating AI training as a sprint fits the operating rhythm of the function.

The day-by-day curriculum

What follows is the format we run with clients. Hours are nominal, most days run from 9 AM to 4 PM with a working lunch and two short breaks. Pre-work and homework between days matter as much as the in-room time.

Day 1, Foundation + first wins

Morning (3 hours), AI fundamentals specific to procurement. Not generic AI 101. Specifically: how language models handle long documents like contracts and RFPs (and where they fail), why generic prompting produces vague output in procurement workflows, what context the model needs from you to produce something you can ship, and the four data-handling rules every procurement professional needs internalized before they ever paste a supplier name into an AI tool.

This morning is where you lose people if it's done wrong. The temptation is to spend 90 minutes on transformer architecture. Don't. Spend 90 minutes on "here are 3 supplier proposals, let's read them in AI together and see what it surfaces" and you'll have the room.

Working lunch, Each person on the team comes to lunch with one real piece of work they own this week. A live RFP. A contract that needs reviewing. A category review that's due. A supplier proposal sitting in their inbox. The afternoon is built around that work.

Afternoon (3 hours), Every person runs their own workflow end-to-end with AI assistance. The facilitator (us, or whoever you've designated internally) circulates. Two rounds: first round is rough draft with light AI assistance. Second round is "now show the rest of the team your output and what surprised you." Peer learning starts immediately.

Homework, Each participant brings tomorrow's input ready. If tomorrow is RFP day, they bring a real RFP brief. If tomorrow is contract day, they bring a real contract. No exercises with example data. Real work or it doesn't count.

Day 1 success criteria: Every person has run AI against one real piece of their own work and presented the output to the team.

Day 2, Sourcing and RFP deep dive

Morning, Hands-on workshop on the highest-time-cost sourcing workflows. Live RFP drafting from a real stakeholder brief. Multi-supplier response evaluation against a weighted rubric. Bid clarification question generation. Each participant works on their own live event; the room produces simultaneous workflow output.

The pattern we use is "shadow then solo." Show one example end-to-end as a group (~30 minutes), then everyone runs the same workflow on their own work (~90 minutes), then a peer review round (~60 minutes).

Afternoon, Negotiation prep specifically. BATNA analysis with AI assistance. Should-cost modeling from market data. Counter-proposal language for a real upcoming negotiation. Concession ladder construction. Every participant leaves with a usable prep document for an actual negotiation in their pipeline.

Homework, Each participant runs the next sourcing workflow on their own list (not the one we did together) and brings the output to Day 3.

Day 2 success criteria: Every person has used AI to produce a sourcing deliverable they will actually use this quarter.

Day 3, Spend, suppliers, and contracts

Morning, Spend analysis day. Live work on real spend data, with the participant's own ERP extract. Category classification, maverick spend identification, consolidation hypotheses, anomaly detection. The procurement analysts on the team often have their highest-leverage day here, these are the workflows where AI compresses the most clock time.

If the team doesn't have an extract handy, we walk through a sanitized one we bring. But the depth of the day improves dramatically when participants run their real data.

Afternoon, Split into two threads. Contract managers and sourcing leads work on contract review (clause extraction, risk flagging, redline summarization) using a real MSA. Category managers and SRMs work on supplier scoring and risk monitoring (supplier discovery, scorecard refresh, ESG profile). Cross-pollination at the end, each thread presents back what they learned to the other thread.

Homework, Each participant identifies the 2 highest-frequency workflows they own where AI compresses the most time. Brings those to Day 4 as the basis for their personal prompt library.

Day 3 success criteria: Every person has either categorized real spend, reviewed a real contract, or scored a real supplier using AI, and surfaced something useful from it.

Day 4, Shared infrastructure day

This is the day most training programs skip entirely. It's also the day that determines whether the training survives the next 90 days.

Morning, The team builds shared context documents together. Your category taxonomy, with the language and definitions your team actually uses. Your supplier list, with the right attributes attached (preferred status, contract terms, geographic scope, performance history). Your standard contract template. Your evaluation rubrics. Your code of conduct. Every document the team will attach to AI prompts over the next 90 days, packaged once so no one has to rebuild from scratch.

This is unsexy work. It's also the highest-leverage 3 hours of the entire week. Every workshop we've run where the team skipped this day saw adoption drop materially by week 6.

Afternoon, The team builds its shared prompt library. Every workflow worth automating, captured as a named prompt with the right context attached. We organize by procurement role (sourcing lead, category manager, contract manager, analyst, SRM, tactical buyer, CPO) so each person can find their relevant prompts fast. We seed the library with our role-based playbooks: the Claude Cowork Playbook if the team is on Claude (105 prompts across 7 roles), or the Codex Playbook if the team is on ChatGPT/Codex (same 7-role structure, prompts tuned for OpenAI's strengths). Either way the team adapts, edits, and adds their own as they work through it.

Workspace tooling configuration is the small last step. Set up the team's shared Claude project (or ChatGPT custom GPT, or whichever tool you've standardized on) with the context documents and prompt library pre-loaded. Now anyone on the team can run a workflow from a consistent starting point.

Day 4 success criteria: The team has a shared prompt library and shared context infrastructure that lives somewhere accessible to all of them. If they don't, redo Day 4 before moving on.

Day 5, Showcase, governance, and 30/60/90 commit

Morning, Every team member presents one workflow they've committed to running with AI going forward. Not a hypothetical, a workflow they own, with the data they'd use, the prompt they'd run, the output format they'd produce. The presentation is to the rest of the team, the exec sponsor, and ideally one or two stakeholders from outside procurement (finance is the right pick, they're who you'll later need to convince the training worked).

Each presenter takes questions. The room collectively pressure-tests every commitment. By the end of the morning, everyone has either confirmed their commitment or refined it based on peer feedback.

Afternoon, Three things, in order. Governance: confirm the team's data-handling policy, the approved AI tools, the workspace conventions. The team writes this down themselves rather than receiving it as a document from IT or legal, they're the ones who'll have to follow it.

Then 30/60/90: every person writes their personal adoption plan. Day 30: which workflows they'll have used AI for at least 5 times. Day 60: which workflows they'll have automated into their weekly rhythm. Day 90: how much time they expect to have saved and what they'll do with it. These plans get shared with the exec sponsor who tracks them.

Finally, the show-and-tell rhythm. Every 2 weeks, one person on the team demonstrates a workflow they ran with AI in the last fortnight. Peer learning beats expert teaching for sustained adoption, this rhythm is what compounds over months.

Day 5 success criteria: Every team member has committed in writing to a 30/60/90 plan with specific workflow targets. Show-and-tell calendar is scheduled. Governance is locked.

What "good" looks like at the end of week 1

If the week worked, you'll see these outcomes by Friday afternoon:

• 80%+ team participation in the workshop across all 5 days. Below that, adoption will stall, re-scope or extend.
• A populated prompt library with at least 30 prompts the team has actually used during the workshop (not just copied from a template).
• At least one shipped deliverable per participant that was AI-assisted and used in their actual work. RFP, contract summary, category brief, supplier scorecard, something they wouldn't have produced as well or as fast without AI.
• Shared infrastructure in a shared location: prompt library, context documents, workspace conventions, governance policy. All accessible to every team member.
• A 30/60/90 plan per person, signed off by the exec sponsor.
• A show-and-tell calendar through the next 90 days, with named owners for the first 6 sessions.

If you finish Friday missing any of those six, the gap is what you address in the first month of follow-through. They're all recoverable. They're also all preventable if you build them into the curriculum upfront.

The pitfalls in week-long programs (so you can avoid them)

We've watched these patterns derail otherwise-well-designed weeks. Each one is preventable.

Day 1 spent on theory instead of practice. The single most common failure mode. If your Day 1 afternoon isn't every participant doing real work, scrap the design and start over. Theory loses procurement audiences fast, they're senior, they're skeptical, they have other things to do.

No homework between days. If participants leave Day 1 without bringing inputs for Day 2, the week breaks down. Each day's homework is the connective tissue. Make it mandatory, make it tied to their real work, and make sure the facilitator reviews it the morning of the next session.

Exec sponsor not in the room. When the CPO or category director shows up only on Day 5 to give a closing speech, the team reads that as "this is training, not a strategic priority." When they show up Day 1, work alongside the team on Day 2 or 3, and run a real workflow themselves on Day 4, the team reads that as "we're all learning this together." The difference in adoption at day 60 is dramatic.

No shared infrastructure day. Trying to compress Day 4 into 90 minutes at the end of Day 5 is the version of this failure we see most often. The shared infrastructure day deserves a full day of its own time because the work it produces is what survives the next 90 days. Skip it and the training reverts to individual notebooks within a fortnight.

No 30/60/90 commitments. Workshops that end with "great week everyone, let's see what you do with it" don't produce durable adoption. The written commitment with named owners and dated check-ins is the mechanism that turns a workshop into a program.

How we run this with clients

We deliver this 1-week format as a custom-scoped engagement for procurement teams. We facilitate the workshop, build the shared infrastructure with your team during the week, and stay involved through the 30/60/90 adoption arc. We've run this with 10+ procurement functions across category mixes and team sizes, what you see above is the version that consistently produces durable adoption.

We also bring two things internal teams can't easily replicate: pattern-recognition from running this with multiple procurement functions (we know what fails in week 2, in month 2, and how to prevent both), and the Claude Procurement OS, seven production-ready Claude skills your team can install and have running by Day 2. The OS shortens the time from "we have AI access" to "the team is shipping AI-assisted work" by a meaningful amount.

If you'd like to talk through whether this format fits your team, size, category mix, current AI maturity, the right scope, book a 20-minute scoping call.

The self-led version for individuals

If you're a procurement professional whose team isn't ready for a formal program yet, you can run a self-led version of the same week on your own. The structure compresses meaningfully:

• Day 1: Read our AI Training for Procurement playbook (15 minutes) and pick one workflow you own that you'd like to compress this week.
• Day 2: Run that workflow with AI assistance, using one of the role-specific prompt guides from the Cowork Playbook bundle.
• Day 3: Install the free Procurement OS and run one of the seven skills against your own data.
• Day 4: Build your personal context document, your supplier list, your category taxonomy, your standard templates, that you'll attach to every prompt going forward.
• Day 5: Pick one peer in your function. Demo what you built. The peer accountability is what compounds.

If you want the productized version that goes deeper than the self-led path, modules per Procurement OS skill, a monthly newsletter on what's new in AI for procurement, and access to our monthly practitioner roundtable, that's the Procurement AI Academy. $49 to try a single module, $499/year for full access.

Frequently asked questions

How much does a 1-week AI procurement training program cost?

It depends on team size, category complexity, customization required, and whether you want the 30/60/90 follow-through included. Most of our engagements fall in the mid-five-figures to low-six-figures range. The variable that moves the cost most is whether the curriculum is customized to your specific categories and supplier base or run from our standard pattern, both work, the standard is faster to ship and the customized is stickier post-workshop.

Can it be done remotely?

Yes. We've run this format virtually, in-person, and hybrid. The hybrid version, in-person for Day 1 and Day 5 (the anchor days), virtual for Days 2–4, has the best participation and the lowest cost. Fully remote works but requires more facilitator discipline to keep the energy up.

What's the minimum team size?

Below 5 people, an individual subscription model with regular peer share-outs is usually more efficient than a workshop. The 1-week format hits its stride between 8 and 25 participants. Above 25, we recommend splitting into two parallel cohorts.

What if our team is bigger, does this format scale?

The format scales to about 30 in one cohort. Above that, we run multiple parallel cohorts (each ~20 people) over consecutive weeks with the same facilitator, and pull all cohorts together for the Day 5 showcase. For functions above 100 people, the 3-month phased rollout format works better than the intensive 1-week, more about that in our AI Training for Procurement pillar.

What tools does the team need access to in advance?

Whichever AI tool you've standardized on (Claude, ChatGPT, or Copilot, see our Claude vs ChatGPT for Procurement comparison for the choice framework if you haven't picked yet). Plus a shared workspace surface (Claude Projects, custom GPTs, or Copilot custom agents). IT setup needs to be done before Day 1, workshop time isn't for account provisioning.

What's the single biggest predictor of whether the week sticks?

Exec sponsor presence in the room. Not "kicks off Day 1 with a speech." Actually in the room, doing the work, running their own workflow on Day 2 or 3, presenting in the showcase Friday. When that happens, day-90 adoption is 80%+. When it doesn't, adoption drops to 30-40% within a quarter.

Start here

If you're scoping a 1-week AI training program for your procurement team, the three concrete next steps:

1. Pick the exec sponsor. Before the curriculum, before the calendar, before anything else. The single person whose visible participation will signal that this is strategic, not training.
2. Decide on the tool stack. Claude, ChatGPT, or both. Our Claude vs ChatGPT for Procurement comparison covers the framework if you haven't picked yet.
3. Book a 20-minute scoping call with us at moleculeone.ai/procurement-ai-training and we'll talk through your team size, category mix, and timeline. Or download the Cowork Playbook bundle and start running the prompts with your team, that's the lowest-friction way to test whether a structured week is worth the investment.

The format works. The question is whether you can secure the calendar protection, the exec presence, and the homework rigor that make the week earn its keep. Those three things are what separate the AI training programs that produce durable adoption from the ones that produce energetic Friday afternoons followed by quiet Mondays.