← Back to the console
How to use

A 60-second guide to the Velocity Console.

The Console is a live lead-triage tool. It takes 400 sample leads, scores every one on BANT (Budget · Authority · Need · Timeline), and lets you filter, inspect, route, and even score brand-new leads in real time. Here's how to drive it.

Open the console →

Four things you can do

Everything runs in your browser — no login, no server, no wait.
1

Read the pipeline at a glance

The strip of numbers at the top is your live snapshot. It updates instantly whenever you filter.

  • Leads in view · High / Medium / Low counts
  • Avg BANT / 12 — average score of what's shown
  • Never contacted — leads the old manual process dropped
2

Work the queue

Slice the 400 leads down to exactly what you care about.

  • Search — type any word (region, role, a phrase in the message)
  • Tier chips — All / High / Medium / Low
  • Source and Sort — by score, newest, or slowest response
  • Only never-contacted — surface the dropped leads
3

Open a lead & route it

Click any row. The panel on the right shows the full picture.

  • The lead's own message and details
  • Its BANT bars and total, with the reason
  • The recommended action + SLA, and how long it actually waited
  • Hit Route this lead to action it — the queue updates
4

Score a brand-new lead

Click ⚡ Score a lead (top-right). This is the real engine, live.

  • Type or paste any message, or click a preset (Strong / Warm / Cold)
  • Pick source, role, size → Score this lead
  • See its BANT breakdown, tier, and routing decision instantly
This uses the same scoring logic as the 400 leads — proof the engine actually reads and reasons over the text, not a canned result.

What the scores mean

Each lead is scored 0–3 on four signals; the total (0–12) sets the priority and the routing SLA.
SignalWhat it measures
BudgetMoney / approval / spend signals — is there budget to buy?
AuthorityIs the writer a decision-maker or buyer? (role + language)
NeedHow specific and pressing is the pain?
TimelineHow soon must they act? (deadline / buying now)
TierBANT totalRouting SLAAction
High8–125 minAlert an AE + auto-book a call
Medium3–760 minSDR queue, same-hour follow-up
Low0–224 hAutomated nurture sequence
For reviewers

What this demonstrates

A quick guide if you're evaluating the work behind it.

30-second demo

  1. "Here's a real intake queue — 400 leads, scored and prioritized." (filter to High)
  2. "Click a hot one — it explains why it's high and what to do." (open a lead)
  3. "And it's not a mockup —" (⚡ Score a lead → a preset → Score) "same logic, running live on anything you type."

Under the hood

  • LLM-based BANT scoring (Claude) with structured JSON outputs
  • A deterministic rules engine, ported to run client-side
  • Interactive data UI — filtering, sorting, live KPIs, routing state
  • Zero dependencies — hostable free on GitHub Pages