Solutions / Use case

Revenue operations automation, from campaign to commission.

Marketing, sales and finance each run their own systems, and revenue operations sits in the gaps between them. When those systems don't talk, audiences go stale, deals drift and the forecast gets rebuilt in a spreadsheet. Tray.ai connects every handoff, so the data moves on its own and RevOps spends the week on the rules.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.
Jump to the stages
One deal moving through revenue operations: a lead who attended a webinar in Marketo becomes an opportunity in Salesforce, the call's next step is logged from Gong, a 12% discount is approved in Slack, the deal is in the forecast snapshot in Snowflake, it closes won in Salesforce, and the revenue is credited back to the webinar in Marketo.

The short answer

What is revenue operations automation?

Revenue operations (RevOps) automation is the work of keeping marketing, sales and finance running on the same data: syncing the CRM and the marketing platform, feeding ad audiences, getting calls into the deal record, keeping the pipeline current, approving discounts, snapshotting the forecast, crediting revenue to campaigns and paying commission. It runs across CRM, marketing automation, ad platforms, call recording, the warehouse and payroll, and most of the manual work happens in the handoff between two of them.

  1. 1 CRM and MAP
  2. 2 Ad audiences
  3. 3 Calls to CRM
  4. 4 Pipeline hygiene
  5. 5 Deal desk
  6. 6 Forecast
  7. 7 Attribution
  8. 8 Commission
more campaigns managed per FTE at Wavo
69%
less manual reporting at Wavo
50%
a month of sales ops time saved on commission calculations at Finance Leader
~10 hrs
to build Abridge's custom call sync into Salesforce
1–2 weeks

The revenue operations process, stage by stage

Eight stages, each with what breaks and a how-to guide for building it.

  1. 1

    CRM and marketing platform sync

    People, accounts and lifecycle stages match in the CRM and the marketing platform, with one system in charge of each field.

    Where it breaks: Both systems update the same field every night, and neither team trusts the other's numbers.

  2. 2

    Ad audiences from the CRM

    Ad audiences are built from the live CRM, with customers and open deals left out before anything is uploaded.

    Where it breaks: Paying to show acquisition ads to a customer in the middle of a renewal.

  3. 3

    Calls into the deal record

    Next steps and attendees from each call are written to the deal, and anything commercial waits for the rep.

    Where it breaks: The call was recorded and analysed, and the deal still shows whatever the rep typed afterwards.

  4. 4

    Pipeline hygiene

    Stale deals are found by stage and size, and each owner is asked to fix their own, with a link to the record.

    Where it breaks: A weekly report of dirty deals that has been emailed for a year without the numbers changing.

  5. 5

    Deal desk approvals

    Discounts and non-standard terms go to the right approver in Slack, and the quote can only go out at the approved terms.

    Where it breaks: The approval sits in a manager's inbox and the quote goes out anyway, at a bigger discount.

  6. 6

    Forecast snapshots

    The pipeline and every forecast call are copied to the warehouse each week and never edited, so any week compares with any other.

    Where it breaks: Nobody can say what the forecast was three weeks ago, or which deals moved since.

  7. 7

    Campaign attribution

    Touches are tied to the account and the deal, joined to real ad spend, and reported in more than one model.

    Where it breaks: Attribution rebuilt in a spreadsheet every quarter, and disputed every quarter by someone with a different model.

  8. 8

    Commission and payroll

    Closed deals are checked against the plan, each line shows how it was worked out, and the total is reconciled before payroll.

    Where it breaks: A rep queries a statement and it takes two days and a spreadsheet to answer.

Three ways to connect the revenue stack

  • Built-in syncs. The CRM and the marketing platform ship a connector for each other. It covers that one pair, with the field rules it was built with, and nothing past it.
  • Custom code. Full control, and your team owns the fixes, changes and monitoring for as long as it runs.
  • An integration platform. Every handoff in one place, with the same error handling, logging and access control. This is Tray.ai: RevOps builds the workflows and owns the rules, IT governs them.

Three neighbouring processes have pages of their own: lead routing, order-to-cash and Customer 360.

The Tray.ai platform behind it

Tray.ai is the enterprise orchestration platform for data and AI. These are the parts of it that run revenue operations automation.

Intelligent Integration

The iPaaS built for the AI era.

Merlin Agent Builder

Build AI agents that act, not just chat.

iPaaS Governance

AI governance built in, not bolted together.

The metrics revenue operations automation moves

What RevOps, marketing and sales leaders measure, and which stage each number depends on.

Records out of sync
People or accounts whose key fields differ between the CRM and the marketing platform.
What moves it Deciding which system owns each field, and syncing only what changed. How to build a CRM to marketing automation sync 
Cost per opportunity
Ad spend divided by the opportunities it sourced.
What moves it Audiences that leave out customers and open deals, refreshed at least daily. How to build an ad audience sync 
Stale pipeline value
Value of open deals with a past close date, no next step or no recent activity.
What moves it Owners asked about their own deals each week, with the specific field to fix. How to build pipeline hygiene automation 
Time to approve a discount
Hours from a rep's request to the approver's decision.
What moves it Requests sent to the approver in Slack with the deal in view, and moved up when nobody answers. How to build deal desk approvals 
Forecast accuracy
Each rep's and manager's commit compared with what actually closed.
What moves it Weekly snapshots of the pipeline and the call, kept unchanged and scored at period end. How to build a forecast snapshot sync 
Pipeline by campaign
Opportunity value credited to each campaign, in each attribution model.
What moves it Touches tied to the account and joined to real spend, reconciled to the pipeline finance reports. How to build a campaign attribution pipeline 
Commission disputes
Statement lines queried by reps each period.
What moves it Statements that show the working on every line, issued before payroll runs. How to build a commission data to payroll sync 

