Loops for Revenue Operations

Revenue operations already lives between systems. CRM says one Amount. The regional sheet says another. The AE’s message says “slipped.” Monday hygiene is the ritual that tries to list those conflicts before finance signs a number: missing close dates, stages that do not match activity, commit deals with no activity, duplicates. The failure mode is a fluent story that hides the disagreement — or an unattended job that “fixes” stages in bulk before anyone names who wins. McKinsey’s State of AI (2025) finds AI adoption deep in commercial functions while scaling governance lags: hygiene still wins forecast quality, not a better paragraph.

This page is unattended standing-order work, not the shared collaborative room where RevOps, sales, and finance sign a forecast. The standing order runs when the opportunity moves, the sheet lands in the folder, or the calendar says Monday, and it skips when nothing material changed. It produces the artefact the room needs — a conflict list, a hygiene CSV, a skip log — and stops. For the room that resolves conflicts and signs the number, read collaborative AI for revenue operations.

Three nouns get conflated in every vendor deck. Keep them as vocabulary, not as a product menu:

• Eval loop — a sensor that grades a run after the fact. Did the write match the signed payload? See eval loops for enterprise agent harnesses.
• Standing-order loop — a compiled recipe that admits a run when a trigger fires. Trigger, steps, run record, notify. See what is loop engineering and the standing-order loop definition.
• Agentic workflow — an interactive path that still reasons when the route is not fully known. See what is an agentic workflow.

The hygiene and definitional work still wins forecast quality, not better paragraph generation. Automate the hygiene signal. Keep the number on the roster.

What a RevOps standing-order loop is

Three common starts, from six things that start a loop:

1. When the opportunity moves — stage, close date, or Amount changes in CRM against the rule set finance cares about.
2. When the file lands — the regional sheet appears in the shared location with yesterday’s timestamp.
3. When the calendar says Monday — the hygiene list: missing fields, duplicates, commit deals with no activity.

The job is narrow: detect that start, run the saved steps, produce the artefact the room needs, and stop. It does not resolve conflicts. Resolution has a name on the collaborative job. A loop is not an agent: the standing order does not negotiate with sales. It runs the recipe or skips.

Deterministic triggers matter more here than model routing. If the start condition is fuzzy, you will run every Monday even when nothing moved — or miss the week the sheet arrived on Tuesday. Prefer sensors you can explain to finance: field delta, file mtime, calendar with a timezone.

Skip when nothing changed. That skip is a first-class outcome. A loop that always produces a narrative trains people to ignore it. A loop that writes “skipped: no delta since last run” is evidence you are not burning tokens for theatre.

Compare loop vs workflow vs agent: the standing order is the deployed, unattended instance; the collaborative forecast is the human-stopped workflow; an agent is the reasoning actor for unknown branches. Loop vs RPA is the cousin when someone still wants a bot to click the CRM screen.

Why RevOps should care

Because the conflict is the work, and unattended listing is the part worth automating.

RevOps already pays a reinterpretation tax every week. Someone re-exports. Someone else filters a different region. Audit — or just next quarter’s new hire — asks what ran last Monday and the answer is “ask Sarah.” A personal script, a fragile Zap, or a heroic analyst export can produce a list. They rarely produce a skip log, a recipe version, and a run record the controller would recognise.

The failure mode for automation is picking the fluent story. The model summarises “pipeline is healthy” while Amount still disagrees with the sheet. Or the automation writes stages in bulk because the demo looked tidy. The collaborative room exists so resolution stays human and signed. The standing order exists so detection and listing do not depend on someone remembering to export.

You should care if:

• Monday hygiene already happens in a personal script, a Zap, or an export nobody can replay
• Amount disagrees with the board pack and nobody can tell what ran last week
• “CRM fixes” still happen in side chats after the list exists
• finance opens the meeting by asking whether the sheet arrived

What is collaborative AI remains the definition for the room. This page is only the standing order beside it. How to evaluate loop engineering is the buying sheet: triggers, skip logs, and replay matter more than eloquence.

