SiSu RevOps

M3  /  L3.3  /  about 15 minutes

Scope it, cost it, and revise what you wrote in Module 1

"Clean up the CRM."

You have said it and heard it. It is not a task, it is a mood with a verb attached. Hand it to an agent with file access and you get exactly what you asked for: changes, everywhere, made confidently, with no record of which rows were touched or why.

This lesson turns that sentence into something that can be done and checked, prices it, and sends you back to your Module 1 list.

What you will be able to do

  • Rewrite an open-ended task into a scoped one with four named components.
  • Say what a task costs in usage terms, and when that changes the decision.
  • Re-score your fit log with the instrument and notice which tasks moved.

The rewrite drill

The product fact underneath this: open-ended, recursive or poorly defined tasks raise both the likelihood and the impact of errors. Scoping is a teachable skill, fixed by writing, not by a better model.

Four components. A brief missing any one is under-scoped, and the failure's shape tells you which.

Component What it is The failure when it is missing
Definition of done The condition that makes it finished It keeps going, or it stops early and you cannot tell which
Out-of-scope list What not to touch, named explicitly It touches things nobody asked about
Stopping condition When to stop and ask instead of continuing It pushes through the ambiguous 8 percent and you inherit the guesses
Exceptions rule What to do with anything unresolvable It guesses, and the guesses are invisible

The drill, worked on the real sentence:

Before. "Clean up the accounts file and fix anything that looks wrong."

After.

Input:   10-data/accounts.csv (308 rows). Do not modify it.
Scope:   the country column only.
Rule:    canonical country values are full country names as written in
         DATA-DICTIONARY.md. Flag any row whose country value is not one.
Output:  30-output/country-cleanup/proposed-changes.csv with columns
         account_id, column, current_value, proposed_value, reason.
Out of scope: every other column. Do not merge accounts. Do not touch
         health_score. Do not touch anything on a Churned account.
Definition of done: every row in accounts.csv has been examined and is
         either absent from the output or present with a proposed value.
Stopping condition: if more than 5 percent of rows are unresolvable, stop
         and report instead of continuing.
Exceptions: anything you cannot resolve goes to
         30-output/country-cleanup/exceptions.csv with the account_id and
         the reason. Do not guess.

Three things changed, and only one is about clarity.

It named one defect class. Not "anything that looks wrong": one column, one rule, with real work to do. answer-keys/PLANTED-ISSUES.md in your pack, which you open only after attempting the lab, documents ACC-02838 as united states, ACC-02841 as DE, ACC-02974 as netherlands and ACC-03002 as The Netherlands, all class inconsistent-values.

It changed the blast radius. "Fix" writes to the file; "propose" writes a different file and leaves the source alone. Same value, one class lower, a human in the middle.

It made the output checkable. A proposed-changes file with a reason column is verifiable row by row. A cleaned file is not: the evidence of what changed was destroyed by the change.

Check yourself: rewrite one open-ended request from your own week, with all four components.

Usage is a triage input

Cowork draws on the same plan allowance as Claude.ai chat and Claude Code, under a 5-hour rolling window plus a weekly cap. Complex multi-step Cowork tasks consume materially more allowance than standard chat, and Pro users hit limits fastest under heavy use.

Worth knowing: this course teaches the shape, never a number. Anthropic does not publish stable allowances, and we have not verified any figure. A specific allowance quoted anywhere, even in a confident blog post, is folklore until you have read it on your own account page.

What the shape means for triage:

  • A big hygiene pass is not free; what it costs is your chat. One shared pool means a full-file pass started at 14:00 can leave you without chat at 16:00, on a Thursday in quarter-end week, when three people need something.
  • Run heavy passes when you will not need chat. A scheduling decision, not a technical one.
  • Split a large job into batches, by region, owner or segment. Batching also gives you a verification point after batch one, which you wanted anyway.
  • "This task would consume my week" is a legitimate reason to decline or reduce scope, stated in the delegation policy rather than unspoken.

Check yourself: for your largest shortlist task, when in the week would you run it, and why?

Revise the fit log

Go back to cowork-fit-log.md, the fit log you wrote yourself in Module 1, and re-score every row with the five-factor test, writing the deciding factor on each.

Expect two or three rows to move each way. Up-movers are usually tasks you thought too messy; messy usually means high Volume with a real source of truth, the best profile there is. Down-movers are usually tasks you were enthusiastic about, where Checkability turned out to be 2. That is the point of writing the log before you had the instrument: nobody learns from a list they scored correctly the first time.

Check yourself: produce section 1 of delegation-policy.md, the scored inventory, with a decision per row.

Try this now: run it both ways

Both passes run in the revenue-workspace/ folder you built in Module 2, on the practice-pack data already copied into 10-data/.

Pass 1, the request as people actually write it.

Clean up the accounts file and fix anything that looks wrong.

Pass 2, the scoped rewrite. The block from the rewrite drill, verbatim.

Two decisions behind pass 2 are worth copying. It is smaller and draft-only, not more detailed: adding instructions to an unbounded task just makes a longer unbounded task. And its stopping condition was set before any output existed, because one set after seeing the output is a rationalisation. Here the country rule resolves cleanly and it never fires. Fine: a smoke alarm that never goes off is working.

