Eleven job sources measured over 30 days: one found 2,450 of 2,552 new companies

    Who this was forA B2B company that prospects off job postings in three countries, with a sweep that runs every morning.

    Counting what each job source returns, then capping the one that pays

    All case studies

    The drawing

    11 job sources30 days of runs,counted per sourceNew companies persourceFixed cap: 70 searchesa day, 23 per countryPause list for setdaysSweep spends insidethe cap

    The problem

    The sweep pulled from 11 sources. More sources sounds like more coverage. Nobody had counted what each one returned.

    The paid search source had a daily allowance set by a formula. On the day we looked, it allowed 242 searches. We replaced it with one fixed number anyone can read and change.

    What we built

    A per source count from the sweep's own run log: 30 days, every run. For each source we counted runs, calls, raw postings, and new companies. We also checked that the free boards weren't failing quietly. Every one answered every time. They just don't list the roles this client prospects against.

    Then a fixed cap. The paid source now runs at most 70 searches a day, split 23 per country, so three country runs can't pass 70. The cap lives in one settings row. Changing it takes one update and no deploy.

    A pause list sits beside it. A listed day records a skip, spends nothing, and makes no cards. The next day runs as normal.

    What it produced

    SourceRunsNew companies
    Search based jobs source912,450
    Job board API7367
    Job feed aggregator3531
    Job data API333
    Seven free remote boards, combined2381
    • One source found 96 percent of the new companies, 2,450 of 2,552.
    • Seven boards ran 238 times between them and found 1 company.
    • The cap read back from the live settings: 70 a day, 23 per country.
    • The first pause covered a weekend. Read back through the released code's own clock, both mornings skip and Monday runs.

    Your scenario

    If your sweep pulls from many sources, count new companies per source before you add another one. Apollo.io filters accounts by active job postings. Our Job Posting Monitor on Apify pulls postings from several sources in one run. Send us your source list and we'll tell you which one we'd cut first.

    Related tools: Apollo.io, Apify, Job Posting Monitor on the Apify Store, Job Posting Monitor

    Some of the links on this page are affiliate links.

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

    Published October 27, 2026

    Last updated October 28, 2026