Manycrawl
Download

Use cases / Lead generation

Build the list, then find out who can actually pay

Most lead lists fail at the same place: they have names and no way to tell a real prospect from a dormant one. This recipe builds the list, fills in contact data, and then adds the two signals that separate them.

Where it stops working — Apollo emails stay locked, and firmographics needs a LinkedIn company URL that Maps will not give you.

1–2kresults per Apollo search, without spending an Apollo credit
78 / 78Maps places that came back with a website on a real run
1 actionper row processed, and importing rows is free

The recipeSix steps, in this order

  1. 1

    Apollo or Google Maps

    Apollo when you know the firmographic shape you want. Maps when the segment is defined by place rather than by industry code. Both put one row per company in a table.

  2. 2

    Email finder

    Reads each company's own website and takes the addresses published on it. Free, no key, and the ones it finds are real rather than guessed.

  3. 3

    Find email by domain

    For the rows step 2 left empty. Put a run condition on it so it only fires where Email is blank: skipped rows cost nothing, and you only pay Findymail for the gaps.

  4. 4

    Company firmographics

    Industry, size, HQ and follower count from the public LinkedIn page. This is what lets you cut the list down to the segment you actually sell to.

  5. 5

    Tech stack detector

    The fit check. A Shopify store, a HubSpot shop and a WordPress site last touched in 2019 are three different conversations, and the stack tells you which one you are walking into.

  6. 6

    Filter, then export

    Filter to rows that have an email and match your segment, and send them straight into a Manyreach sequence or out as CSV.

Why this orderCheap signals first

Steps 2 and 5 need no API key at all. Step 3 is the only one that costs money outside Manycrawl, and it runs last among the contact steps, on the smallest possible set of rows. Putting the paid lookup behind a run condition is the single biggest lever on what a list costs you.

What it costsPay for the work, not the seat

Importing a 500-company list is free; running three columns over it is 1,500 actions. Pro is $39/month with no action limit; Lite is $19/month with 5,000 actions. The fetching runs on your own machine, from your own IP, so the price stays flat however long the list gets — unlike a credit-priced tool, where every row enriched is another charge.

How that compares with Clay

Where this recipe stops working

Apollo emails stay locked, so step 2 and 3 are doing real work rather than unlocking something you already had. Company firmographics needs a LinkedIn company URL per row, which Apollo gives you and Maps does not. And the stack is only what a page reveals: a hand-built site with no third-party tags comes back empty, which is not the same as having no stack.

FAQQuestions people actually ask

How many rows before this gets expensive?

One action per row per column. A 500-row list through steps 2, 4 and 5 is 1,500 actions, which is well past the free 500, inside Lite's 5,000 a month, and nothing for Pro's unlimited tier.

Do I need both Apollo and Maps?

No. Pick whichever matches how your segment is defined. Running both and merging is useful mainly when you want local coverage that Apollo's database is thin on.

Can I skip the email finder and just use Findymail?

You can, and it will cost more. Published addresses cover a real share of a list for free; paying for those rows too is money spent on data that was sitting on the homepage.

Will this keep running on its own?

Turn on auto-run for the enrichment columns and set the source to re-check on a schedule. New companies arrive already enriched. It only runs while the app is open.