GTM Revenue Architecture

This playbook defines the complete go-to-market system, from lead acquisition through conversion. It covers every stage including sourcing, enrichment, scoring, AI personalization, outreach, and deliverability protection. The system is designed with privacy first, deliverability protection, hyper-personalization, and safeguards throughout.

System Architecture

Part 1: Lead Sourcing

Apollo.io (Primary Outbound Source)

Purpose: Company and contact discovery, enrichment, and outreach sequencing. API rate limit: 10,000 calls per month on base plan.

Filters to Use

RB2B (Website Visitors)

Purpose: Capture inbound intent from website visitors. Script placed on all pages captures company, role, pages visited, and time on site. Data pushed to HubSpot and Clay.

RB2B Processing Flow

1. RB2B identifies company from IP address
2. RB2B estimates role from behavior patterns
3. Signal pushed to Clay via webhook
4. Clay enriches with full firmographics
5. Scoring engine calculates intent
6. High-intent visitors routed to sales

LinkedIn Sales Navigator

Purpose: Relationship intelligence and warm introductions. Manual process: identify target accounts, find connections at target companies, track updates, build relationship before outreach.

Lead Sourcing Checklist

• Apollo account configured with target filters
• Icypeas connected to Clay webhook
• Trigify.io triggers configured
• RB2B script installed and tested
• LinkedIn Sales Navigator lists defined
• Competitor list configured in blocklist
• Deduplication rules in place

Part 2: Data Enrichment

Clay as Enrichment Hub

Clay orchestrates data from multiple providers and applies transformations. It is the central hub for all enrichment with access to 50+ data providers.

Why Clay

• Single interface for all data providers
• Custom formulas for data transformation
• Webhook integrations for automation
• Built-in AI for enrichment logic
• Data never leaves your control

Data Providers

Breeze Intelligence (formerly Clearbit)

Company and person data enrichment, now part of HubSpot's Breeze AI suite. Requires active HubSpot subscription.

Note: Credits expire monthly (no rollover). ~$0.45/credit.

Apollo

Provides contact and engagement data including email verification with status types: inbox_ready (high deliverability), accept_all_mailserver (medium), bounced (do not use), unknown (verify with secondary tool).

Dropcontact

GDPR-compliant enrichment with explicit consent. Data deleted on request. Email verification, phone number, LinkedIn profile, company data.

Technographics (What Tools Companies Use)

Technographic Personalization Use Cases

Enrichment Checklist

• Clay account with all providers connected
• Breeze Intelligence API configured and tested
• Apollo API configured and tested
• Dropcontact GDPR compliance confirmed
• BuiltWith technographics enabled
• Email verification step configured
• Deduplication formulas in place
• Fallback logic for failed enrichment

Part 3: Lead Scoring

Lead Score = Intent Score + Firmographic Score + Technographic Score + Behavioral Score

Intent Score (0-40 points)

Firmographic Score (0-30 points)

Technographic Score (0-20 points)

Routing Thresholds

Part 4: Hyper-Personalization with Local LLM

Privacy Architecture

The problem with SaaS AI services: sending lead data means that data leaves your control. Sensitive company information, contact details, and strategy goes to third parties.

Ollama Setup

# macOS
brew install ollama

# Start Ollama
ollama serve

# Pull models
ollama pull llama3
ollama pull phi3
ollama pull mistral

# API endpoint
POST http://localhost:11434/api/generate

Personalization Prompts

Initial Outreach (Cold Email)

You are an expert sales copywriter. Write a personalized cold email.

Lead Information:
- Name: {first_name}
- Title: {title}
- Company: {company_name}
- Company Size: {employee_count} employees
- Industry: {industry}
- Funding Stage: {funding_stage}
- Recent News: {recent_news}
- Technologies: {tech_stack}
- Pain Points: {inferred_pain_points}

Requirements:
- Length: 50-100 words
- Tone: Professional but conversational
- Include specific reference to their company/situation
- Mention a relevant pain point
- Clear CTA (meeting request or reply)
- No generic phrases like "I noticed your company"

Output only the email body.

Personalization Data Inputs

Personalization Checklist

• Ollama installed and running
• Primary model downloaded (Llama-3 or Mistral)
• API endpoint tested
• Clay integration configured (HTTP request to Ollama)
• Prompt templates documented
• Output validation in place
• Rate limiting configured

Part 5: Email Sending Infrastructure

Multi-Account Strategy

Sending all emails from one account or domain destroys deliverability. Email providers detect patterns and flag accounts that send too much, too fast, or too similarly.

The Rotation Matrix

Domain Strategy

Primary Branded Domains (Reply Only)

Used for: Receiving replies, warm follow-ups after response, VIP prospects, long-term relationship emails. 1-2 domains only. Do not send cold email from these.

