Revenue operations agent Status: Live

Revenue operations software: how Oliv AI's Oliver keeps every agent on one sales process

How revenue operations software keeps one sales process across your tools: what Oliv AI's Oliver agent holds in the process handbook, how a change gets approved and how every agent then follows it.

| For revenue operations managers and revenue leaders | Verified 3 Nov 2026 | 20 min read

Revenue operations software earns its place when your sales process, qualification rules and handoffs stay consistent without being rebuilt in every tool. Oliv AI's Oliver agent holds all of that in one process handbook, from your ICP and personas to your methodology and approval rules. Every other Oliv AI agent works inside those rules. When the process changes, you tell Oliver in plain language. It proposes the update, waits for your sign-off, then passes it to every agent that depends on it.

At a glance

What the Oliver agent is

Oliv AI's Oliver agent is one of two super agents in Oliv AI. The other is Oliv AI's Olivia agent, who works with reps on deals. Oliver works on the business rather than within it. Every other agent works on deals, contacts and activities, and Oliver owns the rules they all run by.

On Home, Oliver's pill reads Your Chief GTM Engineer. In the agent picker it describes itself in one line: "I learn how your team operates and turn it into the rules every other agent follows."

What the handbook holds

The handbook is a set of structured, interlinked documents. Update the ICP, and the qualifying criteria across agents update with it.

• ICP definition. Who you sell to, and the qualifying signals.
• Persona library. The roles you target and what they care about.
• Sales methodology. MEDDPICC, BANT, SPICED or a custom framework, and the fields each stage requires.
• Approval workflows. When the pricing desk gets involved, and the deal size where manager sign-off starts.
• POC process. What makes a POC eligible, what success looks like and how long it should run.
• Proposal standards. What goes into a proposal, who reviews it and the approval steps.
• Territory and segmentation rules. How pipeline is divided, and who owns what.

The handbook lives in Playbook, pinned at the bottom of the sidebar. A file tree groups markdown files into folders such as Market, Prospecting and Sales, with Search playbook above them. Each file opens on the Edit tab with a rich-text toolbar. A status row shows Synced, the last editor and a word count, and Oliver sits in a panel on the right.

A sample handbook page such as Target Market.md opens with a Winning Zone table, then runs through Priority Segments, Disqualification Signals, Owner Notes, Trigger Events, Agent Behavior, How This Page Gets Used In Practice and Change Log Guidance. Sales Process.md holds a Sales Stages table with win percentages, activities and exit criteria. Sections such as Stage Rules, Deal Risk Flags, Forecast Category Guidance and Deal Driver Alerts follow. The Process Graph shows this playbook as agents read it.

What Oliver writes to

• The company process handbook.
• Platform configuration: agent settings, schema definitions and field mappings.
• Every Olivia conversation, which inherits the handbook context.
• The CRM schema, through the CRM Manager agent, when a process change needs new fields or new mappings.

Why the Oliver agent matters

What it's for

Oliv AI's Oliver agent is for the people who decide how the company sells. It makes your process something every agent reads and follows, instead of a document people forget.

How it helps

• One change, everywhere. A new rule reaches scorecards, tracking fields and agent context together.
• Same rules for every rep. Two reps can't track different data points on the same type of opportunity.
• Drift gets flagged. Deals or activity outside your norms go to a person for review.
• The playbook learns. Oliver spots patterns across deals and drafts the next update for you.
• You stay in charge. Oliver's proposals wait as Pending Review until a person approves them.

What happens without it

The real process lives in training decks and in managers' memories. A new rep needs three to six months to learn it. A new methodology or ICP has to be pushed into six tools by hand, and until that happens every rep runs a different version.

Why buyers care

RevOps leads, VPs of Sales and CROs buy Oliver. RevOps configures and owns the handbook. Sales leaders care most when they change methodology, shift the ICP or reset approval thresholds, because that is when consistency breaks first.

The Oliv AI approach to the Oliver agent

Picture a head of revenue operations leaving a meeting with a new rule. From Monday, an SDR passes a meeting to an AE only when the account fits the target segment and discovery notes are complete. Twelve SDRs and twenty AEs need to follow it.

Teams often handle this with a slide, a Slack post and a few CRM field changes, then a short training session. That work tends to stretch over weeks. Until every tool and scorecard catches up, SDRs and AEs may each be running a slightly different version of the rule.

