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 3 · Lesson 3.3 · 13 min

Making Sense of Messy Spreadsheets

Turn a messy real-world spreadsheet into clean data and plain-English answers, without touching the original file.

Module 3
Your First Real Task

From testing the tool to delegating real work

Bruno Ashford
Bruno Ashford · Module 301 / 12
The shift

A chatbot waits. An agent goes and looks.

Claude Code works inside a folder on your computer.

  • Reads and searches your files
  • Plans before it acts
  • Asks before it changes anything
  • Checks its own work when asked
Bruno Ashford · Module 302 / 12
The loop

Explore, Plan, Execute, Review

  1. 1ExploreRead the data. No output yet.
  2. 2PlanApprove the approach first.
  3. 3ExecuteLet it work.
  4. 4ReviewIt checks, then you check.
Bruno Ashford · Module 303 / 12
A truth that hurts
Most bad AI output starts with asking for the answer before anyone looked at the problem.
Bruno Ashford
Bruno Ashford · Module 304 / 12
Safety first

Plan mode: think without touching

Press Shift+Tab until plan mode shows.

  • Claude reads and proposes
  • Nothing changes until you approve
  • Use it for anything touching real data
Bruno Ashford · Module 305 / 12
Messy spreadsheets

Five moves to clean data

Your original file is never touched.

  • Protect the original
  • Get a mess report
  • You set the business rules
  • Ask business questions
  • Reconcile the totals
Bruno Ashford · Module 306 / 12
Illustrative example, practice file

What a mess report finds

30rows in the sample file
4date formats in one column
3spellings of one customer
0changes to the original
Bruno Ashford · Module 307 / 12
Analysis vs. judgment

Ask for a decision, not a summary

Weak requestStrong request
What do you think?Choose between these 3 options
Summarise the dataCite numbers and source files
Give me insightsRisks and what proves us wrong
Write a reportOne page, recommendation first
Bruno Ashford · Module 308 / 12
The Delegation Brief

Brief it like a new hire

  1. 1GoalWhy the task exists
  2. 2ContextWhat a new hire needs
  3. 3InputsExact files to use
  4. 4OutputFormat, length, file name
  5. 5GuardrailsOff limits, and when to ask
Bruno Ashford · Module 309 / 12
Habits

Four habits of owners who delegate well

Small habits, big difference.

  • Ask it to look before acting
  • Read every permission prompt
  • Ask which files it used
  • Type /clear between tasks
Bruno Ashford · Module 310 / 12
Your project

A one-page diagnosis of your data

Real data, three recommendations, evidence for each.

  • Original file untouched
  • Totals reconciled
  • Every claim cites a number
  • An owner for every action
Bruno Ashford · Module 311 / 12
Recap
You do not need to be technical. You need to brief well and check the work.
Bruno Ashford
Bruno Ashford · Module 312 / 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.

1Put the file in the folder and protect the original

Download the practice file 03-sample-messy-sales.csv into your Company/sales folder. Tell Claude the original is read-only. Every cleaning job should produce a new file so you can always go back.

Prompt for Claude
The file sales/03-sample-messy-sales.csv is the original. Never edit it. Any cleaned version goes into a new file with -clean in the name.
2Ask for a mess report first

Before cleaning anything, get a list of every problem Claude can find. This is your chance to make business decisions, like whether a refund counts as a sale.

Prompt for Claude
Read sales/03-sample-messy-sales.csv and give me a mess report: inconsistent dates, duplicate rows, customer names spelled differently, missing values, amounts stored as text, and anything else odd. Do not fix anything yet. For each issue, suggest how you would handle it.
3Decide the rules, then let it clean

Answer its questions in business terms. You decide what a duplicate is and how refunds are treated. Claude does the tedious part and writes the clean copy.

Prompt for Claude
Go ahead with these rules: dates as YYYY-MM-DD, merge customer names that are clearly the same company, remove exact duplicates, keep refunds as negative amounts, and flag any row you are unsure about in a new column called check. Save it as sales/03-sample-messy-sales-clean.csv.
4Ask business questions, not spreadsheet questions

You do not need to know formulas. Ask the question you would ask your finance person, and ask for the answer in a small table with the method explained.

Prompt for Claude
Using the clean file: what was revenue by month, who are the top 5 customers by revenue, which sales rep has the highest average deal size, and what share of revenue came from refunds? Show small tables and explain in one line how you calculated each.
5Reconcile before you trust

The clean total should match the original total minus what you chose to remove. Ask for that reconciliation every time. If it does not add up, you have found either a bug or a business insight.

Prompt for Claude
Reconcile: what is the total in the original file, what is the total in the clean file, and exactly which rows explain the difference?

Every business I have ever looked inside has the same spreadsheet: the one three people edit, with dates in four formats, a customer spelled five ways and a column called "notes 2". You know the answers are in there. You just never have the two hours to dig them out.

This is where Claude Code earns its keep fast. It can read the file, find the mess, clean a copy and answer your questions in minutes. In this lesson you will do it on the practice file included with this module, then on your own.

Key points

  • Never let Claude edit the original file. Always a cleaned copy.
  • Get a mess report before any cleaning.
  • You set the business rules. Claude does the tedious work.
  • Ask business questions in plain English.
  • Always reconcile totals between original and clean data.

Avoid

  • Letting the agent overwrite the only copy of your data.
  • Accepting its cleaning choices without deciding the business rules yourself.
  • Asking for formulas when you really want an answer.
  • Skipping the reconciliation because the numbers look reasonable.
Real-world example: an e-commerce store

Priya sells homeware online and exports orders from two platforms into one spreadsheet. The mess report found the same customer under three email variants, 42 test orders from her own checkout, and currency symbols mixed into the amount column. After cleaning, the top 20 customers turned out to drive 38 percent of revenue, a figure she had guessed at 15 percent. She launched a VIP email the same week.

Bruno Ashford Subscribe