Secondary Sending Domains (Cold Outreach)

Used for: All cold email campaigns. These carry the reputation risk. If they burn, you have 35-40 more. Never cluster mailboxes on the same domain.

Primary (reply only):
- listlab.com

Secondary Sending Domains (35-40 total, 2-3 mailboxes each):
- send.getlistlab.com (2-3 mailboxes)
- mail.listlab.io (2-3 mailboxes)
- outbound.listlab.co (2-3 mailboxes)
- contact.getlistlab.com (2-3 mailboxes)
- [continues for 35-40 domains total]

Domain Registration Tips

• Register domains with different registrars when possible
• Use slightly varied WHOIS information where possible
• Set up identical DNS (SPF, DKIM, DMARC) on all domains
• Never send from domains that share obvious patterns (domain1.com, domain2.com)

IP Strategy

Use dedicated IPs only. Shared IPs mean other people's bad practices affect your deliverability.

IP Rotation

With 3-5 IPs and 100 mailboxes, distribute mailboxes across IPs. If one IP gets flagged, remove it from rotation while it recovers. The remaining IPs continue operations.

Infrastructure Scale

Safe high-volume cold email requires significant infrastructure investment. This is not optional if you want to protect deliverability at scale.

Why This Scale Matters

Sending 30 emails/day from 100 mailboxes = 3,000 potential emails/day. Combined with strict per-mailbox limits, this protects against single-point failures. If one mailbox gets flagged, you lose 1% of capacity, not 100%.

Mailbox Daily Limits (Conservative)

These limits are lower than platform maximums because cold email is detected and penalized more aggressively. Better to send less from more mailboxes than more from fewer mailboxes.

No Tracking (Plain Text Only)

Sending Platforms

Instantly.ai (Primary Platform)

Use for: All cold email campaigns. Provides warmup network, mailbox rotation, campaign management, and reply routing.

• Warmup feature sends 10 emails/day automatically
• Mailbox rotation distributes volume across infrastructure
• Unibox consolidates all replies for easy management
• Campaign controls enforce per-mailbox limits

Smartlead.ai (Supplementary)

Use for: Lower volume, higher personalization, multi-channel sequences (email + LinkedIn), more control over individual mailbox settings.

Slack Automation (Rep Notifications)

Real-time Slack notifications ensure immediate rep follow-up on engaged leads.

• Positive reply received: Notify assigned rep in Slack with lead details
• Meeting booked: Alert sales team and create calendar event
• Hot lead detected: Immediate Slack to founder channel
• Negative reply: Log to suppression, no further action needed

# Example Slack webhook payload for positive reply
{
  "channel": "#sales-alerts",
  "text": "New reply from lead",
  "blocks": [
    {
      "type": "section",
      "text": {
        "type": "mrkdwn",
        "text": "*Positive Reply Detected*\n:email: {lead_email}\n:building: {company_name}\n:hand: Assigned to: @{rep_name}"
      }
    }
  ]
}

Deliverability Safeguards

Essential Settings

• SPF records configured for all sending domains
• DKIM signatures enabled
• DMARC policy set (start with "none", move to "quarantine")
• Postmaster tools configured (Google, Microsoft)
• No tracking pixels or click redirect links
• Plain text emails or minimal HTML only
• Physical address in footer (CAN-SPAM requirement)

Warm-Up Protocol (Instantly)

Use Instantly's built-in warmup feature for all mailboxes. This sends realistic reply-chain emails using Instantly's network of other accounts, building natural sender reputation over 4-6 weeks before any cold emails go out.

Pre-Warmed Domains Exception

If you have existing warmed domains with established reputation, they can bypass the warmup phase. New domains and mailboxes always go through the full warmup cycle.

Accelerated Warmup Options

Standard 4-6 week warmup may be too slow. Options to accelerate safely:

Option 1: Scale Infrastructure (Recommended)

More domains and mailboxes means more parallel warmup capacity. Launch with full infrastructure day one.

Result: 200 mailboxes x 20 emails (post-warmup week 1) = 4,000 emails/day potential. Each domain warms in parallel. Launch with domains staggered by 1-2 weeks.

Recommended Approach for Q2 2026

Scale infrastructure for fastest safe ramp:

1. Start NOW with 60-80 domains in Instantly warmup
2. Scale dedicated IPs to 10 for parallel warmup capacity
3. Stagger new domains: 10-15 per week until full capacity
4. Target: 2,000-3,000 emails/day by launch week

Reply Rate Metrics (No Open Tracking)

Open tracking is disabled because tracked pixels hurt deliverability. Reply rate is the primary engagement signal.

Reply Classification

Not all replies are equal. Classify and route accordingly:

