How we run it / Prospeo

How we use Prospeo to find verified mobile numbers for decision makers

Searches are free. A verified mobile is 10 credits. Set the filter in the search, qualify before you reveal, then prove the number twice.

By Corey Leon · Sep 21, 2026 · about 4 min read

Prospeo.io is where the verified mobiles come from. It is the source for my own lists and for every client list that is not on another vendor's contract. The trick is not the tool. It is where you put the filter.

Most people search, export, then try to find phone numbers for the export. I set verified mobile inside the search. Searches are free, so I scan thousands of rows and only pay for the ones that pass everything else.

Disclosure first: I am a paid Prospeo.io content partner and the code on this page, MKCY4Z, is mine. If you sign up and use it at checkout, it credits me. The process below is what I ran last week, code or no code.

The build, in six steps

  1. 01

    Put verified mobile inside the search

    The search-person endpoint takes a verified-mobile filter as part of the query. Turn it on before the titles, before the industries, before anything. Now every row that comes back is a person the vendor believes has a mobile it can verify.

    No exporting 2,000 rows to find 300 with phones. The search itself costs nothing.

  2. 02

    Write the filter set from the buyer, not from the tool

    For a trades client last week: Owner, President, CEO and General Manager. Companies with 5 to 100 people. The trades industries the client sells to. United States. Then one line that came from the client that morning: remove the operations titles, because at that size the owner picks up the phone.

    The filter set is a description of one buyer. If it takes more than a few lines, the buyer is not defined yet.

  3. 03

    Qualify on your side before you reveal

    Two runs scanned 1,425 and 3,375 rows. My own script qualified 300 and 342 against the buyer profile. Live dedupe against three CRM orgs took those to 150 and 170 net-new. All 320 were verified-mobile matches, and they cost 3,105 credits, about 10 each.

    A third run scanned 4,175 rows, qualified 301, netted 150, and cost zero credits because the session state was reused. Scan wide. Reveal narrow.

  4. 04

    Enrich in bulk by LinkedIn URL

    The bulk-enrich-person endpoint accepts an identifier and a linkedin_url directly. No person-id lookup first. Send the URLs from your qualified list and take the mobiles back in one pass.

    The finder endpoints are deprecated. Do not build on them.

  5. 05

    Then prove the number twice

    Verified is a prediction. A bounce is the truth. Prospeo-verified emails still hard bounce sometimes, and on job changers the email points at the old employer while LinkedIn shows the new one, 7 of 9 in one test.

    So every list goes through the Apify still-in-role check, then every mobile goes through Trestle and is kept only if line_type says Mobile. On the last build the two checks removed 10 people and 19 numbers that Prospeo had, in good faith, called verified.

  6. 06

    Do the credit math before you start

    A verified mobile reveal is 10 credits. 200 mobiles is 2,000 credits. Last week 320 mobiles took 3,105.

    And the numbers hold up on the phone. On my board, Prospeo-sourced mobiles connected at 13.1 percent against 7.8 percent from another vendor, though the sample is small enough that I call it a lean, not a fact.

Run this today

  1. Write the buyer in five lines: titles, headcount, industries, location, verified mobile on.
  2. Run the search with verified mobile on. Reveal nothing yet.
  3. Score every row against the buyer in your own script. Drop the near-misses.
  4. Dedupe against every CRM you own before you spend a credit.
  5. Bulk enrich by LinkedIn URL. Take the mobiles back in one pass.
  6. Run Apify for still-in-role, then Trestle for line type. Hold what fails.
  7. Load to your CRM with Line Type Mobile and Validator Trestle on every lead.

Free

The trades filter set and the credit math

The exact search I ran last week and what 200 mobiles cost. If you sign up to Prospeo.io, code MKCY4Z at checkout is my partner code.

SEARCH    /search-person  (free to run)
Titles    Owner, President, CEO, General Manager
Size      5 to 100 employees
Industry  the trades the client sells to (for example construction, roofing, HVAC, plumbing, electrical)
Location  United States
Mobile    verified only, set IN the search
Exclude   operations titles when the owner is the buyer
Reveal    10 credits per verified mobile
Bulk      POST /bulk-enrich-person   {"identifier": "...", "linkedin_url": "..."}
Math      200 mobiles = 2,000 credits.   Last week: 320 mobiles = 3,105 credits.
Then      Apify still-in-role -> Trestle line_type == Mobile -> CRM
Code      MKCY4Z at checkout (my partner code; the process runs the same without it)

Free

The 10 prompts that run this.

Text me the word prompts and I text you the pack. Then tell me what you sell and I'll say which one to run first.

Text me 'prompts'

or text prompts to +1 (617) 710-6179

Want to read them first? The 10 prompts are here.

Texting me starts a two-way conversation. Reply STOP any time.

FAQ

The questions I get on this.

Is a Prospeo verified mobile really verified?

It is verified as far as a vendor can verify: their model says the number reaches the person. It does not know if the line is a cell or if the person still works there. That is why Apify and Trestle run after it. On the last build they held out 10 people and 19 numbers.

How many credits does a mobile cost?

Ten. Searches are free. Last week 320 mobiles cost 3,105 credits, so plan on 10 each and budget the reveal after you have qualified, not before.

What is the code MKCY4Z?

My Prospeo.io partner code. If you sign up and use it at checkout, it credits me. It does not change anything on this page. The process runs the same without it.

Why not just email the list?

On a job-changer list the email points at the old company 7 times in 9. Mobiles follow the person. Build for mobiles you can call, and let the email run behind the calls on the same list. Here is what the calls cost.

The rest of the system

One page per tool.

The systemThe whole stack in six pieces, and how they fit. CloseSmart views, the 10-call cap, drafts only, the post-call note. ClaudeThe ten prompts, the org chart, and the model routing. ApifyWho posts, who changed jobs, who already left. The actor and the trap. TrestleOne API call, one field. The drop list and why the score is ignored. Stop wasting timeFour measured rules, and the numbers that made my own count go down.

The 10 prompts Pricing The install Book a call