# B2B Outbound Deliverability & Infrastructure OS ==================================================================== MODULE 1: DOMAIN PORTFOLIO TOPOLOGY, DNS GOVERNANCE & AUTHENTICATION ==================================================================== - Secondary Domain Portfolio Architecture: * Primary Brand Domain: `revsignal.io` (Completely isolated; zero cold outbound dispatched). * Portfolio Strategy: 20 dedicated secondary domains using commercial and directional prefixes: - `getrevsignal.com`, `tryrevsignal.com`, `revsignalhq.com`, `userevsignal.com`, `revsignalapp.com`, etc. * DNS Registrar & Management: Managed through Cloudflare DNS. All records set to DNS Only (Grey Cloud) to ensure direct SMTP mail routing without proxy interference. * HTTP 301 Permanent Redirect: In Cloudflare, a root wildcard rule routes all web traffic safely: `*getrevsignal.com/*` -> 301 Redirect -> `https://revsignal.io/?utm_source=outbound&utm_medium=domain_redirect`. - Master DNS Record Matrix: | Record Type | Host / Name | Target Value / Content | TTL | Purpose / Compliance Standard | | :--- | :--- | :--- | :--- | :--- | | MX | `@` | `1 ASPMX.L.GOOGLE.COM.` | 3600 | Primary Google Workspace mail routing | | MX | `@` | `5 ALT1.ASPMX.L.GOOGLE.COM.` | 3600 | Secondary Google Workspace mail routing | | MX | `@` | `5 ALT2.ASPMX.L.GOOGLE.COM.` | 3600 | Secondary Google Workspace mail routing | | TXT | `@` | `v=spf1 include:_spf.google.com ~all` | 3600 | Single SPF record (Zero lookup bloat; SoftFail ~all) | | TXT | `google._domainkey` | `v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAz8...` | 3600 | 2048-bit Google Workspace cryptographic signature | | TXT | `_dmarc` | `v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@revsignal.io; pct=100; adkim=r; aspf=r` | 3600 | Quarantine policy with daily aggregate XML feedback | | CNAME | `track` | `prox.smartlead.com` | 3600 | Custom white-labeled tracking domain with SSL | ==================================================================== MODULE 2: MAILBOX CAPACITY PLANNING & 21-DAY REPUTATION RAMP PROTOCOL ==================================================================== - Mailbox Allocation & Capacity Model: * Total Infrastructure Scale: 20 Domains x 2 Inboxes per Domain = 40 Active Inboxes. * Naming Convention: First.Last (`sarah.chen@getrevsignal.com`) and First (`sarah@getrevsignal.com`). * Daily Sending Cap: 25 targeted outbound emails + 20 warmup interactions = 45 total emails/inbox/day. * Total Fleet Output: 40 inboxes x 25 outbound = 1,000 targeted emails/day (22,000/month). * ESP Distribution: 28 inboxes on Google Workspace (70%) and 12 inboxes on Microsoft 365 (30%) to maintain balanced IP exposure. - 21-Day Linear Warmup & Reputation Ramp Schedule: | Day Range | Warmup Sends/Day | Active Cold Sends/Day | Total Volume/Day | Target Reply % | Stage Gate Criteria | | :--- | :--- | :--- | :--- | :--- | :--- | | Days 1 to 5 | 5 | 0 | 5 | 40% (Network simulated) | DNS verification; zero outbound | | Days 6 to 10 | 12 | 0 | 12 | 35% (Network simulated) | Reputation baseline establishment | | Days 11 to 14 | 20 | 0 | 20 | 30% (Network simulated) | Full warmup load; check Google Postmaster | | Days 15 to 17 | 20 | 10 | 30 | 25% Blended | Launch initial targeted cohort | | Days 18 to 20 | 20 | 18 | 38 | 20% Blended | Scale volume; monitor bounce rates | | Day 21+ | 20 | 25 | 45 | 15% Blended | Steady-state operations | - Reputation Safeguards & Auto-Pause Circuit Breakers: * Bounce Rate Circuit Breaker: Automatic campaign pause if any inbox exceeds a 1.5% bounce rate over 48 hours. * Spam Complaint Threshold: Hard stop if Google Postmaster spam complaints reach 0.05% (well ahead of Google's 0.08% ceiling). * Domain Quarantine Protocol: If inbox placement drops below 85% on seed lists, pause cold sends for 14 days and run pure warmup recovery. Replace permanently if unrecovered after 14 days. ==================================================================== MODULE 3: DYNAMIC SEMANTIC MESSAGE VARIANCE & ICP PERSONALIZATION ==================================================================== - Enterprise Message Variance Architecture: * Replaces static mass broadcasting with contextual semantic variations. * Permutation Matrix: 12 subject line combinations x 18 observation variations x 24 value proposition angles x 12 low-friction CTAs = 62,208 mathematically unique variations, eliminating content repetition across email service providers. - Verbatim Multi-Tier B2B Outbound Messaging Matrix: * Subject Line Variations: ```text {Quick observation regarding|Thought on|Note regarding} {{company_name}}'s {sales pipeline|revenue execution|pipeline coverage} ``` * Email Body Variance Structure: ```text Hi {{first_name}}, {Noticed that {{company_name}} is expanding the sales team|Saw that you are hiring commercial AEs|Saw your team is scaling revenue operations} {on LinkedIn|recently|this quarter}. {Most sales leaders we speak with mention that|A common challenge revenue leaders share is that|VPs of Sales often tell us that} {reps spend over a third of their week manually updating CRM fields|pipeline visibility is skewed by subjective stage forecasting|deals stall late in the cycle due to unmapped buying committees}. {We developed RevSignal to|RevSignal was designed to|We built a revenue execution platform that} {automatically capture buyer engagement signals from email and calls|provide automated CRM activity logging with stage risk alerts|give sales leaders real-time visibility into deal health}, {which helped teams like Seismic and Thoughtspot improve forecast accuracy by 28%|allowing sales teams to reduce slippage on enterprise deals|resulting in an 18% lift in quarterly quota attainment}. {Open to reviewing a brief 2-minute video overview|Would you be opposed to a brief introductory conversation|Worth exploring how this compares to your current setup} {later this week|next Tuesday}? Best regards, Sarah Chen RevSignal Technologies RevSignal Inc., 500 Howard Street, San Francisco, CA 94105 Opt-out: If you prefer not to receive future insights, reply with "unsubscribe". ``` ==================================================================== MODULE 4: LIST VERIFICATION WATERFALL & SENDER REPUTATION SAFEGUARDS ==================================================================== - 3-Stage Lead Verification Waterfall: * Stage 1: Syntax & Record Validation (ZeroBounce / MillionVerifier). Strip invalid formatting, dead domains, and role-based emails (info@, sales@, admin@). * Stage 2: SMTP Mailbox Ping. Perform real-time MX server handshakes to confirm valid mailbox addresses (250 OK response). * Stage 3: Catch-All Risk Segregation. Isolate catch-all (accept-all) domains from the primary sending queue. - Catch-All Management & Honey-Pot Prevention: * Verified Catch-Alls Only: Validate catch-all addresses via secondary verification tools (e.g., Scrubby) before sending. * Volume Throttling: Catch-all accounts must never exceed 8% of total daily sending volume, protecting domain reputation from dormant spam traps. - Global Exclusion & Suppression Governance: * Central suppression list automatically excludes: existing customer domains, active CRM opportunities, historical unsubscribes, and partner/competitor networks. ==================================================================== MODULE 5: TURNKEY CAMPAIGN JSON, OBSERVABILITY & METRIC SCORECARD ==================================================================== - Turnkey Campaign Configuration JSON (Smartlead API Schema): ```json { "campaign_name": "Enterprise_VP_Sales_Pipeline_Excellence", "schedule": { "timezone": "America/New_York", "days_of_week": [1, 2, 3, 4, 5], "start_hour": "08:30", "end_hour": "17:00" }, "settings": { "track_open_rate": false, "track_link_clicks": false, "custom_tracking_domain": "track.getrevsignal.com", "min_time_between_emails_seconds": 210, "max_new_leads_per_day": 350, "send_as_plain_text": true, "stop_on_lead_reply": true, "warmup_enabled": true, "warmup_ratio_percentage": 40 }, "mailbox_pool": [ "mb_google_revsignal_01", "mb_google_revsignal_02", "mb_microsoft_revsignal_01" ], "webhooks": { "on_reply": "[https://api.revsignal.io/webhooks/outbound/reply](https://api.revsignal.io/webhooks/outbound/reply)", "on_bounce": "[https://api.revsignal.io/webhooks/outbound/bounce](https://api.revsignal.io/webhooks/outbound/bounce)" } }