← Answers
Answers · Revenue Operations

What AI workflows should a RevOps team build in Salesforce and HubSpot?

Short answer. Start with the workflows that sit on a decision someone makes many times a day: enriching and routing a new lead, scoring it with a reason, drafting the first reply, flagging deals that have gone quiet and checking the forecast. Build each inside the CRM you already run, keep a person approving anything that reaches a customer, and measure it against a baseline you wrote down first.
Updated ·by Shivil Sahni

Five workflows worth building first

Enrich and route: a new lead gets company data, a matched account and a named owner in seconds. Score with a reason: a score plus the two or three facts behind it, shown where reps already work. Draft, do not send: a first reply or follow-up written from the record for a rep to approve. Deal watch: open deals with no activity, a pushed close date or no next step are flagged to their owner every week. Forecast check: what reps called is compared with what the stage history supports.

Where each lives in Salesforce

Routing and field updates are built in Flow, with assignment rules for the simple cases. Scoring can use Salesforce's own AI features where your edition and licenses include them, or a model outside Salesforce that writes a score and its reasons back to fields. Keep the logic in Flow before reaching for code, and build in a sandbox first where your edition has one.

Where each lives in HubSpot

Routing, rotation and alerts are built in workflows, which need the Professional or Enterprise tier. Rule-based scoring is configured in score properties, and predictive scoring depends on your tier. Use HubSpot's built-in AI features first where your plan includes them, and add outside tools only for what they cannot do.

What to get right before any of them

Every one of these reads the CRM and acts on it with confidence, so the records come first. Each lead and deal needs an owner, each stage needs one meaning, and the fields a workflow reads need to be filled in. Write down the baseline before you build: how long a lead waits, how many have no owner, how many hours the team spends on the task today.

How to tell it worked

Compare the same numbers after a month, and ask the reps whether they use it. A workflow that changes what happens next gets used. One that produces a report nobody opens does not, however clever the model behind it.

Related

Want this built inside your own stack? Book a call, or ask the concierge in the nav.

© 2026 zRev Solutions
FAQ Insights Privacy & Terms