What is actually inside the group, how much we can recover on every lead, and what that data makes possible once it's in your hands.
A 60,000-member Facebook group, all of them on target: self-published authors, exactly Nespola's audience. Today it's a number on a page: no contacts, no way to reach any of them off-platform.
Our job is to turn that membership into an asset you own: qualified, verified contacts with as much usable information attached to each one as we can recover.
That is the whole of our remit: we deliver the list, you decide what to do with it. This document explains what will be in it and what it makes possible, so you can make that call with the full picture.
The numbers below are measured on real data from your group. Of the 43 emails, 16 were found on public company pages and 27 were inferred from a confirmed company domain.
Every contact arrives with more than an email: website, LinkedIn, Instagram, and other public channels, roughly 3 channels each. That's what makes the asset usable on several fronts instead of one. Projected across the full group: ~3,000 verified emails.
Business owners and professionals with a real public presence. From these we recover email, phone and social profiles. This is the segment where email, calling and LinkedIn work.
No public contact data: personal Facebook profiles simply don't publish it, and we verified this across several independent technologies. They're still reachable, just only through ad audiences.
Email, phone and LinkedIn all draw from the same contactable core: they are the same people reached from different angles. That's exactly what lifts conversion: someone who gets an email, then a call, then sees an ad converts far better than someone who only gets an email. But it does not multiply how many people you can reach.
The only channel that reaches the majority of the group is the Meta ad audience. That's why it should be treated as a primary channel, not a complement.
This is not a plan we're proposing. It's what the delivered data supports. Which of these you run, in what mix and in what order, is entirely your call. Our job is to make sure the file is rich enough that all four stay open to you.
It's seeded from the verified emails in the core and lets you reach authors with the same profile well beyond the 60,000 in the group. This is the point where the asset stops being a list and becomes an acquisition engine.
The group isn't yours. The moment the first campaign goes out, it only takes one member forwarding it to an admin for the group to be closed or cleaned out, and at that point the asset is no longer recoverable.
So there is one rule: complete the extraction first, communicate second. Never the other way round, and never in parallel.
There's a second reason not to wait. The sending infrastructure (dedicated domains and mailboxes) needs 3–4 weeks of preparation before it can carry real volume. That's the true bottleneck on the launch date: the contacts will be ready before the infrastructure is.
Extraction is ours and starts as soon as you give the go-ahead. Infrastructure is yours and is worth starting early purely because of the lead time. Neither waits on the other, but both are hard to recover if left late.
One file, and a single objective behind it: as much usable information on every lead as can be recovered. An address is the minimum. The point is the full contactable picture, so a gap in the data never closes a channel off to you.
Delivering the data is the first step. What happens next determines the result, and it's where most projects stall: sending infrastructure to prepare correctly, reputation to build, sequences to write and test, audiences to configure, calls to organize.
Both are separate from the data delivery. If either is of interest, we'll talk it through and send a dedicated proposal.
That's all we need from you. The sending domains flagged in section 05 are on your side and independent of our delivery. Worth starting early because of the lead time, but not something we're waiting on.
Questions? Write to cristoforo@nodeagency.ai.
Updated quote: see the proposal