Sales and Marketing Alignment Procedures

How to Run the 5 Sales and Marketing Alignment Procedures That Fix B2B Pipeline

To restore predictable B2B pipeline under board pressure, follow these 5 steps, diagnose misalignment, design a joint revenue SLA, govern the lead handoff, run joint quarterly planning, and install shared measurement. You will need 4 prerequisites, including CRO and CMO sponsorship and CRM access. This process takes approximately 6 to 10 weeks. The Starr Conspiracy recommends starting only after both function leads commit to a single revenue number.

Step Summary

1. Diagnose sales and marketing misalignment with a scored audit.
2. Design a joint revenue SLA both functions will sign.
3. Govern the lead handoff with a closed-loop CRM process.
4. Run joint quarterly planning against shared targets.
5. Install shared measurement with one source of pipeline truth.

Run them in order. Diagnosis feeds the SLA. The SLA defines the handoff. Handoff data feeds planning. Planning sets the measurement frame.

This is a procedure library, not alignment tips. Each procedure produces a named artifact (scorecard, SLA, configured CRM handoff, one-page joint plan, shared dashboard) and a governance mechanism. That is what makes pipeline creation inspectable. For working definitions of MQL, SQL, demand states, and sourced pipeline, see our B2B revenue alignment glossary.

Prerequisites, What You Need Before Starting

Before running Step 1, confirm the following are true:

• Executive sponsorship. The CRO and CMO have agreed, in writing, to a single sourced-pipeline number for the next four quarters.
• CRM access. A RevOps lead or analyst has admin-level access to opportunity, lead, and campaign objects in the system of record (Salesforce, HubSpot, or equivalent).
• Historical data. The last four quarters of pipeline, MQL-to-SQL conversion, and closed-won data are exportable and clean enough to trust for decisions.
• A shared definition of an opportunity. If sales and marketing disagree on what counts as a qualified opportunity, pause and resolve that first using the working definitions in our B2B revenue alignment glossary.
• Time on the calendar. Block 6 to 10 weeks. This is a sequenced operational change, not a workshop.

If any prerequisite is missing, these procedures will produce documents nobody honors. The common symptom set is familiar, sales says leads are junk, marketing says follow-up is late, RevOps is refereeing, and the board deck numbers do not match between functions.

Objection check, "we already have an SLA." Most existing SLAs fail because they were written without the diagnosis in Step 1 and without the consequence clause and CRM configuration in Steps 2 and 3. If yours has all three, skip to Step 4. If not, start at Step 1.

Step 1, Diagnose Sales and Marketing Misalignment

Run a scored audit before writing or rewriting any SLA. The diagnosis procedure quantifies misalignment so you stop arguing about whether it exists. Most revenue teams skip this and jump straight to building an SLA, which is why the SLA fails inside a quarter.

Score five dimensions, 1 to 5, where anything under 3 is a fracture and anything under 2 is where you start:

• Definition agreement. Do both functions define MQL, SQL, and opportunity the same way?
• Handoff hygiene. What percent of MQLs receive sales follow-up within the stated window?
• Conversion benchmarks. Where do leads stall across demand states (inquiry, engaged, accepted, qualified, opportunity)?
• Pipeline-source attribution. Can both functions agree on who sourced what?
• Trust signal. A five-question anonymous survey of both teams covering definitions, follow-up quality, lead quality, attribution fairness, and confidence in the joint number.

Why this fails in real life, leaders assume they know the answer and skip the survey. The survey is what gives you political cover for Steps 2 through 5.

Output, a one-page diagnosis scorecard with the five scores, the three highest-leverage fractures, and a recommended sequence.

Immediate benefit, revenue leaders get a single page to take to the board instead of a 40-slide deck.

Confirm, the scorecard is signed by both function leads and version-controlled in your shared drive before proceeding. The signed scorecard becomes the input to Step 2.

If you cannot get both leads to sign within 10 business days, talk to us about facilitating the diagnostic.

Step 2, Design a Joint Revenue SLA

Draft a two-page SLA that defines what marketing owes sales, what sales owes marketing, and what happens when either side misses. Vague SLAs are worse than no SLA. Alignment is a engagement enforced by workflow.

Marketing commitments. Monthly MQL volume target by segment. A defined MQL (scoring threshold plus fit criteria). A lead-data completeness standard.

Sales commitments. A follow-up window, start at 24 to 48 business hours as an internal starting point and calibrate to your baseline. A minimum touch cadence, 5 to 8 attempts across channels. A disposition requirement, every MQL gets a status in CRM within the follow-up window.

