SiSu RevOps

M1  /  L1.2  /  about 15 minutes

Your first end-to-end run

An account executive drops into your Slack at 09:12: "Can you pull me everything on Vireo before the 11 o'clock?" You know what that means: open the account record, work out which opportunity rows are still live, find the last touches, notice the amount is in pounds while the ARR field is in dollars. Twenty minutes of clicking, and again on Thursday. Do it once, properly, on shipped data, so you have seen the whole loop before anyone asks you to trust it. This lesson is read-only: nothing writes outside the output folder you create.

What you will be able to do

  • Point a working session at a folder and get back a file, not a chat reply.
  • Describe what happened in terms of the task loop, not clicks.
  • Read your own output for the thing that matters most: what it did not know.

Choose the folder on purpose

Before the brief, you choose a folder. Most people make this choice by accident.

The shipped dataset lives in the data/ folder of your practice pack, the zip you downloaded from the course page and unzipped into your course folder. The pack root around it holds the templates, the labs and the answer keys. Point at data/, not the pack root: Claude cannot read or write outside the directories you explicitly grant, so everything inside the folder is in scope, including files you forgot were there. Copy the folder somewhere of your own first; nothing here modifies a file, but the habit is free.

Check yourself: which folder did you grant, and what is one thing in the parent that you did not?

Write the brief, then run it

Try this now Type this brief exactly. Do not paraphrase. Module 4 explains why it looks like this. For now, notice that it names files, names an output, and says what to do about things it cannot answer.

Read accounts.csv, contacts.csv, opportunities.csv and activities.csv in this folder.

Produce a one-page snapshot of the account named "Vireo Retail PLC" and write it to
first-run/account-snapshot.md.

Sections, in this order:
1. Who they are: segment, industry, employee count, country, region, owner, CSM,
   customer since, ARR in USD, billing currency, health score, renewal date, tier.
2. Open opportunities: for each one, opportunity id, name, stage, amount with its
   currency, type, expected close date, forecast category, days in stage, next step.
3. Closed history: one line per closed opportunity, oldest first.
4. Contacts: name, title, persona, last activity date.
5. Last three activities: date, type, subject, owner, outcome.
6. What the data does not tell you: anything a person would want before this call
   that is not in these four files. Be specific about which field is missing or
   ambiguous.

Do not infer anything that is not in the files. If a field is blank, say it is blank
rather than filling it in.

If it answers in the chat instead of writing the file, say: "Write it to first-run/account-snapshot.md in this folder and confirm the file exists."

Check yourself: what are three things in that brief that a one-line request would not have carried?

Read what came back

