HubSpot, Salesforce, Zoho, Odoo or Pipedrive. The operating model comes first, the platform carries it.
Every platform below can hold a well-designed revenue system. None of them supplies one. Each ships defaults, and a default is a starting point that someone has to replace with a decision.
Revops builds on the CRM already in place. Licences stay in your name, we hold no reseller agreement and take no vendor commission, and when a platform genuinely cannot carry the logic we show the evidence rather than assert it. What follows is what each platform provides, and the design question it leaves to you.
Platform capabilities described on this page reflect vendor documentation as of September 2026. Products change, and we re-verify before scoping any build.
HubSpot
Revenue operations on HubSpot
What the platform provides. HubSpot ships eight default lifecycle stages: Subscriber, Lead, Marketing Qualified Lead, Sales Qualified Lead, Opportunity, Customer, Evangelist and Other. A Super Admin can add, rename and reorder custom stages under Settings, Objects, Contacts, and the defaults cannot be deleted. Lifecycle stage, lead status and deal stage are three separate properties serving three different purposes.
What it leaves to design. The design question is what each stage means in your business, because the default definitions are placeholders rather than standards. The second question is whether stages move automatically or by hand, since manual updates make funnel reporting unreliable. The work is lifecycle and deal stage definition, property governance, workflow rationalisation, and reporting built on those definitions.
Salesforce
Revenue operations on Salesforce
What the platform provides. Salesforce consolidated its automation on Flow. Creation of new Workflow Rules and Process Builder automations has been disabled in stages since the Winter 23 release, and Salesforce set 31 December 2025 as the end of support date for both. Existing automations continue to run after that date but receive no bug fixes. The official Migrate to Flow tool converts one to one, which turns a hundred workflow rules into a hundred flows.
What it leaves to design. The design question is whether to migrate or to rebuild. A one-to-one conversion preserves the logic and the sprawl at the same time, so the opportunity is to consolidate the automation landscape while it is being moved. Alongside that sit field and object rationalisation, stage gate enforcement through validation and Path, forecast category rules, and a reporting layer aimed at managers rather than at administrators.
Zoho CRM
Revenue operations on Zoho CRM
What the platform provides. Zoho CRM provides Blueprint, a no-code process engine built from States and Transitions, configured under Setup, Process Management, Blueprint. It enforces the paths you define, so a record cannot skip from one state to another unless the transition exists, and individual actions within a transition can be marked mandatory or optional.
What it leaves to design. The design question is what to make mandatory, because Blueprint enforces exactly what it is told and nothing else. The second question is data authority, since Zoho is usually adopted as a suite and the same customer can exist across several Zoho applications. The work is process design before Blueprint construction, module and layout standardisation, a system of record per object, and analytics rebuilt on one metric dictionary.
Odoo
Revenue operations on Odoo
What the platform provides. Odoo CRM tracks leads and opportunities through customisable kanban pipeline stages configured under CRM, Configuration, Stages, with sequence, team assignment and stage-triggered email templates. Enterprise adds predictive lead scoring, which estimates win probability from historical won and lost data. The module integrates natively with Sales, Website, Email Marketing and Accounting.
What it leaves to design. The design question is where the commercial record stops and the operational record starts, because in Odoo the customer exists in the CRM, the order, the invoice and often the project at the same time. The work is pipeline design with written exit criteria, activity and stage rules, an explicit system of record across the modules, and reporting that reads both the commercial and the operational side.
Pipedrive
Revenue operations on Pipedrive
What the platform provides. Pipedrive provides a Leads Inbox that holds prequalified leads before they become deals, unlimited customisable pipelines, custom lead scoring, deal rotting to flag untouched opportunities, and pipeline-specific fields on higher plans. Usage limits on leads, deals and custom fields vary by plan.
What it leaves to design. The design question is what qualifies a lead to leave the Leads Inbox, because Pipedrive supplies the container and not the criterion. The second is how many pipelines the business genuinely needs, since multiple pipelines are easy to create and hard to report across. The work is lead qualification criteria, pipeline architecture, required fields per stage, and rotting and activity rules that make the pipeline self-policing.
Platform-neutral first
The operating model does not change with the tool.
Every engagement produces the same artefacts regardless of platform: definitions, stage models, routing rules, a metric dictionary and governed dashboards. Only the configuration differs, which is why a migration rarely solves a commercial problem.
The capabilities a build normally configures are <a href="#/revops/revenue-systems/crm-revenue-data">CRM & Revenue Data</a>, <a href="#/revops/revenue-systems/workflow-automation">Workflow Automation</a>, <a href="#/revops/revenue-systems/lead-routing">Lead Routing</a>, <a href="#/revops/revenue-systems/opportunity-management">Opportunity Management</a> and <a href="#/revops/revenue-systems/reporting-forecasting">Reporting & Forecasting</a>.
Questions
Frequently asked
Will you tell us to change CRM?
Only with evidence. Every platform on this page can carry a well-designed revenue system, so a migration recommendation has to name the specific capability that is missing and what it costs to work around.
Are you a partner or reseller of these platforms?
No. We hold no reseller agreement and take no vendor commission, which is what allows the recommendation to be worth something.
What if we use a platform that is not listed?
The method does not change. The five layers, the definitions and the workflow logic are platform-neutral. Only the configuration work differs.
Who maintains the system afterwards?
Your administrator. Every build ends with documentation and a handover session, because a system that only its builder can maintain is a dependency rather than an asset.
Our Salesforce org still runs Workflow Rules. Is that urgent?
It is not an outage risk, since existing automations continue to run past the end of support date. It is a maintenance risk, because bugs will not be fixed, and it is an opportunity to consolidate rather than convert one to one.
Start with a read of what you already own.
The Diagnostic includes a configuration review of your current platform, so the repair plan states what can be fixed where you are before anything else is considered.
