Operating
Walkthrough: weekly pipeline review
One recurring job, end to end: the request, the automation settings, how the run works, and what the reviewer receives.
The request
Every Monday at 07:00, review the pipeline in the CRM. Flag deals with no next step, a close date in the past, or an owner who has left. Correct what the playbook allows, hold anything that needs a judgment call, and post a summary to #revops with the record links attached. Treat the CRM as the system of record. Ask before changing a close date on anything above $50k.
Automation settings
| Setting | Value |
|---|---|
| Trigger | Schedule, weekly, Monday 07:00, local time |
| Mode | Fresh run, because each week is independent |
| Operating package | Pipeline review: the Skill, the CRM connection, the hygiene rules, the checks |
| Tools | CRM read and write, Slack post to one channel |
| Limits | One invocation per week, with a compute ceiling |
| Identity | The RevOps service identity |
| Review owner | The RevOps lead, who receives exceptions |
| Evidence required | Read-back on every write before the invocation reports success |
How the run works
- 01Read the pipelinePull open deals with the fields the hygiene rules depend on.
- 02Classify against the rulesMissing next step, stale close date, departed owner, or clean.
- 03Correct what the playbook allowsThe changes the package explicitly authorizes, one record at a time.
- 04Read each record backConfirm the write landed before counting it as done.
- 05Hold the judgment callsAnything above the threshold stops and becomes a question.
- 06Post the summaryTo the named channel, with links into the records that changed.
What the reviewer receives
- The artifact: a summary in the channel, with links into the records that changed.
- The evidence: what was read, what was written, and a read-back confirming each write landed.
- The exceptions: the deals the run declined to touch, and why each one needs a person.
- The activity record: whether the invocation ran or was skipped, and any error.
The run stops before the consequential action rather than after it. A close date above the stated threshold comes back as a question, not as a change you discover later.