I have already built the core pattern: APIs → evidence → scoring → opportunity briefs → human action.
For Luzione, I built a Growth Engine that combined public project signals, behavioral intent and CRM context to find new accounts, identify project participants, enrich opportunities and prioritize commercial action. The Xthings version would use different signals, but the architecture is directly transferable.
A working revenue-intelligence system, not a slide.
These metrics are from the Luzione Growth Engine work and are included to show the operating scale of the system I have already built.
Legacy opportunity records reviewed and re-scored to remove stale or unsupported priority.
Current evidence-based records after cleanup and reclassification.
Durable project profiles with building type, positioning, occupancy, scope, confidence and evidence.
Permit-market adapters across 20 metros, including 96 via Shovels and 17 municipal / Socrata paths.
Shovels, municipal permit data, Brave News, Instagram enrichment, PostHog, GA4, Gmail and Shopify in the implemented / connected workflow.
Signals become useful only when they create a better next action.
The Xthings version should combine external project signals, product / partner intent and CRM evidence without automating outreach blindly.
Permits, construction, company growth, partner applications, product intent and ecosystem signals.
Resolve company, property, project, partner and contact identities into one commercial record.
Current stack, project type, incumbent, decision roles, protocols, timing and evidence quality.
Partner IQ, Account IQ, Lead IQ and confidence remain separate so weak evidence cannot masquerade as high fit.
Why now, value hypothesis, technical fit, open questions and recommended next action.
Human-approved outreach, partner motion, CRM update and win/loss feedback into the model.
What I would adapt for Xthings.
The strongest Xthings signals are closer to physical infrastructure, commercial build-outs, technology replacement and developer / partner intent.
Commercial electrical, low-voltage, multifamily, industrial and renovation activity routed into Account IQ.
New facilities, security leadership, workforce growth and site expansion create direct-sales timing signals.
Integrator service footprint, certifications, vertical mix and active project types feed Partner IQ.
Partner forms, developer-doc interest, demos and approved product analytics can raise Lead / Account priority.
Expansion, funding, leases, new construction, compliance events and platform replacement signals.
Past opportunities, objections, integrations, contacts and next actions prevent the engine from treating every signal as net-new.
Who sourced the deal, protection window, end customer, stage and commercial ownership.
Use conversion, margin, implementation effort and expansion to recalibrate what “high IQ” actually means.
Same operating logic, different commercial evidence.
This is the direct transfer from the system I built to the system I would build with Xthings' data and tools.
Permits, development news, project participants, architects, contractors, property scope, intent and estimated furniture opportunity value.
Commercial build-outs, low-voltage permits, integrator portfolios, facility expansion, developer intent, legacy stack signals, API interest and estimated hardware + software opportunity.
Why now, building type, scope, timing, confidence, participants and recommended commercial review.
Why now, installed environment, partner route, protocol fit, buying roles, pilot hypothesis, integration risk and recommended next action.
Turn repeated API, protocol and deployment questions into reusable technical-commercial proof.
Convert real win/loss evidence into sharper value propositions for integrators, property, industrial and enterprise buyers.
Aggregate repeated partner and account requests with opportunity value before asking Product to prioritize new work.