This page compiles every ## Unverified section in the 15 research notes and every :::gap and :::flag callout on the hub's pages (190 callouts across 105 pages). Most gaps fall into four patterns. Google and Microsoft say almost nothing about cold-email infrastructure. Revenue figures are estimates. No benchmark states its method. Our search budget ran out before Reddit, G2 and several regulators' sites could be read.
The questions are ranked by how much the answer would change the decision of an EU-based founder entering this market: what to build, where to sell it and on whose infrastructure. Cost estimates are our judgement of effort, not sourced figures, unless a link says otherwise. Where a disagreement between sources is the problem rather than a missing fact, it lives in Contradictions register.
The ten questions that would most change the decision
1. Can anyone get Google Workspace inboxes at scale, legitimately, in 2027? Resellers sell Google mailboxes at $2.50–3.50 while Google's Business Starter list price is about $7 (Inbox & domain infrastructure, vendor-sourced). Nobody documents how. We also could not verify whether Google is restricting Workspace supply to cold-email resellers: one Maildoso help line is the only evidence (Infrastructure strategy: build or partner, Provider rules: Google, Microsoft and the ESPs). Why it matters: inboxes are the biggest line in the customer's budget (Value chain), and inbox resale is how sequencers now make margin (Unit economics). If supply is grey-market, a "transparent infrastructure" wedge (Transparent infrastructure) is strong and a resale model is fragile. How to find out: ask three infra vendors (Zapmail, InboxKit, Mailforge) for tenant ownership and Google reseller-partner status in writing, and ask one authorised Google Workspace reseller in Germany what its cold-email policy is. Cost: a week of calls and email.
2. What are the real suspension and burn rates by infrastructure type? The only figures are competitors' estimates: about 22% of new high-volume Google accounts suspended within 90 days versus under 9% on Microsoft (EmailBison, no method), and about 25% of reputable providers' clients hit in the October 2025 wave (Salesforge newsletter). No source names which panels were shut down (Provider crackdowns). Why it matters: suspension rate sets churn, support load and the economics of every infra model in Infrastructure strategy: build or partner. How to find out: run a cohort. Buy 20 Google, 20 Microsoft and 20 private-SMTP mailboxes from two suppliers each and send real, compliant B2B campaigns at 15–25 a day for 90 days. Track suspensions, bounces and replies per mailbox. Cost: roughly $3–4.50 per mailbox per month at the prices on Zapmail and Mailforge, plus domains and founder time.
3. Is there a paying DACH and EU market for a compliance-first sequencer? No survey shows how many German B2B firms send cold email despite §7 UWG, or which tools they use; the only tool list is one 2026 blog (Germany). No DACH-native volume sequencer surfaced, but absence was not proven (Non-English markets). Why it matters: it decides whether EU-native compliant outbound and Governed volume for sales teams are businesses or features. How to find out: 30 interviews with DACH agencies, founders and RevOps leads; a landing page with EUR pricing and a waitlist; LinkedIn ads to German sales leaders. Cost: 3–4 weeks of founder time and a small ad budget.
4. What is an EU-based sending platform's own liability under UWG, GDPR and the DSA? We found no German judgment on a cold-email SaaS provider's own liability; the Störerhaftung analysis on Germany is reasoning from principles. How the DSA classifies a sequencer, and whether it is itself an "electronic communications service", is open (Platform liability: what the sequencer itself risks). Why it matters: a US platform can treat users' German law breaches as the user's problem; a German-domiciled platform is easier to reach. How to find out: a written opinion from a German competition-law (UWG) firm and a data-protection firm on three scenarios: you only send; you also supply data; you also write copy with AI. Cost: two fixed-fee opinions; get quotes first.
5. What outcomes do customers actually get: positive replies and meetings, with a stated method? No 2025–26 source publishes a positive-reply or meeting rate with a clear denominator, classification method and distribution (Reply benchmarks). No vendor says how it calculates "positive reply rate" (Campaign analytics). No controlled study compares AI-written and human-written email (AI personalisation, Copy and personalisation layer). Why it matters: outcome pricing, kill criteria and the Trust as positioning wedge all need this number. How to find out: get 3–5 agencies to share anonymised campaign exports (sends, delivered, replies, human-labelled positives, meetings) in exchange for a free benchmark report. Cost: a few weeks of analysis.
6. How do European B2B recipient domains split across Google, Microsoft, gateways and local hosts? No reliable 2026 split exists even for the US; the only proxy is sender-side data from Saleshandy (How filtering works). No vendor documents ESP matching for European providers such as IONOS, Strato or T-Online (ESP matching). Why it matters: it decides whether ESP matching, Microsoft-first outbound or an EU-provider routing feature is worth building. How to find out: MX-lookup 50,000 DACH and EU company domains from any lead list and classify the providers. Cost: a day of scripting. This is the cheapest high-value question on the page.
7. Do warmup pools help, do nothing, or get senders punished? No statement from Gmail, Outlook or Yahoo about warmup networks, and no controlled study (Does warmup work?). The Validity "Heatwave" claims (sharing with Spamhaus, permanent listing) could not be verified. Instantly's "9% improvement" for its premium pool is its own analysis (Built-in warmup). Why it matters: building or buying a warmup network is a large commitment, and Mailbox health engine depends on knowing what actually protects a mailbox. How to find out: split 40 new mailboxes into pool-warmed and plain-ramped cohorts, then measure seed placement and real reply rates over 60 days. Cost: mailboxes plus a placement tool such as MailReach at $19.50 per mailbox per month.
8. Where is Microsoft going on cold-email tenants? Microsoft promised "smarter, more adaptive" outbound limits with no date (Microsoft rules: Outlook.com and Microsoft 365 limits). Practitioners report suspensions of resold Outlook tenants with no Microsoft statement. A vendor's 2026 claims (bulk-sender registration, 3M accounts blocked) are unsourced (Provider crackdowns). Basic SMTP AUTH goes default-off at the end of December 2026 (OAuth verification and the end of basic auth). Why it matters: Microsoft is the cheapest big-provider capacity today and the basis of Microsoft-first outbound. How to find out: follow Microsoft 365 Message Center; ask two Microsoft CSP partners about cold-email tenant policy; include Microsoft tenants in the cohort test in question 2. Cost: low, ongoing.
9. Which CASA level will Google assign, and is there a legitimate way around it? CASA quotes run from about $540 to $6,000 a year, with an unverified $15k–75k "legacy" figure. We could not confirm which assurance level applies to a sequencer with tens of thousands of users, or which level Instantly and Smartlead hold. Nor is it stated whether an admin-trusted but unverified app can use restricted scopes in that domain (OAuth verification and the end of basic auth). Why it matters: it decides OAuth-first vs app-password architecture (Sending architecture), time to launch and the self-hosted option. How to find out: request quotes from two CASA labs; ask Google's OAuth verification team in writing about admin-trusted apps; inspect Instantly's documented admin flow. Cost: a few hours plus the assessment itself.
10. How big, how profitable and how churny are the incumbents really? Instantly's 2026 revenue ($38.2M) is a GetLatka estimate only. Smartlead's "$20M+" comes from competitors' content (Smartlead). No vendor discloses gross margin (Unit economics), support headcount or cost to serve (Build costs and team). The only churn figure is Instantly's early ~10% monthly (Founders and small B2B teams). Why it matters: it sets the size of the prize, how far price can fall (Pricing strategy) and what Kill criteria are realistic. How to find out: interviews with former Instantly and Smartlead support and success staff; affiliate dashboards from creators who promote both (they see churn); your own beta cohort. Cost: two weeks of outreach.
Market and players
| Question | Why it matters | How to find out | Pages |
|---|---|---|---|
| Any 2025–26 funding for Smartlead, Instantly, PlusVibe, EmailBison or Salesforge? | A funded volume player changes price-war odds | Crunchbase, company registries (Estonia for Salesforge), founder posts on X/LinkedIn | Funding and exits |
| Who owns EmailBison: founders, entity, launch date, headcount? | It is the agency-tier benchmark at $599 flat, and an acquisition or partner candidate | Ask EmailBison directly; agency operators on its private Slack | EmailBison |
| EmailBison overage pricing and any affiliate programme | Sets the real top-tier price ceiling | Request a demo; ask two of its agency customers | EmailBison, Distribution |
| PlusVibe founder identity, team, revenue, customers | A low-priced clone with a Polish legal footprint is the nearest EU-adjacent rival | Polish company registry; Product Hunt history | PlusVibe |
| Salesforge 2026 revenue and its mix between sequencer, infra and Agent Frank | Tests whether infra resale out-earns software | Estonian annual reports (public); founder posts | Salesforge, Mailforge |
| lemlist headcount, co-founders, HQ; any funding at all | lemlist is the EU proof that bootstrapped multichannel works | French company registry (lempire); founder interviews | lemlist, Funding and exits |
| Classic-tool revenue (Reply, Snov.io, Klenty, Mailshake, Hunter, GMass, Saleshandy) | All are GetLatka estimates at ±50% | Founder interviews; Woodpecker-style filings where listed | Market size, Reply.io, Snov.io, Klenty, Mailshake, Hunter, GMass, Saleshandy |
| Is Mailshake still actively developed; who owns it? | A stagnant base is a migration target | Changelog cadence; ask support | Mailshake |
| QuickMail revenue, headcount, HQ; does MonsterOps mean reduced investment? | Same migration logic | Founder posts; customer interviews | QuickMail |
| Owners, funding and revenue of infra vendors (Zapmail, Scaledmail, MailReach, Inboxkit, Hypertide, Cheap Inboxes); Mailforge's link to Salesforge | Partner due diligence before you resell their inboxes | Company registries; ask for contracts and invoices | Inbox & domain infrastructure, Zapmail, Scaledmail, MailReach, Mailforge |
| Salesloft ARR, Clari merger terms, Vista's 2021 price, Feb 2026 layoffs | Gauges how hard the suites can fight downmarket | Vista and Clari releases; SEC filings of acquirers | Salesloft, Funding and exits |
| Outreach ARR after 2023 | Same | Sacra; former staff | Outreach |
| Apollo 2026 ARR, the "fivefold" claim, when Matt Curl became CEO | Apollo is moving into deliverability and could squeeze the bottom | Apollo newsroom; Sacra's source | Apollo.io |
| Amplemarket funding after 2022, current ARR | Small suite with deliverability tooling | Founder posts | Amplemarket |
| ZoomInfo price sheet; status of ZoomInfo Engage | Shows whether data giants still sell sending | Vendr-style contract data; ZoomInfo sales call | ZoomInfo |
| HubSpot Sequences usage and Sales Hub revenue | Size of the "sequencer inside the CRM" installed base | Not disclosed; proxy via HubSpot partner agencies | HubSpot Sequences |
| 11x and Artisan 2026 ARR, retention, funding; did both "revert to hybrid"? | Tests whether the autonomous AI SDR is dead or just repricing | Former customers; TechCrunch follow-ups | 11x, Artisan, AI SDR layer |
| AiSDR and Regie.ai founding, funding, prices | Sets the floor for AI SDR pricing | Sales calls (both quote-based) | AiSDR, Regie.ai |
| How much of Reply.io's revenue comes from Jason AI SDR | Tests the split "volume plan + AI SDR" model | Former staff; Reply.io customer calls | Reply.io |
| AI SDR adoption and churn statistics ("41% in production", "2% persist", "$5.81B market") | All unsourced; used widely in pitch decks | Trace to primary sources or drop | AI SDR layer |
| Revenue of the suite layer and of cold-email agencies | The hub's $0.8–1.2B suite guess is unsourced | Bottom-up from seat counts; agency surveys | Market size |
| 2026 newcomers in sequencing | Our sweep stopped early; expect more sub-$50 tools | Product Hunt and r/coldemail scan | Sequencing & sending |
| Unify ARR and the date of its switch to $0–60/seat | A signals player cutting prices 90% is a market signal | Sacra update; founder posts | Unify |
| Clay Solutions Partner commission | Matters if you partner with Clay agencies for distribution | Ask Clay partnerships | GTM engineers |
| Copy.ai's cold-email product and price | Possible copy-layer partner or competitor | Sign up | Copy and personalisation layer |
| Bombora, G2 Buyer Intent pricing; RB2B ARR | Cost of signal inputs for a signal-led sequencer | Sales calls | Signals layer |
| Nooks and Orum funding and seat prices; direct-mail tools | Scope of the multichannel adjacency | Crunchbase; pricing pages | Multichannel: LinkedIn, calls, SMS and video |
| Expandi independence; HeyReach "fastest growing" badge issuer | Low stakes | Company registry; badge issuer | Expandi, HeyReach |
Deliverability and providers
| Question | Why it matters | How to find out | Pages |
|---|---|---|---|
| How do resellers sell Google seats below list price (discounts, regional pricing, panels)? | Provenance risk for any inbox you resell | Ask resellers for invoices; ask an authorised Google reseller | Inbox & domain infrastructure, Value chain, Unit economics |
| Has Google terminated reseller partners or acted against reseller-provisioned cold inboxes in 2025–26? | "The most important fact" on Provider rules: Google, Microsoft and the ESPs | Reseller interviews; agency operators who lost inboxes | Provider rules: Google, Microsoft and the ESPs, Provider crackdowns |
| What thresholds trigger Google AUP action against Workspace senders? | Enforcement against accounts, not mail, is undocumented | Cohort test (question 2); suspension notices collected from customers | Google and Yahoo sender rules |
| Does Gmail filter Workspace (business) recipients with the same thresholds as personal Gmail? | Most cold mail goes to business recipients the bulk rules do not cover | Seed and real-recipient tests split by recipient type | How filtering works, Google and Yahoo sender rules |
| How do providers weight replies, reads and deletes? | Engagement design (reply-first sequences) rests on folklore | No public answer; infer from controlled tests | How filtering works |
| Do Gmail or Microsoft filters detect LLM-written text as such? | Decides whether AI copy is a deliverability risk in itself | No primary source; A/B identical lists with human vs AI copy | The AI shift, Copy and personalisation layer |
| How do Gemini summaries, Gmail AI Inbox, Apple Intelligence and Copilot change reply rates? | Recipient-side AI may bury cold mail or summarise it away | Track reply rate by recipient client over 2026–27 | The AI shift |
| Does an open-tracking pixel itself hurt placement? Does List-Unsubscribe push cold mail to Promotions? | Determines defaults for tracking and headers | Paired placement tests, pixel on vs off, header on vs off | Content and tracking, Authentication: SPF, DKIM, DMARC, BIMI, ARC and one-click unsubscribe |
| How Spamhaus treats newly observed domains (ZRD) | Sets domain-ageing advice | Spamhaus documentation; ask Spamhaus | Reputation and blocklists |
| Postmaster v2 data threshold (~200/day claimed); did the promised new dashboards ship? | Whether any first-party telemetry exists for low-volume senders | Connect test domains and watch | Reputation and blocklists |
| Microsoft's "adaptive" outbound limits; the original April 2025 "Junk first" wording; formal MERRL withdrawal notice | See question 8 | Message Center; Microsoft tech community | Microsoft rules: Outlook.com and Microsoft 365 limits, Provider rules: Google, Microsoft and the ESPs |
| Are seed accounts reused across placement vendors and filtered differently? | Seed tests may mislead customers | Run the same mailbox through two vendors at once | Inbox placement testing |
| Does ESP matching lift placement, and by how much? | All numbers are unaudited | Matched vs unmatched cohort on one list | ESP matching |
| Do Validity "Heatwave" and Spamhaus share warmup-network data? | A warmup network could become a liability | Ask Validity; watch for listings | Does warmup work?, Warmup networks |
| Independent placement data for AirMail, Maildoso, Zapmail and Scaledmail inboxes | Partner and competitor quality | Buy 10 of each; placement-test monthly | Instantly, Maildoso, Zapmail, Scaledmail |
| Does Zapmail put customers on shared or per-customer tenants? | Shared tenants were what Google suspended | Ask Zapmail; inspect tenant IDs on purchased inboxes | Zapmail |
| What does InboxKit's "$30 Azure tenant up to 100 mailboxes" license? | Licensed users vs shared mailboxes changes Microsoft compliance | Buy one; check licence assignment | Infrastructure strategy: build or partner |
| Wholesale or white-label API prices from infra partners; Instantly's DFY inbox price | Sets the margin on inbox resale | Partner calls; Instantly sign-up | Infrastructure strategy: build or partner |
| Google Workspace list price in October 2026 | Every inbox model compares against it | Check Google's pricing page manually in a browser | Volume math: what 10k and 100k emails a day cost, Google vs Microsoft vs SMTP |
| Vendor claims to test or discard: PlusVibe 99.7% / 99.8% placement, Instantly 4.2M-account network, Smartlead 5–7M mailboxes, Saleshandy 67.4M connected accounts | Marketing used in competitor comparisons | Ask for methods; otherwise drop | PlusVibe, Warmup networks |
Law
| Question | Why it matters | How to find out | Pages |
|---|---|---|---|
| Platform liability of an EU-domiciled sequencer (UWG Störerhaftung, GDPR Arts 3/28/56, DSA status, ECS status) | See question 4 | Two written legal opinions | Germany, Platform liability: what the sequencer itself risks |
| Any CAN-SPAM, CASL or Spam Act action against a cold-email SaaS platform itself | Tests the "routine conveyance" shield | FTC, CRTC and ACMA enforcement lists; US counsel | United States: CAN-SPAM and state email laws, Canada: CASL, Cold email law: the jurisdiction matrix |
| Has 18 U.S.C. §1037 been applied to a B2B inbox farm? | Inbox resale on falsified registrations could be criminal in the US | US counsel; PACER search | United States: CAN-SPAM and state email laws, Infrastructure strategy: build or partner |
| New US state commercial-email statutes in 2025–26 beyond Washington's HB 2274 | Subject-line linting scope | State-law tracker; US counsel | United States: CAN-SPAM and state email laws |
| German DPA fines aimed at B2B cold email; DSK view vs Inteligo Media | Changes GDPR exposure on top of Abmahnungen | German data-protection counsel | Germany, GDPR and ePrivacy |
| EU DPA decisions against Apollo, ZoomInfo or Lusha | Signals whether US data vendors are next after KASPR | EDPB register; national DPA sites | Data sourcing law, Contact data and enrichment |
| Final EDPB Guidelines 1/2024 on legitimate interest | The legal basis for most B2B contact data | EDPB website | GDPR and ePrivacy |
| Details from prior knowledge: StWL, Bisnode, Dutch AP scraping note, hiQ settlement, LinkedIn vs Apollo/Seamless | Used in data-sourcing arguments | Fetch primary sources (UODO, AP, court records) | Data sourcing law, GDPR and ePrivacy |
| Low-confidence country rows (HR, LV, LU, BG, SI, IS, GR, RO, CZ, LI) and Switzerland's "mass advertising" scope | Needed before hard-coding recipient-country gating | Local counsel per country, or one pan-EU firm's survey | EU/EEA country matrix |
| UK DUAA "legitimate interest" wording; Schedule 13 commencement; ICO fines on B2B email | The UK is the biggest opt-out market in Europe | legislation.gov.uk; ICO enforcement page in a browser | UK: PECR and DUAA 2025 |
| France's phone-canvassing opt-in law from Aug 2026 | Affects B2C phone, not B2B email | Légifrance | France |
| CASL private right of action still suspended; EBR durations; 2025–26 CASL actions | Canada exposure for North American customers | CRTC; Canadian counsel | Canada: CASL |
| Australia penalty unit; NZ penalties; Singapore labelling and damages; India ₹250 crore cap; Australia APP 7 | APAC rows rely on prior knowledge | Fetch statutes directly | Australia, New Zealand and APAC, Cold email law: the jurisdiction matrix |
| Smartlead ToS and DPA; Instantly Sending Policy; any public abuse-desk process | Benchmark for your own terms and KYC | Fetch in a browser; ask sales | Platform liability: what the sequencer itself risks |
| Is assigning AI-written output to the user (Instantly's clause) enforceable? | Matters once you write copy for users | Counsel | Platform liability: what the sequencer itself risks |
| Person-level website-visitor identification under German law | Determines whether EU signals can be person-level | German data-protection counsel | Signals layer |
Customers
| Question | Why it matters | How to find out | Pages |
|---|---|---|---|
| How many lead-gen agencies exist; what do they charge per meeting and per retainer? | Agencies are the volume tools' core buyer; $150–500 per meeting is hearsay | Agency interviews; Clay's 186-agency directory as a seed list | Lead-gen agencies, Market size |
| How many founders and small teams run cold email; their churn | The largest review base, and the churniest | Affiliate creators' dashboards; your own beta | Founders and small B2B teams |
| What German and EU firms actually use for outbound | Sizing EU-native compliant outbound (question 3) | Interviews; job ads naming tools | Germany, Non-English markets |
| Local sequencers and US-database coverage gaps in DACH, Spain/LatAm and India | Where a localised product has an edge | Test Apollo and Instantly SuperSearch on 500 known local contacts each | Non-English markets, Contact data and enrichment |
| Thread-level complaint counts on r/coldemail by vendor | The review-mining pass could not read Reddit | Scrape with an API key; read manually for a week | Customer voice |
| How common is "suite for warm, volume tool on secondary domains for cold"; does RevOps know? | Defines Governed volume for sales teams | Survey 50 SDR leaders; RevOps community | In-house SDR teams, Enterprise RevOps buyers |
| How many companies have a dedicated RevOps function or sales-engagement seats? | Enterprise segment size | LinkedIn title counts | Enterprise RevOps buyers |
| GTM-engineer salaries and Clay Sequencer usage ("800k+ emails monthly" ambiguous) | Whether the headless-sending buyer is big enough | Clay community; job postings | GTM engineers, Clay |
| YouTube and Skool community sizes; whether vendors pay creators beyond affiliate commission; affiliates' share of revenue | Distribution cost of entry | Ask three creators directly | Distribution, The info economy |
| Does the AI-SDR buyer want approval queues at volume-tool prices? | Basis of the human-in-the-loop opening | Interviews with churned 11x/Artisan customers | AI SDR layer, Fully autonomous AI SDR |
Product and tech
| Question | Why it matters | How to find out | Pages |
|---|---|---|---|
| CASA level, incumbents' CASA status, admin-trusted app path | See question 9 | Lab quotes; Google OAuth team | OAuth verification and the end of basic auth, Build costs and team |
| Microsoft Graph Outlook throttling limits | Sizing Graph workers for an Microsoft-first outbound engine | Microsoft docs in a browser; load test | Sending architecture |
| How incumbents built their schedulers, ingestion and warmup | No engineering posts exist; architecture is reconstructed | Hire or interview ex-engineers | Sending architecture |
| Support load and cost to serve; engineering vs support split | "The most uncertain line" in the budget | Ex-staff interviews; beta ticket data | Build costs and team |
| Does Instantly charge for skipped AI-reply drafts? | Pricing reference for The reply desk | Test on a paid account | AI reply agent |
| Smartlead native AI reply drafting and AI writer; Apollo AI writing | Feature-matrix gaps | Free trials | AI reply agent, AI personalisation, Copy and personalisation layer |
| Reply-classification accuracy; AI-drafted vs human reply conversion | Every number is a vendor claim | Label 1,000 replies yourself; compare tools | Replies, booking and handoff, Campaign analytics |
| Instantly native LinkedIn steps; Apollo multichannel, rotation and branching | Feature parity checks | Trials | Multichannel steps, Inbox rotation, Conditional sequences and subsequences |
| Spintax support at lemlist, Salesforge, Apollo, Outreach, HubSpot | Low stakes | Trials | Spintax and message variants |
| Do vendors auto-provision HTTPS on custom tracking domains? | HTTP-only redirects are a negative signal | Set one up on each | Custom tracking domains |
| SSO at Instantly, Smartlead, EmailBison; Instantly's SOC 2 status | Enterprise-readiness gap | Ask sales; trust centres | Workspaces, roles and SSO, Enterprise RevOps buyers |
| EmailBison white-label depth; Instantly CRM integration gating | Agency feature parity | Demo; trial | White-label and agency portals, CRM sync |
| HubSpot and Outreach daily sequence caps | Only one third-party source | Vendor knowledge bases | Sending limits and throttling |
| Verification accuracy on catch-alls; database accuracy; list decay rate | Bounce risk drives mailbox burn | Run a neutral bounce test on 5,000 contacts across five vendors and publish it | Built-in email verification, Built-in lead database, Contact data and enrichment, Email verification |
| Signal-triggered vs list-based reply rates | Whether Signal-triggered sequencer beats spray | 20 signal-referenced messages against your baseline, as Overloop suggests | Signals layer |
| Instantly MCP rate limits and launch date; MCP coverage vs full API | Agent-native parity | Test with an agent client | API, webhooks and MCP, AI campaign builder |
| Why no sequencer sells pay-per-meeting or pay-per-positive-reply | Either an opening or proof the economics fail | Model it with data from question 5 | Business models |
| Clay Sequencer pricing, volumes and deliverability record | The brain tool could absorb the sending layer | Sign up; ask Clay agencies | GTM engineers, Clay |
| Does "Inboxflow" exist? | Reply-tool landscape completeness | Low stakes | Replies, booking and handoff |
What we would do first
Questions 6 and 9 cost almost nothing and should be answered this month: an MX classification of EU company domains and two CASA quotes. Questions 1, 2 and 7 share one experiment, a 90-day mailbox cohort across suppliers and providers, which also produces the provider-mix and burn data that Infrastructure strategy: build or partner and Mailbox health engine need. Questions 3 and 4 decide whether the company is EU-first or export-first and should run in parallel with the cohort. See Kill criteria and The first 90 days for how the answers feed the plan.