Qualified lead routing model
This is the operating model for turning buyer-intent submissions into monetizable vendor conversations without becoming a generic directory.
Lead qualification
Intent score, budget, urgency, workflow, industry, systems used, and implementation constraints determine routing priority.
Vendor eligibility
Vendors qualify by category fit, integration coverage, setup complexity, support responsiveness, and verified profile completeness.
Revenue path
Start with free matching, then add claimed profiles, sponsored visibility, qualified lead fees, vendor analytics, and dataset/API licensing.
Routing statuses
- new_match: buyer submitted matching wizard with vendor recommendations
- qualified: buyer has budget, urgency, and clear workflow owner
- needs_research: vendor fit unclear or data enrichment needed
- routed: sent to one or more relevant vendors or implementation partners
- closed_loop: outcome tracked for vendor analytics and future scoring
What gets routed
- Top recommended vendor slugs and match scores
- Buyer intent score and urgency
- Workflow goal and vertical
- Required systems/integrations and implementation constraints
- Budget range and company size
Next build sequence
- Apply the Supabase buyer-intelligence migration
- Store structured fields as columns instead of message enrichment only
- Create an internal lead routing view/export
- Add vendor claim fields for preferred lead categories and geography
- Track close-loop outcomes: accepted, rejected, booked, won, stale