Let an observed event build the account list, not a purchased one

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

    Hiring and funding signals as the trigger, not the list

    All case studies

    The drawing

    Job postingsEvent observedFunding recordsReporting datesCompany enters thelistOpening line names theevent

    The problem

    A bought list tells you who exists. It doesn't tell you who has a reason to talk this month. So the first line of the email ends up about the sender.

    What we built

    Lists that start from an event instead of a filter, built in Clay from our own actors on Apify. A company enters the list because something happened that we can point to: it posted a go to market role, it raised money, or its reporting date is coming up. The opening line names that event, so the reader can check it against their own company.

    What it produced

    Three builds from this library used the pattern.

    • Our own client acquisition pipeline discovered 831 companies from 1,727 job postings for go to market roles, on a September 2026 read. Every company is on the list because of a posting.
    • A job posting pipeline for a client turned 209 postings into 40 cards a person could approve with one click.
    • A reporting calendar of 658,166 public company rows gave a client the date each company reports, so outreach landed in the window around it.

    None of these lists was bought. Each was generated by an event someone can verify.

    What runs now

    Our signal builds start from the event and keep it on the row, so the copy can cite it.

    Your scenario

    If your opening line could be sent to any company on your list, start the list from an event. Our GTM Hiring Signal Scraper and Company Funding Record return the posting or the round with its date, ready to cite in a Clay column. Send us your ICP and we'll tell you which event we'd use to build the list instead.

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

    Published October 20, 2026

    Last updated October 22, 2026