Open Source GTM Playbooks: Our Entire Process, Free

Open source GTM playbooks are complete, step-by-step operational guides for building go-to-market infrastructure from scratch - covering everything from ICP research and data architecture to outbound launch sequences and reporting dashboards. This article shares the actual playbooks we use at GTME to build revenue systems for B2B companies, with nothing held back. The tools, the processes, the timelines, the templates - everything a GTM Engineer or revenue leader needs to build a modern go-to-market engine.

Why give this away? Two reasons. First, transparency builds trust. You can read these playbooks, implement them yourself, and generate real results without ever talking to us. Second, most companies that read this will realize that implementing it all properly requires significant time and expertise, and a portion of them will hire us to do it. That's the business model. No gates, no lead forms, no "download the PDF" capture pages. Just the playbook.

Playbook 1: ICP Research Playbook

Objective

Define your Ideal Customer Profile with enough specificity to drive targeting, messaging, and scoring decisions across all GTM systems.

Timeline: 5-7 Business Days

Step 1: Analyze Your Existing Customers (Day 1-2)

Start with what you already know. Pull your customer data and segment it.

Data to extract from your CRM:

• Company name, domain, industry
• Employee count, revenue (if available)
• Deal size (ACV)
• Sales cycle length (days from first touch to close)
• Churn status (still active, churned, expanded)
• Source (inbound, outbound, referral, event)
• Primary contact title and department

Analysis to perform:

1. Segment by deal outcome:

Segment: Best customers | Definition: Top 20% by ACV, still active, lowest churn | What to Analyze: What do they share?

Segment: Good customers | Definition: Active, average ACV, reasonable retention | What to Analyze: Common traits

Segment: Churned customers | Definition: Canceled or didn't renew | What to Analyze: Why did they leave?

Segment: Bad-fit customers | Definition: Low ACV, high support cost, or fast churn | What to Analyze: What made them bad fits?

1. Identify patterns across best customers:

- What industries are overrepresented? - What employee count range appears most? - What titles bought? (VP Sales? CTO? CEO?) - What was their stage/funding when they bought? - What technology were they using? - How did they find you?

1. Calculate unit economics by segment:

Metric: Average ACV | Best Customers: ? | Average: ? | Churned: ?

Metric: Sales cycle (days) | Best Customers: ? | Average: ? | Churned: ?

Metric: LTV (lifetime value) | Best Customers: ? | Average: ? | Churned: ?

Metric: CAC (cost to acquire) | Best Customers: ? | Average: ? | Churned: ?

Metric: LTV:CAC ratio | Best Customers: ? | Average: ? | Churned: ?

Tools: CRM export (HubSpot or Salesforce), spreadsheet for analysis

Step 2: Enrich Your Customer Data (Day 2-3)

Your CRM data is incomplete. Enrich it to find patterns you can't see with existing fields.

Run every customer through these enrichments:

• Firmographic: Apollo or Clearbit for employee count, revenue, industry, location, founding year
• Technographic: BuiltWith for tech stack at time of purchase
• Funding: Crunchbase for funding stage and amount when they became a customer
• Growth signals: LinkedIn for employee count change over last 12 months

Build an enriched customer analysis table:

Company: Customer A | Industry: B2B SaaS | Employees: 120 | Revenue: $15M | Tech Stack: HubSpot, Outreach | Funding Stage: Series B | ACV: $48K | LTV: $144K | Churn?: No

Company: Customer B | Industry: FinTech | Employees: 85 | Revenue: $10M | Tech Stack: Salesforce, Apollo | Funding Stage: Series A | ACV: $36K | LTV: $72K | Churn?: Yes

Company: ... | Industry: ... | Employees: ... | Revenue: ... | Tech Stack: ... | Funding Stage: ... | ACV: ... | LTV: ... | Churn?: ...

Step 3: Define Your ICP Framework (Day 3-4)

Synthesize customer analysis into a structured ICP definition.

ICP definition template:

``` PRIMARY ICP:

• Industry: [specific industries, not "B2B SaaS" but "B2B SaaS selling to mid-market"]
• Employee count: [range, e.g., 50-500]
• Revenue: [range if available, e.g., $5M-$50M ARR]
• Funding stage: [e.g., Series A through Series C]
• Geography: [e.g., US and Canada, English-speaking markets]
• Tech stack indicators: [e.g., uses HubSpot or Salesforce, has outbound tools]
• Growth signals: [e.g., hiring in sales/marketing, recently funded]
• Negative filters: [e.g., NOT government, NOT healthcare (HIPAA), NOT agencies]

TARGET PERSONAS (in priority order):

1. Primary buyer: [title, department, seniority level]

- What they care about: [top 3 pain points] - How they buy: [evaluation process, stakeholders involved]

1. Champion: [title, department]

- What they care about: [day-to-day problems] - How to engage: [what content/messaging resonates]

1. Technical evaluator: [title, department]

- What they evaluate: [specific criteria] - How to engage: [demo, technical content, proof of concept] ```

