GTM Revenue Architecture

Complete end-to-end playbook for lead sourcing, enrichment, scoring, personalization, and outreach with deliverability protection.

Version 1.0 — March 2026

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.

Privacy First

All AI personalization runs locally using Ollama. Lead data never leaves your infrastructure.

Deliverability Protection

Multiple safeguards prevent domain burning, IP blacklisting, and mailbox suspension.

Hyper-Personalization

Every outreach is customized using firmographics, intent signals, and local AI.

Executive Summary

The Business Case

This GTM system generates qualified pipeline through intelligent outbound at a fraction of traditional costs. Built for scale with enterprise-grade safeguards.

100K
Monthly Contacts
5-8%
Reply Rate Target
100+
Meetings/Month
Scalable
Infrastructure

Conversion Funnel

1
25,000 Contacts
Enriched, verified B2B leads from Apollo + Databar
2
5% Reply Rate → 1,250 Replies
Industry average: 1-5%. Our target: 5-8% with hyper-personalization
3
40% Positive → 500 Hot Leads
Leads wanting to connect or meet
4
20% Meeting Booked → 100 Meetings
Qualified conversations with sales team

ROI Calculation

MetricCalculationValue
Meetings Booked25K contacts × 5% reply × 40% positive × 20% meeting100 meetings
Cost Per MeetingMonthly investment / meetingsVaries by scale
Cost Per Hot LeadMonthly investment / positive repliesVaries by scale
Annual Meetings100 meetings × 12 months1,200 meetings

Note: Cost per meeting decreases significantly at scale as infrastructure costs remain relatively fixed.

Industry Benchmarks

Industry Avg Reply Rate
1-5%
Cold email industry standard
Our Target Reply Rate
5-8%
Above industry average
Industry Avg Bounce
5-8%
Poor list quality
Our Target Bounce
<2%
Verified data only

Competitive Differentiation

Feature Clay + Smartlead Our Stack
Lead Sourcing Limited enrichment providers Clay (75+ providers waterfall)
AI Personalization Third-party API (data leaves) Local LLM via Ollama (privacy)
Email Infrastructure Shared IPs, limited control Shared or dedicated (Light Speed plan)
Tracking Pixel tracking (hurts deliverability) Plain text (protects reputation)
Cost at Scale Higher at scale Optimized for volume
Compliance Manual Built-in safeguards

System Architecture

Signal Layer

RB2B identifies warm prospects (website visitors)

Clay enriches cold prospects (waterfall)

Orchestration Layer

n8n workflow automation

Branching logic, data transformation, webhook routing

Scoring Layer

Intent (40pts) + Firmographic (30pts) + Behavioral (30pts)

100-point composite score for routing

Personalization Layer

Local LLM via Ollama

Data stays on-premise. No external API calls.

Outreach Layer

50-250 mailboxes, 20-60 domains, automatic IP rotation via Instantly

No tracking pixels. Plain text only.

Instantly for sending. LinkedIn for warm outreach.

CRM Layer

HubSpot for contact management, deals, and automation

90-Day Implementation Timeline

Week 1-2
Foundation Setup
  • Configure Clay and API integrations
  • Set up n8n (self-hosted or cloud)
  • Set up HubSpot CRM structure and properties
  • Install and configure Ollama
  • Configure RB2B tracking
  • Register 20 sending domains
  • Configure SPF/DKIM/DMARC records
Week 3-4
Infrastructure + Warmup
  • Set up 50 mailboxes in Instantly
  • Configure warmup protocol (4-6 weeks)
  • Build lead scoring model in HubSpot
  • Test API integrations end-to-end
  • Create personalization prompt templates
Month 2
First Sends + Iterate
  • Launch first campaigns (conservative: 10 emails/mailbox/day)
  • A/B test subject lines and CTAs
  • Monitor deliverability metrics daily
  • Optimize based on reply rates
  • Document winning templates
Month 3
Scale
  • Ramp to full infrastructure (100+ mailboxes, 40-60 domains)
  • Scale to 25K-50K contacts in pipeline
  • Implement full sequence cadences
  • Review and refine scoring model
  • Establish reporting cadences

