eConstruct Homes — AI Lead Engine

The Bottleneck Nobody Solved

After the Palisades and Altadena fires, thousands of California homeowners were displaced overnight. Every high-end builder in LA wanted those rebuild contracts — but the discovery problem was brutal. CAL FIRE's Damage Inspection System (DINS) publishes structured records of every destroyed property. Los Angeles County's assessor maintains ownership records. LADBS tracks permit activity. Apollo holds contact data. The information exists — it's just scattered across five systems, none of which talk to each other.

The builder who wins is the builder who sees the homeowner first, contacts them first, earns their trust first, and signs the contract first. Human prospecting cannot win this race. An agent swarm can.

The Agent Swarm

The eConstruct Homes AI Lead Engine runs seven named agents in continuous loop:

• ladbs-scrape — harvests LA Department of Building & Safety permit data on an interval
• assessor-enrich — cross-references destroyed-structure addresses against county assessor records to identify homeowners
• apollo-enrich — attaches verified phone and email to each homeowner lead
• deed-monitor — watches for title transfers and ownership changes
• score-leads — an LLM grader that assigns each lead an A / B / C / D grade based on property value, displacement recency, permit activity, and contact quality
• email-nurture — runs multi-touch sequences that adapt based on reply signals, promoting a lead from warm to hot
• sla-alert — the closer. The moment a lead crosses the hot threshold, it fires an SMS to the owner's phone with the lead summary and booking link

Each agent logs its runs to the mission-control dashboard with status (success / running / failed) and duration. The owner sees the pipeline live.

The Dashboard

Mission Control surfaces four headline metrics at the top: Total Leads, Hot Leads, Won Deals, and Agent Runs. A lead-source donut shows the split between CAL FIRE DINS ingestion and consultation-page captures. A live activity feed shows every agent execution in real time. Current state: 779 leads ingested, 10 recent agent runs, CAL FIRE pipeline producing the dominant share of high-intent inventory.

Why SMS, Not Email, for the Final Handoff

Hot leads have a response-time half-life measured in minutes. Email notifications get buried. Push notifications get dismissed. SMS gets opened. The SLA-alert agent is deliberately the loudest, rudest, most interruptive handoff in the stack — because by the time a lead is flagged hot, the builder has one shot to get on the phone before a competitor does.

What This Replaces

Before this system: a two-person sales team manually sourcing from CAL FIRE PDFs, spending thirty minutes per lead on enrichment, and sending generic cold emails that got ignored.

After this system: one owner with a phone, responding to pre-qualified hot leads in real time, with a full audit trail of every touch.

The Pairing

This backend powers the lead funnel behind eConstructHomes.com. The front-end case study covers the GEO/AISEO strategy that owns generative search for Palisades and Altadena rebuild queries. Together they form a closed-loop acquisition system: AI search finds the inbound, agent swarm finds the outbound, human closes the contract.