A response is not a prospect until a person says it is.
Any platform can deliver leads. The advantage is the evidence-backed system that decides what a response means, protects data integrity, requires approval before saving anything, and learns which acquisition produced real revenue.
Every route in — paid, discovered, imported, manual — stops at the same decision.
Find
Discovery across verified records, local data and the signals your market leaves behind.
FindVerify
Every record checked before it is saved. Nothing invented, nothing implied.
FindScore
Fit and intent, with the evidence for the score shown beside it.
FindPersonalise
Outreach drafted per person, per channel, from your approved facts.
ReachFollow up
Sequences that keep going between calls, with review gates where you want them.
NurtureNo code path saves a prospect without human approval.
Paid campaigns, discovery, imports and manual records all pass through the same governed approval path. A submission is preserved as immutable evidence — it does not become a saved relationship until someone reviews it and decides.
Map the market before you touch it.
Reach is worthless without judgement. These six steps sit between a data universe and a single approved message.
- 01
Market mapping
Define segments, territories, account clusters and underserved niches.
- 02
Discovery
Find businesses and people that match approved fit criteria.
- 03
Verification
Improve completeness and prioritise records supported by stronger evidence.
- 04
Intent signals
Combine timing, relevance, relationship and lifecycle signals.
- 05
Market making
Shape categories, offers and narratives around unmet demand.
- 06
Reviewed activation
Move selected opportunities into review, consent and messaging controls.
Coverage, verification level and permitted fields vary by source, geography, plan and applicable data-protection law. “Up to 5B” describes the maximum available data universe, not the records available in every market.
Seven steps between a raw response and a saved prospect.
Each step is a real guarantee, not a processing stage. Together they are why the record can be trusted enough to act on.
- 01Receive
Accept a signed webhook, provider sync or first-party form. The raw body is preserved immutably.
- 02Authenticate
Verify the signature, resolve the correct workspace and business, reject unknown mappings.
- 03Deduplicate
Compare platform id, email, phone and known identity. Deterministic matches run first.
- 04Validate
Check the contact path is real and reachable. A submitted value is never replaced by a guess.
- 05Analyse
Evaluate offer relevance, fit, intent, completeness, risk, urgency and the next action.
- 06Review
Create a review item with clear evidence and any duplicate warning. No prospect exists yet.
- 07Approve
Only approval creates the saved prospect and its workspace — in one atomic transaction.
Every field says where it came from.
This is the difference between a database you act on and one you second-guess. A submitted email and an inferred company are both useful — but they are never shown as the same kind of truth.
Inference never overwrites fact
An inferred value carries a distinct badge and cannot replace something the person actually submitted. Missing stays visibly missing — the system will not invent a placeholder to fill a gap.
Submitted
Provided directly by the person through a form, message or explicit interaction.
Platform verified
Returned by an authorised platform, with an immutable source reference.
Externally verified
Confirmed by a named validation source, shown with provider, time and confidence.
User confirmed
Confirmed or corrected by someone on your team. User, time and prior value are recorded.
AI inferred
Inferred from context or patterns — not verified fact. Carries a distinct badge.
Missing
Not known. Displayed as unknown. No placeholder identity or contact path is fabricated.
Five ways a review can end.
Review is the only door into your saved relationships. Whichever decision you make, the original submission and its reason are retained.
- Approve
Creates the saved prospect and a dedicated workspace together.
Prospect createdSubmission retained - Merge
Attaches the submission and campaign activity to an existing prospect. No duplicate.
Prospect createdSubmission retained - Reject
Retains the source submission and reason under retention policy. No prospect created.
Prospect createdSubmission retained - Needs information
Holds it in review and triggers an allowed follow-up request.
Prospect createdSubmission retained - Assign or defer
Sets an owner and review date without changing save status.
Prospect createdSubmission retained
Outcomes travel back to whatever created them.
Internal lifecycle events are recorded for every relationship. Selected, consented events are relayed back to the ad networks so optimisation targets qualified pipeline instead of raw lead volume.
- Lead submitted
- Review approved
- Prospect qualified
- Meeting booked
- Opportunity created
- Customer won
- Revenue recorded
Only consented events are relayed, so optimisation targets pipeline rather than lead volume.
Know which activity actually created revenue.
That answer only exists if every prospect carries its evidence and its origin. That is what iQ Prospects is for.