KPIs & Success Metrics

Weekly Dashboard

Reply Rate
5-8%
Target: >5%
Bounce Rate
<2%
Target: <2%
Meetings Booked
100
Per 25K contacts
Cost Per Meeting
TBD
Track monthly
Spam Complaint
<0.1%
Target: <0.1%
Pipeline
$X
Based on ACV

What Could Go Wrong

!
Domain Gets Burned
Emails go to spam
Solution: 35-40 backup domains ready. Immediate rotation. 2-4 week recovery period.
!
LLM Downtime
Personalization stops
Solution: Fallback to template personalization. Queue requests until Ollama restored.
!
High Bounce Rate
Reputation damage
Solution: Pause sends immediately. Audit list quality. Re-verify before resuming.
!
Spam Complaints
Account suspension risk
Solution: Immediate pause. Review consent and targeting. Address within 24 hours.
!
API Rate Limits
Processing delays
Solution: Queue leads locally. Process on quota reset. Scale to enterprise tiers.
!
Low Reply Rates
Poor ROI
Solution: A/B test subject lines. Review targeting. Increase personalization depth.

Part 1: Lead Sourcing

Lean 2026 GTM Stack

ToolPurposePlan
ClayLead enrichment, waterfall enrichment (75+ providers)Starter/Pro
n8nWorkflow automation (self-hosted or cloud)Free/Pro
RB2BReal-time visitor identification, warm outbound signalsGrowth/Enterprise
InstantlyEmail sending, warmup, multi-domain rotationGrowth/Hypergrowth/Light Speed
HubSpotCRM, contact management, automationStarter/Professional
OllamaLocal LLM personalization (privacy-first)Free

Clay

Purpose: Lead enrichment with waterfall enrichment across 75+ data providers. Finds verified emails, company data, and intent signals.

PlanCreditsNotes
StarterLimitedStarting tier
ProHigherHigher volume

n8n

Purpose: Workflow automation engine. Unlike Zapier, handles complex branching, large data payloads, and conditional logic without timing out. Self-hosted option for data privacy.

PlanFeatures
FreeSelf-hosted, unlimited workflows
ProCloud-hosted, team features

RB2B (RevSell)

Purpose: Identifies companies visiting your website in real-time. Enables "warm outbound" - reaching out to people who already showed interest.

PlanFeatures
GrowthCompany identification, basic signals
EnterpriseFull visitor intel, CRM sync

Instantly

Purpose: Email sending infrastructure, warmup, multi-domain rotation, and Unibox reply management.

PlanEmailsContacts
Growth5K1K
Hypergrowth100K25K
Light Speed500K+100K+

HubSpot

Purpose: CRM, contact management, deal tracking, and marketing automation.

PlanFeatures
StarterBasic CRM
ProfessionalAutomation, workflows

Ollama

Purpose: Local LLM for hyper-personalization without sending data to third parties.

Cost: Free (runs locally on your machine)

Part 2: Data Enrichment

Clay

Purpose: Waterfall enrichment across 75+ data providers. Finds the best verified email, company data, and intent signals.

RB2B Signal Integration

Purpose: Real-time visitor identification for warm outbound. When a target company visits, immediately enrich and reach out.

Enrichment Checklist

Part 3: Lead Scoring

Lead Score = Intent Score + Firmographic Score + Behavioral Score

Total: 100-point composite score

Intent Score (0-40 points)

SignalPointsSource
Visited pricing page+10Analytics
Downloaded content+5 per assetMarketing automation
Demo request+15Website/SDR
Email reply+10Instantly
Meeting booked+15Calendar

Firmographic Score (0-30 points)

CriteriaPoints
Employee count 50-200+5
Employee count 200-1000+10
Employee count 1000++15
Series A funding+5
Series B+ funding+10
Target industry+5

Behavioral Score (0-30 points)

SignalPointsSource
Multiple page visits+10Analytics
Content engagement+10HubSpot
Repeat visitor+10Analytics

