Who it's for
- Sales and growth ops teams who need to prioritize a finite rep capacity.
- Founders running outbound who want to work the best leads first.
- Anyone turning a raw local list into a ranked, workable pipeline.
Score local leads on real attributes - ratings, reachability, web presence.
The problem
Most lead lists are unscored: every row looks equally promising until a rep wastes time finding out otherwise. Without consistent attributes, you cannot prioritize, so high-value and dead-end leads get the same effort.
biz collect returns the same structured signals for every business - ratings, reviews, whether there is a reachable email and phone, web presence, opening hours - so you can compute a fit or reachability score before a human touches the list. Because the fields are stable, the scoring logic is written once and applied to every lead.
The workflow
POST a search for the category and region you sell into, then poll GET /v1/jobs/:id until you have the structured list of businesses to score.
Decide which fields drive your score - for example, rating and review count for quality, presence of a deduped email and phone for reachability, and a website for web presence.
Because every record shares the same schema, normalize the chosen fields into comparable values (for example, 0 to 1) without per-source special cases.
Combine the normalized signals into a single score per lead and rank the list, so the most reachable, highest-quality businesses rise to the top.
Send the highest-scoring leads to reps or an outreach sequence first, and tier the rest, so effort follows the score instead of list order.
Fields & endpoints
ratings, reviewsQuality signals you can weight to favor well-established businesses.
email(s), phoneReachability signals - a lead with a deduped email and phone is far more workable.
website, social profiles, outgoing linksWeb-presence signals that hint at a business's maturity and activity.
live open/closed status, opening hoursOperational signals that help you focus on active, contactable businesses.
stable JSON schemaSame fields every time means the scoring logic is written once, not per source.
Example
Suppose a growth team has a list of several hundred local businesses from a biz collect search and limited rep capacity. They define a simple score: higher rating and review count raise it, a present email and phone raise it, and a working website raises it.
Because every record has the same fields, they compute the score across the whole list in one pass and route the top tier to reps first. Reps spend their time on reachable, well-rated businesses instead of working the list top to bottom. This is an illustrative scoring approach; the right weights depend on what predicts a good fit for your offer.
Everything you need to ship this workflow:
Lead scoring
Collect leads with a search, pick scoring signals from the returned fields (ratings, reviews, presence of email and phone, website), normalize them, combine into one score per lead, and rank the list so the best leads are worked first.
Ratings and review count for quality, deduped emails and phone for reachability, website and social profiles for web presence, and open/closed status and hours for operational signals. Every record shares these fields.
Because the same fields come back for every business, you write the scoring logic once and apply it to the whole list - no per-source special cases or field-name guessing that would skew the score.
No. biz collect provides consistent, structured signals; you choose the weights and compute the score in your own pipeline. That keeps the scoring logic specific to what predicts a good fit for your offer.
Yes. The free tier's 200 signup credits plus 20 daily login credits, with no card and free polling, are enough to pull a real list and test a scoring model before scaling up.
Still have questions? Talk to us.
Related guides to take your business-data workflow further.
Sign up free with 200 signup credits, no credit card. POST a search, poll the job, and wire the structured JSON straight into your stack.