Score every lead. Pay per match.
Lead Scoring appends firmographic, demographic, and technographic attributes to every inbound lead — company size, revenue, industry, job title, seniority, funding signals, and tech stack — so your scoring model ranks on ICP fit. Billed per matched record. No subscription, no seat license, no contracts.
Built for teams that need lead context before the rep touches it.
Four shapes of customer who benefit most. If you recognize your workflow, the math is in your favor.
Give your model the attributes it was built to consume.
Scoring models trained on firmographic and demographic features can only perform if those fields are populated. Append company size, revenue band, industry, and job seniority to every inbound record before the model runs — so predictions reflect ICP fit, not just who clicked a nurture email.
Route the highest-probability accounts first.
Without fit data, reps default to FIFO or gut feel. Enrich every inbound lead with firmographic signals and let the score decide priority. High-fit accounts land at the top of the queue; poor-fit leads get deprioritized before anyone wastes call time on them.
Fill short-form gaps without asking more questions.
Short signup forms capture an email and a name. Lead Scoring fills the rest — company headcount, industry, role, and tech stack — so your routing logic, segmentation, and downstream reporting work without forcing users through a ten-field form that kills conversion.
Segment and personalize on firmographic signals.
Campaign personalization and list segmentation require attributes your CRM often doesn't have. Enrich your nurture list on enrichment day so sequences can branch by company size, vertical, and growth stage — and so reporting reflects actual audience composition, not self-reported data.
Stop routing leads on gut feel.
Your first scored lead lands in under a minute. If you don't use the API for a month, you don't pay for the month. That's the entire deal.
- Charged only on a matched record
- No seat license required
The honest answers.
If something below doesn't cover your case, ping us — we answer directly, no SDR funnel.
What does "pay per enriched record" actually mean?
+
You're billed once per lead that returns a matched enrichment result. If a record can't be matched to a company or professional profile, you're charged zero for that record. No monthly floor, no minimum batch size, no tiered pricing.
What firmographic and demographic fields does Lead Scoring return?
+
Firmographic: company name, domain, industry, employee headcount, estimated revenue, HQ location, funding stage, total funding raised, headcount growth rate, and recent funding signals. Demographic: job title, seniority level, department, and role function. Technographic (optional): tech stack categories and specific tools in use.
What if a lead can't be matched to a company or profile?
+
Unmatched records cost zero. The API returns a clear no-match response so your pipeline can branch — route unmatched leads to a manual review queue or a fallback enrichment source without paying for a failed lookup.
Does this work with short-form signups where I only have an email?
+
Yes. Email is the primary key. Lead Scoring resolves the email to a professional profile and parent company, then appends firmographic and demographic attributes without requiring a company name or domain from the submitter.
How does billing work?
+
You're charged per matched record. No monthly fee, no minimum spend — you only pay when a lead returns a result.
How is this different from Clearbit, ZoomInfo, or Apollo enrichment?
+
Those are subscription products with seats, dashboards, and annual contracts. Lead Scoring is one endpoint billed per matched record. If you need a UI and a full GTM platform, those are the right tools. If you need enrichment as one step in an agent, a scoring pipeline, or a SaaS workflow, an API priced per result is a better shape.
What's the rate limit?
+
100 RPS per key by default; we'll lift it on request. Concurrency-fair queueing means batch enrichment jobs never starve real-time inbound flows on the same key.