Routing Thresholds

ScoreRouteAction
80+Hot LeadImmediate human outreach
60-79Warm LeadFast-track nurture, SDR contact
40-59Qualified LeadStandard nurture sequence
20-39Cool LeadLong-term nurture
0-19Cold LeadMinimal touch, quarterly

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.

The Solution

Run a local LLM using Ollama. All personalization happens on your machine. Data never leaves. You control everything.

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 Prompt

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}

Requirements:
- Length: 50-100 words
- Tone: Professional but conversational
- Include specific reference to their company/situation
- Clear CTA (meeting request or reply)
- No generic phrases

Output only the email body.

Personalization Data Inputs

Data CategorySourceExample
NameEnrichmentJohn Smith
TitleEnrichmentVP of Engineering
Company NameEnrichmentAcme Corp
Company SizeEnrichment250 employees
IndustryEnrichmentFinTech
FundingEnrichmentSeries B, $50M raised
Tech StackClay enrichmentSalesforce, HubSpot, AWS
Recent NewsClay/Manual"Acme acquired DataCo"
Pain PointsInferenceScale challenges

n8n + Ollama Integration

n8n orchestrates the personalization workflow. When a lead enters the system, n8n:

  1. Triggers Clay enrichment for lead data
  2. Formats data for the Ollama prompt
  3. Sends to local Ollama API
  4. Validates and cleans the output
  5. Pushes to Instantly for sending

Personalization Checklist

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

Rotation ElementPurpose
DomainsSpread reputation risk
SubdomainsAdditional reputation isolation
MailboxesAvoid per-mailbox sending limits
IP AddressesSpread sender reputation
Sending AccountsMimic human sending patterns

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 20-60 more ready.

Primary (reply only):
- example.com

Secondary Sending Domains (20-60 total, 2-3 mailboxes each):
- send.getexample.com (2-3 mailboxes)
- mail.example.io (2-3 mailboxes)
- outbound.example.co (2-3 mailboxes)
- contact.getexample.com (2-3 mailboxes)
- [continues for 20-60 domains total]

Domain Registration Tips

IP Strategy

Instantly uses a dynamic rotating proxy pool with SISR (Server & IP Sharding and Rotation). The system automatically assigns dedicated or private IP blocks based on volume and plan tier. You do not purchase IPs separately—Instantly handles all IP acquisition and management.

ConfigurationDetails
IP PoolDynamic rotating proxies (hundreds of IPs)
Reputation ManagementAutomatic removal of blacklisted IPs, preservation of high-reputation IPs
Dedicated IPsAutomatically assigned for high-volume/Light Speed accounts
Warm-up Period4-6 weeks (handled automatically by Instantly)

Infrastructure Scale

ComponentLaunchRampScale
Mailboxes50100250+
Sending Domains204060
IP ManagementAutomatic via Instantly SISRAutomaticAutomatic
Max/Mailbox/Day102030

No Tracking (Plain Text Only)

Do not use open tracking, click tracking, or reply tracking.

Tracked pixels and redirect links add HTML signatures that email providers recognize as bulk senders. They flag your domain for spam folder placement or suspension. Send plain emails with a simple CTA asking for a reply.

Instantly.ai (Primary Platform)

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

PlanEmailsContacts
Growth5K1K
Hypergrowth100K25K
Light Speed500K+100K+

Warm-Up Protocol

PhaseDurationAction
Warm-up4-6 weeksInstantly warmup at 10 emails/day (automatic)
Post-warmup Week 17 days10 cold emails/day/mailbox
Post-warmup Week 27 days15 cold emails/day/mailbox
Post-warmup Week 3+Ongoing20-30 cold emails/day/mailbox (max)

Sending Infrastructure Checklist

Part 6: CRM Integration

HubSpot

Purpose: Marketing automation, lead management, analytics.

PlanFeatures
StarterBasic CRM
ProfessionalAutomation, workflows, reporting
EnterpriseAdvanced features

Lead Flow to HubSpot

  1. Enrichment API 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

