Axonix Data Sources

Client slug: axonix
Research date: 2026-05-17
Evidence posture: Public/niche data-source strategy, not accepted market truth
Rule: Avoid Apollo/ZoomInfo-style generic filtering as the primary data strategy. Find the world, do not just filter the world.

Data Strategy Summary

Axonix should build its first account map from public facility and project signals:

Official facility/location pages.
Municipal permits, planning agendas, zoning packets, and site-plan approvals.
Property pages, tenant resource pages, property manager portfolios, broker pages, and building data.
State/county license/entity/property records where legally usable.
Industry-specific pages: car wash expansion pages, church campus pages, warehouse pages, GC portfolios, MSP/AV partner pages.

Generic enrichment can help fill contact names only after human approval. It should not define the Pain-Qualified Segment.

Data Source Catalog

Source type	Relevant wedges	Specific public sources/access points	API/export	Reliability	Timeliness	Cost	Coverage/granularity	Priority	Caveat
Official account/facility pages	All wedges	Account websites such as Logos, Gholston's, Metro Wire, Woodside, Triumph, Quick Pass, Gardner White, One Campus Martius.	Usually no API; manual or site-specific parsing.	High for self-published facts.	Varies.	Free.	Named account/location.	High	Self-published pages prove fit, not pain or intent.
Municipal building permits and planning packets	Car wash, retail, office, warehouse, referral partners	Detroit Open Data building permits, city planning agendas, zoning reports, local PDF packets.	Detroit open data may provide structured access; many cities are PDF/manual.	High when primary municipality.	Often current to agenda/permit updates.	Free.	Address/project-level.	High	Terms and field freshness must be checked before automation.
BS&A Online municipal property/building records	Office/property, warehouse, retail, car wash	`https://bsaonline.com/` for participating municipalities.	Portal/manual; some structured records depending municipality.	Medium-high.	Varies by municipality.	Free/limited paid depending use.	Parcel/address-level.	Medium-high	Must respect terms; coverage is fragmented.
Oakland County Property Gateway	Office/property, retail, warehouse	`https://gis.oakgov.com/PropertyGateway/`	Web GIS; export options vary.	High for county records.	Varies.	Free public access.	Parcel/address-level.	Medium	Useful for parcel/property context, not pain.
LARA security alarm contractor licensing	Referral partners, claim safety	Michigan LARA security alarm contractor page.	Search/manual.	High for licensing context.	Current as state records.	Free.	License/entity-level.	Medium	Use for verification and claim safety, not targeting pain by itself.
LARA electrical licensing	Referral partners, claim safety	Michigan LARA electrical licensing information.	Search/manual.	High for licensing context.	Current as state records.	Free.	License/person/entity-level.	Medium	Do not imply unlicensed status for anyone.
Michigan entity search	All named business accounts	Michigan LARA corporation/entity search.	Search/API availability unclear.	High for entity existence/registered agent.	Current as state records.	Free.	Entity-level.	Medium	Not a pain signal.
FMCSA SAFER company snapshot	Warehouses/logistics	`https://safer.fmcsa.dot.gov/CompanySnapshot.aspx`	Manual query; bulk options require review.	High for motor-carrier records.	Current enough for safety/registration checks.	Free.	Carrier/entity-level.	Medium	Relevant only for transport/logistics accounts.
OSHA establishment/inspection data	Warehouse, manufacturing, construction/referral	`https://www.osha.gov/data`	Download/query options.	High federal source.	Varies by dataset.	Free.	Establishment/inspection-level.	Medium	Do not use OSHA history as a sales scare tactic without careful review.
ENERGY STAR certified building data	Office/property	ENERGY STAR certified buildings search/PDF data.	Search/download options vary.	High for building facts.	Annual/periodic.	Free.	Building-level.	Medium	Shows building profile, not low-voltage pain.
Property manager portfolios	Office/property, referral partners	NAI Farbman, PA Commercial, DEI Properties, RIMS, CBRE Detroit.	Mostly web pages/PDFs.	Medium-high self-published.	Varies.	Free.	Portfolio/company-level.	High	Good for channels and named account fit; not pain proof.
GC and construction portfolios	Referral partners, retail/office build-out	Walbridge, The Diamond Firm, Orlins, George H. Pastor & Sons.	Mostly web pages.	Medium-high self-published.	Varies.	Free.	Project/company-level.	Medium-high	Good partner fit; not proof of project need unless current project signal exists.
Church campus and event pages	Churches	Woodside, Triumph, Kensington, Oak Pointe, Metropolitan UMC.	Usually no API.	High for official location/service facts.	Current enough if pages maintained.	Free.	Campus/service-level.	High	Do not infer security incidents.
Car wash location and expansion pages	Car wash	Quick Pass, Jax, Clean Express/EWC, Zax, Tommy's Express.	Usually no API.	High for official locations and expansion announcements.	Current to page/press date.	Free.	Location/operator-level.	High	Does not prove equipment problems.
Store locators	Retail/multi-site	Gardner White, Belle Tire, Emagine, McLaughlin's, Prime House Depot.	Usually no API.	High for official location facts.	Current to site.	Free.	Location/operator-level.	High	Need additional trigger for stronger PVP.

