Enter the registration and use Check case before creating another lead, HPI import or route run for the same vehicle.
Cloudflare protected
Signing in
£0 Google stack
Backend loading…
Buyer route command centre.
Enter the vehicle once. CarKonnect gets a ranked buyer strategy with commercial buyers, private routes, communities, warnings and quote logging.
⌁
No route generated yet
Complete the vehicle intake, then run the buyer route engine.
Step 2 / Ranked buyer strategy
Vehicle profile
—
Ranked decision records
Awaiting routes
Buyer routes
Select a route to review score factors, evidence freshness, warnings and approval together.
Step 3 / Seller reality check
Evidence-based value expectation engine
Pull stored HPI/vehicle intelligence, compare the customer target against route-based market bands, and produce a customer-safe explanation.
Value bands
Route-based realistic ranges
No reality check built yet.
HPI bridge
Stored intelligence status
Bridge not checked yet.
Customer position
Expectation gap
Enter the customer target and build a check.
Customer-safe output
Reality summary
The customer-safe summary will appear here.
Phase 9.3 / Seller handling
Conversation script
Build a reality check or click Generate seller script to create copy-ready staff wording.
Pipeline / Step 3 & 6
Quote Intelligence & Ops
Track real net offers, compare buyers, and turn recommendations into action.
Offer decision
Net offer comparison
Compare the customer outcome after fees, transport and deductions.
No buyer quotes loaded yet.
Buyer performance
Top proven buyers
No quote evidence loaded yet.
Lead outcomes
Best offers by lead
No lead quote summaries yet.
Risk control
Outliers & QA
No quote risks loaded yet.
Evidence capture
Manual quote log
Record buyer offers manually when they come from phone, email, WhatsApp or buyer portals.
Manual action
Add follow-up task
Generated output
Latest outreach drafts
No operational pack generated yet.
Follow-up queue
Open tasks
No operational tasks loaded yet.
Customer summary
Latest customer-safe draft
Generate a pack to create a customer summary.
Phase 9.4 / Ops tracker + outcome learning
Track buyer contact, best offers and final outcomes
Record which buyers were contacted, what they offered, the final route and the final achieved price. This creates a clean learning trail without any paid HPI API call.
Buyer tracker
Log buyer contact / offer
Outcome learning
Log final case outcome
Latest buyer activity
Buyer contact tracker
No buyer contacts logged yet.
Learning log
Latest outcomes
No outcomes logged yet.
Case timeline
Current case activity
No current case activity yet.
Admin / QA & System Health
Command Centre
Run automated checks across buyer routes, source links, and monitor backend readiness.
Open issues
Priority QA queue
No QA status loaded yet.
Selected issue
Issue detail
Select a QA issue to inspect its impact and recommended action.
Automation
Trigger controls
Trigger status not loaded yet.
The daily trigger runs the lightweight QA sweep only. Link checks are intentionally manual/capped to protect free Apps Script quotas.
Coverage
Queue breakdown
Source—
Routes—
Quotes—
Portfolio governance
Buyer consolidation
Run the portfolio audit to separate direct buyers from sale channels and identify evidence-safe duplicates.
Portfolio strength
Active buyer shortlist
Rank direct buyers by evidence, source quality and operational fit while protecting specialist and regional coverage.
Run the strength review before changing the live recommendation shortlist.
System health
Backend status
BuyerFinder guide
Current route intelligence workflow
Follow the case from duplicate protection and stored HPI intake through ranked routes, realistic value guidance, quote evidence, QA, buyer contact and final outcome learning.
No paid HPI calls
Use Find HPI data to populate stored vehicle, valuation and risk facts. BuyerFinder does not make a paid HPI call.
Confirm make, model, year and mileage, then add condition, seller priority and every material vehicle flag.
Run the engine and review warnings, first-wave actions and separate commercial, private, community and next-step lanes.
If staff judgement beats the recommendation, log the override route, approver, reason and customer impact before acting.
From Routes, open Price Reality to compare the customer target with route-based value bands and generate customer-safe wording.
In Pipeline, log gross offer, fees, deductions, net customer amount, payment speed, collection method and outcome.
In Admin, review source, route, duplicate, stale-evidence and quote findings. QA totals are data findings, not app crash counts.
Run the Admin portfolio audit before expansion. Direct buyers count toward the controlled ceiling; marketplaces, auctions, listings and communities remain separate sale channels.
Use the buyer strength review to protect specialist and regional coverage while moving excess unproven buyers into a reversible validation queue.
In Pipeline, generate buyer outreach, customer-safe summaries and owned follow-up tasks for the active route run.
Record contact method, status, offers, follow-up date, owner and notes so real buyer behaviour becomes evidence.
Save the final route, achieved price, outcome status, time to outcome and learning reason for future scoring.
Open the matching Vehicle Intelligence Sale workspace, refresh BuyerFinder status and import the stored route run.
Four workspaces:
Intake holds vehicle facts, Routes holds ranked recommendations and Price Reality, Pipeline holds quotes and operational follow-up, and Admin holds QA and system health.
Refresh protection:
The current recommendation is restored for up to seven days on the same device. This protects active route work from an accidental refresh.
Starting another vehicle:
Press Clear. It removes the intake, visible routes and saved active recommendation from that device; it does not delete historical backend route runs.
Buyer evidence standard:
Official sources support route confidence, but a buyer becomes commercially proven only through real contact, quote and outcome evidence. After a backend code upgrade, use Sync backend schema once. Use the expansion and rebuild controls only after intentional database or evidence changes.