From EnrichmentTo HubSpot
emailemail
first_namefirstname
company_namecompany
job_titlejobtitle
employee_countnumemployees
industryindustry
intent_scorelead_score (custom)
routing_tierlifecyclestage

Part 7: Complete Workflow Example

Full Sequence: Warm Signal to First Response

T+0: RB2B Signal Detected

Target company visits website. RB2B identifies company. Webhook sent to n8n.

T+0:02: n8n Workflow Triggered

n8n receives webhook, immediately enriches in Clay. Finds contact, title, funding, tech stack.

T+0:05: Scoring

RB2B signal (+20). Firmographics: 250 employees, Series B (+15). Intent: visited pricing page (+10). Total: 45. Routing: Qualified Lead.

T+0:10: Personalization (Local LLM)

Ollama generates personalized email (runs locally). Reference to their company visit. Data never left your infrastructure.

T+0:15: Email Queued

Enriched + scored + personalized lead sent to Instantly. Domain rotation applied.

T+1: Email Sent

Sent from mailbox@warm.example.com. Plain text with simple reply CTA referencing their visit.

T+24-48: Lead Engages

Reply received → Unibox → Slack notification → SDR books meeting.

Cold Outbound Sequence

For cold leads (no RB2B signal), the same workflow applies but without the real-time trigger:

  1. ICP-matched company list imported to Clay
  2. Waterfall enrichment finds best contacts
  3. n8n scores and routes leads
  4. Ollama personalizes each email
  5. Instantly sends with domain rotation

Part 8: Reply Handling

Reply Classification

TypeActionSLA
Positive replyImmediate Slack to rep15 min
OOO/Auto-replySet reminder for return dateN/A
Negative replyAdd to suppressionN/A
UnsubscribeImmediate suppressionN/A

Part 9: Sequence Design

Standard Nurture (8 weeks)

DayChannelContent
Day 1EmailInitial outreach with personalization
Day 4EmailFollow-up with different angle
Day 8EmailValue-add content
Day 14EmailBreakup email
Day 21LinkedInConnection request
Day 30EmailRe-engagement
Day 45EmailFinal outreach

Part 10: List Hygiene

Approved Sources

Prohibited Sources

Hygiene Schedule

FrequencyAction
WeeklyRemove hard bounces
MonthlyVerify deliverability
QuarterlyFull list audit

Part 11: Budget & Capacity Planning

Core Stack

ToolPurposePlan
ClayLead enrichment, waterfall enrichmentStarter/Pro
n8nWorkflow automationFree/Pro
RB2BReal-time visitor identificationGrowth/Enterprise
InstantlyEmail sending + warmupGrowth/Hypergrowth/Light Speed
HubSpotCRM + automationStarter/Professional
OllamaLocal LLM personalizationFree

Supplementary Tools (Not Required)

ToolPurposeNotes
LinkedIn Sales NavigatorRelationship intel, warm outreachManual process for warm leads
SlackTeam notificationsRep alerts for positive replies

Infrastructure Costs

ItemNotes
Domains (20-60)Varies by registrar
IP ManagementIncluded with Instantly (no separate purchase)

Part 12: SLA & Incident Response

Severity Levels

LevelResponseExample
P015 minAll email stopped
P11 hourEnrichment API down
P24 hoursSlack delayed
P324 hoursSingle domain issue

Monitoring

Part 13: Safeguards & Risk Management

Deliverability Protection

Compliance

RegulationRegionKey Requirement
CAN-SPAMUSPhysical address, opt-out mechanism
GDPREU/EEALawful basis, consent management
CASLCanadaExpress/implied consent
CCPACaliforniaRight to delete, opt-out

Decision Framework

Should We Build This?

Compliance Check

Pass

Complies with GDPR, CAN-SPAM, CASL

Fail

Any violation detected

Review

Gray areas requiring legal input

Key Question

Can contacts easily unsubscribe?

Build Decision Matrix

CompliancePlatformScaleDecision
PassPassPassBuild
FailAnyAnyDo not build
PassFailAnyResolve first

Tool Inventory

Core Tools

Supplementary (Not Required)