Map the company's public footprint before you write a word to it

    Who this was forOur clients and us. This is a pattern that runs through several builds in this library, written up once.

    Website and social presence mapped before outreach

    All case studies

    The drawing

    noyesnoyesCompany name or domainResolve and normalizethe domainCompany page found?Logged as no companypagePeople found?Logged as company, nopersonFootprint mapped:site, social, trafficMessage written

    The problem

    Most lists arrive with a purchased industry field and a headcount band. Neither tells you whether the company is visible, active, or reachable where you plan to reach it. A message written on a purchased field reads like one.

    What we built

    The same sequence, every time, mostly in Clay with our own actors on Apify. Resolve the company to one clean domain. Find its company page. Find its people. Then map what's public: the website, the social profiles, and how much traffic the site gets. Only then write.

    Each step logs a miss as a named outcome, not a blank.

    What it produced

    Two builds from this library show why the order matters.

    • On a 5,216 row company table, normalizing domains first took 0 credits and found 0 duplicates, even though 1,906 rows carried a "www." prefix. Every later step ran on one row per company.
    • On a 475 row single state build, mapping presence before outreach split the misses into two kinds: 180 companies with a profile and no findable person, and 136 with no company page at all. That split set a market ceiling of 159 reachable leads.

    Neither result came from a purchased field. Both came from observing what each company actually has in public.

    What runs now

    Our account research starts with the footprint. The messages that follow cite something the reader can check on their own site or profile.

    Your scenario

    If your list came with an industry field and nothing else, map the footprint first. Our Company Social Presence Mapper and Domain to LinkedIn URL Resolver run on Apify and drop straight into a Clay table. Or send us 20 rows, and we'll show you what their public footprint says before you write to them.

    Client names are always kept confidential at MMG, so they have been removed from this case study.

    Published October 13, 2026

    Last updated October 17, 2026