SiSu RevOps

M1  /  L1.1  /  about 12 minutes

Which of your Monday can leave your hands

Open last week's calendar and sent folder. Somewhere in there is the work that never appears in a job description and eats the day anyway: the forty-minute reporting request, the pre-call research, the CRM fields you update on Friday. You have probably tried a chat assistant on some of it. It writes well, but it cannot open the export in your downloads folder, and every Monday you paste the same context in from scratch. Before you decide what to do about that, you need a list.

What you will be able to do

  • Write down your recurring work with an honest minute count. Every decision in this course starts here.
  • Say, for any task, whether it needs a conversation, a working session with your files, or a person, and name the reason.
  • Describe the loop a working session runs, and the two moments where you can change its direction.

Where your week actually goes

Everything this lesson uses came in the practice pack from the course page; if you have not downloaded it, do that first.

Try this now Open templates/M1/cowork-fit-log.md from your practice pack and fill only the first two columns for twelve to twenty-five tasks. Four minutes, before any product enters the picture. This list is the spine of Modules 1, 3 and the capstone.

Task Minutes per week
Rebuild the weekly pipeline movement view 45
Answer ad hoc "how many X" questions in Slack 90
Pre-call research on named accounts 120

Three rules keep it honest:

  1. Recurring only. If it happened once, it is not on this list.
  2. Minutes as they really are, including the part where you go and find the file.
  3. Name the work, not the tool. "Rebuild the movement view", not "use the BI tool".

Leave the other columns blank. You fill them in Lesson 3 and again in Module 3.

Check yourself: which three tasks cost you the most minutes per week?

Chat, Code, Cowork

Cowork is a mode of the Claude application that runs multi-step work on real files and connected tools, not just text in a chat window. It sits alongside Chat and Code as a third mode of the same product. Anthropic's framing is the most useful sentence anyone has written about it: Chat is a conversation; Cowork is a working session where you describe the task, Claude plans and executes it, and you steer along the way.

Two things follow, and both matter to you.

It was built for people who do not write code. Anthropic aimed it at non-developers after noticing developers already using the coding agent for non-coding work.

It has a filesystem. Point it at a folder and it can read, create and modify files inside it. That is what moves work out of the chat window, and it is the source of every risk in Module 2.

Worth knowing: reporting on Anthropic's own session data indicates most Cowork usage is business operations and content creation, not coding. The exact percentage is unverified, so take the direction and skip any number you see quoted, including ours, until you read it at source.

Check yourself: can you tell the three modes apart in one sentence each?

The task loop, and the two places you steer

  you describe an outcome
     -> Claude plans
        -> Claude executes across multiple steps against real files
           -> you steer

You get two steering points, and they are not equally good.

Before, in the brief you write. The cheap one. Everything you say up front costs a sentence and saves a rerun. Module 4 turns this into a seven-part template.

During, by interrupting. You can stop a running task and narrow it ("only the EMEA accounts") or correct it ("the amount field is in local currency"). This one is expensive, and Module 4 teaches when to stop correcting and rewrite instead.

There is no third steering point. Once a run has produced eleven files, reading them is not steering, it is checking: a different discipline with its own cost, and the Check letter of TRACK.

Check yourself: which of the two steering points have you been neglecting?

Watch the difference

The same question, asked two ways, on the shipped Talvera data.

In a chat window. Paste 40 rows of the pipeline export and ask "which of these are stuck?" You get a competent answer about those 40 rows. For the other 488 rows, you paste again. Next week, you paste again. The context dies when the tab does.

In a working session. Point Cowork at your pack's data folder and write: "Read opportunities.csv. List every open opportunity where days_in_stage is more than double the segment norm in the data dictionary. Output a markdown table with opportunity id, account id, stage, days in stage, owner." It reads the file itself, applies the rule across all 528 rows, and writes a file.

The whole difference: you did not paste the data. Pasting caps the job at what fits in a conversation. Pointing at a folder caps it at what is in the folder, which is why "what else is in the folder" is the most important question in Module 2.

Files or conversation?

These get conflated because both start with you typing a request, and the wrong call wastes either an hour of setup or an afternoon of pasting.

Needs a conversation:

"Help me think through whether we should keep running the SMB motion at all after the pricing change. I have a view and I want it challenged."

No file answers this. The inputs are your judgment and things you have not said out loud yet. The output is a better-formed opinion, not an artifact. The tell: the output is an opinion you will hold, not a file you will send.

Needs files:

"For every open opportunity in the pipeline export, tell me which ones have a close date that has already passed, and group them by owner."

The answer exists in the data and nowhere else, across hundreds of rows. You could not paste enough of the file into a chat to answer honestly. The tell: a file already holds the right answer, and the job is to get it out.

The trap case. "Draft the renewal email for our largest at-risk account" looks like conversation work because the output is prose. Wrong axis. The question is not whether the output is words, it is whether the inputs are in files. This email is only worth sending if it names the right renewal date, amount, stakeholder and the thing that went wrong, and all four sit in records: accounts.renewal_date, the open opportunity amount, contacts.persona, and a support ticket history. A chat draft will be fluent and generic, and you will spend longer fixing its facts than writing it yourself.

The real conversation-shaped task hiding next to it is "what is our position going into this renewal". Keep that a conversation. Drafting the email that carries the position is file work. And note: the email is draft-only, not read-only, because a human sends it. Lesson 3 makes that distinction properly.

What you keep

cowork-fit-log.md, columns 1 and 2 filled, in your own folder rather than a shipped course folder. Lesson 3 adds three columns. Module 3 re-scores the whole thing with the five-factor fit test.

Check yourself

  1. Take the highest-minute task on your log. Name the file, export or system that holds the right answer for it. If you cannot name one, say what that tells you about handing it over.
  2. One of your tasks probably has an output that is prose but inputs that are records. Which one, and which column of your log did you nearly put it in?
  3. You have a run going that is producing the wrong grouping. Was the cheaper fix available before or during? Say what the sentence would have been.
Answers

Items marked Open run on your own list and have no key.

1. Open, and the checkable part is what a blank means. If you cannot name a file, export or system, Checkability is low, and Module 3 makes that a veto: you would be handing over work whose correctness you cannot test.

2. Open. The usual case is a drafting task: prose output, record inputs. If yours went into the conversation column, re-read the trap case above.

3. Before. Grouping is scope, and scope is the cheapest thing to fix in the brief: "group by region, not by country". Correcting during the run buys you this output. Putting it in the brief buys you this output and next week's.

Where this goes next

Next lesson: you run one, on data you did not have to prepare, and get a real file out of it.

Track labs: every track lab starts from a row on this fit log, so a thin log makes for thin labs. Part B of the exercise sheet in labs/LAB-01 of your practice pack (start with its README) is the full build.