Consequence clause. This is what most teams skip. Sample language, "If marketing misses MQL volume two months running, the pipeline target is renegotiated, not absorbed silently by sales. If sales misses the follow-up window on more than 15% of MQLs (calibrate threshold to your baseline), those leads recycle to nurture and do not count against marketing's conversion rate."

Name an arbitration owner inside the SLA. RevOps decides disputes on definitions, breaches, and attribution. Review our how to build a sales and marketing SLA guide for the structure.

Output, a signed two-page SLA with named owners and a 90-day review date.

Immediate benefit, fewer mid-quarter renegotiation fights.

Confirm, the SLA is signed, version-controlled, and the review date is on both leaders' calendars. The signed SLA becomes the configuration spec for Step 3.

Step 3, Govern the Lead Handoff

Operationalize the SLA inside the CRM. Without this step, the SLA is a poster on the wall. If it is not in the CRM, it did not happen.

Configure four things in your system of record:

• A lead-routing rule that assigns every MQL to a named sales rep within 5 minutes of crossing the scoring threshold.
• An automated SLA timer that flags any MQL not actioned within the SLA window.
• A disposition picklist with a fixed value set (working, disqualified, recycled, converted) that blocks closure of the lead record until selected.
• A closed-loop feedback field where sales tags the disqualification reason (bad fit, bad data, bad timing, no response).

The disqualification-reason field is the one that changes everything. Without that data, marketing cannot fix lead quality and the argument restarts every quarter.

Pair the configuration with rep enablement, a 15-minute training and a one-page reference, and manager inspection, a weekly review of SLA timer compliance.

Why this fails in real life, teams configure the picklist but skip manager inspection. Without weekly review, compliance drifts inside 30 days.

Output, a configured CRM handoff with documented field definitions.

Immediate benefit, response-time compliance becomes inspectable in real time.

Confirm, SLA-timer compliance is above 85% and disposition tagging is above 90% across two full weeks before proceeding. If either is below, stop and fix enablement or system design before moving to Step 4.

Step 4, Run Joint Quarterly Planning

Replace the two-meeting model (marketing plans, then presents to sales) with a single working session that produces one plan owned by both functions.

Cadence, quarterly, 4 weeks before the quarter starts. Required attendees, CMO, CRO, RevOps lead, demand-gen lead, and sales-development lead.

Agenda:

• Review last quarter against SLA.
• Review pipeline coverage by segment (coverage ratio is pipeline divided by target).
• Identify the two or three pipeline gaps that need solving.
• Assign campaign and outbound plays against those gaps.
• Commit to MQL and SQL volume needed to hit coverage.

Add a weekly 30-minute SLA exception review between planning sessions, owned by RevOps, with a standing invite and a running agenda. That is where disputes get resolved before they become quarterly arguments. For PLG motions, swap "outbound plays" for "product-qualified-lead routing rules," the procedure adapts, the artifact does not.

Why this fails in real life, the meeting becomes a readout. Force the one-page output or the session failed.

Output, a one-page joint plan listing coverage target, segment focus, play assignments, owners, and SLA numbers.

Immediate benefit, surfaces the misalignment teams have been managing around for years.

Confirm, the one-page plan is signed by the CRO and CMO, stored in the shared drive, and targets match the dashboard definitions in Step 5. The signed plan becomes the measurement spec for Step 5.

Step 5, Install Shared Measurement

Build a single dashboard both functions trust. The deliverable is not a tool. It is an agreement about which numbers matter.

Define five dashboard tiles, no more:

• Sourced pipeline by function. Marketing-sourced means the first touch (the earliest CRM-recorded interaction) was a marketing program. Sales-sourced means the first touch was outbound by an SDR or AE. Disputes are adjudicated by RevOps using first-touch CRM data, this is the arbitration rule that ends the marketing-sourced versus sales-sourced fight.
• Pipeline coverage ratio against the quarter target.
• SLA compliance, marketing's MQL delivery and sales' follow-up rate.
• MQL-to-opportunity conversion by segment.
• Sales cycle length by sourced channel.

Build the dashboard in the system both functions already use (Salesforce reports, HubSpot dashboards, or a BI layer on top). Do not introduce a new tool to solve a trust problem. Review the dashboard in the quarterly planning session from Step 4.

Why this fails in real life, teams add a sixth and seventh metric to satisfy a stakeholder, then nobody trusts the dashboard.

Output, a single shared dashboard with documented metric definitions.

Immediate benefit, the CRO and CMO present the same numbers to the board without translation.

Confirm, both function leads sign off on metric definitions and dashboard accuracy before any board deck or investor update uses the numbers. If they will not sign, stop and resolve the definition dispute before publishing.