Wedge-Specific Data Recipes

Car Wash Data Recipe

Goal: Identify operators where exterior/tunnel/vacuum/kiosk low-voltage complexity is visible from public sources.

Sources:

Official operator location pages.
Expansion press.
City planning/site-plan packets for new car washes.
Building permit portals.
Google Maps only as a human review aid, not a canonical source unless explicitly approved.

Signals:

Multiple sites or new site openings.
Tunnel, vacuums, RFID/member lane, app lane, kiosk, weather-exposed equipment.
Public expansion language.
Municipal site-plan packets showing new build-out.

Classification rule: Segment-level output is pqs_hook. Named operator + public expansion/site detail is proto_pvp. True PVP would need a specific public project/permit/opportunity or risk that is actionable without follow-up.

Warehouse/Logistics Data Recipe

Goal: Identify sites where dock/yard/cross-dock/WMS/security/cabling complexity is public.

Sources:

Official warehouse pages.
FMCSA records for carriers where relevant.
Industrial property pages and broker sheets.
Expansion announcements.
Building permits and occupancy records.
OSHA data only for careful internal context.

Signals:

Square footage.
Cross-docking, multiple dock doors, WMS, 24/7 surveillance, food-grade/ISO claims.
Expansion or doubled capacity.
Proximity to DTW, I-94/I-275, or industrial corridors.

Classification rule: Named facility and public features can support proto_pvp. Do not claim operational risk or incidents without proof.

Church/Multi-Campus Data Recipe

Goal: Identify churches where multiple campuses, service times, kids/student areas, livestreaming, or public events create operational complexity.

Sources:

Official campus/location pages.
Service-time pages.
Livestream pages.
Event calendars.
Public school/campus partner location pages where services meet off-site.
Permits only if renovation/build-out is public.

Signals:

Multiple campuses.
Multiple service times.
Kids/student ministries.
Livestream.
Public school auditorium or rented worship space.

Classification rule: Use respectful pqs_hook language around operations and volunteer-friendly systems. Named campus rows can be proto_pvp; do not infer security threats.

Office/Property Manager Data Recipe

Goal: Identify buildings and managers where tenant access, visitor flows, camera coverage, conference AV, and network handoff are likely material.

Sources:

Official property pages.
Tenant resource pages.
Property manager portfolios.
ENERGY STAR/building pages.
Broker pages and office market reports.
Permits for tenant improvements and renovations.

Signals:

Large square footage.
Mixed use: office, retail, event, data center, hotel, public amenities.
Tenant resources, visitor registration, maintenance request portals.
Active leasing or repositioning.

Classification rule: Named buildings with public use mix can support proto_pvp; true PVP needs a specific public project, deadline, or low-effort opportunity.

Multi-Site Retail/Referral Partner Data Recipe

Goal: Identify operators and partners where standardization and low-voltage scope coordination create account-level fit.

Sources:

Store locators and official location pages.
Expansion announcements.
GC and property manager portfolio pages.
Municipal permits and planning agendas.
Business license/entity records.

Signals:

Multiple stores or new location.
Retail/POS-area visibility language.
Construction services, facility management, project consultation.
Tenant fit-outs or restaurant/commercial project portfolios.

Classification rule: pqs_hook for segment pain. proto_pvp when a named account has a public expansion/remodel/site-standardization signal. True PVP requires a specific public project or opportunity that the recipient can verify and act on.

Sources To Avoid As Primary Strategy

Apollo, ZoomInfo, Sales Navigator, or generic industry filters as primary source of account fit.
Scraped private data, paid datasets, or vendor exports without approval.
Incident/crime/security scare claims without public, account-specific proof and human review.
Private mailbox, CRM, campaign, Google Drive, Smartlead, Apollo, Attio, Supabase, Trigger.dev, Resend, Lucidchart, Comfy, or MCP-connected vendor sources.

Source References

Source IDs, URLs, allowed-use assumptions, and evidence weights are maintained in clients/axonix/agentic-environment/source-registry.md.