RevOps (Revenue Operations) is an organizational design in which "Marketing, Sales, and Service departments operate on common data, processes, and technology." However, in many organizations today, divisions still occur, such as ``Sales ignores leads passed by Marketing,'' ``Information on customers who have received orders from Sales does not reach CS,'' and ``No one can see where orders are being lost.'' In this chapterLifecycle Stage automatic transition design, lead routing, MQL → SQL handoff, handoff to CS, RevOps metrics and integrated reportingExplains everything from design to implementation.
The problem that RevOps is trying to solve is the structural problem of ``walls between departments hindering business growth.'' Marketing says ``I passed on the lead,'' Sales says ``I don't have any usable leads,'' and CS says ``I don't know what kind of customers I received.'' The root cause of this division isData, processes, and goal settings varyThat's true.
| conditions | Specific content | How to achieve this with Operations Hub |
|---|---|---|
| ① Common definition | The definitions of MQL, SQL, and SAL are consistent in Marketing/Sales/CS. Everyone understands “MQL leads by how many points” based on the same standard. | Calculate lead score Implement WF and MQL promotion conditions in HubSpot so everyone can see the same logic |
| ② Automated handoff | As soon as the MQL is reached, Sales will be notified and once an order is received, customer information will be passed to CS. Don't rely on manual emails or spreadsheets | Lifecycle Stage Transition WF/Handoff notification WF/Task automatic creation Build a process that works even if people forget using WF |
| ③ Common indicators | Marketing does not track the number of MQLs, Sales the number of orders, and CS the churn rate, but all departments share the conversion rate of the entire funnel. | Visualize the entire funnel of “Leads → MQL → SQL → Orders → 12 Month Retention Rate” on one dashboard with a custom report |
Lifecycle Stage is one of HubSpot's most important properties. It represents the 8 stages a contact is currently in: Subscriber → Lead → MQL → SQL → Opportunity → Customer → Evangelist.In organizations where this does not work automatically, everyone is making decisions by looking at the old Stage.A problem arises.
A common design mistake is creating a WF that "automatically demotes from MQL to Lead when the score drops". If you do thisA lead that Sales is chasing suddenly returns to Lead one day.A confusion ensues. As a general rule, Lifecycle Stages are designed in one direction (promotion only). Decrease in score will be managed in a separate "re-nurturing target list" and the stage itself will not be lowered.
The accuracy of MQL decisions is determined by the design of lead scoring. If the score is too low, Sales will receive a large number of unusable leads, creating a sense of distrust that ``Leads from Marketing cannot be used.'' If your score is too high, you will miss out on promising leads.Appropriate score design is the foundation of a trusting relationship between Marketing and SalesBecome.
Handoff is the most trouble-prone point in RevOps. Discrepancies in understanding whether it was handed over or not handed over, information necessary for handover not being conveyed, and leads getting cold due to too long a time lag—automate these with workflow."Even if people forget or information leaks, the process doesn't stop."Make it a design.
Create a WF that automatically escalates if Sales does not contact you within 24 hours of MQL promotion. Specifically, "If hs_sales_email_last_replied is blank after 25 hours after becoming an MQL, create a warning task to the Sales manager."Instead of waiting for people to notice SLA violations, the system automatically tracks them.Design is the foundation of RevOps.
RevOps reports are not just a list of numbers for each department.“Visualize the entire funnel from lead generation to customer continuation in one flow.”It has to be something. If Marketing only tracks the number of MQLs and Sales only tracks the number of orders, it is impossible to see where in the funnel the funnel is stuck.
Visualize conversion rates by funnel stage with HubSpot's Custom Report. Select the "Contact" object in the report builder and create a "Change in number of contacts by Lifecycle Stage" graph. Furthermore, by adding the dataset created in Data Studio (Chapter 4) to the report's data source,Integrated funnel reporting combined with data outside of HubSpot (Snowflake billing data, BigQuery product usage data)can be made.
| Report type | Setting method | Update frequency | Main viewers |
|---|---|---|---|
| Funnel conversion rate report | Custom Report → Funnel Chart → Number of Contacts by Stage | Weekly updates | Marketing / Sales / CS Leader/RevOps |
| Pipeline prediction report | Transaction report → Amount by stage/Scheduled closing date | Automatically updated daily | Sales Leader/CFO/CEO |
| MQL SLA Compliance Report | Calculated columns using custom properties (mql_date, first_contact_date) | weekly | Sales Manager/RevOps |
| Churn & NRR Report | Combine CS tickets + HubSpot customer data + billing data in Data Studio | monthly | CS leader/CFO/management team |
| Attribution report | HubSpot Multi-Touch Attribution Reports + Custom Reports | monthly | Marketing Leader/CMO |
In organizations where RevOps has matured, the practice of having everyone view and discuss the same HubSpot dashboard at weekly Revenue Review meetings has become established. Marketing, Sales, and CS do not each bring in separate reports using their own tools.One common dashboard becomes the Single Source of Truthis the goal of RevOps. The purpose of this chapter's design is to build that dashboard using HubSpot and Data Studio.
Any automation will be meaningless if MQL definitions are not consistent across departments. First, Marketing and Sales agree on ``what constitutes an MQL'' and implement that standard in HubSpot. Automation without agreement will only create automated chaos.
Automatic demotion due to low scores is a source of confusion. As a general rule, stages are only promotions. Demotions are managed manually and as exception handling. MQL promotion conditions should be designed simply with two elements: "score threshold + engagement conditions", and should not be too complicated.
You can start with a simple round robin, but as you grow, you will need to branch out by Enterprise/Mid-Market/SMB classification, region, and industry. Routing logic can be implemented using custom code actions (Chapter 3) to handle complex conditions.
WF automates three points: what to pass (information set), when to respond (SLA), and what will happen if it is not met (escalation). Handoffs that rely on human goodwill are bound to fail. Create a design that follows the mechanism.
“The number of MQLs has increased” is not enough. MQL → SQL Conversion rate/SQL → Order conversion rate, cycle time, and churn rate can be visualized on the same dashboard, and only then can you see where the problem is in the funnel.
If we discuss things with different tools and indicators, we'll end up with an argument that says, ``That's not what our numbers say.'' The goal of a RevOps organization is to have all departments agree on HubSpot's unified dashboard as a single source of truth.