A handoff rule looks like one decision, but it touches qualification fields, coaching standards, routing and the context a rep reads before a call. Once agents do much of that work, the rule only has to be changed in the place every agent reads from.

Oliv AI puts that place in its Oliver agent. The RevOps head describes the new rule in plain language. Oliver proposes the handbook update and the related field changes, and the proposal waits for a person to approve it. Once approved, the change reaches every agent that depends on it, from the next day forward.

Each proposal opens in Review changes as a line-by-line diff of every file it touches, with its knock-on effects listed under the diff. It waits as Pending Review until someone presses Approve & merge.

Set up the Oliver agent

1. Connect your CRM. Salesforce, HubSpot or Zoho, so Oliver can align with your schema.
2. Gather your process documents. Playbooks, methodology decks and any handbook you already have, even if they are messy or incomplete.
3. Name a RevOps or leadership owner. That person checks the handbook is accurate during onboarding.
4. Populate the first handbook. Oliv AI's onboarding team works with your RevOps lead to translate your playbooks, CRM configuration and methodology into Oliver's structured format. This takes 1 to 2 weeks.
5. Keep it current in one conversation. From then on, tell Oliver what changed and it passes the update to every connected agent.

Choose who runs it

• You Run It. Your RevOps team works with Oliver directly, with full control over every update. Onboarding takes 2 to 4 sessions, with no engineering and no long prompts.
• We Run It. Oliv AI's operators keep your playbooks, scorecards and agent context current for you. You're live in 2 weeks, with no prompts to write.

The RevOps implementation guide walks through the first weeks in more detail.

How a sales process change reaches every tool

Say you tighten the exit rule on one stage. There are three usual ways to get that rule into the tools your team works in, and many rollouts mix them. Each one leaves a different gap.

Announce it: a slide, a Slack post, a training session

You explain the new rule and why it changed, and reps hear it from a person. This builds understanding, which no field setting can do. Its effect ends with the meeting: nothing stops a deal moving on the old rule, and nothing shows you who is still using it.

Enforce it in the CRM: required fields at the stage

You make the rule hard to skip at the moment a deal moves. In HubSpot, for example, a required stage property stops users creating or updating the record until it has a value. This catches a blank field. It misses a field filled in carelessly, and it doesn't reach your scorecards, checklists or decks.

Watch for copies here. HubSpot sets this logic stage by stage inside each pipeline, and cloning a pipeline copies its conditional stage properties. One rule can end up in several pipelines, and each of them needs changing later.

Keep one source every tool reads from

You write the rule once, and whatever enforces it reads that copy. Stale copies stop being a problem, because there is only one to change. A deck or a recorded training doesn't read from the source, so those can still go out of date. This method also spreads a bad change as fast as a good one, so the approval step carries real weight.

Which of these Oliver uses

Oliv AI's Oliver agent works the third way. The handbook is the source, the specialist agents read from it, and a process proposal waits for a person in Review changes. Where a change needs new fields or mappings, the agent writes to the CRM schema through CRM Manager, which covers part of the second way.

The first way stays with you, because telling the team remains a RevOps job. If you're still weighing the wider category, the guide to revenue operations software covers it.

Change your process with Oliver

1. Open Oliver. Choose Oliver in the agent picker on Home, or use its panel beside the Agents marketplace or Playbook. Its saved chats sit in the history panel.
2. Check the autonomy setting. The dropdown under the message box opens on Ask before acting, where Oliver aligns on its approach before taking actions. Act without asking lets it act without asking for permission, and shows a High Risk banner: "Oliver can take action on your settings right now."
3. Ask or tell. The box reads "Ask Oliver anything", followed by data quality, stage accuracy, forecast integrity and pipeline structure. In Playbook, suggestions offer changes such as updating qualification scoring from win/loss patterns.
4. Read the answer. A why question returns a Pipeline Snapshot, then ranked causes. Each cause carries Deals impacted and Value impacted badges and chips for the accounts affected.
5. Find the proposal. A change Oliver proposes appears on the Playbook History tab as Pending Review.
6. Review it. Review changes shows each file as a diff, with removed lines in red and added lines in green. Cards below list the knock-on effects, such as a new CRM field, an agent retrained or deals re-scored.
7. Decide. Press Approve & merge, Request edit or Cancel. Approved changes show as Merged in History.

