A lead is qualified, but nobody follows up. Sales and marketing count different opportunities. A workflow reassigns an account that already has an owner. These are RevOps problems: the system does not reliably connect a business decision to the next person’s work.
I start by choosing one revenue process and following it from the original signal to its outcome. That shows where definitions, ownership and evidence stop lining up. The aim is to make the process dependable before expanding it.
1. Agree the definitions behind the numbers
Take “qualified lead.” Is it a person, a company or an active buying project? Does qualification expire? Can an existing customer qualify for another product? Different answers lead to different records and conversion rates.
Write down the definition, the properties supporting it and the reporting population. Then ask sales and marketing to apply it to the same sample. Disagreement here is useful: it identifies a decision the CRM cannot make on its own.
2. Define the handoff as a commitment
A handoff needs an entry event, a receiving owner, a response expectation and an exception path. A notification alone does not establish that somebody accepted the work.
- Trigger: what event makes the record ready?
- Context: what must the next person know?
- Acceptance: how does the receiving team acknowledge responsibility?
- Exception: what happens when territory, qualification or ownership is missing?
- Feedback: how does a rejected or recycled lead return to the right process?
3. Separate historical milestones from current work
A contact’s lifecycle, the status of a sales follow-up and the stage of a deal answer different questions. Do not use one field for all three. A customer can have a new opportunity; a previously qualified person can be inactive today.
Preserve the history needed for reporting and record current operational status separately. Agree which process can update each property and how conflicting updates are handled.
4. Review exceptions on a regular cadence
Use a small weekly review to examine unassigned work, missed handoffs, stalled deals and disputed reporting records. Give each issue an owner and a next action. Monthly, review whether the underlying definitions or workflows need to change.
A useful dashboard supports a decision. For handoff speed, record the start and end events, business-hours treatment and excluded records. Reconcile a sample with the people doing the work before trusting the trend.
A starting sequence
- Map: follow one process across marketing, sales and service; collect representative exceptions.
- Decide: agree definitions, responsibility and the fields that carry the handoff.
- Implement: configure the smallest useful change and test the normal and exception paths.
- Review: compare the evidence with the acceptance criteria, train the team and assign ongoing ownership.
The pace depends on the number of teams and dependencies. Completion means the process works for its users and its exceptions are visible, not that a fixed number of days has passed.
Worked example: a lead-routing decision
Consider a team routing qualified leads across countries. The following example is illustrative: it shows how to turn an operating requirement into a testable rule before building a workflow.
| Decision | Operating rule | Acceptance check |
|---|---|---|
| Qualification | Route only when the agreed lifecycle conditions are met. | An unqualified contact is not assigned by this workflow. |
| Country | Use the validated country property. Missing values go to an exception queue. | A lead without country gets an exception owner, not a guessed territory. |
| Ownership | Use the published territory mapping. Preserve an existing owner unless reassignment is approved. | Re-enrollment does not silently overwrite an active owner. |
| Reporting | Measure qualified records awaiting assignment over a defined time window. | The report agrees with a manually checked sample. |
This turns a routing requirement into something the team can implement, test and maintain. Keep the decision owner and acceptance checks alongside the workflow.
Download the workflow brief template ↓Continue with the part you need
- Define reporting metrics teams can reconcile
- Run a useful pipeline review
- Decide what to standardize across countries
Find where the handoff breaks.
A HubSpot & RevOps audit connects the data, workflows and reporting to the way your team actually operates.
Explore the audit →