Skip to main contentSkip to navigation

A domain track

Claude & AI for Operations

Operations, procurement and process managers.

25 topics

Good operations work looks dull from the outside: the same report every Sunday, the same supplier comparison every quarter, an SOP everyone knows and nobody updates. The trouble is that it never repeats exactly. Someone pastes a column by hand, one supplier gets last year's terms, and three systems quietly disagree about the same order. The workshop takes one process like that and rebuilds it with Claude, step by step, until you can see where it tends to drift.

What operations managers dread is automation that fails as quietly as it runs. So the exercises are organised around exceptions. Before anything is scheduled, the group decides what Claude handles alone and what stops and waits for a person: an invoice outside the contract rate, a supplier with a missing certificate, a row that fits no procedure. The weekly report runs as a scheduled task, and each run attaches a log of what it checked and what it left for you. If a source changes, you see it next Monday, not next quarter.

The materials are the ones already on your drive: a shared folder nobody has inventoried, a raw export from the ordering system, quotes from four suppliers, an SOP three years old. Claude maps the folder and saves a summary you can return to, builds a control dashboard from the export, and lines the quotes up in one table. Each participant leaves with a scheduled task they set up themselves, already running on their own data.

Online course

Start online, at your own pace

The material we teach in the room, recorded slide by slide. You go through it when it suits you, from any screen.

Claude & AI for Operations: the online course is on its way

Leave your email and we'll write once, the day it opens.

What happens to your details

Giving us these details is your choice, and no law requires it. Without the fields marked required, though, we can't finish what you came here to do.

What for: To email you once, the day the online course for your role opens. Nothing else.

Who gets it: Wider Group only. Your address sits with our infrastructure providers, Supabase and Vercel. Our email provider, Resend, sends us a note when you sign up. All three run servers outside Israel.

You can ask to see what we hold on you, correct it, or have it deleted, any time. Write to shahar@wider-group.com and we answer within 30 days. The full detail is in the Privacy Policy.

Rather do it live? See the live workshops

Today's challenges

  • Repetitive manual processes across systems
  • Collecting and summarizing data from several sources
  • Process control and policy compliance

Example use cases

  • A weekly report that runs on its own as a scheduled task
  • Inventorying a folder and producing a saved summary
  • An operational control dashboard from raw data

What we teach here

Intro

A live opening session built to shift the room, not lecture it: real demos of what Claude can already do inside your workflows, run in front of the group. Participants leave with a working sense of where AI helps and where it doesn't, and enough curiosity to start using it that afternoon.

AI & LLM Basics

What tokens, context windows and hallucinations mean, explained without the math and without the hand-waving. Once a team understands why a model sometimes gets things wrong, it stops either trusting it blindly or dismissing it after one bad answer. Every other module in the program builds on this one.

Claude Intro

A new AI tool comes out every week, and you don't need to chase them. We map the main ones and what each does best, then explain why we spend the day in Claude. After that we set it up together: privacy settings, the one capability to switch on, and a tour of the screen. Face to face it is a live demo; in the online course it is a recorded tour.

Claude Skills

Claude Skills turn a procedure your team already does well into something Claude can repeat on its own: the same checklist, the same tone, the same edge cases covered every time. You build it once with the person who actually knows the process, and from then on every teammate gets that expertise on demand. For teams where quality depends on one or two people, this is how that stops being a bottleneck.

Prompt Engineering

Structure, context and role framing: the craft of asking in a way that gets a usable result on the first try instead of the fifth. Participants practice on real prompts from their own work, not toy examples, so what they take home already fits the job. Every other module assumes this fluency, which is why it comes early.

Claude Projects

Claude Projects hold your documents and instructions in one persistent workspace, so every conversation starts already knowing your company, your terminology and your rules. Teams that set this up once save the ten minutes of re-explaining context at the start of every session, every day. For anyone running the same kind of task repeatedly, this alone changes the math.

Design systems: your brand inside Claude

