Mục lục bài viết37 mục
- 1.Prerequisites
- 2.Step 1: Align on Funnel Stages and Success Metrics
- 2.1Lock the Stage Model
- 2.2Assign Stage Owners for Data Quality
- 2.3Define Minimum Viable Success Metrics
- 3.Step 2: Diagnose Channel–Stage Gaps from QBR Data
- 3.1Pull Last 2–3 Quarters by Channel × Stage
- 3.2Compute Stage Rates and Unit Economics
- 3.3Flag Gaps Using Action-Ready Thresholds
- 3.4Decide Stage Focus
- 3.5Gap Analysis Template
- 4.Step 3: Map Omnichannel Touchpoints and Stage Plays
- 4.1Touchpoint Map Template
- 4.2Example Touchpoint Map (Mid-Market SaaS, 200–1,000 FTE, NA)
- 5.Step 4: Define MQL/SQL Criteria, SLAs, and Owners
- 5.1Fit and Intent Scoring
- 5.2SLA Matrix
- 5.3Disqualification Codes
- 5.4Ownership and Routing
- 6.Step 5: Allocate Budget by Stage Within the Cap
- 6.1Budget Calculator Inputs
- 6.2Formulas
- 6.3Example Budget Allocation
- 6.4Budget Guardrails
- 7.Step 6: Set KPIs, Attribution, and Quality Thresholds
- 7.1KPIs by Stage
- 7.2Quality Thresholds
- 7.3Attribution Approach
- 8.Step 7: Establish Cadence, Governance, and Adoption Plan
- 8.1Meeting Cadence
- 8.2Change Governance (RACI)
- 8.3Adoption Checklist
- 9.Step 8: Package the Playbook for Executive Sign-Off
- 9.1One-Page Executive Summary Template
- 9.2Example (Filled)
- 9.3What Counts as Sign-Off
- 10.Operating Rules for the Quarter
Use this playbook to build an end-to-end GTM with mapped touchpoints, clear MQL–SQL SLAs, and a stage-level budget inside a fixed quarterly cap — packaged for executive sign-off and ready to run without org restructuring.
Prerequisites
Before you start, confirm you have access to:
- Quarterly budget cap and revenue target
- QBR findings plus CRM and marketing automation data segmented by channel and stage
- Current MQL–SQL definitions, with authority to refine them
- An inventory of active channels and plays, each with a named owner
- Stakeholder availability across Sales, Marketing, RevOps, CS, and Finance
- The ability to report basic funnel KPIs by stage
Expected output: A sign-off-ready omnichannel GTM playbook covering touchpoints from awareness to post-purchase, agreed MQL–SQL SLAs with owners and response times, and a stage-level budget split under your quarterly cap.
Step 1: Align on Funnel Stages and Success Metrics
You cannot prioritize channels or allocate budget until stages and success metrics are unambiguous. Misaligned stage names and vague entry-exit criteria are the fastest way to stall handoffs and corrupt attribution data.
Lock the Stage Model
Define each stage with a clear entry trigger and exit condition — both must map to a CRM field or automation rule, not a gut feeling.
| Stage | Entry | Exit |
|---|---|---|
| Awareness | First anonymous touch or reach | Clicked or visited site |
| Consideration | Engaged session or subscription | Known lead with tracked engagement |
| MQL | Meets ICP fit and intent threshold | Accepted by SDR |
| SAL–SQL | Sales accepts and qualifies | Opportunity created with next meeting set |
| Opportunity | Op created | Closed Won or Lost |
| Post-purchase | Closed Won | Renewed, expanded, or churned |
Assign Stage Owners for Data Quality
- Awareness & Consideration — Marketing
- MQL — Marketing to SDR (shared); RevOps owns records
- SAL–SQL — Sales Development or AE per routing rules
- Opportunity — Account Executive
- Post-purchase — CS or Account Manager
Define Minimum Viable Success Metrics
Each stage needs at least one measurable signal before launch.
- Awareness: Reach, view-through rate, branded search volume movement
- Consideration: Engaged sessions, content depth, new known leads
- MQL: Acceptance rate, time-to-first-touch
- SQL: MQL-to-SQL conversion rate, time-to-meeting, opportunity rate
- Opportunity: Win rate, cycle length, average selling price
- Post-purchase: Onboarding completion, NPS/CSAT, expansion rate, GRR/NRR
Common pitfalls: Avoid creating micro-stages your CRM cannot support this quarter. Every entry-exit criterion must be mappable to a CRM property or automation rule — if it isn’t trackable, it isn’t a real stage gate.
Step 2: Diagnose Channel–Stage Gaps from QBR Data
Your QBR already shows where quality drops by channel. Translate that signal into stage-specific constraints so you back the right plays and cut the noise.
Pull Last 2–3 Quarters by Channel × Stage
For each active channel, export: spend, impressions, clicks, new known leads, MQLs, MQL acceptance rate, SQLs, opportunities, pipeline ($), wins, revenue, and time-to-first-touch.
Compute Stage Rates and Unit Economics
- Lead-to-MQL rate by channel
- MQL acceptance rate by source
- MQL-to-SQL and SQL-to-Opportunity rate
- CAC proxy per channel: Spend ÷ Wins (or Spend ÷ Pipeline$ for early-stage channels)
- Time-to-first-touch for inbound MQLs
Flag Gaps Using Action-Ready Thresholds
Any of the following signals a problem you should fix this quarter:
- Inbound MQL with time-to-first-touch over 30 minutes
- Channel with MQL acceptance rate below 60% against your ICP definition
- Stage where velocity is 20%+ worse than last quarter’s median
- Channel contributing less than 5% of total pipeline but consuming more than 15% of spend
Decide Stage Focus
- If acceptance is low but volume is fine: Fix definition, routing, and SLAs
- If SQL and opportunity creation stall: Strengthen bottom-of-funnel plays and sales enablement
- If pipeline is OK but revenue lags: Address discounting, multi-threading, or expansion plays
Gap Analysis Template
Use this for each channel with a diagnosed issue:
Channel:
Stage impacted:
Symptom:
Evidence:
Root cause hypothesis:
Fix type: Play change / SLA / Budget shift
Owner and due date:
Example:
Channel: Paid Social
Stage impacted: MQL acceptance
Symptom: 38% acceptance vs. target 65%
Evidence: ICP fit below threshold; too many student email domains
Root cause hypothesis: Lead gen form too loose; offer attracts non-ICP audience
Fix type: Play change — tighten form fields, pivot offer to case study
Owner and due date: Demand Gen Lead — Week 2
Step 3: Map Omnichannel Touchpoints and Stage Plays
A clear, end-to-end touchpoint map keeps everyone aligned on what runs where, why, and how leads graduate between stages.
Guardrail: Cap at 3 primary plays per stage. If a play doesn’t have entry-exit criteria, a named owner, and a defined measurement, it doesn’t run this quarter.
Touchpoint Map Template
For each play, complete:
Stage:
ICP segment:
Objective:
Primary channel:
Assist channels:
Asset or offer:
Primary CTA:
Entry criteria:
Exit criteria:
Owner:
Handoff note:
Measurement:
Example Touchpoint Map (Mid-Market SaaS, 200–1,000 FTE, NA)
Awareness
- Objective: Reach and generate high-intent traffic
- Primary channel: LinkedIn Sponsored Content
- Assist channels: SEO pillar page, analyst listing
- Asset / CTA: Category POV video + pillar guide / Read the guide
- Entry: First impression or 25%+ video view
- Exit: Site session 60s+ or guide scroll 50%+
- Owner: Brand Lead
- Handoff: Nurture list entry if session depth is met
- Measurement: Reach, video view rate, engaged sessions
Consideration
- Objective: Capture known leads with clear fit signal
- Primary channel: SEO + retargeting
- Assist channels: Email nurture
- Asset / CTA: ROI calculator / Try the calculator
- Entry: Engaged session or retargeting click
- Exit: Lead created with business email and role
- Owner: Demand Gen Lead
- Handoff: Auto-score intent +10 on calculator completion
- Measurement: New known leads, score uplift, CPL
MQL
- Objective: Create sales-ready demand
- Primary channel: Website demo request
- Assist channels: Live chat, review sites
- Asset / CTA: Live demo booking / Book a demo
- Entry: Fit score 60+ and intent score 40+
- Exit: SDR accepted
- Owner: Lifecycle Marketing
- Handoff: Route by territory to SDR, alert in Slack
- Measurement: Acceptance rate, time-to-first-touch
SQL
- Objective: Progress to opportunity
- Primary channel: SDR outbound sequence to hand-raisers
- Assist channels: AE intro video
- Asset / CTA: Mutual evaluation plan / Confirm next meeting
- Entry: SDR connected, need confirmed
- Exit: Opportunity created with next step set
- Owner: SDR Manager
- Handoff: Assign AE, attach discovery notes
- Measurement: Connect rate, meeting set rate, opportunity rate
Post-purchase (First 90 days)
- Objective: Onboard to first value and surface expansion signals
- Primary channel: In-product guides
- Assist channels: CS QBR, customer community
- Asset / CTA: Onboarding checklist and training / Complete onboarding tasks
- Entry: Closed Won
- Exit: Onboarding complete, PQL surfaced
- Owner: CS Lead
- Handoff: Warm intro to AM for expansion PQLs
- Measurement: Time-to-value, product adoption %, expansion pipeline
FL2 check: Achieved when each stage has 1–3 plays with named owners, entry-exit rules mapped to CRM fields, and defined measurements — and Marketing, Sales, and CS leaders have confirmed in one shared document. Watch for plays with vague entry criteria or no routing owner tagged in CRM. If assets and CTAs don’t exist in current tooling yet, they need a sprint in the enablement plan with a due date before launch.
Step 4: Define MQL/SQL Criteria, SLAs, and Owners
SLAs turn intent into pipeline. Keep definitions tight and time-bound so teams can act without new org structures.
Fit and Intent Scoring
- Fit score (0–100): Industry, company size, tech stack, geography, role — with exact CRM field mappings
- Intent score (0–100): Asset depth, frequency, recency, pricing page visits, demo page visits, third-party review clicks
Recommended MQL gate for this quarter:
- Fit 60+ and Intent 40+, or any hand-raiser form submission regardless of score
- Recycle if unresponsive after outreach sequence or fit falls below ICP guardrails
SQL definition: Sales confirms need, use-case alignment, and agreement to a discovery meeting within 14 days of MQL acceptance.
If your org hasn’t set up lead scoring yet: Start simple. Demo or pricing form submission = MQL. Content download + matching ICP industry/size = MQL. Add scoring precision in Q2 once the baseline is running.
SLA Matrix
| Source | Owner | First Response | Sequence | Accept or Recycle | Escalation |
|---|---|---|---|---|---|
| Inbound hand-raiser | SDR | 10 min (call + email) | Day 0 call+email, Day 1 call, Day 2 email, Day 4 call, Day 7 break-up | Within 24 hours | If no connect by Day 2, notify manager |
| Inbound content MQL | SDR | 24 hours | 5–7 touches over 10 days (phone, email, LinkedIn) | Within 5 business days | If acceptance below 60% weekly, trigger Marketing–SDR review |
| Outbound SDR-sourced | AE (SQL creation) | N/A | — | Qualify within 3 business days of SDR connect; create opportunity within 24 hours of qualification | — |
Note on the 10-minute SLA: This requires automated lead routing (e.g., Salesforce assignment rules) and real-time Slack/Zalo alerts firing the moment a hand-raiser hits the queue. Confirm with RevOps that the infrastructure is live before launch — not after.
Disqualification Codes
Create CRM picklist entries (not free text) for: Not ICP, No Timeline, No Budget, Competitor-Locked, Duplicate. Free text cannot be aggregated at quarter end.
Ownership and Routing
- Marketing: MQL creation and definition stewardship
- SDR: First response, acceptance, and connection
- AE: SQL and opportunity creation
- RevOps: Measurement, routing automation, and SLA reporting
FL2 check: Achieved when the SLA matrix is published with named owners, response times, and escalation rules — and SDR and AE managers confirm in writing. If RevOps cannot capture time-to-first-touch and acceptance timestamps in CRM fields, add two required fields with validation rules before launch.
Step 5: Allocate Budget by Stage Within the Cap
Work backwards from your revenue target so every dollar is defensible to Finance.
Budget Calculator Inputs
| Input | Example |
|---|---|
| Quarterly budget cap | $500,000 |
| Revenue target | $4,000,000 |
| Average deal size | $50,000 |
| Win rate | 20% |
| Contingency reserve | 10% |
Formulas
Pipeline needed = Revenue target ÷ Win rate
Opportunities needed = Pipeline needed ÷ Average deal size
Discretionary budget = Budget cap × (1 − Contingency %)
Stage budget = Discretionary budget × Stage weight
Channel budget = Stage budget × Channel weight
Ring-fence proven channels with a minimum floor: Channel minimum = MAX(RequiredMin, StageBudget × ChannelWeight)
Example Budget Allocation
Derived figures:
- Pipeline needed: $20,000,000
- Opportunities needed: 400
- Discretionary budget: $450,000
Stage weights (based on diagnosed QBR gaps):
| Stage | Weight | Budget |
|---|---|---|
| Awareness | 20% | $90,000 |
| Consideration | 20% | $90,000 |
| MQL creation | 30% | $135,000 |
| Conversion to SQL–Opportunity | 20% | $90,000 |
| Post-purchase | 10% | $45,000 |
Channel splits:
- Awareness: 60% SEO content ops, 40% LinkedIn reach
- Consideration: 50% retargeting, 50% review site programs
- MQL creation: 50% demo flow CRO, 30% paid search (brand + competitor), 20% webinars
- Conversion: 70% enablement assets, 30% SDR tools
- Post-purchase: 70% onboarding content, 30% community
Budget Guardrails
- Cap net-new experiments at 10% of discretionary
- Do not fund any channel without a clear path to MQL or SQL this quarter
- Maintain at least 10% contingency unless Finance explicitly agrees otherwise
FL2 check: Achieved when Finance confirms the total equals cap, stage splits are visible, and ring-fenced minimums are explicit. Add one line under each stage: “Gap addressed + KPI” tying spend directly to a diagnosed metric — leaders need to see the logic to approve quickly.
Step 6: Set KPIs, Attribution, and Quality Thresholds
Pick a KPI stack that measures both quality and contribution without introducing an attribution debate mid-quarter.
KPIs by Stage
| Stage | KPIs |
|---|---|
| Awareness | Reach, engaged sessions, brand search lift vs. prior quarter |
| Consideration | New known leads, calculator completions, CPL |
| MQL | Acceptance rate, time-to-first-touch, % hand-raisers |
| SQL | MQL-to-SQL rate, SQL-to-Opportunity rate, time-to-meeting |
| Opportunity | Win rate, cycle length, pipeline coverage |
| Post-purchase | Onboarding completion, product adoption rate, expansion pipeline |
Quality Thresholds
Set each threshold at last quarter’s 75th percentile, or a 10–15% stretch above last quarter’s average.
- MQL acceptance rate target: prior-quarter P75, minimum 60%
- Inbound hand-raiser time-to-first-touch: 15-minute median or better
- SQL-to-Opportunity rate: prior-quarter P75 baseline
Attribution Approach
- Primary source attribution: Used for ownership tracking and compensation credit
- Multi-touch fractional view: Used by Marketing for channel optimization only
Do not change compensation credit rules this quarter. Document the current rules, use the multi-touch view for insights only, and address any conflicts in Q2. Making attribution changes mid-quarter creates political friction that stalls adoption.
FL2 check: Each KPI needs a data source, a named owner, and a weekly reporting cadence. If compensation and optimization metrics conflict, the rule is simple: primary source is the credit system; multi-touch is optimization-only.
Step 7: Establish Cadence, Governance, and Adoption Plan
A clean cadence prevents overcomplication. Your goal is reliable execution with minimal change management overhead.
Meeting Cadence
Weekly (30 min) — Pipeline Quality Standup Attendees: Marketing, SDR, AE, RevOps Agenda: SLA slippage, acceptance rate, SQL creation, fixes for the week
Bi-weekly — Campaign Review Attendees: Marketing, SDR Agenda: Channel-stage KPIs, creative or offer pivots
Monthly — Executive Review Attendees: Sales, Marketing, CS, Finance Agenda: Budget burn by stage, pipeline coverage, forecast risk, reallocation decisions
Change Governance (RACI)
- Requester: Channel owner
- Approver: Function lead
- Consulted: RevOps and Finance (for budget moves)
- Informed: SDR and AE managers
Change thresholds:
- Under 5% budget move within a stage: function lead approves
- 5–15% move between stages: Sales + Marketing leads + Finance
- Above 15%: executive review required
Freeze window: No net-new experiments in the final 2 weeks of the quarter. Safety fixes only. This protects pipeline by keeping Sales focused on closing rather than triaging new campaigns.
Adoption Checklist
Before launch, confirm every item below:
- [ ] Playbook stored in shared drive with version control
- [ ] CRM routing rules tested with 10 sample leads
- [ ] SLA dashboard live with time-to-first-touch and acceptance widgets
- [ ] SDR enablement: talk tracks and email templates published
- [ ] AE enablement: mutual evaluation plans and ROI calculator walkthrough
- [ ] CS enablement: onboarding checklist in-product, QBR template updated
- [ ] Alerting: Slack or email alerts configured for SLA breaches
- [ ] Budget tracker: shared sheet with named owner per line item
FL2 check: Achieved when cadence and RACI are documented on a single page and leaders agree to change thresholds in writing. Add an SLA for dashboard refresh — daily for operational widgets, weekly for executive rollups. If dashboards lag, problems surface too late to fix.
Step 8: Package the Playbook for Executive Sign-Off
Executives sign faster when revenue math, budget, owners, and risks are visible on one page. Use the template below as your cover page; attach the detailed playbook as the annex.
One-Page Executive Summary Template
Goal this quarter
- Revenue target: [number]
- Pipeline needed: [number] at [win rate]
Strategy Omnichannel GTM with 1–3 plays per stage, focused on [top 2 diagnosed gaps from QBR]
Budget within cap
- Cap: [number] | Contingency: [%] | Discretionary: [number]
- Stage split: Awareness [x] | Consideration [y] | MQL [z] | Conversion [u] | Post-purchase [v]
SLAs
- Inbound hand-raiser: 10-minute first response
- Content MQL: 24-hour first response, 5–7 touches over 10 days
- SQL creation: within 24 hours of qualification
Ownership Marketing: [name] | SDR: [name] | Sales: [name] | CS: [name] | RevOps: [name] | Finance: [name]
KPIs
- Quality: MQL acceptance [x%], time-to-first-touch [x min]
- Throughput: MQL-to-SQL [x%], SQL-to-Opportunity [x%], win rate [x%]
Risks and mitigations
- Risk: [e.g., paid social lead quality] → Mitigation: Tighten form fields, pivot offer
- Risk: [e.g., SDR queue capacity] → Mitigation: Route overflow to live chat when queue exceeds 10
Decision asks
- Approve stage-level budget and SLA matrix
- Confirm owners and governance thresholds
Example (Filled)
Goal: $4.0M revenue | $20.0M pipeline needed at 20% win rate
Strategy: 3 plays per stage focused on MQL acceptance rate and faster SQL creation
Budget: Cap $500K | Contingency 10% | Discretionary $450K Stage split: Awareness $90K | Consideration $90K | MQL $135K | Conversion $90K | Post-purchase $45K
SLAs: Hand-raiser 10 min | Content MQL 24 hr | SQL creation within 24 hr of qualification
Owners: Marketing: Taylor | SDR: Jordan | Sales: Casey | CS: Alex | RevOps: Morgan | Finance: Sam
KPIs: MQL acceptance 65% | Time-to-first-touch 15 min | MQL-to-SQL 30% | SQL-to-Oppty 60% | Win rate 20%
Risks:
- Paid social lead quality → tighten form, switch offer
- SDR capacity → route to chat when queue exceeds 10
What Counts as Sign-Off
Verbal approval and signed slides are not enough. To meet FL2, secure written confirmation from each function:
- Finance: Budget by stage equals cap
- Sales and SDR leaders: SLAs and routing rules
- RevOps: Dashboard availability dates
- CS: Post-purchase plays confirmed
Watch for these drift signals: “let’s revisit next month,” no named owners on the one-pager, or open questions remaining on routing fields.
Operating Rules for the Quarter
Keep these visible throughout execution:
- Do not add new stages or change compensation credit rules mid-quarter. Optimize plays and SLAs first.
- Limit experiments to 10% of discretionary. For each new play you add, sunset one that isn’t performing.
- If any SLA cannot be measured in your CRM today, fix the fields before launch — not after.
- Keep the freeze window in the final 2 weeks. No new experiments. Let Sales close.
You now have a practical path to ship an omnichannel GTM this quarter: mapped touchpoints from awareness to post-purchase, MQL–SQL SLAs with owners and response times, and a stage-level budget inside your cap — all packaged for cross-functional sign-off.