Igni for ADU Suppliers & Manufacturers

The problem

• Your product gets specified early in an ADU project, but you only hear about most projects after the design is locked in.
• ADU permit activity is fragmented across dozens of city portals with no consistent format and no reliable ADU label.
• Generic permit feeds don't distinguish a detached new-build ADU — your best fit — from a conversion or a reroof.
• Tracking ADU demand across the markets you ship to means scraping portals by hand, market by market.

Reach ADU buyers while the project is still being scoped

An ADU permit filing is a near-bottom-of-funnel signal: the owner or builder has engaged the building department and usually has a design and budget forming. That's the window when a unit, kit, or component can still be specified — before the design is finalized and the order placed.

Igni surfaces ADU activity with sub-24-hour freshness across 60 cities in 37 US states, so you can reach buyers early rather than after the design is locked. For the timing logic, see our blog post on finding ADU permit leads.

Typed ADU classification matches activity to your product

Not every ADU permit is a fit for what you make. Igni applies a typed ADU classification — detached, attached, junior ADU, conversion, or unknown — inferred from each jurisdiction's structured flags and work descriptions, so a prefab detached-unit maker can focus on detached filings and a conversion-kit supplier can focus on conversions.

That typing turns a raw permit stream into a targeted demand signal for your specific product line. For the underlying definitions, see the glossary entries for an ADU and a junior ADU.

Track ADU demand across every market you ship to

Suppliers often serve a wide geography — sometimes a whole region or several states — which makes manual portal-by-portal tracking impractical. Each city publishes permits in its own format, with its own fields, export limits, and date conventions, so keeping up by hand means repeating the same slog across every market you ship to. Igni ingests directly from official municipal open-data portals and normalizes everything into one consistent schema, so ADU activity across all your markets sits in one comparable feed instead of a stack of incompatible exports.

From there, filter by ADU type, project valuation, ZIP, and city to focus on the exact segments and regions you serve. A prefab supplier shipping detached units across the West can isolate detached filings above a valuation threshold in their delivery footprint; a regional component vendor can watch just the metros they cover. Preview live activity in the permit dashboard and browse the markets covered on the state coverage hub.

Open-data sourcing, contact-driven access

Every record traces back to a city's official open-data portal, so the ADU activity you act on is a verifiable public record, not an opaque purchased list — which matters when you're investing sales effort against a signal. Igni's value is the typing, normalization, and freshness layered on top of that source, while the source itself stays transparent and checkable.

Igni is contact-driven during its pilot: there's no public self-serve checkout yet. To discuss ADU coverage in the markets you supply and how the feed fits your sales motion, request access and tell us which regions and ADU types matter most, and we'll walk through the fit for your product line.

The filters that matter for you

Frequently asked questions