Why alignment fails
Misalignment is structural before it is personal. Marketing is usually measured on leads and sales on bookings, so marketing is rewarded for volume that sales must then work, and sales are rewarded for closing deals whose origin they have no reason to record. Each team sees the other's output but not its constraints. Marketing sees leads ignored; sales see leads that were never worth calling. Add stage definitions that live in two heads rather than one document, a CRM where source fields are optional, and a planning cycle in which marketing's targets are set without sales and sales' targets without marketing, and the conflict is guaranteed regardless of how well the people get on.
The fix has to be structural too. A shared number both teams are measured on, usually pipeline and revenue; definitions written down and configured; an agreement that specifies what each team owes the other; data that makes compliance visible; and a rhythm of meetings where the agreement is checked against the data. The FunnelModel of the customer journey stages. model gives both teams a common picture, and the rest of this guide fills in the parts.
Shared definitions and targets
| Item | Agreed by both teams | Why it matters |
|---|---|---|
| Ideal customer profile | Segment, size, sector, problem, disqualifiers | Marketing targets it; sales qualify against it; both reject leads outside it |
| Stage definitions | Lead, marketing-qualified, sales-accepted, sales-qualified, opportunity, with entry and exit criteria | The contract for the hand-off; see the lead stages guide |
| Lead routing | Who receives which leads, by territory, segment and rotation | Removes "I never got it" from the vocabulary |
| Service levels | Time to accept, time to first contact, attempts before recycling | Makes speed a shared obligation |
| Return reasons | A short list of codes for recycled and disqualified leads | The feedback loop that fixes marketing's criteria |
| Shared targets | Pipeline created, by source; revenue; cost per opportunity | Both teams measured on the same scoreboard |
| Source and campaign fields | Which fields are required on leads and opportunities, and who maintains them | Without them, nothing can be attributed |
| Content commitments | What marketing produces for each stage and who maintains it | Sales enablement as an obligation, not a favour |
The shared target is the most important row. When marketing's number is pipeline rather than leads, marketing has a reason to care about quality, speed and what happens after the hand-off. When sales are measured partly on the conversion of marketing-sourced pipelineValue of sales opportunities whose original source was a marketing activity., sales have a reason to work the leads and to record what happened. Customer acquisition cost (CACCost to acquire one new customer.) across both teams, by segment, is the figure that eventually settles most budget arguments. The lead stages guide covers the second row in full.
Why marketing's target is better set on sales-qualified leads than on marketing-qualified volume is argued in the MQL versus SQL comparison.
The service-level agreement
The agreement is a short document, revised quarterly, that specifies what marketing delivers and what sales does with it. Marketing's side: the number and quality of marketing-qualified leadsA lead that marketing judges ready for sales follow-up against agreed criteria. per month by segment, the criteria they meet, the data each lead carries (source, campaign, fit fields, the actions that qualified it), the follow-up content available, and the time within which marketing responds to a return. Sales' side: the time within which a lead is accepted or returned, the time to first contactAverage time between a new lead arriving and the first contact from sales., the number and spacing of attempts before a lead is recycled, the use of return reason codes, the required fields on every opportunity, and the time within which closed-lost reasons are recorded.
What makes it work is that both sides are measured automatically from CRM timestamps and reported in the same place, in the same meeting. A service level that lives in a document and is checked by complaint is a wish. One that appears as a line on the weekly dashboard, red when missed, changes behaviour within a month. The agreement should also say what happens when a level is missed: not punishment, but a defined escalation and a review of whether the level was realistic.
When the agreement's response target is disputed, the lead response time experiment gives both teams evidence by comparing immediate and standard follow-up on meetings held.
Rituals: reviews and feedback loops
Alignment is maintained in meetings with data, and the cadence matters more than the format. Weekly, a short pipeline reviewA short regular meeting where sales and marketing read the same opportunities from the same data and agree an owned action for each stuck deal. of marketing-sourced leads and opportunities: what arrived, what was accepted, what was returned and why, what moved stage, what is stuck. The weekly pipeline review tutorial sets that meeting up step by step, from the data pack to one owned action per stuck deal. When the agreement itself needs reviewing, the lead management audit scorecard scores it alongside stage definitions, routing and the closed loop. Monthly, a review of the agreement's metrics against the levels, stage conversion by source, and the content requests from sales. Quarterly, a planning session where targets for the next quarter are set together, the ideal customer profileA description of the type of organisation most likely to buy, succeed with the product and stay, used to choose target accounts. and stage criteria are revisited, the agreement is revised, and the attribution read of the previous quarters is discussed.
The feedback loops are the point of the rituals. Return reason codes flow back to marketing and change the criteria and the targeting. Closed-lost reasons flow back and change the content and the positioning. Sales call notes flow back and change the messaging. And marketing's view of what engaged a lead before it was handed over flows forward to sales, so the first call is informed. Activity after the hand-off can flow forward too, and the guide to sales alerts from marketing activity keeps those alerts few enough to be read and judges them by the conversations that follow. The loops only run if someone owns them: a revenue operations role, or a named person on each side, with the job of making sure that what one team learns reaches the other.
Shared data and the CRM
Everything above depends on one system of record with the fields both teams need, filled in consistently. Leads carry source, campaign, the qualifying actions and the fit fields; opportunities inherit the source and add value, stage, close date and reason; activities record the contacts and attempts that the service levels count. Required fields enforce the minimum; validation keeps the values consistent; and a single owner of the data model stops each team inventing fields the other does not use. The CRM fundamentals guide covers the objects, properties and hygiene; here the alignment point is that the CRM is the arbiter, and a dispute that cannot be settled from its data is a dispute about the data. When sellers have stopped keeping that data current, the diagnosis for sales not updating the CRM locates the stale records by owner, stage and field before anyone is blamed.
Two practical rules follow. Marketing should be able to see what happened to every lead it handed over, in the CRM, without asking. Sales should be able to see everything marketing knows about a contact, including which content they engaged with and which campaigns they came through, in the record they work from. Dashboards built for both teams from the same fields, rather than a marketing dashboard and a sales dashboard with different numbers, remove the first cause of most arguments.
Content for sales
Marketing owes sales content, and most sales teams would say they do not get it. The need is specific: pieces that answer the questions asked at each stage of a conversation, in a form a salesperson can send in a minute. Discovery needs problem and category pieces; evaluation needs comparisons, proof, customer stories by sector, security and integration documents; decision needs business cases, implementation plans and references; and objection handling needs honest answers to the questions prospects ask about price, risk and competitors. The pieces should live where sales work, be searchable by stage and question, and be maintained, because an out-of-date comparison is worse than none.
The loop works in both directions: sales know which questions come up and which content works, and a monthly content review with sales is the cheapest research marketing can do. The account-based marketing guide describes the most intense version of this collaboration, where content for named accounts is planned jointly; the same discipline at lower intensity serves every segment. For a named account, that joint planning is written down in an account plan that pairs every marketing play with the sales action and owner beside it.
The usual conflicts and how to settle them
"Marketing leads are rubbish." Settle it with data: acceptance rate, qualification rate and opportunity rate by source, against the criteria. If the rates are poor, the criteria change; if the rates are fine and the complaint persists, the complaint is about something else.
"Sales never follow up." Settle it with timestamps: time to first contact by salesperson against the service level. Usually a routing problem or a capacity problem rather than a motivation one.
"Marketing takes credit for deals sales found." Settle it with a sourcing rule written in the agreement: sourced means marketing created the first touch, influenced means marketing touched the opportunity, and both are reported separately. The measurement guide covers the choices. Where a sales development team prospects outbound, the guide to marketing support for outbound prospecting records outbound as its own source under the same rule. The tutorial on writing the source rule for pipeline turns that written rule into a closed list of origins, an order that decides between two of them, a rule on who sets the value, a lock and a named decider for changes, tested on real opportunities.
"The targets are impossible." Settle it by setting them together, from historical stage rates, with the arithmetic visible. A pipeline target implies a lead target through conversion rates both teams accept.
"We need more leads." Often the KPIA metric tied directly to an objective. conversation that should be about speed, conversion or deal size. Check those first; the pipeline section sets the three guides together and explains why pipeline rather than lead volume is the number to argue about.
An agreement that changed the numbers
A cloud infrastructure vendor's sales team accepted 31% of marketing-qualified leads and contacted them after an average of 52 hours; marketing produced 600 a month and reported on volume. The two teams wrote an agreement: marketing committed to 350 leads a month meeting a rewritten criterion with full source data; sales committed to accept or return within 4 business hours with a reason code, first contact within one business day and five attempts over ten days. Both were measured from CRM timestamps on one dashboard, reviewed weekly. Three months on, acceptance is 78%, average first contact is 3 hours, 19% of accepted leads become opportunities against 7% before, and marketing-sourced pipeline is up 46% on fewer leads. The return codes showed that a third of rejected leads were from a sector marketing had been targeting on a false assumption; the campaign was stopped and the budget moved.
For a whole-year plan built on these agreements, SOSTAC for lead generation shows how sales follow-up capacity caps the lead objective and shapes the control section.
Where the argument is specifically that marketing's qualified leads fail the first sales conversation, the MQL to SQL conversion diagnosis works through scoring, thresholds, unsigned definitions and response speed in turn.
When the complaint is that leads are never contacted at all, the diagnosis of sales not following up on leads checks routing, sync, missing context and capacity before treating it as a question of effort.
Common mistakes
- Treating alignment as a relationship problem. It is an incentive and definition problem; fix those first.
- An agreement with obligations on one side. Marketing commits to volume, sales commit to nothing measurable.
- Service levels without timestamps. If it is not measured from the CRM, it is a hope.
- Separate dashboards. Two sources of truth guarantee two versions of events.
- No return reason codes. The feedback loop that would fix the criteria never runs.
- Setting targets separately. Marketing's lead number and sales' revenue number that do not reconcile through any conversion rate.
- Letting the quarterly review lapse. The agreement drifts from reality within two quarters.
- Enablement as an afterthought. Content for sales is an obligation in the agreement, not a favour granted when marketing has spare time.
