er8ic/Work/Lead Hub

Lead Hub

A reasoning layer over incomplete B2B leads.

An SDR workspace that researches each lead, matches it against the company's offers with cited evidence, and compiles a call brief the SDR reviews before dialling. When the evidence isn't there, it says so instead of guessing.

SectorB2B sales
ProductMulti-tenant web app for SDR teams
What we didProduct strategy · UX/UI · Build
Live demoai-lead-hub-virid.vercel.app ↗

01 · The problemHalf a lead, a full pitch

SDRs receive leads with a company name, maybe a contact and little else. They either spend the morning researching or pitch the wrong offer to the wrong person.

AI research tools fill the gaps with confident guesses, and nobody can tell which facts were checked and which were invented.

The brief: research every lead, recommend an offer only when the evidence supports it, and show where each fact came from.

An offer with no supporting evidence shows as insufficient evidence, never a forced guess.

The rule the match engine follows

02What we built
Research tab

Structured research, with sources

A first pass researches the company on the web and stores each finding with its source and a confidence level. The SDR can ask follow-up questions, and screenshots or PDFs dropped on the lead are read into findings too.

Findings · illustrative
Business model
Source: company website
High
Decision maker
Source: public profile
Medium
Current tooling
Source: uploaded PDF
Medium
Budget timing
No source found
Unknown
Match tab

One recommendation per offer

The engine reasons over the findings against the company's offers, ideal customer profile and sales knowledge. Each offer gets a tier, a confidence, the reasoning, negative signals and citations back to specific findings, or an explicit "do not pitch yet".

Offer match · illustrative
Offer A
Cites findings 1 and 3
Pitch first
Offer B
Negative signal: no budget timing
Do not pitch yet
Offer C
No supporting finding
Insufficient evidence
Brief tab

A call brief, ready to edit

Findings and recommendations merge into an editable, copy-ready call brief from a fixed template. It stays a draft until the SDR marks it reviewed. Logging a call outcome re-runs the match.

Call briefDraft
Who you're calling✓
What they do✓
Offer to lead with✓
Questions to ask✓
Draft→Mark reviewed→Call→Log outcome
Trust

Every field tagged by where it came from

Each field and contact carries a provenance tag, so the SDR knows what a person entered, what AI found, what AI inferred and what has been verified. A maturity checklist, made of plain rules with no AI, shows how ready the lead is on every tab.

Lead maturity
Company identified✓
Decision maker✓
Business understood✓
Need confirmed–
Provenance
User providedUSER
AI researchedAI
AI inferenceINF
Human verified✓
03How a lead moves
01

Research

Web research and uploaded files become findings with a source and a confidence.

  • Follow-up questions
  • Screenshots & PDFs
02

Match

Findings are weighed against each offer, with evidence cited and gaps called out.

  • Tier & confidence
  • Do not pitch yet
03

Brief

A copy-ready call brief from a fixed template, reviewed by the SDR.

  • Editable draft
  • Marked reviewed
04

Learn

Call outcomes are logged and the match runs again with the new facts.

  • Outcome logging
  • Re-matching

04 · Under the hoodHow it's built

Next.js App RouterTypeScriptTailwindPostgreSQL + pgvectorPrismaAuth.jsOpenAI with web searchVision & document input

Each company is its own tenant with Admin and SDR roles. Admins manage the company knowledge: services, offers, ideal customer profile and sales notes. Every AI action fails gracefully with the real error message instead of breaking the page.

Next step Got a project in mind?

Three short steps on the contact page. Or write to hello@er8ic.com.