LeadFi
Lead pre-qualification
Real-time financial pre-qualification for sales leads: the moment the form is submitted, you know whether the lead can afford the offer.
Three fields in. Buying power out.
LeadFi works from a name, an email and a phone number. It identifies the person, runs a soft credit pull with the three major US bureaus, and returns a result a sales team can route on: SQL or NQL, with a tier. The data comes from the bureaus, not from a modeled estimate. The soft pull does not affect the consumer's credit score, and LeadFi is not a lender and makes no credit decision.
- For
- Sales teams with high-ticket offers in the US
- Input
- Name, email and phone. No SSN, date of birth or address
- Reached by
- REST API, MCP server, form widget, Zapier, Make and GoHighLevel
- Language
- English
How it works
- Step 1
A lead submits a form
The business's own funnel captures name, email and phone. LeadFi is triggered through the API, a form widget, or a workflow in the CRM.
- Step 2
Soft pull
LeadFi identifies the person and reads bureau data: VantageScore 4.0, available credit, estimated annual income and debt-to-income ratio.
- Step 3
Qualification
The package's active rule set classifies the lead as SQL or NQL and assigns a tier from 0 to 3. Which rule set scored the lead comes back with the result.
- Step 4
Routing
The result updates the CRM record. A qualified lead goes to the sales calendar and the rest go to a different offer. A direct API request takes about three seconds.
What is inside
Four qualification types
Basic, based on credit score, advanced with multi-criteria rules, and a guided AI setup. Each package has one active type.
Tiers 0 to 3
Every tier is still an SQL; the tier is another way to prioritize. Thresholds are adjustable per package.
Returned data
VantageScore 4.0, available credit limit, annual income, debt-to-income ratio, address and age. A higher package adds assets and a credit report summary.
API and sandbox
Sandbox endpoints are free and return mock data, so the integration and the field mapping can be tested before a real run.
MCP server
Run a pre-qualification inside an AI agent, with a credential separate from the API key.
No-code connectors
Zapier, Make, a GoHighLevel app, and a widget that attaches to existing forms with one script tag.
Bulk and manual
CSV upload for lists, and single requests from inside the dashboard.
Teams
Invite teammates, with separate access to each area of the account.
How it is built
What it runs on
Billing per successful request
A charge is made for each successful pull, not for each unique lead. The amount for that request comes back in the response itself.
API keys are hashed
Keys are stored as hashes, and secret values are redacted before they can reach a log.
Observability without personal data
Every event is recorded with a correlation id, and the log document is built so that personal data is not in it.
Bulk work runs in a queue
Bulk uploads are processed asynchronously in a queue, so they do not slow real-time requests.
What it does not do
These are the product's own statements, not ours.
- It is not a lender and makes no lending or credit decision. That decision belongs to the lender.
- A result is the business's own rules applied to bureau data. It is not an offer of credit.
- It is built for pre-qualifying a business's own prospective customers, not for screening job applicants, tenants or insurance.