Sending Infrastructure Checklist

• ~100 mailboxes across 35-40 secondary domains created
• 2-3 mailboxes per domain maximum
• 3-5 dedicated IPs provisioned
• Primary branded domains configured (for replies only)
• SPF, DKIM, DMARC configured for all domains
• Google Postmaster access enabled
• Microsoft SNDS access enabled
• Instantly warmup enabled: 10 emails/day for 4-6 weeks
• Per-mailbox limits set: 10 (week 1-2), 20 (week 3-4), 30 max (week 5+)
• Reply routing to Unibox configured
• No tracking pixels or redirect links in email templates

Part 6: CRM Integration

HubSpot (Primary CRM)

Purpose: Marketing automation, lead management, analytics.

Lead Flow to HubSpot

1. Clay receives lead from webhook
2. Webhook sends to HubSpot API
3. Create or update contact
4. Apply scoring via workflow
5. Route based on score (Hot → Warm → Qualified → Cool → Cold)

HubSpot Properties to Sync

Salesforce (Sales Team CRM)

Purpose: Sales pipeline management, opportunity tracking. Hot leads pushed as Leads, sales creates Opportunities, stage updates sync back to HubSpot, closed-won triggers revenue attribution.

Part 7: Complete Workflow Example

Full Sequence: Cold Lead to First Response

T+0: Lead Identified

RB2B detects website visitor from target company. Webhook to Clay. Data: Company domain, behavioral signals.

T+0:05: Enrichment Begins

Clay receives lead, calls Breeze Intelligence (85% confidence), calls Apollo for email verification (valid). Enrichment complete. Output: Full firmographics, technographics, verified email.

T+0:10: Scoring

Intent signals: Pricing page visit (+10). Firmographics: 250 employees, Series B (+15). Technographics: Uses Salesforce, HubSpot (+5). Behavioral: 2 content downloads (+10). Total Score: 40. Routing: Qualified Lead.

T+0:15: Personalization (Local LLM)

Ollama receives prompt with all lead data. LLM generates personalized email (runs locally). Output: Custom email, 75 words. Data never left your computer.

T+0:20: Email Queued

Enriched + scored + personalized lead sent to Instantly. Instantly assigns to least-loaded mailbox. Domain rotation applied. Email scheduled for optimal send window.

T+24: Email Sent

Sent from: mailbox3@send.getlistlab.com. Via: Instantly campaign. Plain text email with simple reply CTA. No tracking pixels or redirect links.

T+48-120: Lead Engages

Lead reads email and replies directly. Instantly routes reply to Unibox. Slack notification sent to assigned rep with lead details. SDR books meeting. Lead lifecycle: MQL → SQL → Meeting Booked.

Part 8: Reply Handling & Auto-Reply Detection

Reply Routing

All replies route to Instantly Unibox for unified management. Replies are classified and routed automatically.

Reply Classification Logic

1. Parse reply content
2. Check for auto-reply patterns (OOO, OOF, vacation)
3. If auto-reply: set follow-up reminder for return date
4. If negative reply: add to suppression immediately
5. If unsubscribe request: immediate suppression, compliance log
6. If positive reply: route to assigned rep via Slack

Auto-Reply Patterns

Positive Reply Routing

Positive replies trigger immediate Slack notification to assigned rep.

1. Reply detected in Unibox
2. Content analyzed for sentiment
3. Positive sentiment confirmed
4. Slack webhook fires to rep's channel
5. Rep has 15 minutes to acknowledge
6. Escalate to manager if no response

Slack Notification Automation

Configure Slack notifications via Instantly's webhook integration or Zapier for instant alerts.

Notification Triggers

Slack Message Format

{
  "channel": "#sales-alerts",
  "blocks": [
    {
      "type": "header",
      "text": { "type": "plain_text", "text": "🎯 New Positive Reply!" }
    },
    {
      "type": "section",
      "fields": [
        { "type": "mrkdwn", "text": "*Lead:* {{lead_name}}" },
        { "type": "mrkdwn", "text": "*Company:* {{company}}" }
      ]
    },
    {
      "type": "section",
      "text": { "type": "mrkdwn", "text": "{{reply_snippet}}" }
    },
    {
      "type": "actions",
      "elements": [
        { "type": "button", "text": "View in HubSpot", "url": "{{hubspot_url}}" }
      ]
    }
  ]
}

Response SLA

Accelerated Warmup Options

If standard 4-6 week warmup is too slow, consider these options:

Option 1: Additional Infrastructure

Scale up dedicated IPs and mailboxes for faster warmup.

• Additional IPs: 5-10 more dedicated IPs
• Mailboxes: 50-100 additional per domain
• Cost: ~$500-1000/month
• Benefit: Parallel warmup, faster scaling