Words you will hear

• Trigger. What admits a run: field change, file landing, Monday calendar, manual start.
• Compiled recipe. The fixed steps for this hygiene job. Not “fix pipeline.”
• Skip. A deliberate halt when nothing changed or preconditions failed. Recorded, not hidden.
• Run record. What ran, on which scope, with which recipe version, what was produced or skipped.
• Write-back. A CRM field change. Default off for the standing order.
• Eval loop. The sensor after a signed write: read-back Amount matches the payload.
• Agentic workflow. Open-ended replan — “make pipeline healthy” with no saved recipe.

Do not collapse those last two with the standing order because a slide said “agentic loops.” Ask what starts the run, what is compiled, and what grades the finish.

How to compile one RevOps standing order

Start from a job people already run without the model.

Example: Monday hygiene for Region West

Trigger: Monday 07:00 Europe/London or manual “run hygiene.”

Preconditions: read-only CRM connection scoped to West pipeline; last-run timestamp stored.

Steps:

1. Query opportunities missing close date, stage inconsistent with last activity, Amount null.
2. Compare to last run’s id set. If identical, skip and log.
3. If delta, write the hygiene list and attach a CSV.
4. Notify the RevOps roster — not the whole company.

Explicit non-goals: no stage writes; no customer email; no forecast number.

When a row needs a CRM write, open or update the collaborative forecast job for that week. The standing order may attach the hygiene list there. Finance still signs the number in the room. Write-back governance applies to the write, not to the read-only list.

A second common compile: when Amount moves. Trigger on field delta against finance’s rule set. Produce a conflict row with both CRM and sheet values if the sheet trigger also fired. Do not average them. Do not pick the fluent story. List both. Name who wins on the collaborative job.

RBAC for enterprise AI belongs here: the standing order runs with read grants. It does not inherit a human’s write token.

What “done” looks like

A good RevOps standing-order week:

• The hygiene list exists only if something changed — or a skip log says why not.
• Conflicts are visible with both CRM and sheet values when the sheet trigger fired.
• No CRM field changed without a collaborative sign.
• A new team member can open last Monday’s run and reconstruct what ran without asking the hero who “owns the script.”

The signed forecast still lives on the collaborative job: number, definition, signer, accepted conflicts. The standing order feeds that job. It does not replace it.

Measure: Did finance open the list before the forecast meeting? Did side-chat “CRM fixes” fall? If not, you built another report. Keep a run-log habit the controller would recognise: trigger type, scope, row counts, skip reason, recipe version. When board week goes wrong, you want to open 14 September’s run — not Slack.

That log is also the bridge to eval loops on the write path: the list is feed-forward; the read-back after sign is the oracle. Do not collapse them because both contain the word “loop.”

How to start with one trigger

Pick one start from six things that start a loop. File lands is often easiest — the sheet already has a ritual.

Four weeks:

1. Read-only CRM plus folder watch for one region’s sheet.
2. A conflict or hygiene list with skip when unchanged.
3. Outputs on a run record, not in email only.
4. No CRM writes from the standing order — zero.

Collaborative AI for finance and planning may consume the same hygiene output when pipeline disputes affect the number finance signs. Loops for finance and planning and loops for legal and compliance are the sibling patterns when the trigger is a close pack or a policy file.

If you are still naming the object, what is loop engineering is the discipline and how to evaluate loop engineering is how you refuse a vendor that cannot skip. A loop is not an agent is why hygiene should not invent a stage change.

Unattended work should be boring: same recipe, honest skip, a run record audit trail. Leave the forecast number to the room where someone signs.

How this shows up in Nimbus

Nimbus workstreams can host the standing-order loop and the collaborative forecast room side by side: trigger, compiled recipe, run page, roster notification — and a separate job where finance signs the number. Governance stays on the CRM write, not on the read-only hygiene list.

What is a Nimbus Loop is the product noun for the standing order. Score it with how to evaluate loop engineering before you let it touch stages.