Specialist agents carry a separate control on each of their tools, covered in agent tools and run modes.

Track every change

The History tab lists every change to the playbook, by your company, by Oliver and by Oliv GTM Engineers. Filters narrow it to All, By Oliver, By Your Company or By Oliv GTM Engineer. Each card shows the date, the author, a status, a summary and the number of files changed.

A status reads Pending Review, Merged or Autonomous. Autonomous marks a minor update Oliver applied on its own, such as syncing an agent prompt to a scorecard, noted as "No human review needed".

Changes Oliver drafts for you

Oliver watches what's winning in the field and drafts the next process update for your review. Its own example: "We've seen 14 POCs extend beyond 30 days without a clear qualification gate. Should we add one?" In the Agent Feed, Oliver posts reviews such as a quarterly revenue review, with playbook and agent changes ready for you to review. It also reports when it has updated process files.

How to measure rollout lag after a process change

A process change isn't finished when it's approved. It's finished when the old rule has gone from the last place it lived. Two measures tell you how close you are, and both count days from the approval date.

• Average lag. Add the days each place took to catch up, then divide by the number of places.
• Longest lag. Count the days until the last place catches up. Until then, two versions of your rule are live.

Both have weak spots. A place you forgot to list never appears, so the numbers look better than they are. Both also count when a copy changed, not whether reps follow it, so spot-check recent deals as well. Read longest lag first, because an average can hide one straggler.

Reading lag against the History tab

Oliv AI's Oliver agent gives you the start of the clock. Use the date on a Merged card in History as day 0. Before you approve, Review changes lists the files a change touches and its knock-on effects, which gives you the Oliv AI side of your list. Keep the count for tools outside Oliv AI in your own sheet, with one row per place.

How to roll out a sales process change by hand

This is the manual method, in the order that causes the least rework. It works with any CRM, and you can run it from a shared sheet.

1. Write the rule as one sentence. Say what must be true before a deal leaves the stage. Gartner's 2019 advice was to measure deal progress by customer verifiers, so prefer something the buyer did over something the rep ticked.
2. List every place the old rule lives. Check CRM stage settings, required fields, the rep playbook, coaching scorecards, deal review checklists, forecast guidance and onboarding decks.
3. Name one owner and a date for each place. A place with no owner is the one that stays out of date.
4. Get sign-off and record day 0. Approve first, because a rule changed before sign-off may have to be changed back everywhere.
5. Change the CRM first. That's where a rep meets the rule, so set the required field in every pipeline that has the stage.
6. Update everything that depends on the stage. Work through scorecards, checklists and guidance. If the stage's meaning changed, recheck its win probability, because HubSpot updates deal probability from that setting when a deal moves stage.
7. Tell the team what changes for them. Say which deals the rule applies to, including deals already in the stage.
8. Spot-check deals that crossed the stage since day 0. Any deal that misses the new rule points you to a place still on the old version.
9. Log the change. Record the date, the approver and the reason, so the next person knows which version is current.

Step 2 is where this usually goes wrong. A deck nobody listed keeps teaching the old rule to every new hire, and nobody notices because nothing fails. The other trap sits between steps 5 and 6, when the CRM enforces the new rule while a manager still coaches against the old one. Reps then get two answers.

The same job with Oliver

Oliv AI's Oliver agent changes the middle of that list, not the start or the end. You still decide the rule and say it in plain language. The agent proposes the update, and Review changes shows each file as a diff, with knock-on effects such as a new CRM field or deals re-scored.

Once you press Approve & merge, Oliver passes the change to every agent that depends on it, from the next day forward. That covers scorecards, tracking fields and agent context, without you touching individual agent settings. History takes the place of the log in step 9.

Step 7 stays yours, and so does anything outside Oliv AI, such as a deck or a recorded training. Keep those places on your list. Oliver also surfaces deals outside your norms for human review, which gives step 8 a starting point.

Worked example: one stage rule in seven places

This is an illustrative calculation with sample figures, not an Oliv AI output. A RevOps lead changes the exit rule for one stage, lists the seven places that rule lives and records the day each one catches up.

An average of 5.3 days looks fine, but the old rule survives for 14 days somewhere. Five places have caught up by day 6, and the last two keep the old rule alive for another 8 days. Chase those two first, because a new hire reading the onboarding deck learns the old rule for two weeks after approval.