Option 2: Phased Launch

Launch with existing warmed domains first, add new domains over time.

• Approach: Use 5-10 warmed domains initially
• Scaling: Add 5 new domains weekly
• Benefit: No additional cost
• Tradeoff: Slower total volume growth

Part 9: Sequence Design & Cadence

Email Sequence Structure

Each sequence consists of multiple touchpoints over defined time intervals.

Standard Nurture Sequence (8 weeks)

Cadence Optimization

Send times affect reply rates. Test and optimize based on your audience.

A/B Testing Framework

Test one variable at a time to isolate impact.

Rule: Minimum 100 data points before declaring winner. Statistical significance required.

Part 10: List Hygiene & Data Quality

List Acquisition Standards

High-quality lists produce better engagement and protect sender reputation.

Approved Sources

• Apollo.io (verified business emails)
• Breeze Intelligence (company-verified contacts)
• LinkedIn Sales Navigator exports
• Event attendee lists (with consent)
• Inbound signups (explicit opt-in)

Prohibited Sources

• Purchased lists from unknown vendors
• Scraped email addresses
• Free email domains (gmail, yahoo, etc.)
• Role-based emails (info@, sales@, admin@)

List Hygiene Schedule

Engagement Windows

Contacts have a finite engagement window before becoming stale.

Part 11: Budget & Capacity Planning

Primary Domain Note

list-lab.org is the primary branded domain. Used for replies, customer communication, and relationship emails only. Never used for cold outreach.

Monthly Tool Budget (Launch Phase)

Prices verified from official vendor pricing pages (March 2026).

Apollo.io Pricing (Verified from apollo.io/pricing)

Instantly.ai Pricing (Verified from instantly.ai/pricing)

HubSpot Pricing (Verified from hubspot.com/pricing)

Capacity Planning

Match email volume to Instantly plan limits and infrastructure capacity to protect deliverability.

Volume Targets by Phase

Lead Volume Requirements

Calculate required leads to hit volume targets.

Unit Economics

Track cost per lead and cost per positive reply to ensure efficient spend.

Scaling Triggers

Know when to scale infrastructure based on performance metrics.

Part 12: SLA Definitions & Incident Response

System SLAs

Define expected uptime and response times for each component.

Incident Severity Levels

Incident Response Playbook

P0: Complete Email Failure

1. Check Instantly status page immediately
2. Verify SMTP credentials and domain settings
3. Check for account suspension or rate limiting
4. If platform issue: contact Instantly support
5. If account issue: resolve and retry
6. Document incident and root cause

P1: Enrichment Failure

1. Check Clay system status
2. Verify API keys and permissions
3. Switch to backup enrichment providers
4. Queue leads for later processing
5. Do not send without enrichment data

P1: Reputation Damage

1. Immediately pause affected domains
2. Identify root cause (content, volume, list quality)
3. Do not use affected domains for 2-4 weeks
4. Scale up alternative domains
5. Monitor Google Postmaster for recovery

Rollback Procedures

If a new campaign or change causes issues, rollback immediately.

• Campaign rollback: Pause campaign in Instantly, revert to previous version
• Config rollback: Revert to previous configuration backup
• Domain rollback: Remove domain from rotation, reassign mailboxes
• Template rollback: Restore previous version from version history

Monitoring & Observability

Track system health and performance metrics.

Part 13: Safeguards & Risk Management

Deliverability Protection

Compliance Safeguards

US Regulations (Primary)

International Regulations

Consent Management

Consent is the foundation of compliant outreach. Track and document all consent signals.

Data Privacy & Handling

US-based operations with global outreach requires careful data handling.

• Data residency: US-based cloud infrastructure (AWS US regions)
• Data minimization: Only collect fields needed for outreach
• Encryption: TLS in transit, AES-256 at rest
• Access control: Role-based access, audit logs
• Vendor assessment: All tools reviewed for SOC 2 compliance

System Failure Handling

Monitoring & Alerts

Real-Time Alerts

• Bounce rate >5%
• Complaint rate >0.1%
• API failures >10%
• Unusual volume changes

Daily Review

• Domain reputation scores
• IP reputation scores
• Open and reply rates by domain
• Top performing content
• Bottom performing content

Weekly Review

• Campaign performance
• List quality metrics
• Scoring model accuracy
• Sequence engagement

Tool Inventory

Prices verified from official vendor pricing pages (March 2026).

Lead Sourcing & Data

Enrichment & Data Quality

Email Sending

CRM & Operations

Decision Framework

Should We Build This?

Before implementing any new tool or workflow, evaluate against these criteria.

Compliance Check

Platform Check

Scalability Check

Build Decision Matrix