Revenue operations connectors

The systems revenue operations runs on, grouped by the seat each one fills. Each links to its connector page.

CRM

Where the account, the deal and the forecast live.

Marketing automation

Where campaigns run, leads are nurtured and engagement is recorded.

Advertising and analytics

Where audiences are targeted, spend is recorded and web activity is tracked.

Sales engagement and calls

Where reps run sequences, hold meetings and record calls.

Quotes and approvals

Where the quote is built and the contract is signed.

Compensation and payroll

Where commission is paid and the general ledger is kept.

Data and reporting

Where snapshots, attribution and history are kept and reported.

Collaboration

Where approvals, nudges and alerts reach people.

Connections between them

Field mapping, templates and common problems for the pairings revenue operations automation depends on.

Anything not listed connects through the full connector library, or directly through its API.

Teams running revenue operations automation on Tray.ai

“Tray has allowed us to operationalize AI faster than any other company we are competing with.”

— Brendan Neal, VP Revenue Operations, Wavo

Processes next to revenue operations

These share systems and data with revenue operations without being stages of it.

Revenue operations

How to build lead routing that assigns in seconds

Match the lead to an account first, evaluate rules in a fixed order, catch what they miss, and time it from arrival. The Headless prompts that build it.

Revenue operations

How to build a sales engagement to CRM sync

Log activity without flooding the timeline, suppress sequences on the accounts you must not touch, and keep one definition of engagement. The prompts that build it.

Revenue operations

How to build a territory and quota sync

Apply a plan on its effective date, keep in-flight deals with their owner, and make coverage visible before anybody signs off. The prompts that build it.

Revenue operations

How to build partner deal registration

Check submissions against pipeline in seconds, protect for a fixed window, expire visibly, and settle conflicts with a rule rather than an argument. The prompts.

Revenue operations

How to build an order-to-cash integration

Closed-won to sales order to invoice to cash applied, as a CRM to ERP integration. Retries that never create a second order, a reconciliation loop, and the Headless prompts that build it.

Data operations

How to build a CRM to warehouse sync

Capture history instead of current state, handle deletes and field changes, land raw then model, and prove the row counts. The Headless prompts that build it.

Data operations

How to build a customer 360 and master data sync

Pick a survivorship order per attribute, resolve identity on more than email, and publish a golden record every system can point at. The prompts.

Reading and resources

Assessment

Which of your automations breaks first?

Four questions about each RevOps process your team has automated. Get a ranked list of which one is most likely to stop working, and why.

From the blog

BlogCRM data hygiene: why your funnel numbers describe your dataBlogDrive sales-marketing alignment by sharing sales winsBlogSteal this custom Salesforce SyncBlogThe practical guide to building the perfect tech stack for RevOpsBlogThe ultimate guide to hiring a RevOps ManagerBlogBreaking down the critical steps of the sales cycleBlogGetting started with RevOps: A Beginner’s GuideBlogCRM and marketing automation sync: who's right?BlogAd audience sync: stop advertising to customersBlogConversation intelligence: alerts and CRM syncBlogDeal desk automation: approvals that stickBlogForecast snapshots: why the number keeps movingBlogMarketing analytics and campaign attributionBlogSales commission automation: who checks the math?

Speaking the same language

Definitions for the terms that come up in this conversation.

Workflow automation

Software that executes a defined sequence of steps automatically — moving data, triggering actions, and routing decisions without manual intervention.

iPaaS

Integration Platform as a Service — a cloud-hosted platform for building, running, and managing integrations between applications.

Frequently asked questions

How is this different from marketing automation?

+

A marketing automation platform such as Marketo or HubSpot sends the emails, scores the leads and records engagement. Revenue operations automation connects that platform to everything around it, so the CRM, the ad platforms, the warehouse and finance see the same people, deals and revenue.

Where do lead routing, order-to-cash and Customer 360 fit?

+

Each has its own page. Lead routing covers a new lead from form fill to the right rep. Order-to-cash covers a closed deal from quote to cash. Customer 360 covers one view of each customer across systems. This page covers what sits between and around them.

Which systems does Tray.ai connect in revenue operations?

+

CRM (Salesforce, HubSpot, Microsoft Dynamics 365), marketing automation (Marketo, Pardot, Eloqua, Salesforce Marketing Cloud, Braze, Iterable), advertising and analytics (LinkedIn Ads, Google Ads, Facebook, Google Analytics, Segment), sales engagement and calls (Gong, Outreach, SalesLoft, Zoom), quotes and approvals (DealHub, DocuSign, PandaDoc), compensation and payroll (Gusto, Workday, ADP, NetSuite), and the warehouse (Snowflake, Google BigQuery, Looker). Anything without a connector connects through its API.

Can RevOps build this without engineering?

+

Yes. GitHub's marketing team built its marketing automation and CRM integration with no engineering effort. At Abridge, a GTM systems engineer built a custom sync from the call recording tool into Salesforce in one to two weeks, and a lean systems team supports more than 500 employees.

Should the automation change deals in the CRM?

+

Only the factual fields, such as next steps, attendees and sync status. Close dates, amounts, stages and forecast categories belong to the rep. The automation flags the problem and asks the owner to fix it, so the forecast stays something people will defend.

Where do AI agents fit in revenue operations?

+

In the work people skip. Agents summarize calls into next steps, research accounts before a meeting, draft the reason for a discount request and explain why a deal slipped between two snapshots. Anything that changes an amount, a date or a forecast goes to a person.

Do we have to replace our CRM or marketing platform?

+

No. Tray.ai connects the systems you already run and carries the data between them. The stages above describe what moves between systems, not which ones you use.

Last reviewed 2 October 2026.

See revenue operations automation running on your stack.

Walk through your systems and stages with a Tray.ai expert.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.
Browse the how-to guides