The break. Run pass 1, verbatim, on a copy of 10-data/accounts.csv. No other instructions. Let it finish.

What to look for. Three things, none of them a syntax error.

1. Changes nobody asked for. "Anything that looks wrong" is a wide invitation, and PLANTED-ISSUES.md documents how much the file has on offer:

  • seven inconsistent-values rows in country and industry, including ACC-02948 (leading space in Retail) and ACC-03092 (Hospitality & Leisure);
  • two whitespace rows, ACC-03008 and ACC-03021, trailing spaces in account_name;
  • eight duplicate-accounts rows, for example ACC-02890 and ACC-02988, one company under a punctuation variant;
  • seven missing-values rows, including ACC-02828 and ACC-03073 (blank owners);
  • nine SUBTLE scale-mismatch rows, health scores on a 1 to 10 scale, all owned by CSM Tomasz Jonker: ACC-02805, ACC-02834, ACC-02938, ACC-02945, ACC-02984, ACC-03007, ACC-03043, ACC-03086, ACC-03118.

A pass told to fix what looks wrong will engage with several of these classes. Which ones will vary between runs, because nothing constrains it. That variability is itself the finding: two people running the same sentence on the same file get different edits, which is why you run this rather than read it.

2. No record of what was touched. A cleaned file does not tell you what changed. You cannot diff against a source you overwrote, and you cannot review a decision you cannot see.

3. At least one change that is only visibly wrong from the source. Watch the health scores: the nine scale-mismatch accounts are the trap, and both available moves are wrong. Leaving ACC-03043 at 8 pulls the account into every "health below 40" list. Rescaling it to 80 invents a number no system holds: the file does not record which scale the CSM used. The right move is neither: flag it, name the pattern (nine accounts, one CSM), and ask the person who entered it. An under-scoped brief cannot "ask", so it picks.

The guard. Run pass 2 side by side, put the two outputs next to each other, and answer three questions in writing:

  1. Which rows did pass 2 touch, and how do you know? (Read proposed-changes.csv.)
  2. Which rows did pass 1 touch, and how do you know? (You cannot, and that is the answer.)
  3. What is in exceptions.csv, and what does its length tell you about your brief? An empty exceptions file on messy data is a warning sign, not a success. Module 4 teaches how to read it.

The guard is not "write better prompts". It is three structural changes: one named defect class, a proposals file instead of an edit in place, and an exceptions route for anything ambiguous.

What you keep

revenue-workspace/40-reference/delegation-policy.md, the file you have been writing since Lesson 1, complete:

  1. Scored inventory: every recurring task from the fit log, five factors, total, deciding factor, and a decision (hand over now / after the source of truth is fixed / keep human).
  2. The shortlist: top five candidates with blast-radius class, review gate, approver, reversal plan, and minutes saved per week with verification cost already subtracted.
  3. The never list: your exclusions, each with the Lesson 2 rule that generates it.

Plus cowork-fit-log.md, re-scored, moved rows marked so you can see your calibration change. This is the document a manager approves, and the capstone workflow must come from section 2.

Quick check

  1. Here is a brief: "Go through the contacts file and fix the email addresses." Which of the four scoping components is missing? Rewrite the one line that would do most to make the output checkable.
  2. A large hygiene job is proposed for Thursday afternoon in quarter-end week. State the usage consequence and the right scope change. Do not state a numeric allowance, and say why not.
  3. Your exceptions file after a scoped run on messy data has zero rows. Give the two most likely explanations and say which you would check first.
  4. Which task moved furthest between your Module 1 fit log and your scored inventory? Name the factor that moved it. If nothing moved, you probably scored the log rather than re-scoring it.
Answers

1. All four are missing, and saying so beats picking one. The line that does most for checkability is the output shape: change "fix" to "write proposed-changes.csv with contact_id, column, current_value, proposed_value, reason". That turns an unreviewable edit into a reviewable list and drops the blast radius a class. And the brief is worse than it looks: PLANTED-ISSUES.md records 32 rows in class email-quality covering three different problems with three different correct treatments, and a role-based address like sales@ is not malformed and must not be "corrected" into a person.

2. One shared pool under a rolling window plus a weekly cap, so it can cost you chat access for the rest of the window in the week you need it most. Correct change: batch by segment or owner, first batch now, the rest out of hours. No number, because the allowances are not published and we have not verified any figure.

3. Either the exceptions rule never made it into the run, or the brief was narrow enough that nothing ambiguous fell inside it. Check the first: look for a documented ambiguous case resolved silently.

4. Open, and it is a calibration check on you rather than on the task.

Where this goes next

Next module: Module 4 takes your top shortlist item and turns it into a brief you can run, check with evidence, and keep, so next Tuesday costs a minute instead of forty.

Track labs: the exercise sheet in labs/LAB-03 of your practice pack (start with its README). Part A ships twelve tasks with reference scoring and produces the scoped rewrite of one deliberately open-ended task. CP-03, the module quiz in the interactive app, is the heaviest checkpoint in the foundations track: a wrong answer here is the one that costs money.