Turn fragmented lead inputs into clean, usable company and contact data.
Leads Pro gives outbound teams a fast way to resolve names, companies, work emails, phones, LinkedIn slugs, job titles, seniority, headcount, technologies, and location into a cleaner B2B data layer.
{
"email": "amanda@northpeak.io",
"company": "North Peak",
"name": "Amanda Carter"
}Auto-fill titles and company context before sequences start.
Standardize stale records and route them with stronger confidence rules.
Run enrichment, search, and batch exports without exposing raw datasets.
Useful enrichment inside real outbound workflows.
Leads Pro stays narrow where it should: match, enrich, search, batch, log, and bill by usage. That keeps the product shippable and the positioning clear.
Identity matching
Match by work email, person name, company name, phone, LinkedIn slug, or domain with confidence scoring.
Professional profile payload
Return title, department, seniority, management level, skills, languages, and location in one response.
Company intelligence
Enrich domain, website, industry, revenue, headcount, technologies, and company geo metadata.
Usage-first packaging
Sell API calls and monthly credits instead of handing out raw rows or spreadsheet exports.
Batch and search workflows
Support single enrichment, batch processing, people discovery, company search, and CSV import.
Compliance hooks
Use request IDs, audit-friendly logs, key management, and suppression workflows from the start.
Three steps from stale list to enriched pipeline.
Send sparse lead data
Pass work email, person name, company name, phone, or LinkedIn slug from your CRM, AI agent, or outbound stack.
Resolve and enrich
Match against your curated dataset, apply ranking logic, and return structured person and company JSON.
Route by confidence
Push strong matches into campaigns, review weaker ones manually, and track every request in workspace history.
A focused first release keeps the product credible.
The public surface already includes single enrichment, batch enrichment, people search, company search, API keys, history, and CSV-driven import support.
Request
- Method: POST
- Auth: `Authorization: Bearer <api_key>`
- Accepted inputs: `email`, `phone`, `linkedin`, `name`, `company`, `domain`
- Workspace tools: Search, batch, keys, history
Response fields
- `person.full_name`, `person.job_title`, `person.management_level`
- `person.skills`, `person.languages`, `person.match_confidence`
- `company.name`, `company.domain`, `company.industry`, `company.employees`
- `meta.request_id`, `meta.credits_used`, `meta.dataset_version`
Implementation checklist
Give users a direct AI-native way to use Leads Pro.
The public Skill package lets users connect Leads Pro to ChatGPT, Cursor, Claude, Dify, Coze, and other AI tools with a copy-paste setup instead of custom engineering.
One installable skill URL, one packaged skill, and OpenAPI import.
Users can enrich contacts, search people, search companies, and inspect usage through natural-language workflows once their API key is installed.
Simple volume tiers for teams validating outbound ROI.
Pricing stays lightweight for early adoption and can expand into enterprise contracts later.
$9
For founder-led outbound and early CRM cleanup.
- 500 credits / month
- Single enrichment API
- Dashboard + history
$19
For SDR pods running weekly enrichment and CSV backfills.
- 3,000 credits / month
- Batch enrichment
- Search workspace + exports
$39
For RevOps teams with recurring enrichment jobs and multi-user workflows.
- 15,000 credits / month
- Higher rate limits
- Priority support + invoicing
Sell usable calls, not raw data.
The clearest story for this product is operational leverage: better lead quality, cleaner routing, and faster enrichment inside systems users already have.
Keep compliance visible from day one.
Public language, dataset provenance, deletion handling, and suppression workflows should be explicit product decisions before paid growth scales.
Questions customers will ask before they pay.
What inputs are supported now?
Single enrichment supports email, phone, LinkedIn slug, and name with company or domain.
Can users search instead of calling the API?
Yes. The product now exposes people search, company search, batch input, and CSV-driven import flows.
Is this positioned as raw LinkedIn data?
No. Public positioning stays on enrichment outcomes and workflow utility until legal and provenance review is settled.
What gets built next after the MVP?
Production database sync, billing automation, workspace roles, CRM connectors, and stronger audit controls.