Step 4: Validate with Sales Team (Day 4-5)

Your data analysis shows patterns. Your sales team knows the stories behind the patterns.

Questions to ask your top 3 AEs:

1. Which types of deals close fastest and with least resistance?
2. Which deals do you hate working? What makes them painful?
3. When a prospect says "this is exactly what we need," what do they look like?
4. What's the most common reason deals stall or die?
5. What objections come up in every deal? Which ones kill deals?

Questions to ask your CS team:

1. Which customers are happiest and most engaged?
2. Which customers churn within the first year? What did they look like at signup?
3. Which customers expand? What triggers expansion?

Step 5: Size Your TAM/SAM/SOM (Day 5-6)

With your ICP defined, quantify how big your addressable market actually is.

Use Apollo or Clay to build a count:

Level: TAM (Total Addressable Market) | Definition: All companies that could theoretically use your product | Count Method: Apollo search with loose filters | Typical Range: 10,000-500,000

Level: SAM (Serviceable Addressable Market) | Definition: Companies matching your ICP firmographics | Count Method: Apollo search with ICP filters | Typical Range: 2,000-50,000

Level: SOM (Serviceable Obtainable Market) | Definition: Companies you can realistically reach and sell to | Count Method: SAM filtered by your actual reach capacity | Typical Range: 500-10,000

Step 6: Document and Distribute (Day 6-7)

Create a living ICP document that your entire GTM team references:

ICP document structure:

1. One-page summary (who we sell to, who we don't sell to)
2. Detailed firmographic criteria (with scoring weights)
3. Target personas (with messaging frameworks per persona)
4. Negative filters (explicit disqualification criteria)
5. Market sizing data (TAM/SAM/SOM)
6. Quarterly review schedule (ICP evolves as you learn)

Distribute to: Sales, marketing, product, customer success, and leadership. Everyone should be able to describe your ICP in one sentence.

Playbook 2: Data Infrastructure Setup

Objective

Build the data layer that powers enrichment, scoring, routing, and reporting for all GTM operations.

Timeline: 7-10 Business Days

Step 1: Audit Existing Data Stack (Day 1-2)

Inventory your current tools:

Category: CRM | Tool: HubSpot / Salesforce | Status: Active / Needs config | Data Quality: Clean / Messy | Integration Status: Connected to X, Y, Z

Category: Enrichment | Tool: Apollo / Clearbit / None | Status: Active / Inactive | Data Quality: Good / Stale | Integration Status: Connected to CRM?

Category: Outbound | Tool: Instantly / Outreach / None | Status: Active / Inactive | Data Quality: - | Integration Status: Connected to CRM?

Category: Marketing | Tool: HubSpot Marketing / Pardot | Status: Active / Inactive | Data Quality: - | Integration Status: Connected to CRM?

Category: Analytics | Tool: GA4 / Mixpanel / None | Status: Active / Inactive | Data Quality: - | Integration Status: -

Identify data gaps:

• Which CRM fields are less than 50% populated?
• Where is data entered manually that could be automated?
• What data sources exist but aren't connected?
• Where are duplicates most common?

Step 2: Design Your Data Schema (Day 2-4)

Define what data you need and where it lives.

Contact-level fields:

Field: First name, last name | Source: Form fill or enrichment | Update Frequency: On create | Required?: Yes

Field: Email (verified) | Source: Enrichment waterfall | Update Frequency: On create, re-verify quarterly | Required?: Yes

Field: Title | Source: Enrichment | Update Frequency: On create, update on enrichment refresh | Required?: Yes

Field: Seniority level | Source: Enrichment (derived) | Update Frequency: On create | Required?: Yes

Field: Department | Source: Enrichment | Update Frequency: On create | Required?: Yes

Field: LinkedIn URL | Source: Enrichment | Update Frequency: On create | Required?: Yes

Field: Phone (direct) | Source: Enrichment waterfall | Update Frequency: On create | Required?: No

Field: Lead source | Source: System-generated | Update Frequency: On create | Required?: Yes

Field: Lead score | Source: Calculated | Update Frequency: Real-time | Required?: Yes

Field: Lead status | Source: Manual + automated | Update Frequency: Ongoing | Required?: Yes

Company-level fields:

Field: Domain | Source: Form fill or enrichment | Update Frequency: On create | Required?: Yes

Field: Company name | Source: Enrichment | Update Frequency: On create | Required?: Yes

Field: Employee count | Source: Enrichment | Update Frequency: On create, refresh quarterly | Required?: Yes

Field: Industry | Source: Enrichment (standardized) | Update Frequency: On create | Required?: Yes

Field: Revenue range | Source: Enrichment | Update Frequency: On create, refresh quarterly | Required?: No

Field: Funding stage | Source: Crunchbase | Update Frequency: On create, refresh monthly | Required?: No

Field: Total funding | Source: Crunchbase | Update Frequency: On create, refresh monthly | Required?: No

Field: Tech stack | Source: BuiltWith | Update Frequency: On create, refresh quarterly | Required?: No

Field: HQ location | Source: Enrichment | Update Frequency: On create | Required?: Yes

Field: ICP tier | Source: Calculated | Update Frequency: On enrichment | Required?: Yes

Step 3: Configure CRM Properties (Day 3-5)

In HubSpot (or Salesforce), create custom properties:

1. Create all fields from the schema above that don't exist as default properties
2. Set field types correctly (number for employee count, dropdown for ICP tier, etc.)
3. Create property groups for organization (Enrichment Data, Scoring, Outbound Tracking)
4. Set required fields on deal creation (ensures sales reps fill in critical data)
5. Create calculated properties where applicable (days in current deal stage, etc.)

Standard lifecycle stage configuration:

Stage: Subscriber | Definition: Email subscriber, no other engagement | Triggers: Newsletter signup

Stage: Lead | Definition: Known contact, not yet qualified | Triggers: Form fill, imported list

Stage: Marketing Qualified Lead (MQL) | Definition: Meets basic criteria, engaged with content | Triggers: Score threshold + engagement

Stage: Sales Qualified Lead (SQL) | Definition: Confirmed ICP fit, expressed interest | Triggers: SDR or automation qualified

Stage: Opportunity | Definition: In active sales process | Triggers: Deal created in CRM

Stage: Customer | Definition: Closed-won | Triggers: Deal marked won

Stage: Evangelist | Definition: Active referrer or advocate | Triggers: Manual tag by CS

Step 4: Build Enrichment Pipelines (Day 5-7)

Set up Clay workspace with the following tables:

1. Inbound Enrichment Table - Triggered by webhook from CRM when new lead is created

- Auto-enriches contact and company - Auto-scores against ICP - Pushes enriched data back to CRM - Processing time target: under 60 seconds

1. Batch Enrichment Table - For processing imported lists

- Full enrichment waterfall (Workflows 1-5 from the Clay Cookbook) - Duplicate detection against CRM - Lead scoring and tiering - Export to CRM or outbound tool

1. Signal Detection Tables - Scheduled monitoring

- Funding signal table (weekly) - Hiring signal table (bi-weekly) - Job change table (monthly) - Tech stack change table (monthly)

Step 5: Build Integration Layer (Day 7-9)

Connect your tools into a unified data flow:

Critical integrations:

Integration: Clay -> HubSpot | Direction: One-way (push) | Method: Native integration | Purpose: Push enriched data to CRM

Integration: HubSpot -> Clay | Direction: Webhook trigger | Method: HubSpot workflow -> Clay webhook | Purpose: Trigger real-time enrichment

Integration: Instantly -> HubSpot | Direction: One-way (push) | Method: Native or Zapier | Purpose: Sync email engagement data

Integration: HubSpot -> Slack | Direction: One-way (push) | Method: Native integration | Purpose: Alerts for new leads, deal changes

Integration: Apollo -> Clay | Direction: One-way (pull) | Method: Clay enrichment column | Purpose: Pull contact and company data

Step 6: Data Hygiene Automation (Day 9-10)

Set up automated processes that keep your data clean:

1. Deduplication workflow: Run weekly, merge contacts with matching emails, merge companies with matching domains
2. Data standardization: Auto-format phone numbers, standardize job titles (VP vs. Vice President), normalize industry names
3. Stale record flagging: Mark contacts with no activity in 180+ days for review
4. Bounce cleanup: Auto-set status to "invalid email" when enrichment tools report bounce or invalid
5. Lifecycle stage progression: Automate stage changes based on engagement milestones

Playbook 3: Outbound Launch Sequence

Objective

Launch a production outbound program from zero to first meetings booked in 30 days.

Timeline: 21-30 Business Days (Domain Warming Is the Bottleneck)

Step 1: Domain Infrastructure (Day 1-3)

Purchase sending domains:

• Buy 5 domains to start (example: if main domain is acme.com, buy acme-team.com, getacme.com, tryacme.com, acmehq.com, acmeapp.com)
• Use registrars like Namecheap, Google Domains, or Cloudflare
• Cost: $10-15 per domain per year

Configure DNS for each domain:

• SPF record: authorize your sending platform (Instantly, Smartlead, Google Workspace)
• DKIM record: generate and add the DKIM key from your email provider
• DMARC record: start with p=none for monitoring, move to p=quarantine after 30 days
• Custom tracking domain: set up for each sending platform

Create email accounts:

• 3 Google Workspace accounts per domain (15 total)
• Use real-sounding names that match your team (jeff@, sarah@, mike@)
• Set up profile photos and email signatures
• Cost: $6/account/month = $90/month for 15 accounts

Step 2: Domain Warming (Day 1-28, Parallel with Other Steps)

Warming schedule:

Days: 1-7 | Emails Per Account Per Day: 5-10 | Warm Email Source: Warming tool (Instantly built-in or MailReach)

Days: 8-14 | Emails Per Account Per Day: 10-20 | Warm Email Source: Warming tool

Days: 15-21 | Emails Per Account Per Day: 15-25 | Warm Email Source: Warming tool + small test sends (10-15 real emails)

Days: 22-28 | Emails Per Account Per Day: 20-30 | Warm Email Source: Warming tool + campaign ramp (15-20 real emails)

Days: 29+ | Emails Per Account Per Day: 20-30 | Warm Email Source: Full production sending (keep warming running at 50% volume)

Key warming rules:

• Never skip warming. Starting cold from a new domain results in immediate spam filtering.
• Keep warming running indefinitely alongside campaign sends (reduces volume by ~50% but keeps warm).
• Monitor Google Postmaster Tools starting Day 14 for reputation signals.

Step 3: Build Target Lists (Day 3-10)

Using your ICP definition from Playbook 1:

1. Run Apollo search with ICP firmographic filters
2. Export companies matching your criteria (start with 500-1,000)
3. Run through Clay Company Enrichment Waterfall (Cookbook Workflow 1)
4. Run Tech Stack Detection (Cookbook Workflow 5)
5. Score and tier using Lead Scoring Calculator (Cookbook Workflow 12)
6. For Tier 1 and Tier 2 companies, Find Decision Makers (Cookbook Workflow 2)
7. Run Email Waterfall (Cookbook Workflow 3)
8. Run Duplicate Detection against CRM (Cookbook Workflow 14)

Target list sizes for initial launch:

Tier: Tier 1 | Companies: 50 | Contacts Per Company: 3-5 | Total Contacts: 150-250

Tier: Tier 2 | Companies: 150 | Contacts Per Company: 2-3 | Total Contacts: 300-450

Tier: Tier 3 | Companies: 300 | Contacts Per Company: 1-2 | Total Contacts: 300-600

Tier: Total | Companies: 500 | Contacts Per Company: 750-1,300 | Total Contacts:

Step 4: Create Messaging (Day 7-14)

Write 3 email variants per sequence step:

Step 1 (Initial outreach) - 3 variants:

• Variant A: Problem-agitation angle
• Variant B: Social proof / case study angle
• Variant C: Relevant insight / observation angle

Step 2 (Follow-up, Day 3-4) - 2 variants:

• Variant A: Quick bump with new angle
• Variant B: Value-add (share relevant resource)

Step 3 (Follow-up, Day 7-8) - 2 variants:

• Variant A: Third angle, different pain point
• Variant B: Social proof from similar company

Step 4 (Breakup, Day 12-14) - 1 variant:

• Clean breakup: acknowledge they're busy, leave door open, include booking link

Messaging guidelines:

• Keep every email under 80 words for step 1, under 60 words for follow-ups
• No images, no HTML, no more than 1 link per email
• Subject lines under 6 words
• Open with personalization (use AI email writer output for Tier 1-2)
• End with a specific question, not a generic CTA
• Include an unsubscribe line at the bottom of every email

Step 5: Launch Campaigns (Day 21-28)

Campaign structure in Instantly or Smartlead:

1. Create separate campaigns for each tier (different messaging depth)
2. Assign sending accounts (spread evenly across domains)
3. Set sending schedule: Monday-Friday, 8 AM - 11 AM and 1 PM - 3 PM in recipient timezone
4. Set daily send limits: 20-25 per account
5. Enable A/B testing on step 1 subject lines and body variants
6. Enable auto-reply detection and positive/negative classification
7. Set auto-pause on bounce or complaint thresholds

Ramp schedule:

Day: Day 21-23 | Sends Per Account: 10-15 | Total Daily Sends (15 accounts): 150-225

Day: Day 24-26 | Sends Per Account: 15-20 | Total Daily Sends (15 accounts): 225-300

Day: Day 27-30 | Sends Per Account: 20-25 | Total Daily Sends (15 accounts): 300-375

Day: Week 5+ | Sends Per Account: 25-30 | Total Daily Sends (15 accounts): 375-450

Step 6: Monitor and Optimize (Day 28+, Ongoing)

Daily checks:

• Bounce rate (pause any account above 3%)
• Spam complaint rate (pause any account above 0.08%)
• Reply rate by variant (identify winners/losers)

Weekly analysis:

• Reply rate and positive reply rate by campaign
• Meeting book rate by tier and variant
• A/B test results (declare winners at 200+ sends per variant)
• Deliverability health across all domains

Monthly optimization:

• Kill underperforming variants, create new ones
• Adjust ICP targeting based on response patterns
• Refresh lists (remove unresponsive, add new prospects)
• Review cost per meeting and pipeline generated

Playbook 4: Inbound Routing Setup

Objective

Build a system that instantly enriches, scores, and routes every inbound lead to the right person within 5 minutes.

Timeline: 5-7 Business Days

Step 1: Map Inbound Sources (Day 1)

Source: Demo request | Form/Entry Point: Website demo form | Current Handling: Manual assignment | Target Response Time: Under 5 minutes

Source: Contact form | Form/Entry Point: Website contact page | Current Handling: Shared inbox | Target Response Time: Under 15 minutes

Source: Free trial | Form/Entry Point: Product signup | Current Handling: Automated email only | Target Response Time: Under 5 minutes

Source: Content download | Form/Entry Point: Gated content forms | Current Handling: Marketing nurture | Target Response Time: Under 1 hour

Source: Chatbot | Form/Entry Point: Website chatbot | Current Handling: Real-time (if staffed) | Target Response Time: Real-time

Source: Webinar registration | Form/Entry Point: Webinar platform | Current Handling: Post-event follow-up | Target Response Time: Under 2 hours

Step 2: Build Instant Enrichment (Day 1-3)

Set up Clay webhook triggered by HubSpot form submission:

When any form is submitted:

1. Verify email (ZeroBounce) - reject obvious fakes
2. Enrich contact (Apollo or Clearbit) - title, seniority, LinkedIn
3. Enrich company (Clearbit or Apollo) - size, industry, tech stack, funding
4. Calculate lead score based on ICP fit
5. Determine tier: Hot, Warm, Nurture, or Disqualified
6. Push all enrichment data back to HubSpot contact record

Processing time target: under 60 seconds.

Step 3: Configure Routing Rules (Day 3-4)

Routing logic (implement in HubSpot workflows or Chili Piper):

Condition: Hot lead (Tier 1 ICP fit + demo request) | Route To: Best available AE | Method: Round-robin with availability check

Condition: Warm lead (Tier 2 ICP fit + demo request) | Route To: Available AE | Method: Round-robin

Condition: Hot/Warm lead + contact form | Route To: SDR or AE | Method: Round-robin

Condition: Nurture lead (Tier 3 + any form) | Route To: Marketing automation | Method: Drip sequence

Condition: Disqualified (poor ICP fit) | Route To: Auto-response | Method: Redirect to self-serve

Condition: Existing customer | Route To: Account owner | Method: Direct assignment

Condition: Existing prospect with open deal | Route To: Deal owner | Method: Direct assignment

Routing safeguards:

• If primary assignee doesn't respond within 5 minutes, escalate to next available
• If no one is available (after hours), auto-send booking link email and queue for next business day
• Log all routing decisions for audit and optimization

Step 4: Set Up Notifications (Day 4-5)

Notification system:

Event: Hot lead assigned | Channel: Slack DM | Recipient: Assigned AE | Content: Full enrichment summary + booking link

Event: Hot lead assigned | Channel: Email | Recipient: Assigned AE | Content: Same as Slack (backup)

Event: Hot lead not responded in 5 min | Channel: Slack channel | Recipient: Sales manager | Content: Escalation alert

Event: Demo booked | Channel: Slack channel | Recipient: Team | Content: Celebration + meeting details

Event: High-value lead (Tier 1) | Channel: Slack DM | Recipient: Sales leader | Content: Executive visibility

Slack notification template: ``` New Hot Lead Assigned to You

Name: [Full Name] Title: [Title] at [Company] Company Size: [Employee Count] employees Industry: [Industry] Funding: [Stage] - $[Amount] raised Tech Stack: [Relevant tools] Lead Score: [Score]/100 Form: [Which form they filled out] Message: [If they left a message]

Book the meeting: [Calendar link] View in HubSpot: [CRM link] ```

Step 5: Build Booking Experience (Day 5-6)

For Hot and Warm leads:

1. Immediate email with calendar booking link (Chili Piper, Calendly, or HubSpot Meetings)
2. Calendar link routes to assigned rep's availability
3. Confirmation email includes meeting agenda and what to expect
4. Calendar invite includes prep materials and rep's LinkedIn profile

For Nurture leads:

1. Thank-you email with relevant content
2. Enroll in email drip sequence (3-5 emails over 2 weeks)
3. Re-score after engagement with drip sequence
4. Promote to Warm if engagement threshold is met

Step 6: Measure and Optimize (Day 7, Ongoing)

Track these metrics weekly:

Metric: Time to first response | Target: Under 5 minutes | How to Measure: HubSpot timestamps (form submit to first rep action)

Metric: Inbound-to-meeting rate (Hot) | Target: 40-60% | How to Measure: Meetings booked / hot leads received

Metric: Inbound-to-meeting rate (Warm) | Target: 20-35% | How to Measure: Meetings booked / warm leads received

Metric: Routing accuracy | Target: 95%+ | How to Measure: Audit sample of 20 leads/week

Metric: Enrichment fill rate | Target: 90%+ | How to Measure: Check enrichment data completeness

Playbook 5: CRM Configuration Guide

Objective

Configure HubSpot (or Salesforce) to support all GTM operations with clean data, useful automation, and actionable reporting.

Timeline: 7-10 Business Days

Step 1: Property and Field Setup (Day 1-3)

Create or configure these property groups:

Contact properties:

• Standard: name, email, phone, title, lifecycle stage
• Enrichment: seniority, department, LinkedIn URL, enrichment date
• Scoring: lead score, ICP tier, intent score
• Outbound: last outbound date, outbound campaign, outbound status
• Source tracking: original source, original campaign, referring URL

Company properties:

• Standard: name, domain, industry, employee count
• Enrichment: revenue range, funding stage, total funding, tech stack, year founded
• Scoring: company ICP score, company tier
• Account status: customer status, account owner, account tier

Deal properties:

• Standard: deal name, amount, stage, close date, pipeline
• Tracking: days in current stage, last activity date, next step
• Source: deal source (inbound/outbound/referral), original campaign

Step 2: Pipeline Configuration (Day 3-4)

Standard B2B sales pipeline:

Stage: Qualified | Definition: Lead confirmed as ICP fit, meeting scheduled | Exit Criteria: Meeting completed | Expected Duration: 1-5 days

Stage: Discovery | Definition: Initial meeting completed, needs identified | Exit Criteria: Mutual agreement to continue | Expected Duration: 5-14 days

Stage: Evaluation | Definition: Product demo or trial, technical assessment | Exit Criteria: Positive evaluation, stakeholders aligned | Expected Duration: 14-30 days

Stage: Proposal | Definition: Pricing and terms presented | Exit Criteria: Verbal agreement or counter-proposal | Expected Duration: 7-14 days

Stage: Negotiation | Definition: Terms being finalized | Exit Criteria: Signed contract | Expected Duration: 7-21 days

Stage: Closed Won | Definition: Contract signed | Exit Criteria: - | Expected Duration: -

Stage: Closed Lost | Definition: Deal dead, documented reason | Exit Criteria: - | Expected Duration: -

Step 3: Automation Setup (Day 4-6)

Essential HubSpot workflows:

1. Lifecycle stage progression: Automatically advance contacts through lifecycle stages based on engagement milestones
2. Lead assignment: Route new leads based on territory, segment, and availability (see Playbook 4)
3. Deal stage task creation: Auto-create tasks when deals enter new stages (e.g., "Send proposal" when entering Proposal stage)
4. Stale deal alerts: Notify rep and manager when deals have no activity for stage-appropriate duration
5. Win/loss notification: Alert team on Slack when deals close (won or lost)
6. Data hygiene: Auto-merge duplicates, standardize fields, flag incomplete records
7. Re-engagement: Trigger re-engagement sequence for contacts with no activity in 90+ days

Step 4: Reporting Dashboards (Day 6-8)

Build three core dashboards:

Dashboard 1: Pipeline Health

• Total pipeline value by stage
• Pipeline created this month vs. goal
• Deals by stage with aging indicators
• Win rate by stage (conversion rate between stages)
• Average deal size trend (monthly)
• Pipeline velocity (average days per stage)

Dashboard 2: Activity and Outbound Performance

• Emails sent, opened, replied (by campaign)
• Meetings booked (by source: inbound, outbound, referral)
• Reply rate and positive reply rate trends
• Cost per meeting by source
• Sequence performance comparison

Dashboard 3: Revenue and Forecasting

• Closed won revenue vs. target
• Weighted pipeline (deal value x stage probability)
• Forecast accuracy (last month's forecast vs. actual)
• Revenue by source (inbound, outbound, expansion, referral)
• Average sales cycle length trend
• Win rate trend (monthly)

Step 5: User Training and Documentation (Day 8-10)

Create CRM usage documentation covering:

1. How to create and update contacts (required fields, data standards)
2. How to create and manage deals (stage definitions, exit criteria)
3. How to log activities (calls, meetings, emails)
4. How to use dashboards and reports
5. What's automated (so reps don't duplicate effort)
6. Common mistakes and how to avoid them

Training sessions:

• 60-minute session for sales team: CRM workflow, deal management, dashboards
• 30-minute session for marketing: lead source tracking, campaign attribution
• 30-minute session for leadership: reporting dashboards, forecast reviews

Playbook 6: Reporting Dashboard Setup

Objective

Build a reporting layer that gives leadership visibility into GTM performance, enables data-driven decisions, and holds the team accountable to targets.

Timeline: 5-7 Business Days

Step 1: Define KPI Framework (Day 1)

Executive dashboard KPIs:

KPI: Pipeline created | Definition: Total new pipeline value this period | Target: Monthly target | Frequency: Weekly

KPI: Pipeline velocity | Definition: Average days from creation to close | Target: Benchmark by segment | Frequency: Monthly

KPI: Win rate | Definition: Closed won / (closed won + closed lost) | Target: Target by segment | Frequency: Monthly

KPI: Revenue closed | Definition: Total closed-won revenue | Target: Monthly/quarterly target | Frequency: Weekly

KPI: CAC (Customer Acquisition Cost) | Definition: Total sales + marketing spend / new customers | Target: Target ratio | Frequency: Monthly

KPI: LTV:CAC ratio | Definition: Average customer lifetime value / CAC | Target: 3:1 minimum | Frequency: Quarterly

KPI: Meetings booked | Definition: Total meetings from all sources | Target: Weekly target | Frequency: Weekly

KPI: Cost per meeting | Definition: Total outbound spend / meetings booked | Target: Target by channel | Frequency: Monthly

Outbound-specific KPIs:

KPI: Emails sent | Definition: Total outbound emails delivered | Target: Weekly target | Frequency: Daily

KPI: Reply rate | Definition: Total replies / emails delivered | Target: 5-10% | Frequency: Weekly

KPI: Positive reply rate | Definition: Positive replies / emails delivered | Target: 2-4% | Frequency: Weekly

KPI: Meeting book rate | Definition: Meetings / emails delivered | Target: 1.5-3% | Frequency: Weekly

KPI: Deliverability rate | Definition: Delivered / sent | Target: 95%+ | Frequency: Daily

KPI: Bounce rate | Definition: Bounced / sent | Target: Below 2% | Frequency: Daily

KPI: Spam complaint rate | Definition: Complaints / delivered | Target: Below 0.05% | Frequency: Daily

Step 2: Build in HubSpot (Day 2-4)

Report types to create:

1. Funnel reports: Lead -> MQL -> SQL -> Opportunity -> Customer conversion rates
2. Attribution reports: Revenue and pipeline by source (inbound, outbound, referral, event)
3. Activity reports: Emails, calls, meetings by rep and team
4. Pipeline reports: Pipeline by stage, aging, velocity
5. Revenue reports: Closed revenue by month, quarter, segment
6. Forecast reports: Weighted pipeline vs. target

Step 3: Build External Dashboard (Day 4-6, If Needed)

For more complex reporting needs, supplement HubSpot with Metabase, Looker, or Google Sheets:

When you need external dashboards:

• Combining data from multiple tools (HubSpot + Instantly + Clay + Stripe)
• Custom cohort analysis not supported by HubSpot
• Real-time outbound performance monitoring with granular detail
• Board-level reporting with specific formatting requirements

Recommended approach:

1. Export HubSpot data via API or scheduled exports
2. Pull Instantly/Smartlead data via their APIs
3. Combine in a lightweight data warehouse (BigQuery, Snowflake) or even Google Sheets for smaller teams
4. Build dashboards in Metabase (free, self-hosted) or Looker

Step 4: Set Up Automated Reporting (Day 5-7)

Weekly automated reports:

Report: Pipeline weekly summary | Audience: Sales team + leadership | Delivery: Slack + email (Monday AM) | Content: New pipeline, closed deals, at-risk deals, key metrics

Report: Outbound performance | Audience: GTM Engineer + sales leadership | Delivery: Slack (Friday PM) | Content: Reply rates, meeting book rates, A/B test results, deliverability

Report: Inbound summary | Audience: Marketing + sales | Delivery: Email (Monday AM) | Content: Inbound leads by source, conversion rates, response times

Monthly automated reports:

Report: Revenue review | Audience: Leadership | Delivery: Slide deck (first week of month) | Content: Revenue vs. target, pipeline health, forecast, channel performance

Report: GTM system performance | Audience: GTM Engineer + leadership | Delivery: Document | Content: System uptime, enrichment costs, automation performance, optimization opportunities

Report: ICP validation | Audience: Sales + marketing + product | Delivery: Meeting agenda | Content: Win/loss analysis, ICP accuracy, recommended adjustments

Step 5: Review Cadence (Ongoing)

Implement these recurring reviews:

Meeting: Pipeline review | Frequency: Weekly (30 min) | Attendees: Sales team + leadership | Agenda: Deal updates, forecasts, blockers

Meeting: Outbound standup | Frequency: Weekly (15 min) | Attendees: GTM Engineer + sales | Agenda: Campaign performance, A/B results, next tests

Meeting: Revenue review | Frequency: Monthly (60 min) | Attendees: Full GTM team + leadership | Agenda: Monthly numbers, channel analysis, ICP review

Meeting: Quarterly planning | Frequency: Quarterly (2 hours) | Attendees: GTM leadership | Agenda: Target setting, resource allocation, strategy adjustments

Implementation Priority Matrix

If you can't do everything at once, prioritize based on your biggest gap:

Situation: No outbound program | Start With: Playbook 1 -> 3 -> 2 | Then: Playbook 5 -> 6 | Then: Playbook 4

Situation: Outbound underperforming | Start With: Playbook 2 -> 1 (validate) | Then: Playbook 3 (rebuild) | Then: Playbook 6

Situation: Inbound leads being wasted | Start With: Playbook 4 -> 2 | Then: Playbook 5 -> 6 | Then: Playbook 3

Situation: CRM is a mess | Start With: Playbook 5 -> 2 | Then: Playbook 6 -> 4 | Then: Playbook 1 -> 3

Situation: Need better reporting | Start With: Playbook 6 -> 5 | Then: Playbook 2 | Then: Playbook 1 -> 3 -> 4

Situation: Starting completely fresh | Start With: Playbook 1 -> 2 -> 5 | Then: Playbook 3 -> 4 | Then: Playbook 6

FAQ

How long does it take to implement all six playbooks?

Implementing all six playbooks sequentially takes approximately 8-12 weeks for a company with existing CRM infrastructure, or 12-16 weeks when starting from scratch. The biggest bottleneck is domain warming (21-28 days in Playbook 3), which should start on Day 1 regardless of which playbook you begin with. Most companies see initial results (first meetings from outbound) within 30-35 days if they start Playbooks 1, 2, and 3 in parallel.

Can I implement these without a GTM Engineer?

A technically comfortable RevOps professional or growth marketer can implement Playbooks 1, 4, 5, and 6 without engineering support. Playbooks 2 and 3 require someone comfortable with Clay, APIs, and email infrastructure - either a GTM Engineer, a technical marketing ops person, or an agency. If you don't have internal technical capability, agencies like GTME implement the full playbook set in 6-8 weeks.

How much does the full tool stack cost?

The minimum viable tool stack for all six playbooks costs approximately $1,500-3,000/month. This includes Clay ($500-1,000), Instantly or Smartlead ($200-400), Apollo ($200-400), email verification ($50-100), Google Workspace for sending domains ($90-150), and HubSpot (free CRM or $800+ for Operations Hub). Advanced setups with intent data, ABM advertising, and premium enrichment providers can reach $5,000-15,000/month.

How often should I update these playbooks?

Review and update your ICP definition (Playbook 1) quarterly based on new win/loss data. Review data infrastructure (Playbook 2) monthly for data quality and enrichment coverage. Optimize outbound campaigns (Playbook 3) weekly based on performance data. Review routing rules (Playbook 4) monthly based on conversion metrics. Update CRM configuration (Playbook 5) quarterly as processes evolve. Refresh reporting dashboards (Playbook 6) monthly to ensure metrics stay relevant and accurate.

What's the difference between following these playbooks and hiring GTME?

These playbooks give you the same strategic framework and process that we follow at GTME. The difference is execution speed, depth of implementation, and ongoing optimization. A company implementing independently typically takes 2-3x longer, encounters more integration issues (which we've already solved for past clients), and has less benchmark data to calibrate against. Hiring GTME gets you faster implementation (4-8 weeks), production-tested workflows, and ongoing optimization based on cross-client performance data. Many companies start with these playbooks, implement what they can, and engage us for the complex pieces or ongoing management.