This lesson is being recorded

Every video of this course is being uploaded to my YouTube channel. Subscribe so you do not miss it.

Bruno AshfordBruno Ashford @brunoashfordSubscribe

Module 9 · Lesson 9.2 · 11 min

Operations: Inventory, Scheduling, Vendors

Automate the recurring operational checks that keep the business running: stock levels, staff schedules and supplier follow-ups.

Module 9
Back-Office Playbooks

Operations, finance and reporting, done by agents and signed off by you

Bruno Ashford
Bruno Ashford · Module 901 / 12
The quiet cost
Revenue gets the attention. The back office quietly takes your weekends.
Bruno Ashford
Bruno Ashford · Module 902 / 12
Lesson 9.1

No SOP, no delegation

A process that lives in one head cannot be delegated.

  • Talk it through once, let Claude interview you
  • Generate the SOP from the template
  • Test it literally on real files
  • Promote it to a skill
Bruno Ashford · Module 903 / 12
Lesson 9.2

The weekly operations check

  1. 1InventoryReorder before you run out
  2. 2SchedulingCatch double bookings early
  3. 3VendorsSpot price creep
  4. 4Exceptions onlyOne line if all is fine
Bruno Ashford · Module 904 / 12
Lesson 9.3

Finance with a safety net

Exported files in, reviewed drafts out.

  • Never share your bank login
  • Every line gets a confidence flag
  • Humans review medium and low
  • Each correction becomes a rule
Bruno Ashford · Module 905 / 12
Lesson 9.4

The reminder ladder

Days lateActionWho
3Friendly nudgeAgent drafts, you approve
14Firm reminderAgent drafts, you approve
30Personal callYou
60Formal noticeYou decide

Adjust the days to your payment terms.

Bruno Ashford · Module 906 / 12
Illustrative example, not research

What changed for one agency

52 to 34average days to collect
15 minweekly approval time
4personal calls in a quarter
Bruno Ashford · Module 907 / 12
Lesson 9.5
The value of a report is not the numbers. It is the three sentences that say what changed and what we do next.
Bruno Ashford
Bruno Ashford · Module 908 / 12
Lesson 9.5

Rules for an honest report

Speed is useless if the numbers are wrong.

  • Every number cites its source file
  • Missing means MISSING, never estimated
  • Commentary names clients and amounts
  • Verify the headline figure yourself
Bruno Ashford · Module 909 / 12
Lesson 9.6

The one-page owner dashboard

  1. 1SalesPipeline, conversion, average deal
  2. 2MarketingCost per booked lead
  3. 3CashBalance, runway, overdue
  4. 4OperationsCapacity, quality, deadlines
Bruno Ashford · Module 910 / 12
Project

Your automated monthly report

Built from your own files this week.

  • One SOP documented and tested
  • Reconciliation and aging reviewed
  • Report with cited numbers
  • Dashboard with 8 to 12 KPIs
Bruno Ashford · Module 911 / 12
Recap
Let the agent do the counting. Keep the judgement, the approvals and the decisions for yourself.
Bruno Ashford
Bruno Ashford · Module 912 / 12
01 / 12

Use ← → to move. The marker highlights text and the pencil draws on the slide; navigation locks while you annotate. Undo removes the last mark, Esc exits.

1Collect your operational exports in one folder

Create an ops folder and drop in the files you already have: a stock CSV from your store or POS, a schedule export from your booking tool, a supplier price list. If a tool has a connector, you can use it later (Module 6), but files are the fastest safe start. On Windows PowerShell, create each folder with its own mkdir command, or simply in File Explorer.

Terminal
mkdir -p ops/inventory ops/schedule ops/vendors
2Write your rules in plain English

Tell Claude what good looks like: minimum stock per product, maximum jobs per technician per day, acceptable price change from a supplier. Put these rules in your CLAUDE.md or in a rules file so every run uses the same thresholds.

Prompt for Claude
Create ops/rules.md with our operating rules: reorder any product when stock falls below 3 weeks of average sales, flag any technician with more than 5 jobs in a day, and flag any supplier price increase above 5 percent versus last month. Ask me for any number you are unsure about.
3Run the weekly operations check

Ask Claude to read the latest exports, apply the rules and give you a short exceptions report. Only exceptions: if everything is fine, the report should say so in one line.

Prompt for Claude
Read the latest files in ops/inventory, ops/schedule and ops/vendors. Apply the rules in ops/rules.md. Give me an exceptions report only: what needs a decision, why, and your suggested action. Save it as ops/reports/ops-check-YYYY-MM-DD.md with today's date.
4Draft the actions, do not send them

For each exception, let Claude prepare the next step: a purchase order draft, a rescheduling suggestion, an email to the supplier asking about the price change. Drafts go to a folder for you to approve. Sending comes later, and only with the approval rules from Module 11.

Prompt for Claude
For each item in today's exceptions report, draft the action: purchase order lines for reorders, a proposed new schedule for overbooked technicians, and a short, polite email to any supplier with a price increase. Save drafts in ops/drafts. Do not send anything.
5Turn it into a skill

When the check has run well for two or three weeks, package it as a skill so anyone on the team can run it with the same rules. In Module 10 you will schedule it to run on its own every Monday at 7am.

Operations problems rarely arrive as a crisis. They arrive as a quiet spreadsheet that nobody opened on Monday: a product that sold out on Wednesday, a technician double-booked on Thursday, a supplier invoice that doubled without anyone noticing. By Friday it is a crisis.

An agent is very good at the boring vigilance that humans skip. It can read your stock export, your booking calendar export and your supplier price list every week, compare them against rules you set, and hand you a short list of things that need a decision. You stay the decision maker. The agent becomes the person who always checks.

Key points

  • Agents are best at the dull vigilance humans skip.
  • Rules in plain English make every run consistent.
  • Exceptions only: a report nobody reads is worse than no report.
  • Draft actions freely, send them only with approval.

Avoid

  • Asking for a full summary of everything instead of exceptions.
  • Changing thresholds in the prompt each week instead of in the rules file.
  • Letting the agent place orders or email suppliers before you trust the checks.
  • Feeding it stale exports and trusting the result.
Real-world example: an e-commerce store

A UK skincare brand with 180 SKUs used to discover stock-outs from customer complaints. The owner now exports stock and the last 90 days of sales every Monday, and Claude flags the products that will run out within three weeks, plus two suppliers whose prices crept up. In the first month the check caught four stock-outs before they happened and one 12 percent price rise that nobody had noticed. The whole routine takes her ten minutes of reviewing instead of an hour of scrolling.

Bruno Ashford Subscribe