Skip to content
Use caseSellingIntermediate

Stop chasing reps for the same three fields

Write your process as rules something evaluates every day, and let the exceptions come to the person who can fix them.

RRRevTech RevOpsRevenue operations team 3 minUpdated

The job

“I want to get the process followed without personally chasing anybody.”

  • RevOps
  • Sales managers

Process documents do not enforce anything. They are read once during onboarding and thereafter serve as the thing a manager points at during a difficult conversation. Between those two moments the process is whatever people remember of it, which varies by team, by tenure and by how busy the quarter is.

The alternative is not more chasing. It is writing the parts of the process that can be evaluated as conditions, so the exception finds the person who can fix it on the day it happens, rather than being discovered in a quarterly clean-up when the record is too old for anybody to remember what was true.

What it moves

  • CRM data completeness
  • Stale opportunity rate
  • Workflow exception volume

The division of labour

What RevTech does, and where you decide

Agent workEvaluates the rules you authored on a schedule, and raises what matched to the roles you chose
Human gateA person resolves every finding — the rule engine never edits a record
Workflow KPICRM data completeness

In the product

How to do it

  1. Step 1 of 5

    Write rules, not policies

    Rules live under AI Agents → Sales Process. A rule is a condition something can evaluate against a record: this field, this comparison, this value, on Deals or Accounts or Contacts. "Keep the pipeline clean" is not a rule. "A deal in Negotiation with no next step scheduled for more than ten days" is.

  2. Step 2 of 5

    Choose the severity, which chooses the lane

    Severity is a budget rather than a label. Critical, Attention and Low map onto the Critical, High and Low lanes of everybody’s queue, so marking everything critical does not raise urgency, it removes the meaning of the word.

  3. Step 3 of 5

    Name who receives it

    Every rule requires an explicit choice of which roles receive what it finds, drawn from your own role catalogue. An empty selection is never read as "everyone" — a rule with nobody on it says it needs setup rather than quietly broadcasting.

  4. Step 4 of 5

    Read the rules as a report

    Every rule you write becomes a row in Pipeline Hygiene, under Reporting: its open matches at its last run, coloured by severity, with cards for open matches, critical matches, rules with matches and active rules. Select a bar to open that rule in Sales Process. It is the one place to see which parts of the process are being followed and which are not, without asking anybody.

    Pipeline Hygiene report: open matches against each Sales Process SLA rule, such as next step, activity logging and multithreading.
    The Pipeline Hygiene report. Each of the workspace’s Sales Process rules is listed with the number of open records currently matching it, so RevOps can see which standard is slipping most. Sample data. Screenshot of the RevTech application; sample data.
    Pipeline Hygiene: open matches for each Sales Process rule, largest first. Demo data.
  5. Step 5 of 5

    Measure the backlog, not the breaches

    The count of findings goes up when you add a rule and down when you switch one off, which makes it useless as a measure of health. What tells you the system is working is whether the open matches on the rules you kept are shrinking week on week.

    RevTech: The rule editor defines the object, description and conditions for a stalled-opportunity rule.
    The rule editor defines the object, description and conditions for a stalled-opportunity rule. Captured from the current application with illustrative sample data. Screenshot of the RevTech application; sample data.
    A rule, and the evidence for what it matched. The author’s own wording travels with the finding.

What arrives

What this puts in your Action Center

ItemWhat is preparedHow it resolves
ComplianceThe issue and a suggested fix, from a rule your organisation authoredThe flagged record
Data · NewObjectEnrichment candidates for a missing required field, or a summary of a new record to confirmThe record

Where this is today

Pipeline Hygiene shows how many records each rule matched, not which ones; the records reach the people each rule notifies as Action Center cards. Opening the report needs both pipeline access and access to the Sales Agent’s rules.

What to take away

  • If it cannot be evaluated against a record, it is a policy, not a rule.
  • Severity is a budget. Everything critical means nothing is.
  • Recipients are an explicit choice; an empty one is never read as everyone.
  • Backlog trend is the health measure. Breach count moves when you change the rules.
  • Pipeline Hygiene turns your rules into a report: open matches by rule, every week.
Demo

See how the work gets done.

Explore how agents prepare work across your revenue teams, and how people review it, guide it and decide what happens next. Fictional data. Real product.

Explore the demo