Ask a RevOps lead what they have automated and you will hear about assignment rules, stage-change alerts, and a Slack notification when a deal crosses six figures. All useful. None of it gives a rep back a single hour.
The reason is that these workflows automate the plumbing around the record while leaving the authoring of the record to a human. That authoring step is where the six hours a week live.
Here are the five workflows that actually move the number, in the order we would build them.
1. Post-call field population
The highest-value automation in sales, and the one almost nobody has. After every call, the opportunity's fields — stage, close date, amount, next step, pain, budget authority — should be written from what was said, not from what the rep remembers on Friday.
Build this first because everything downstream depends on it. A forecast model, a health score, and a churn signal are all worthless on top of fields that were guessed.
What good looks like
- Fields written within seconds of the call ending, not queued for review
- Every value traceable to a timestamp, so a manager can verify it in one click
- Custom fields included — the ones your business actually runs on
- Writes reversible and logged, so nobody fears the automation
2. Buying committee construction
Deals are lost to people who were never in the CRM. Someone says "I'll need to run this past our CFO" on call three, and unless the rep types that in, the committee has one contact in it right up until the deal stalls in procurement.
Automate stakeholder detection: when a name and a role are mentioned, create or update the contact, set the role, and link it to the opportunity. Then flag the gap — which roles a deal of this shape usually needs and does not yet have.
3. Next-step enforcement
"Next step" is the single most predictive field in most pipelines and the most consistently empty. It goes stale within days because it is a snapshot of an intention.
Instead of reminding reps to update it, derive it. What was agreed at the end of the call is almost always stated out loud. Capture that, write it, and expire it automatically when its date passes without a meeting.
A required field produces a filled field, not a true one. Deriving beats demanding.
4. Silence detection
Most automation triggers on activity. The more useful signal is its absence. A deal that had three touches a week and now has none for nine days has changed state, and no stage field will tell you.
Build a workflow that watches the gap between the last real exchange and today, weighted by where the deal sits and how it behaved before. Then have it draft the re-engagement rather than just raising an alert — an alert is another task, and the goal is fewer of those.
5. Follow-up drafting
Last, because it depends on the first four. Once the record is accurate and the committee is mapped, the follow-up writes itself: reference the pain they described, answer the objection they raised, address the stakeholder who actually signs.
Keep a human in the loop by default. Draft, do not send. Most teams that eventually enable auto-send do it for meeting confirmations and recaps, and never for anything negotiating.
The order matters
Every one of these depends on the one above it. Teams that start at five — buying an AI email tool while the CRM stays empty — get impressive drafts that reference nothing, and quietly stop using them within a month.
Start where the typing is. The rest becomes easy, and most of it stops needing to be built at all.
The AI Sales Operating System.
Your Phantom listens, understands every conversation, updates your CRM, and tells you exactly what to do next.
Join Waitlist →