Revenue organizations love to say “marketing and sales are aligned,” but alignment is not a feeling. It is shared definitions, shared targets, clear handoffs, and a cadence that makes gaps visible early enough to fix them. When those mechanisms are missing, every quarter looks the same: marketing says leads are good, sales says leads are bad, SDRs say they can’t reach prospects, and pipeline coverage erodes.
8.1 Shared Definitions: Lead, MQL/SQL, Opportunity, Pipeline, Revenue
Every revenue engine runs on language. If the words mean different things to different functions, you cannot measure performance, diagnose problems, or hold teams accountable without turning meetings into arguments. The fix is not a 40-page taxonomy. It is a short metric dictionary with definitions tight enough to inspect and consistent enough to learn from.
Start by separating interest from intent, and activity from commitment. A download is interest. A request for a security review is intent. Ten emails sent are activity. A scheduled meeting with an agreed agenda is a commitment. Your definitions should require evidence at each step.
Lead: a contact associated with an account that has engaged in a way that indicates potential interest. Minimum requirements are valid contact data and an attributable source. An account can have many leads; most are noise without ICP fit and a trigger.
MQL (Marketing Qualified Lead): a lead that meets an agreed threshold of fit and engagement for a segment. Fit is an ICP proxy (industry, role, environment). Engagement is buying-correlated behavior (demo request, pricing intent, event follow-up). The definition must state what is excluded; otherwise, volume becomes the goal.
SQL (Sales Qualified Lead): a lead that has been contacted and validated by sales development and meets minimum evidence: correct persona, plausible trigger, and a next step the prospect agreed to. SQL is not “we tried calling.” SQL is “the buyer engaged and confirmed a problem worth exploring.”
Opportunity: a revenue pursuit with an identified buying group and a documented value hypothesis. An opportunity should not be created at the first meeting by default. It should be created when the rep has confirmed a reason to act, a path to decision, and a scope that matches your standard offer boundaries.
Pipeline: the dollar value of active opportunities in a defined period, weighted or unweighted depending on your forecast rules. Pipeline is an inventory of decision processes that must advance. Track freshness and stage advancement as rigorously as dollars.
Revenue: closed-won bookings (or recognized revenue) that meet commercial policy standards. In recurring models, keep the relationship explicit: bookings create ARR; retention sustains it; expansion compounds it.
The definitions above matter only if they are connected to owners and evidence. Operationalize by attaching entry criteria and exit criteria to each step of the funnel. Entry criteria define what must be true to count the item. Exit criteria define what must be true to advance it. Managers can then audit reality quickly instead of debating intentions.
Template: minimum funnel criteria (illustrative; adapt by segment).
- MQL entry: ICP-fit threshold met + engagement action from an agreed list.
- SQL entry: live connection + confirmed persona + confirmed trigger + agreed next step.
- Opportunity entry: confirmed pain/outcome + stakeholder map started + initial value hypothesis documented.
- Pipeline eligibility: opportunity meets stage exit criteria and has an identified next customer commitment.
To make the dictionary usable, add a short list of required reason codes any time an item moves backward: rejected MQL, rejected SQL, closed-lost, or recycled opportunity. Keep the list small (10–15 codes) and review it monthly. When the same two codes dominate, you’ve usually found a system problem—targeting, messaging, or qualification—not a rep problem.
Attribution won’t be perfect; make it consistent. Default: credit the source that originated the opportunity and track influence separately so you can optimize the system using evidence.
8.2 ABM Playbook: Targeting, Orchestration, and Measurement
Account-based marketing (ABM) is not “personalized email.” It is a coordinated, account-first growth system for segments where accounts are scarce, buying groups are large, and proof matters. ABM works when your target list is high quality, your message is built around triggers and outcomes, and sales and marketing run a shared orchestration plan with clear ownership.
Start with one target account list. If sales has one list and marketing has another, ABM becomes a branding exercise instead of a pipeline engine. Build the list from your tiering and ICP rules (Chapter 4) and keep it stable for a quarter. Then segment it by the few variables that change the motion: industry/use case, trigger type, and relationship state (known vs unknown, active vs dormant).
Define the ABM “units of work.” The units are not campaigns; they are plays applied to accounts. A practical ABM program runs three to five plays at any time, each tied to a trigger. Examples include a regulatory deadline play, a renewal displacement play, or an expansion rollout play. Each play needs a narrative, a proof pack, and a call to action that creates a concrete next step.
Orchestration is where ABM succeeds or fails. Orchestration means sequencing touches across channels and roles so the account experiences one coherent conversation. Decide who leads each moment: marketing creates relevance, SDRs convert relevance into conversations, AEs convert conversations into mutual plans, and executives or partners unlock access. If you don’t define the handoff, the account gets noise instead of momentum.
Template: ABM orchestration grid (for each play).
- Weeks 1–2: marketing launches trigger content + retargeting; SDR runs a sequence referencing the trigger; AE sends a tailored point-of-view note to two stakeholders.
- Weeks 3–4: invite targeted stakeholders to a short executive webinar or roundtable; SDR follows with a specific ask; AE runs discovery on engaged accounts.
- Weeks 5–6: deploy proof (reference call, ROI workshop, security review plan) for engaged accounts; re-tier accounts that stayed cold.
Don’t confuse personalization with relevance. Relevance is showing you understand the account’s context and can connect it to an outcome. Use personalization sparingly: one account-specific insight that supports your point of view, not a list of trivia.
A simple way to choose channels is to match them to the job: ads and content to create awareness, SDR outreach to earn a reply, events to convene peers, and executives or partners to open doors. Orchestration beats channel perfection.
Measure ABM using account progression. ABM success is movement from target accounts to engaged accounts, from engaged to meetings, from meetings to opportunities, and from opportunities to wins. Because ABM cycles can be long, add leading indicators that show whether trust is building: stakeholder coverage, acceptance of the value hypothesis, and completion of de-risking steps (security review scheduled, pilot agreed).
ABM scorecard: review monthly with sales and marketing together.
- Account coverage: % of target accounts touched across at least two channels in the last 30 days.
- Engagement quality: % of accounts with engagement from ICP personas.
- Meeting conversion: meetings booked per 100 target accounts, by play.
- Opportunity creation: opportunities created and accepted, by play, with ICP rating.
- Pipeline health: freshness and stage advancement for ABM-sourced opportunities.
ABM needs a “stop doing” rule. If an account does not progress after a defined number of cycles, change the play, change the channel mix, or deprioritize the account. Discipline forces learning instead of hoping.
8.3 SDR/BDR Model Design: Coverage, Sequences, Handoffs, Quality Control
Sales development is the conversion layer between awareness and pipeline. When SDR/BDR systems are designed well, they create qualified conversations, raise AE productivity, and surface market feedback early. When designed poorly, they generate meetings that don’t convert and create conflict over “lead quality.”
Start by deciding the SDR mission by segment. In high-velocity SMB, SDRs often qualify inbound and set meetings fast, with limited research. In enterprise, SDRs run targeted outbound to named accounts, with deeper research and multi-threading. Mixing missions without clarifying expectations creates the complaint: “SDRs set bad meetings.” Often those meetings simply didn’t match the intended motion.
Coverage design has three levers: account allocation, role specialization, and time allocation across inbound versus outbound. Inbound is usually higher conversion but more volatile; outbound is more controllable but requires better targeting and messaging. Set explicit mix targets by segment and staff to those targets.
Coverage options:
- Pod model: one SDR aligned to a small set of AEs and a defined account list; best for ABM and enterprise where tight coordination matters.
- Pooled model: SDRs work from a shared queue with routing logic; best for high-velocity inbound where speed matters.
- Hybrid model: pooled for inbound, podded for outbound into priority accounts; common in mid-market.
Sequences should be designed around the buyer’s reason to care, not the seller’s desire to book time. A good sequence tries to earn a micro-commitment: a short conversation to confirm a trigger, a referral to the right owner, or permission to send a relevant asset. Avoid a barrage of “just checking in.”
Sequence anatomy: the minimum elements that make outreach credible.
- Trigger hook: a reason the account might care now, grounded in a segment pattern.
- Outcome promise: a specific outcome others achieved, expressed conservatively.
- Proof snippet: a short proof point (benchmark, reference category, result range).
- Clear ask: a small, time-bound request with two options (meet vs refer).
- Exit line: a polite disengagement that preserves brand if they are not interested.
Quality control comes from definition discipline and manager inspection. If “SQL” means “we booked a meeting,” then meetings will be optimized over pipeline. Instead, define a qualified meeting standard and inspect it weekly. The standard should include persona fit, a stated trigger or problem, and a mutually agreed agenda. For enterprise, add a stakeholder expectation: at least one additional buying-group name identified by the end of the first conversation.
Handoffs are where momentum is gained or lost. The best handoff is a transfer of context that allows the AE to continue the conversation rather than restart it. Require a standard handoff note and, for priority accounts, a brief three-way transition call.
Example prompts to document an exception request clearly
- Why now: the trigger or initiative in the customer’s language.
- Who: role, seniority, disposition; other names mentioned.
- What matters: success criteria and risks; competitive context if stated.
- Next step: meeting date/time, agreed agenda, and the commitment to earn.
- Assets sent: what the prospect has already seen.
Align incentives to progression, not just meetings. A practical approach blends credit for qualified meetings with accelerators for opportunities accepted by AEs and additional rewards for pipeline or closed-won influence. Keep the plan simple enough that SDRs can explain it in one minute.
8.4 Content That Sells: What Sellers Actually Use and What They Ignore
Most organizations produce too much content and too little proof. Libraries grow, sellers can’t find what they need, and they default to improvisation. The goal of sales content is not to educate in the abstract; it is to help a buyer make a decision. That requires clarity about where content is used in the selling journey and what job it performs.
Content that sellers use has three traits: it is short, it is specific, and it is designed to be forwarded. A long whitepaper may help a brand, but it rarely moves an active deal unless it contains something the buyer can quote internally. In contrast, a one-page value summary, a two-slide point-of-view story, or a short customer proof clip can change stakeholder belief quickly.
Organize content by use case and stage, not by product. Sellers think about customer problems and next steps. When you store content by product module, you force the rep to translate under time pressure, and they often choose the wrong asset. A better structure is a small set of “deal kits” per segment or use case, each with a clear purpose.
Deal kit components: the few assets that cover most selling needs.
- Point-of-view opener: a one-page narrative that frames why change and why now.
- Value summary: quantified drivers, assumptions, and a conservative payback range.
- Proof pack: two to three relevant case studies, a reference path, and a credibility artifact (security, compliance, validation).
- Implementation plan: milestones, responsibilities, and typical time to value.
- Competitive guide: decision criteria, trade-offs, and proof to defend your advantage.
Build content from real deal moments. Ask top reps what they send after the first meeting, what they send before the executive call, and what they send when procurement pushes back. Those moments are where content either reduces friction or is ignored. Then design assets explicitly for those moments. For example, an ROI summary should be a finance-friendly outline a buyer can adapt for internal review, not an infographic.
Make proof concrete. “We have customers like you” is not proof. Proof is a specific result in a relevant context with enough detail to be credible: baseline, change achieved, time to value, and what made it work. If you cannot share names publicly, create anonymized but specific proof and offer named references under NDA.
Content governance: to avoid library sprawl, establish a simple lifecycle. Every asset has an owner, a review date, and a measured usage rate. Retire assets that are not used. Update assets when the product changes, competitive claims shift, or proof is no longer current. Your goal is not the most content; it is the highest conversion content.
Template: content usefulness score (run quarterly).
- Findability: can a seller locate it in under 30 seconds?
- Usability: can it be used live or forwarded as-is?
- Relevance: is it tied to a segment/use case and a stage?
- Proof strength: does it contain verifiable evidence, not just claims?
- Adoption: % of active reps using it at least monthly.
Train managers to coach with content. Sellers will use what managers inspect. In deal reviews, ask, “What proof has the buyer accepted?” and “What asset will we send next to move the decision?” Those questions create discipline: content becomes a lever for progression, not a box-check for marketing.
8.5 SLAs And Operating Rhythm: How Alignment Becomes Operational
Alignment becomes real when it is governed. Governance does not mean bureaucracy; it means explicit commitments, tracked performance, and a cadence for resolving issues quickly. The core tools are service-level agreements (SLAs) between functions and an operating rhythm that inspects the system end to end.
An SLA should cover four domains: definitions, speed, quality, and feedback loops. Definitions specify what counts. Speed specifies response times and handoff windows. Quality specifies evidence thresholds and rejection rules. Feedback loops specify how the system learns and improves. When these are written, “alignment” stops being subjective.
Template: marketing–SDR–sales SLA (practical starting point).
- Targeting: marketing focuses X% of spend on ICP-A accounts and refreshes the target-account list quarterly; sales maintains accurate ownership within five business days of changes.
- Speed-to-lead: SDRs attempt first contact within one hour for high-intent inbound from ICP-A accounts during coverage hours, and within 24 hours for all other inbound; marketing routes leads with required fields completed.
- Qualification standard: SDRs mark SQL only when persona and trigger are confirmed and a next step is agreed; AEs accept or reject SQLs within 24 hours with a required reason code.
- Recycle rules: rejected SQLs return to nurture with a reason code and a recommended next action; marketing reports recycle outcomes monthly and adjusts targeting/content accordingly.
- Capacity signals: if response times exceed SLA for two consecutive weeks, leadership adjusts routing or staffing within one week.
SLAs work only when exceptions are inspected. The point is not to punish; it is to see where the system breaks. If inbound response is slow, is it staffing, routing, or data quality? If SQL acceptance is low, is the definition too loose, the ICP too broad, or the play irrelevant? Without inspection, SLAs become dead documents.
Build an operating rhythm with three layers. Weekly: run a 30-minute funnel review on leading indicators—speed-to-lead, conversion rates, pipeline created, and stage advancement for new opportunities. Monthly: run a deeper review by segment and source, including win/loss themes, content usage, and discount patterns for sourced deals. Quarterly: revisit ICP, account tiers, ABM plays, and capacity allocation.
Design forums to produce decisions. A useful weekly funnel meeting answers: what is off track, why, and what will we do this week? If the meeting becomes a dashboard tour, it will be ignored.
Use a small set of shared KPIs that connect marketing and sales outcomes: ICP-qualified pipeline created, meeting-to-opportunity conversion, opportunity acceptance rate, and pipeline-to-bookings conversion by source. Avoid overloaded dashboards with dozens of metrics; people will choose the one that supports their narrative. Fewer metrics create clearer accountability.
Embed alignment into frontline management. Give managers tools to inspect early-stage quality: random audits of SDR handoff notes, sampling of discovery calls, and stage criteria checks for new opportunities. When managers coach to standards, and marketing sees how those standards affect conversion, the system becomes more truthful.
When you get this right, you stop arguing about lead quality and start improving the engine. Marketing knows which plays create pipelines. SDRs know what “good” looks like and have the assets to earn conversations. AEs receive fewer but better opportunities and can spend time on value and deal control rather than re-qualifying noise. The company can scale demand generation and sales capacity without scaling chaos.