What good looks like, both leaders present the same five tiles, RevOps resolves disputes inside a week, and the quarterly plan is signed without a side conversation.

How to Sequence These Procedures

Default is sequential, each procedure's output is the next procedure's input. Run in parallel only under the exceptions below.

Decision rules:

• Always start with Step 1. If the scorecard shows definition disagreement under 2, fix definitions before designing an SLA.
• If your board deck locks in the next 30 days and pipeline is missing by more than 30%, run Steps 1, 2, and 3 in parallel. Defer 4 and 5 to next quarter.
• If conversion rates look fine but sales claims lead quality is bad, the issue is Step 3 disposition data. Start there.
• If both functions have the same numbers but disagree on what they mean, the issue is Step 5. Start there.
• If the trust survey is the lowest score in Step 1, the issue is not operational. Bring in a third party to facilitate.

On the "we do not have time" objection, board pressure is the time. If you are not ready to engage on all five, review the SLA guide and start with Step 2.

Common Mistakes to Avoid

• Skipping Step 1 because leadership already knows the problem. The scorecard is political cover for the changes in Steps 2 through 5. Without a scored diagnosis, every change feels like one function blaming the other.
• Writing an SLA with no consequence clause in Step 2. Commitments without consequences are aspirational. Define the consequence in writing, or do not bother with the document.
• Configuring the handoff without the disqualification-reason field in Step 3. Marketing cannot improve lead quality without structured reason data, and the argument restarts every quarter.
• Treating Step 4 joint planning as a status update. If you leave without a signed one-pager, the meeting failed.
• Buying a BI tool in Step 5 instead of agreeing on numbers. Agree on the five tiles first. The tool comes later, or not at all. In The Starr Conspiracy client work, we require the signed metric definitions before any dashboard build begins.

The Bottom Line

Sales and marketing alignment is not a culture problem. It is an execution problem with a defined operational surface, five procedures, run in order, producing five artifacts a board can see. Outcomes depend on prerequisites and adoption, but the pattern holds, teams that finish Step 5 stop arguing about alignment and start arguing about strategy.

The cost of skipping the work is concrete, late follow-up, disputed attribution, and board deck numbers that do not match between functions. If you cannot get both function leads to sign the Step 1 scorecard within 10 business days, the issue is sponsorship, not process. That is the trigger to bring in a third party.

The Starr Conspiracy runs facilitated diagnostic sprints and SLA working sessions for B2B revenue teams under board-level pipeline pressure. If your board deck locks in the next 30 days, talk to us about facilitating Steps 1 through 3, you will leave with a signed scorecard, a draft SLA, and a documented CRM handoff spec.

Related Questions

How long does it take to fix sales and marketing misalignment?

The full five-procedure sequence typically runs 6 to 10 weeks for a mid-market B2B team with clean CRM data. Steps 1 through 3 deliver visible operational change in the first month. Steps 4 and 5 require a full quarter to show pipeline impact because they depend on a planning cycle and a measurement cycle running end-to-end.

Who should own the alignment process, sales or marketing?

Neither. RevOps owns the process, the CRO and CMO co-sponsor it, and both function leads are accountable for the artifacts. If sales owns it alone, marketing is treated as a service desk. If marketing owns it alone, sales does not show up. Shared sponsorship with operational ownership in RevOps is the only model that holds across quarters. For more on the operating model, see our B2B revenue alignment glossary.

What if sales refuses to disposition leads?

This is a manager inspection problem, not a rep problem. Make disposition a required field that blocks lead closure in CRM, add it to the weekly sales manager review, and tie SLA compliance to the quarterly business review. If disposition rates stay under 90% after two weeks of enforcement, escalate to the CRO as an adoption issue, not a tooling issue.

What is the difference between an SLA and a handoff process?

The SLA is the engagement, what each function commits to deliver and what happens when commitments are missed. The handoff process is the CRM configuration and workflow that operationalizes the engagement day to day. You need both. An SLA with no handoff configuration is a poster. A handoff configuration with no SLA is a workflow nobody is accountable to.

Can we run these procedures without a RevOps team?

Yes, but you will need a named owner with admin-level CRM access and at least 20 hours a week dedicated for the 6 to 10 week sequence. In smaller B2B teams, this is often a marketing operations manager or a sales operations analyst with a temporary scope expansion. Without a named operational owner, the procedures stall at Step 3.

How do we know the alignment work is working?

Three signals. SLA compliance above 85% on both sides for two consecutive months. Both function leads presenting the same pipeline numbers to the executive team without translation. And the quarterly planning session producing a one-page joint plan that both leads sign without a side conversation afterward. If all three are true, the alignment work is holding.