When someone asks your business for a demo, what happens next?
Who receives the request? Who follows up? And how do you know it happened?
These sound like simple questions. But answering them may require checking the CRM, messaging a salesperson, and asking marketing where the enquiry came from.
Now follow that same person through the rest of the journey. They speak with sales, become a customer, and meet your onboarding team. At each step, someone needs to take responsibility, and the right information needs to reach them.
Your people may be working hard and doing their individual jobs well. Still, the customer experiences the whole business. They feel the delays, the repeated questions, and the promises that did not reach the next team.
Revenue operations, or RevOps, helps you organise those connections.
For B2B businesses, it brings structure to how teams attract customers, manage opportunities, deliver value, and maintain customer relationships. It also gives leadership a clearer view of where the process is working and where it needs attention.
Revenue operations is the practice of aligning the people, processes, data, and technology involved in generating, converting, and retaining revenue.
It connects marketing, sales, customer success, and other relevant functions through shared definitions, clear responsibilities, coordinated processes, and reliable information. This alignment across departments is central to HubSpot’s definition of RevOps.
In everyday work, RevOps helps a business answer questions such as:
The work includes agreeing on those answers, putting them into practice, and checking whether they produce the intended result.
A CRM can support this work, but the business still needs to make the decisions behind it. Creating a field called “Qualified” does not establish what qualification means or who is responsible for assessing it.
A B2B purchase can involve several decision-makers, multiple conversations, and requirements that change during the buying process. After the sale, the relationship may continue through implementation, support, renewal, and expansion.
Inside the business, different teams own different parts of that experience.
Marketing might measure enquiries. Sales might measure opportunities and closed deals. Customer success might measure adoption and renewals. Each team needs its own measures, but it also needs to understand how its work affects the next team.
Consider a marketing campaign that generates a large number of enquiries. The campaign may appear successful, yet sales may struggle because the enquiries lack essential information or do not match the intended customer profile.
The useful question is what happens across the connection: are the right people entering the process, reaching the right owner, and receiving an appropriate response?
RevOps helps teams investigate those connections and agree on improvements.
As a business grows, it also becomes harder to depend on informal coordination. A process that once worked through a conversation between two colleagues may now involve several departments and systems. Clear ownership and documented rules help that process remain manageable.
The scope of RevOps depends on the business model and organisational structure. Marketing, sales, and customer success are commonly central to it, with support, finance, and delivery teams involved where their work affects the revenue journey.
| Team | Main responsibility | What RevOps helps coordinate |
|---|---|---|
| Marketing | Attract prospects, generate demand, and nurture interest | Lead definitions, campaign tracking, qualification criteria, and sales handoffs |
| Sales | Understand buying needs, manage opportunities, and close business | Assignment rules, deal stages, follow-up expectations, forecasting, and post-sale handoffs |
| Customer success | Help customers achieve value and maintain the relationship | Onboarding, adoption, customer health, renewals, and expansion processes |
| Support | Resolve issues and help customers use the product or service | Ticket routing, escalation, service standards, and visibility into customer problems |
| Finance | Manage billing, collections, and financial reporting | The transfer and reconciliation of relevant contract, invoice, payment, and customer information |
| Leadership | Set direction, allocate resources, and evaluate results | Shared priorities, performance definitions, accountability, and visibility across teams |
These teams do not all need to report to the same person. They do need an agreed way to work together.
For example, finance can remain responsible for invoicing while RevOps helps define how complete billing information reaches finance after a deal closes.
RevOps becomes useful when recurring problems cross team boundaries or when the systems no longer reflect how the business operates.
A website form captures the request correctly. The record appears in the CRM. Yet nobody can confidently explain who should respond or how quickly.
The business needs more than a notification. It needs assignment rules, response expectations, a clear owner, and a way to identify exceptions.
A RevOps review would examine what happens to new enquiries, existing customers, duplicate submissions, and requests that do not fit the usual assignment criteria.
Marketing reports 100 qualified leads. Sales says only 20 were qualified.
Before deciding who is correct, examine the definitions.
Marketing may use engagement as its qualification criteria. Sales may require a confirmed need and a realistic buying timeline. Both reports could be consistent with their own rules while still creating confusion.
RevOps helps establish definitions that distinguish these stages and clarify what should happen between them.
One salesperson moves a deal forward after sending a proposal. Another waits until the buyer confirms that the proposal is being reviewed.
The stage name is the same, but the meaning differs. That makes pipeline reporting less useful.
RevOps helps define progression criteria, required information, and responsibility for keeping opportunities current.
During sales, a customer explains their goals, timeline, and requirements. After signing, onboarding asks for the same information again.
Some repetition may be necessary to confirm details. Reconstructing the entire conversation usually points to a handoff problem.
RevOps helps determine which information must be captured, who provides it, and how the receiving team confirms that it has what it needs.
A property is renamed, a workflow is adjusted, or an integration mapping is changed. Later, a report stops working or records begin moving through the wrong process.
RevOps includes the governance needed to maintain these connections: documentation, permissions, testing, change review, and ongoing ownership.
At Revefied, we use People, Process, and Platform as a practical framework for explaining and improving revenue operations.
Data and measurement run across all three. People maintain information, processes define when it is captured, and platforms make it available for action and analysis.
Every important step needs a responsible owner.
That includes the person performing the work, the person receiving it, and the person who decides what happens when something goes wrong.
For a marketing-to-sales handoff, the business should agree on:
These responsibilities may sit with a small number of people in a growing company. What matters is that they are understood.
Team adoption belongs here too. People need to know why a process exists, what is expected of them, and where to raise concerns.
A useful process describes the steps, decisions, requirements, and exceptions involved in achieving an outcome.
“Send new leads to sales” is a starting point. It leaves several decisions open:
Does every lead go to sales? What information is required? What happens if the person is already a customer? When should an unanswered enquiry be escalated?
Agreeing on these details gives the team something consistent to follow and improve.
The level of documentation should fit the work. A straightforward handoff may need a short checklist. A complex process involving several systems may need a process map and more detailed rules.
The platform includes the CRM and connected systems used to record information, coordinate actions, and measure performance.
In HubSpot, this may involve properties, pipelines, views, tasks, workflows, permissions, and dashboards. The specific setup depends on the business requirements and available functionality.
Start with a clear requirement, such as:
“New demo requests must reach an appropriate owner, and the team lead must be able to identify requests awaiting follow-up.”
That requirement gives the implementation a purpose and provides a basis for testing it.
Consider a fictional B2B software company called Northstar.
Northstar has a marketing team, four salespeople, and a customer success manager. Its website generates demo requests, and its CRM stores prospect and customer information.
However, several gaps have developed:
The team chooses to improve the journey from demo request to onboarding.
| Step | Business decision | Supporting system change |
|---|---|---|
| Capture the request | Agree on the minimum information needed to assess and assign an enquiry | Update the form and relevant CRM properties |
| Assign an owner | Define assignment rules and a fallback owner for exceptions | Configure routing and a view for unassigned requests |
| Manage follow-up | Set response expectations and escalation responsibilities | Create tasks and visibility into overdue follow-up |
| Manage the opportunity | Agree on clear criteria for each deal stage | Update the pipeline and supporting requirements |
| Prepare the handoff | Specify customer goals, agreed scope, stakeholders, and commitments | Create a structured handoff checklist |
| Accept onboarding | Require the receiving team to confirm ownership and flag missing details | Track handoff status and unresolved gaps |
| Review performance | Choose measures that show whether the process improved | Report on response times and handoff completeness |
The team can then assess the results against its starting point.
Are more requests receiving timely attention? Are fewer records left unassigned? Does customer success receive the information it needs?
Those questions help determine whether the changes are working. They also reveal where further adjustment is needed.
These responsibilities often overlap, especially in smaller organisations. The difference is primarily their scope.
| Function | Primary focus |
|---|---|
| Marketing Ops | Processes, data, technology, and measurement that support marketing execution |
| Sales Ops | Processes, systems, and analysis that support sales performance |
| RevOps | Shared operating practices and connections across the revenue journey |
| CRM administration | Configuration, maintenance, access, and usability of the CRM |
One person may perform work across several of these areas.
For example, creating a deal property is a CRM administration task. Deciding what it means, when it should be completed, who maintains it, and how it affects onboarding requires a broader operational discussion.
Effective RevOps brings that business context into the implementation.
Choose measures that relate directly to the problem being addressed.
If your concern is slow follow-up, begin with response times and overdue requests. If onboarding regularly receives incomplete information, track handoff completeness and the time spent resolving gaps.
| Area | Example measure | What it helps you understand |
|---|---|---|
| Lead management | Time to first sales response | Whether enquiries receive timely attention |
| Qualification | Percentage of handed-off leads accepted by sales | Whether teams are aligned on qualification |
| Sales | Stage conversion and sales cycle length | Where opportunities progress or stall |
| Onboarding | Time to the first agreed customer value milestone | How effectively customers get started |
| Retention | Customer retention or renewal rate | Whether customer relationships continue |
| Data quality | Percentage of records missing essential information | Whether the process has the information it needs |
Define each measure carefully.
For response time, does the clock run during business hours or calendar hours? Does an automated acknowledgement count as a response? Which enquiries are included?
Those decisions affect what the number means.
Review operational measures alongside commercial outcomes. Faster follow-up may improve the buying experience, but revenue also depends on demand, product fit, pricing, and sales execution. A process improvement should be evaluated within that wider context.
You do not need to redesign the whole business at once. Choose one recurring problem that matters to customers or the team.
“Improve the CRM” is too broad to guide the work.
A more useful starting point is:
“Demo requests do not consistently reach the right salesperson, and we cannot see which ones are waiting for follow-up.”
That statement identifies a process, a failure, and a visibility gap.
Speak with the people doing the work and trace several recent examples through the process.
Look at what actually happened. Where did someone wait? Which information was missing? When did a colleague have to step in manually?
Include an exception as well as a straightforward case.
Define the steps, ownership, required information, and conditions for moving forward.
Bring the receiving team into the discussion. A handoff is only useful if it gives that team what it needs to act.
Translate the agreed process into the CRM and any connected systems.
Test the normal path and relevant exceptions. Check both the action and its consequences: did the right owner receive the record, was the information preserved, and can the outcome be reported accurately?
Explain what has changed, why it matters, and what each person needs to do.
Assign someone to review performance, collect feedback, and maintain the process. Business requirements change, so the setup will need attention over time.
Use these questions in your next team discussion:
If an answer is unclear, record the uncertainty and identify who can help resolve it. You now have a specific improvement to investigate.
No. Smaller businesses can apply RevOps principles through clear responsibilities, consistent definitions, connected processes, and reliable data.
The amount of structure should match the business. A small team may begin with one agreed handoff and a few shared measures.
You need accountable ownership and participation from the relevant departments. Whether that requires a dedicated team depends on the complexity and volume of the work.
Some businesses use an internal operations lead with specialist support. Others build a team or engage an external partner.
No. RevOps can be supported by different CRM platforms and connected tools.
The decisions about people, processes, data, and measurement apply regardless of the technology. HubSpot is one platform that can support their implementation.
An external partner can provide discovery, process design, implementation, reporting, and ongoing operational support.
Internal stakeholders still need to participate in business decisions, provide context, and support adoption. The relationship works best when responsibilities and priorities are clear.
No. RevOps can improve coordination, execution, and visibility, while revenue remains influenced by several commercial factors.
Set clear objectives for the operational work and evaluate how those improvements contribute to the wider business goals.
Choose one recent customer and trace their experience from first enquiry through sales and onboarding.
Could each team see the information it needed? Was ownership clear? Did anyone have to chase details or repeat work?
Use what you find to choose one improvement, agree on an owner, and define how you will know it helped.
If your team needs support applying that work in HubSpot, explore Revefied’s HubSpot RevOps services. We help businesses design processes, implement improvements, and keep their systems aligned with how their teams operate.