Loading…
Loading…
This is the website-facing version of the directory work in the codebase. A directory owner gets a category intake path, buyer routing matrix, billing gate, delivery handoff, lead inventory, and outcome reporting without handing clients a pile of tools.
Local directory, media site, niche directory, community portal, review site, or association that wants to monetize demand.
Service provider, franchisee, agency, sponsor, or partner that pays for routed opportunities in approved categories and markets.
The downstream visitor who submits a category-specific request and receives a clear next step without seeing internal tools.
The team that monitors route health, buyer capacity, billing status, delivery outcomes, and revenue performance.
Capture surface
The requester chooses a category, market, urgency, contact method, and problem description from a public intake page.
Routing engine
The system resolves the active buyer node for that tenant, category, location, and exclusivity rule.
Revenue guard
If billing enforcement is enabled, inactive subscriptions are blocked before delivery so unpaid buyers do not receive leads.
Delivery hub
Qualified lead details are sent through the delivery hub to CRM, webhook, automation, or simulated handoff when credentials are not connected.
Operator reporting
The route is logged with category, node, delivery mode, outcome, and trace events for operator review.
| Category | Market | Intent | Buyer node | Price band |
|---|---|---|---|---|
| Plumbing | Erie, PA | Emergency and same-day jobs | plumber_erie_test_1 | $35-$95 per qualified lead |
| HVAC | Erie, PA | Repair, replacement, and maintenance | hvac_erie_test_1 | $45-$125 per qualified lead |
| Roofing | Any local service market | Storm damage, quotes, insurance work | Configured buyer node | $60-$180 per qualified lead |
| Dental | Any clinic market | New patient, emergency, high-value treatment | Configured buyer node | $40-$150 per qualified lead |
These are the fields the directory needs to route a request immediately after submission. The operator can swap categories, markets, buyer rules, and delivery destinations without changing the customer experience.
Category
Plumbing, HVAC, roofing, dental, legal, SaaS
Location
City, ZIP, territory, service area
Urgency
Emergency, this week, researching, recurring need
Contact
Name, email, phone, preferred response path
Problem
Plain-language description of what the requester needs
Consent
Permission and routing disclosure for the lead handoff
A customer-facing page that asks only for the information required to route the request.
Visible category-to-buyer rules with fallback, billing, and delivery states.
Buyer-facing inventory with score, temperature, category, market, and claim action.
The sellable solution that creates the intake, routing, pricing, buyer onboarding, and reporting outputs.
Website-rendered documentation for the Erie seeded implementation and production limitations.
Read-only website view of the route resolver and delivery handoff implementation.
Capture urgent local service demand, qualify it, route it, and prove source-level ROI.
A launched local lead capture workspace with intake, scoring, follow-up, embed code, and operator view.
Open packageTurn directory traffic into routed, monetizable lead demand.
A category-based directory intake system with buyer routing, source tracking, and monetization surfaces.
Open packageRoute leads to the right territory while keeping brand-level visibility.
A territory-aware capture and routing system with operator controls and territory reporting.
Open packagePackage qualified leads into buyer-ready inventory with pricing, claim, and outcome tracking.
A launched marketplace surface with inventory, buyer claim flow, pricing logic, and revenue tracking.
Open packageErie is only the seeded example. The same frontend and routing pattern works for many directory categories.
A complete solution: pages, route logic, buyer handoffs, monetization, and reports.