Marketing operations is the system that turns marketing activity into pipeline sales will actually work: shared lifecycle definitions, clean lead capture, routing with response SLAs, scoring, campaign operations, email infrastructure, and reporting that ties channels to pipeline and revenue. We build it in your marketing platform and CRM, most often HubSpot, so marketing and sales argue about strategy instead of about whose number is right.
What marketing operations covers
| Area | What it decides |
|---|---|
| Lifecycle and lead management | How a lead is captured, what qualified means, and how fast it reaches a rep. |
| Lead scoring | Which leads sales should work first, based on fit and behavior. |
| Campaigns and email | How campaigns get built and launched cleanly, and whether your email actually arrives. |
| Attribution | Which channels and campaigns earned the pipeline, with a method finance can check. |
| Reporting | The numbers leadership reviews, from one source everyone trusts. |
Where marketing operations breaks
Leads leak between marketing and sales
Form and source leads slip through without ever reaching a rep, and the ones that do reach someone sit for hours or days first. Nobody notices until sales complains about lead quality, when the real problem was speed.
Nobody agrees what qualified means
Marketing hits its MQL target, sales ignores half of the leads, and both teams have a dashboard proving they are right. Without shared lifecycle definitions encoded in the system, the argument repeats every quarter.
Reporting stops at the MQL
Reports show clicks, opens and MQLs but never connect to pipeline or closed revenue, so marketing cannot show its contribution and budget conversations run on opinion.
Two teams, two numbers
Marketing and sales bring different figures for the same metric to the same meeting, and someone rebuilds the monthly deck by hand to reconcile them.
Manual work crowds out marketing
List pulls, campaign setup, data fixes and report assembly take the time that should go to the programs themselves.
Lifecycle and lead management
It starts with capture: form strategy, source tracking, deduplication on entry and data validation, so every lead arrives in the CRM once, with its source intact. Then the definitions. We facilitate agreement between marketing and sales on what counts as an MQL, an SQL and a recycle, and encode those definitions as lifecycle stages with feedback loops, so a rejected lead returns to nurture with a reason instead of disappearing.
Routing is where speed is won or lost. Routing rules, round-robin assignment, SLA timers and escalations get a lead to the right rep while it is still warm, and the SLA report shows where it is not happening. In one engagement, moving routing into the CRM took median first touch on an inbound lead from about 31 hours to 9 minutes; the embedded RevOps case study has the detail. Prioritizing which leads to work first is the job of scoring, covered in depth in lead scoring your sales team will actually use.
- Form strategy, source tracking, deduplication on entry and validation, so the lead arrives in the CRM once, with its source intact.
- Marketing and sales have agreed what counts as an MQL, an SQL and a recycle, and those definitions are lifecycle stages the CRM enforces.
- Fit and behavior decide which leads get worked first. Scoring has its own page: lead scoring your sales team will actually use.
- Routing rules and round-robin assignment put the lead with the right rep, and an SLA timer starts. If it runs out, an escalation fires.
- The rep makes first contact while the lead is still warm, and the SLA report shows where that is not happening. In one engagement, moving routing into the CRM took median first touch from about 31 hours to 9 minutes; the embedded RevOps case study draws it to scale.
- A lead sales rejects goes back to nurture with a reason instead of disappearing, and the reasons feed back into the definitions.
Campaign operations and email
Campaign operations is the production line behind every program: intake and briefs, builds, QA, launch checklists, and naming and UTM conventions that make campaigns reportable afterwards rather than a forensic exercise. Event-triggered journeys and nurture programs run from templates, so launching the next campaign is faster than the last. More on this under campaign operations and email automation.
Underneath the campaigns sits email infrastructure, which is easy to ignore until messages start landing in spam: sending domain authentication with SPF, DKIM and DMARC, list hygiene, and subscription and consent management. Mailbox providers now expect bulk senders to authenticate properly, and a campaign that never reaches the inbox has no conversion rate to optimize.
Attribution you can interrogate
Attribution models disagree by design: first touch, last touch and multi-touch each answer a different question, and none of them is the truth. What matters is that the method is written down, the tracking underneath it is complete, including UTMs and offline touches such as events, and anyone can trace a number back to the records that produced it. We separate sourced pipeline from influenced pipeline, report cost to acquire by channel, and show the working, so the finance team can check the figure rather than take it on faith. Our attribution page covers model choice in more depth.
Reporting tied to revenue
We start with a marketing KPI framework that maps funnel metrics, pipeline influence and channel return to the revenue goal, then build the dashboards: in the CRM where it can answer the question, or in Looker, Power BI or Tableau on top of a warehouse when the sources are too many. Sourced and influenced pipeline, revenue contribution and cohort views sit alongside executive and board summaries with commentary. Agreeing the definitions and a single source of truth first is what ends the whose-number-is-right debate. Company-level forecasting and board reporting are covered under revenue forecasting.
Sales says our leads are bad. Who is right?
Usually both, partly, and the data can settle it. Before judging lead quality, check what happened to the leads: were they routed to someone, contacted quickly, and rejected for a written reason? Most "bad lead" arguments turn out to be routing and response problems that look like quality problems.
Sales saw 61 leads worth working and called the rest junk. But 96 of the 200 never got a timely first touch, so nobody knows whether they were good. Fix routing and response first; then judge quality.
An illustration with made-up numbers, not a client's.
Four things end the argument for good:
- One written lead definition that both teams sign, encoded as lifecycle stages in the CRM.
- A required rejection reason from a short picklist, so "bad lead" becomes data: wrong fit, no budget, student, competitor, duplicate, could not reach.
- An SLA report showing time to first touch by rep and by source.
- A monthly review of rejected leads by marketing and sales together, which feeds changes back into the definition and the scoring model.
What should our MQL definition be?
A fit threshold plus a buying signal, written so a rep can check it in ten seconds. Fit says the company and person match your ideal customer profile. The signal says they are in market now. Leads that ask for a demo or pricing should skip the MQL step and go straight to sales.
| Part | What it checks | Example |
|---|---|---|
| Fit | Company and person match the ICP | B2B, 50 to 500 employees, VP or head of a revenue team |
| Signal | A behaviour that shows buying interest | Pricing page and a case study in the same week, or a webinar plus a reply |
| Hand-raise | Skips scoring, goes straight to a rep | Demo request, contact sales, trial sign-up |
| Exclusions | Never an MQL, whatever the score | Students, competitors, existing customers, personal email with no company |
| SLA | What sales owes each MQL | First touch within one business hour for hand-raisers, one day for MQLs |
Treat MQL volume as a diagnostic rather than a target. The moment it becomes the goal, the definition drifts downward. Which metrics should judge marketing instead is covered in our GTM metrics guide.
How much pipeline should marketing source?
Work it back from the bookings target, not from a fixed percentage. Divide the target by your win rate to get the qualified pipeline sales needs, then apply the share marketing has actually sourced over the last four quarters. That gives marketing a pipeline number, an opportunity count and a lead count it can plan against.
To book $2M at a 25% win rate, sales needs $8M of qualified pipeline. If marketing sources 40% of it, that is $3.2M: about 80 opportunities, or 1,600 leads at your lead to opportunity rate.
Starting values are made up. The sums are pipeline = target ÷ win rate, and opportunities = pipeline ÷ deal size.
If the lead number looks impossible, the levers are win rate and deal size as much as lead volume. Coverage and in-quarter conversion are covered in the pipeline and forecast guide.
Why are leads not showing up in Salesforce?
When HubSpot and Salesforce are connected, a lead that never arrives is almost always blocked by one of five things. Check them in this order:
- The inclusion list. HubSpot only syncs contacts that meet the integration's inclusion rules. A new form or source that is not in the list never syncs.
- A required field or validation rule in Salesforce. If Salesforce requires a field HubSpot does not send, the record fails and shows up as a sync error, not as a lead.
- Duplicate rules. Salesforce matching rules can block a record that looks like an existing lead or contact.
- Owner mapping. An owner in HubSpot who is not an active Salesforce user can stop the record from being assigned.
- Field mappings that changed. A renamed or deleted field breaks the mapping silently.
The integration's sync error list in HubSpot shows which of these it is. The lasting fix is a weekly check of sync errors and an alert when they spike, so leads are not lost for a month before anyone notices. If the leads arrive but the two systems still report different numbers, see why HubSpot and Salesforce reports do not match.
Platforms
We work in HubSpot Marketing Hub most often, as well as Marketo and Marketing Cloud Account Engagement, formerly Pardot, and integrate the ad platforms, analytics tools and enrichment services around them. If the CRM underneath needs work first, that is covered under CRM and revenue systems.
What it costs
Published 2026 market benchmarks put a focused revenue operations audit at 2,500 to 10,000 dollars, project-based work at 10,000 to 150,000 or more, and entry-level ongoing retainers at 3,000 to 8,000 a month. A scoped piece such as a lifecycle and routing rebuild sits toward the lower end of the project band.
Ranges as published in MergeYourData's 2026 RevOps pricing benchmarks. Market-wide figures, not our rate card. More detail in our guide to what RevOps consulting costs.
Our own marketing operations projects start from $12,500 for up to 25 CRM users with mostly clean data. The estimator adjusts it for your team and your data in a minute.
What you keep
- Written lifecycle definitions and the routing and SLA rules that enforce them, in your own systems.
- Campaign templates, naming conventions and launch checklists your team can run without us.
- An attribution method that is documented, not a black box.
- Dashboards built on agreed definitions, under your admin ownership.
If your marketing ops seat is empty or about to be, interim cover is built for exactly that, and RevOps as a Service covers ongoing support across marketing, sales and customer success.
Frequently Asked Questions
What is marketing operations?
Marketing operations (MOps) is the function that manages marketing technology, processes, data, and reporting. It ensures marketing programs run efficiently, leads are properly managed, and results are accurately measured and attributed.
How do you improve marketing-to-sales handoff?
We implement lead scoring models, define MQL/SQL criteria with sales alignment, set up automated routing workflows, and create SLA tracking dashboards. This ensures sales receives the right leads at the right time with full context.
How do we align marketing and sales on lead quality?
We facilitate shared definitions of what counts as an MQL, an SQL and a recycle, then encode them in the system with feedback loops so the definitions actually stick.
Which marketing platforms do you work in?
HubSpot Marketing Hub most often, as well as Marketo and Marketing Cloud Account Engagement, formerly Pardot. We also integrate ad platforms such as Google, LinkedIn and Meta, analytics tools and data enrichment services.
BI tool or CRM dashboards?
It depends on your needs. For many teams CRM dashboards are enough; for complex, multi-source reporting we build in Looker, Power BI or Tableau on top of your warehouse. We recommend the simplest thing that works.
How do we end the whose-number-is-right debate?
By agreeing on definitions and a single source of truth, then building every report from it, so marketing, sales and finance read the same number from the same place.
How do we settle arguments about lead quality?
Check what happened to the leads before judging them: whether each was routed, contacted within the SLA and rejected for a written reason. Then agree one written lead definition, require a rejection reason, report time to first touch, and review rejected leads monthly with both teams.
How much pipeline should marketing source?
Work it back from the bookings target: divide the target by your win rate to get the qualified pipeline sales needs, then apply the share marketing has sourced over the last four quarters. Divide by average deal size for opportunities, and by your lead to opportunity rate for leads.
Ready to Scale Your Marketing Engine?
Book a free 30-minute review and we will trace a handful of your recent leads from first touch to rep, and show you where they leak.
Take the RevOps Health Check Book a Free Review