Do not read the output for whether it sounds right. Read it for four things, in order.

  1. Did it use all four files? Section 5 is the tell. If activities are missing, it answered from one file and stopped.
  2. Does anything reconcile? accounts.arr_usd is 121920.0 and the open renewal is 96000.0 GBP. The build rate is GBP = 1.27 USD (DATA-DICTIONARY.md, in your pack's data folder, Conventions section), and 96,000 times 1.27 is exactly 121,920. Two numbers from two files agreeing is the cheapest evidence you will ever get.
  3. Did it invent anything? Scan section 1 against accounts.csv field by field. It is one row.
  4. Is section 6 real? A "what the data does not tell you" section that says "nothing" is a failed section, and on this account it is provably failed.

What our run looked like

Yours will differ in wording and section order. That is why the course ships reference artifacts, not answer keys.

What it got right. Section 1 matched accounts.csv row ACC-02858 field for field: Mid-Market, Retail, 538 employees, United Kingdom, EMEA, owner Bettina Farrow, CSM Niamh Ricci, ARR 121,920 USD, currency GBP, health score 36, renewal 2026-09-17, Tier 2. Section 2 found one open opportunity, OPP-006874, Renewal 2026, Negotiation, 96,000 GBP, close date 2026-09-17, Best Case, 42 days in stage, next step "Chase signed order form, sponsor left".

The dangerous number. The output said probability 85. We did not ask for it. DATA-DICTIONARY.md defines opportunities.probability as the stage default: not the rep's call, not evidence about this deal. An 85 on a slide is a forecast claim; here it is a lookup table. We struck it and wrote the reason into section 6.

What section 6 should contain. Three things this data cannot tell you:

  • The economic buyer may not be there. contacts.csv lists Wouter Nyberg, Chief Operating Officer, persona Economic Buyer, last activity 2026-05-08. No field says whether a person still works there. The absence is the finding, and the folder holds a call note that speaks to it.
  • The renewal is in GBP, the ARR field is in USD. Sum this account into a regional total without converting and you have a wrong number. Converting is the analyst's job, per the data dictionary.
  • Health score 36 has no definition in the data. A number with no rule behind it.

What we did not ask, on purpose: whether the deal will close. No file holds the answer, so the output would have been fluent and unfounded. Module 3 turns that judgment into an instrument.

Now you try: Oldcastle Leisure Inc

You are covering for a colleague. The CS lead wants the same snapshot for Oldcastle Leisure Inc, a Mid-Market hospitality customer, before a call this afternoon. Same four files (accounts.csv, contacts.csv, opportunities.csv, activities.csv), different account, on purpose: you are running a loop, not reproducing an answer. Grant your copy of the pack's data/ folder. No connectors. Read-only: the only file written is your output.

Try this now

  1. Grant the folder. Say out loud what is in its parent that you did not grant.
  2. Fill the four gaps in the starter brief below, then run it.
  3. Do not correct it mid-run, even if it goes somewhere odd. Let it finish, so you see what an unassisted run produces.
  4. Run the four checks, in order.
  5. Add one sentence at the bottom: the thing you would not put in front of the customer without checking, and why.
Read accounts.csv, contacts.csv, opportunities.csv and activities.csv in this folder.

Produce a one-page snapshot of the account named "Oldcastle Leisure Inc" and write it
to first-run/oldcastle-snapshot.md.

Sections:
1. Who they are: <<GAP 1: list the exact account fields you want, by column name>>
2. Opportunity history: every opportunity on this account, oldest first, with
   opportunity id, name, type, stage, amount, currency and close date.
   <<GAP 2: state what to do if the same opportunity id appears on more than one row>>
3. Contacts: name, title, persona, last activity date.
4. Last three activities: date, type, subject, owner, outcome.
5. What the data does not tell you: <<GAP 3: say what counts as a good answer here,
   so it does not write "nothing">>

Constraints: <<GAP 4: one line telling it what not to infer>>

Stuck? Take the hints in order.

  1. The gap that matters most is not formatting. This account's opportunity history has a shape problem; a snapshot that adds up the amounts without noticing prints a number no system in the company holds. What do a row count and an identifier count each tell you?
  2. Count two things in opportunities.csv for account_id = ACC-02848: rows, and distinct opportunity_id values. Compare your total against accounts.arr_usd. Write the instruction that makes the agent do the same comparison.
  3. GAP 2: report the duplicate identifier rather than silently picking a row, count each opportunity once, and never add a Renewal amount to a New Business amount (renewal amounts restate current ARR, per the data dictionary). GAP 3: name at least two classes of unknown, such as a field with no definition, and a fact a person on the call would ask about that no column carries.

What a correct run finds (templates/M4/ in your practice pack carries the mature version of this brief). The checkable parts, read from the shipped files:

  • Account. ACC-02848, Oldcastle Leisure Inc, Mid-Market, Hospitality, 302 employees, United States, NA, owner Ursula Ulrich, CSM Helena Zabala, contract start 2023-10-19, ARR 55,000 USD, currency USD, health score 37, renewal date 2026-10-19, Tier 2, Customer.
  • Opportunity history. Four rows, three opportunities. OPP-007468 New Business 55,000 USD Closed Won 2023-10-19. OPP-007132 Renewal 2024, 55,000 USD, Closed Won 2024-10-19. OPP-007099 Renewal 2025, appearing twice, at 69,000 USD with close date 2025-10-19 and at 55,000 USD with a blank close date. Both are documented in answer-keys/PLANTED-ISSUES.md in your pack, which you open only after attempting the lab, under the classes duplicate-opportunity-rows and missing-values.
  • Contacts. Three: Ulrich Steenkamp (Payroll Analyst, End User), Fabian Nyberg (Chief Information Officer, Economic Buyer), Tobias Lombardi (Director of IT, Champion).
  • A correct "what the data does not tell you" contains at least: OPP-007099 has two conflicting amounts and the file does not say which is right; no renewal opportunity exists for the 2026-10-19 renewal date; health score 37 has no stated definition.

Section order, table versus prose, and wording may all legitimately differ. What may not: an output that prints a single total without mentioning that one opportunity id appears twice is wrong, however good the rest looks.

Worth knowing: four rows, three opportunities, one duplicate missing its close date. The arithmetic that goes wrong first is not the hard arithmetic. It is counting.

What you keep

first-run/account-snapshot.md and first-run/oldcastle-snapshot.md, in your own folder. Keep them even though they are rough: Module 4 regenerates the same snapshot from a written brief and diffs the two. You cannot make that comparison later if you delete the before picture now.

Check yourself

  1. Your run produced a total for Oldcastle Leisure. Name the two source-of-truth comparisons that would tell you whether it is right, and say which file each one lives in.
  2. The demo struck the probability field from the Vireo snapshot. Give the reason in one sentence that does not use the word "wrong".
  3. You granted the pack's data/ folder. If your own CRM export had been sitting in that folder, what would have changed about this run? Answer in terms of what the agent could reach, not what it was told.
Answers

1. Row count against distinct opportunity_id count, both from opportunities.csv: four against three. Sum of Closed Won New Business and Expansion amounts against accounts.arr_usd, in accounts.csv: 55,000 against 55,000. The second only works because it names which types go in, since Renewal amounts restate current ARR rather than adding to it.

2. Because opportunities.probability is the stage default: a property of the stage, not evidence about this deal. It would read the same on any opportunity in Negotiation.

3. Nothing about what it was told, everything about what it could reach. The export would have been inside the granted directory, so in scope for every request in the session, including ones where you had forgotten it was there. Nothing would have warned you.

Where this goes next

Next lesson: you close this session, open a new one, and ask for the same thing on another account. What happens is the most important limit in the product.

Track labs: Part A of the exercise sheet in labs/LAB-01 of your practice pack (start with its README) is this run at full scope, with a measured baseline.