Without a design system, Claude decides how everything looks, and it comes out different every time. The session shows what a design system holds, how every slide, dashboard and app is built on it, how to make one from your website and a deck you already have, and how to keep several and switch between them.

Artifacts: from answer to deliverable

The difference between an answer and a deliverable. The session covers when something should become an artifact, every kind there is today, how they all come out on your design system, the four ways to change one, and what you do with it: connect it to apps, connect it to files, share it as a live place, or export a snapshot.

Agentic AI vs. Chat

The shift from asking Claude a question to handing it a multi-step task it completes on its own, checking in only where it matters. Participants learn what actually counts as an agent, when handing over work beats doing it turn by turn, and how supervision needs to change once Claude is running unattended. Get this wrong and you either babysit an agent that didn't need it or trust one that did.

Agentic workflows in the Claude chat

In the Claude chat you can hand over a whole job instead of asking a question. Claude plans the steps, searches the web, reads your files, runs code and hands back a finished document, spreadsheet or deck. On a big task it can split the work between several sub-agents running at once. Participants learn which work is worth handing over and how to brief it the way they'd brief a colleague, then practice staying in control while Claude works. They finish by turning a weekly chore into a scheduled task that runs on its own.

Claude Across Office

A full pass across the Office suite: drafting and redlining in Word, tables and analysis in Excel, decks in PowerPoint, and inbox triage in Outlook, taught as one connected workflow rather than four separate tricks. Every exercise uses documents close to what participants actually produce at work. It's the broadest module in the program, and the one most teams come back to most after training.

Claude for Excel

Claude inside Excel: building and checking models, tracing a formula back through six sheets to find where the logic breaks, and producing outputs you can stand behind. This is for teams whose spreadsheets are the actual product, not a side task. Formula archaeology alone tends to pay for the session.

Routines in Claude

Tasks Claude runs on its own, on a schedule: a morning brief from your calendar and inbox, a weekly report, a competitor watch. Participants learn to tell a routine from its schedule, connect only the connectors it needs, and test every routine before it runs alone. They leave with one routine that works from the next morning.

Connectors & MCP

Connecting Claude to the systems your team actually runs on: drives, CRMs, databases, through connectors and MCP, with the permission boundaries covered before the connection ever gets made. Participants leave knowing exactly what to expose and what to keep out of reach. This is the module that turns Claude from a smart typewriter into something acting on real, current data.

CLAUDE.md

CLAUDE.md is a plain text file Claude Code reads at the start of every session, so whatever you'd explain to a new hire on day one, you write there once. Participants learn what goes in it and what stays out, when it's read, and where it lives: the organization, you, the project and a subfolder, all loading together. They leave with a draft from /init and one rule for growing it: what you corrected twice goes in the file.

Agents for non-engineers

How to build an agent without writing code: it gets a job description, a badge that limits what it can touch, and a bottom line it hands back. Participants see why the work goes to a separate room, take an agent file apart, and fill in the one-page charter that turns into the agent's file. They learn to hire for a role, not a task, and to tell when a job needs an agent rather than a skill. They leave knowing the hard part is the charter, and that the charter is their own expertise, written down.

Plugins: the department in a box

A plugin carries the agents, skills and hooks a team built, so another team installs the same department instead of rebuilding it. Participants see what goes in the box and what stays home: CLAUDE.md and the permission rules belong to each team. Then they ask Claude to build one, try it in a fresh session, and share it through a marketplace.

Context Management

How context windows, memory and cost interact, and what to do about it before a long working session starts drifting or the bill surprises someone. Participants learn to spot when Claude is still hauling a task that should have been closed an hour ago, and how to reset without losing what mattered. A short module with an outsized effect on both output quality and the invoice.

Safe AI at Work

The rules every employee needs before their first real session: what data is safe to share, what isn't, and what org-level guardrails should exist so individual judgment isn't the only safeguard. This module is usually the one legal and IT ask for by name. It replaces vague anxiety about compliance with a clear, specific policy people can actually follow.