How Oliver works with other agents

Oliver doesn't work deals itself. It is the layer every execution agent reads from.

Olivia

Oliv AI's Olivia agent runs the front line inside Oliver's boundaries. Oliver sets the stages, ownership and handoffs, and Olivia operates inside them from day one. The Olivia agent page describes her side of the pair.

Coach

Oliv AI's Coach agent takes its methodology and process standards from Oliver. Every rep is coached against the same current rules.

Deal Driver

Oliv AI's Deal Driver agent grounds its deal alerts in the qualification framework Oliver defines.

CRM Manager and Forecaster

The field definitions Oliver keeps decide what Oliv AI's CRM Manager agent tracks and updates. The methodology Oliver defines feeds Oliv AI's Forecaster agent, so the forecast rests on one qualification standard.

Portfolio Manager and Prospector

Health signals and escalation thresholds for Oliv AI's Portfolio Manager agent come from the same handbook. Territory and segmentation rules keep Oliv AI's Prospector agent on strategy when the ICP shifts.

Who uses Oliver, and how

Revenue operations

RevOps managers own Oliver. They define the handbook and approve the changes Oliver proposes, and one conversation replaces edits across many tools. More on Oliv AI for revenue operations teams.

VPs of Sales and CROs

When the market focus shifts, Oliver realigns every agent to the updated ICP. It runs your methodology across every rep interaction without a training cycle, and flags drift before it shows in pipeline quality. See how sales teams work with Oliv AI.

Heads of customer success

Oliver enforces your health standards across every account and carries each renewal criteria change to your CS agents. It also surfaces retention patterns across your book and drafts policy updates for review. Read more on Oliv AI for customer success.

Enablement leads

Enablement sees the effect through coaching. The Coach agent works from the methodology Oliver keeps current, so the standard reps are trained on matches the one agents enforce. The guide to sales methodology automation covers scoring calls against a framework.

How Oliv AI compares for revenue operations software

Many platforms let an admin set up a sales methodology in settings. Oliver takes a process change in a chat, applies one change to every agent that depends on it, and drafts the next update from patterns across your deals. Oliv AI is the only platform in this table that does all three.

Revenue operations software features, from each platform's public documentation:

Yes: documented and built in. Partly: documented with a limit, shown in brackets. Not in docs: not found in the vendor's public documentation.

Competitor details checked against each vendor's public documentation on 21 October 2026. Features and plans change, so confirm with the vendor before you decide.

Limits and things to know

• It doesn't work deals. Oliver doesn't act on individual opportunities. That is Olivia and the specialist agents.
• It doesn't track the CRM itself. Oliver defines what should be tracked, and CRM Manager does the tracking.
• It isn't a reporting tool. Oliver can answer a why question about your pipeline, and Olivia, Forecaster and Coach bring you cross-deal insight by reading Oliver's structured layer.
• Change management is still yours. Oliver handles the configuration, but telling the team about a change remains a RevOps job.
• Act without asking carries a warning. Only Oliver shows the High Risk banner, because it can change your settings.
• Minor updates can apply on their own. History marks them Autonomous, so read it to see what changed without a review.
• It isn't a one-time setup. The handbook stays accurate only if you keep telling Oliver what changed.

Common questions

Further reading

• Set up and manage object pipelines: how HubSpot sets conditional stage properties and required fields, and what cloning a pipeline copies.
• HubSpot's default deal properties: which deal properties HubSpot updates by itself when a deal changes stage.
• Gartner on the linear sales process: a 2019 press release on measuring deal progress by customer verifiers.

Related

• Oliver on oliv.ai: the agent's own page, with the two set-up paths.
• The Olivia agent docs: the front-line super agent that works inside Oliver's rules.
• Deal Driver agent docs: deal alerts built on Oliver's qualification framework.
• Agent tools and run modes: how approval works for each agent action.
• Prepare for a meeting: the brief that carries your methodology into each call.
• Run deals as an account executive: the rep's day inside the rules Oliver keeps.
• Sales process automation guide: automating each stage of the sales process.
• Scaling revenue operations: keeping process consistent from 25 to 200 reps.
• Oliv AI product documentation: every documented agent and feature.

Updated 3 November 2026: added how a process change reaches every tool, how to measure rollout lag, the manual method and a worked example.