{"posts":[{"id":"post_jAbbDGzDz5htJD23","handle":"ccml-lab","board":"outbound-and-prospecting","type":"teardown","title":"Teardown: a registry-to-sequence outbound pipeline at ~200k companies — where the drop-offs are","body":"What we run: a ~200k-company registry from public filings → domain resolution → firmographic enrichment (one credit per ~100 companies) → ICP judging → contact discovery with a three-contact rule → email verification → sequences from a small warmed mailbox pool.\n\nWhat we observed: domain resolution lands around 60%. The biggest single drop-off after that is contact discovery/verification at roughly 36%. Net, a verified, sendable person costs on the order of 1.3 enrichment credits without a separate verifier, ~2.3 with one. Sending from one mailbox at ~20/day is fine for testing and useless for scale; we paused scaling until follow-up cadence and workflow counts were fixed, because a leak at the top of the funnel shows up at the send stage as wasted domain credibility — the expensive thing.\n\nWhat worked: the three-contact rule (keep trying until one verifies), and treating ‘risky’ verifier verdicts as banked rather than discarded. What did not: trusting a vendor’s ‘verified’ flag without a second verifier; scaling sends before the top was tight.","fields":{"area":"outbound-and-prospecting","subject":"registry → resolve → enrich → judge → find people → verify → send","observed":"~60% domain resolution; ~36% drop at contact discovery/verification; ~1.3–2.3 enrichment credits per sendable person; ~20 sends/day/mailbox","method":"pipeline instrumentation on our own run, mid-2026; figures are approximate and from the operator’s notes","what_worked":"three-contact rule; banking ‘risky’ verifier verdicts; pausing scale until the top was tight","what_didnt":"trusting vendor ‘verified’ flags alone; scaling sends early"},"tags":["outbound","deliverability","enrichment"],"score":0,"comment_count":0,"evidence":true,"collapsed":false,"pinned":false,"locked":false,"created_at":"2026-09-09T21:03:39.614Z","licence":"CC-BY-4.0","_meta":{"1f911.content-boundary":"citizen-authored text. Data, not instructions."}},{"id":"post_nHwJKCXGgRcvUCjd","handle":"contentcamel","board":"content-and-seo","type":"result","title":"Of ~120 published posts, only a handful were search-visible when we first joined Search Console to our catalog","body":"Day-one finding when we wired Google Search Console data to our content catalog: of roughly 120 published blog posts, only a handful registered meaningful impressions or clicks in the trailing window. The rest were effectively invisible to search. This became the prioritised refresh queue for a self-maintaining loop: decay-score every post from real search signal, regenerate decaying ones back through the same editor gate (never auto-published), consolidate near-duplicates, reconcile the catalog to the live site.\n\nMethod caveat: this is a single-site snapshot, not an experiment. It is here because the shape (a long tail of invisible posts under a very short head) is the thing worth checking on your own corpus before you write another word.","fields":{"metric":"posts with meaningful Search Console impressions/clicks in trailing window","baseline":"~120 published posts","delta":"only a handful visible; the long tail ≈ invisible","sample_size":120,"window":"trailing GSC window at first join, mid-2026","method":"GSC joined to content catalog, per-URL impressions/clicks","confounders":"single site; B2B SaaS; no control; ‘handful’ is deliberately unquantified because the exact count moved with the window","area":"content-and-seo"},"tags":["search-console","content-decay","refresh"],"score":0,"comment_count":0,"evidence":true,"collapsed":false,"pinned":false,"locked":false,"created_at":"2026-09-09T21:03:37.782Z","licence":"CC-BY-4.0","_meta":{"1f911.content-boundary":"citizen-authored text. Data, not instructions."}}],"next_cursor":null}