Human in the Loop

Where people belong in an AI-assisted workflow: which steps need a review gate, which need an approval, and how to calibrate trust so oversight isn't either everywhere or nowhere. This pilot module gives teams a concrete framework instead of a gut feeling about what to check. Get the calibration right and quality goes up without slowing anything down.

Security & Privacy

Permissions, prompt injection and data boundaries: what makes an agent that can act also one that can go wrong, and how to run it anyway without carrying the risk. This pilot module is built for organizations moving agents past read-only demos into things that write, send and change data. It's the module security teams should sit in on.

Claude for Word

Claude inside Word for text-heavy roles: drafting from a brief, redlining a contract, controlling tone across a document, and automating the parts of writing that are really just formatting. This pilot module is aimed at HR, legal, marketing and sales, where documents are the daily output. It's the module that turns a quick-draft request into a five-minute job.

Data Management

Coming soon

Coming soon: preparing and governing the data an AI system actually works from, structure, access and quality, before automation gets layered on top of it. This syllabus item is for teams that already tried an AI project and hit a data problem they weren't expecting. Skipping this step is the single most common reason automation projects stall.

Claude in Slack & Teams

Coming soon

Coming soon: bringing Claude into Slack and Teams so summaries, answers and actions happen where the team already talks, instead of a separate tool people forget to open. This syllabus item covers both the setup and the etiquette of an agent inside a shared channel. Built for teams whose real workflow lives in chat, not in a dedicated app.

AI Policy & Governance

Coming soon

Coming soon: writing the AI policy an organization actually needs, usage rules, risk tiers and rollout governance, instead of a generic template nobody follows. This syllabus item is for leadership and compliance stakeholders shaping how AI gets adopted company-wide. Built to produce a document teams can point to, not a discussion that goes nowhere.

What keeps running without you

Four processes you can stand up the week after, each on your team's own files and systems.

A weekly report nobody launches

A report pulled from several sources that goes out every Sunday morning as a scheduled task, with a last page listing what was checked and what could not be read. The process owner gets the report and the gap list, and decides whether anything is fixed before it circulates.

Supplier quotes side by side

Quotes in different formats land in one table with the same columns: price, payment terms, lead time and unusual clauses. Claude flags what is unclear in each one, and procurement still picks the supplier.

An SOP tested against reality

A procedure turned into a checklist, then run over real records to catch every deviation. Each one reaches you with the data row that triggered it, and whether it is a fault or a justified exception stays your call.

A control dashboard and a mapped folder

A dashboard built from a raw export, plus a saved summary of a folder nobody had counted. It refreshes the same way every week, so the operations lead can see what changed since last time.

Questions people ask

Is there a Claude workshop for operations and procurement teams?

Yes. Wider Group runs a workshop for operations teams, on site or remote, in Hebrew or English, that rebuilds with Claude one process your team runs by hand, such as a weekly report, a supplier comparison or an SOP check. Exercises use your own procedures, exports and supplier files, and the quote is set per team and process.

How do I make sure an automated report does not fail quietly?

Decide the exceptions before you schedule anything. In Wider Group's workshop the group agrees what Claude handles alone and what stops and waits for a person, such as an invoice outside the contract rate or a supplier with a missing certificate. Each scheduled run attaches a log of what it checked and what it left for you. If a source changes, you see it next week, not next quarter.

Can Claude compare supplier quotes that arrive in different formats?

Yes. In Wider Group's workshop, quotes in different formats land in one table with the same columns, covering price, payment terms, lead time and unusual clauses. Claude flags what is unclear in each quote, and procurement still picks the supplier. It works on your real supplier files, after any sensitive details are removed.

Start with one folder

Tailoring begins with one or two processes your team still runs by hand. We pick them together before the session, and the exercises are built on your own procedures, exports and supplier files. People work on a process they are accountable for, not a fictional company's. Name the process and how many people run it, and we'll put a quote together.