Axonix Wedge Analysis

Client slug: axonix
Research date: 2026-05-17
Evidence posture: Public-research synthesis, not accepted market truth
PQS definition: Pain-Qualified Segment

Wedge Ranking Summary

Scoring uses four dimensions requested for this packet: existentiality, timing, public data availability, and practical outbound usability. Scores are not market validation.

Detailed Wedge Analysis

Wedge 1: Car Wash Multi-Site Uptime And Exterior Low-Voltage Reliability

Overall score: 7.75/10
Classification: pqs_hook at segment level; proto_pvp when tied to a named car wash operator and public facility signals.

Existentiality: 7.0/10
Car washes rely on daily throughput, cameras, kiosks/app lanes, vacuums, tunnel visibility, exterior equipment, and weather-exposed low-voltage systems. A weak camera/network/access setup does not shut down the business by itself, but downtime, blind spots, and poor evidence during incidents can create real operating pain.

Timing: 7.5/10
The car wash category shows visible Metro Detroit expansion and new-site activity. Express Wash Concepts announced a fourth Detroit metro Clean Express site and additional Detroit-area openings planned through 2025. Jax publicly promotes more than 50 Metro Detroit locations. Quick Pass states four Metro Detroit locations and more on the horizon. Sources: axonix-src-express-wash-detroit-2026-05-17, axonix-src-jax-home-2026-05-17, axonix-src-quick-pass-locations-2026-05-17.

Data availability: 8.0/10
Public sources include official location pages, expansion press, municipal planning reports, building permits, zoning/planning agendas, and local business lists. The data identifies named sites and expansion signals, but true PVP quantification would require more detailed public permit or incident data.

Practical outbound usability: 8.5/10
The message is concrete and facility-specific: tunnel view, vacuum lot, app lane/kiosk, weather-rated cameras, PoE/network cabinet, and support handoff. It maps directly to Axonix's published car wash industry page and services.

Example safe angle:
pqs_hook: "Your wash model depends on tunnel, vacuum-lot, kiosk, and app-lane visibility. The low-voltage weak point is usually the network and weather-rated handoff, not the camera brand."

Why this beats generic targeting:
Instead of "car washes need security," the wedge targets operators with public multi-site or new-site signals and a clear infrastructure stack: exterior cameras, tunnel visibility, kiosks, app/member lanes, vacuums, lighting, and support.

Wedge 2: Warehouse/Logistics Dock, Yard, And Rack Infrastructure Visibility

Overall score: 7.50/10
Classification: pqs_hook at segment level; proto_pvp when tied to named warehouse signals like square footage, docks, surveillance, WMS, or expansion.

Existentiality: 7.5/10
Warehouse and logistics sites have inventory, docks, yard movement, staff access, after-hours risk, and networked systems. Poor visibility and undocumented cabling can create operational friction, incident review gaps, and expensive rework.

Timing: 6.5/10
Timing is strongest when public sources show expansion, new capacity, or build-out. Metro Wire publicly described doubled HQ/distribution space in Sterling Heights. Logos and Gholston publish Metro Detroit warehouse details, including square footage and facility features. Sources: axonix-src-metro-wire-warehouse-2026-05-17, axonix-src-logos-3pl-detroit-2026-05-17, axonix-src-gholston-warehouse-2026-05-17.

Data availability: 8.0/10
Official warehouse pages, FMCSA records, property records, industrial listings, permits, and broker reports can identify named facilities. For a true PVP, the packet would need cross-source public proof of a specific gap or opportunity.

Practical outbound usability: 8.0/10
The wedge translates cleanly into site-assessment language around dock coverage, rack/PoE load, cable paths, remote view, access workflows, and service documentation.

Example safe angle:
proto_pvp: "Your Romulus/Warren warehouse pages already mention surveillance, cross-docking, WMS, or large storage capacity. That is exactly where low-voltage design needs dock, rack, PoE, and remote-access planning before cameras are treated as standalone devices."

Why this beats generic targeting:
The public data identifies actual facilities and operational shape instead of filtering for "warehousing" in a generic database.

Wedge 3: Office/Property Manager Tenant Access, Camera, And AV Modernization

Overall score: 7.25/10
Classification: pqs_hook broadly; proto_pvp for named buildings or property managers with public portfolio evidence.

Existentiality: 6.5/10
Tenant access, cameras, conference AV, Wi-Fi, and visitor workflows can affect tenant experience, leasing competitiveness, service tickets, and building operations. The pain is meaningful but usually not immediate shutdown risk.

Timing: 6.0/10
Timing can come from tenant turnover, renovations, office repositioning, amenity upgrades, and leasing efforts. Public property pages for One Campus Martius, Southfield Town Center, GM Renaissance Center, and Michigan Central show large, amenity-heavy facilities with access/AV/network complexity. Sources: axonix-src-one-campus-martius-2026-05-17, axonix-src-southfield-town-center-2026-05-17, axonix-src-gm-ren-cen-hines-2026-05-17, axonix-src-michigan-central-about-2026-05-17.

Data availability: 8.5/10
Property pages, tenant resources, ENERGY STAR building data, broker pages, management portfolios, and permit records can identify named facilities and likely technology touchpoints.

Practical outbound usability: 8.0/10
The outreach can target property managers, building engineers, office managers, and project managers with concrete building workflow language.

Example safe angle:
proto_pvp: "One Campus Martius publicly combines office, retail, events, and data-center uses in one building. That mix makes access, conference AV, cameras, network segmentation, and handoff documentation a building-operations issue, not a device-install issue."

Why this beats generic targeting:
It starts with the building's public usage mix and tenant experience, not a generic "commercial real estate" persona.

Wedge 4: Multi-Campus Churches And Public-Gathering Access/AV/Security Operations

Overall score: 6.88/10
Classification: pqs_hook broadly; proto_pvp for named campuses with public location/service evidence.

Existentiality: 6.5/10
Churches manage open public access, children/student areas, volunteer keys, AV/livestreaming, parking, and service-time surges. A failure can create safety, trust, and operational issues, but most public data does not prove immediate pain.

Timing: 6.0/10
Timing is stronger around new campuses, added service times, large events, school partnerships, or renovations. Public campus/location pages identify multi-campus complexity for Woodside, Triumph, Kensington, and Oak Pointe. Sources: axonix-src-woodside-locations-2026-05-17, axonix-src-triumph-locations-2026-05-17, axonix-src-kensington-locations-2026-05-17, axonix-src-oak-pointe-2026-05-17.

Data availability: 7.5/10
Official campus pages, service times, event calendars, livestream pages, school partnership locations, and public meeting/permit records can support account fit. Incident or security-risk proof should not be inferred without evidence.

Practical outbound usability: 7.5/10
The message can be respectful and operational: volunteer-friendly access, kids/student spaces, AV/livestream reliability, cameras, cabling, and handoff.

Example safe angle:
pqs_hook: "Multi-campus churches often have the same low-voltage problem in different clothes: volunteer access, kids-area visibility, worship AV, and network handoff all need to work for non-technical teams."

Why this beats generic targeting:
The church campus page itself identifies locations, service times, and operational complexity. It avoids fear-based or unsafe security claims.

Wedge 5: Multi-Site Retail/Services And Referral-Partner Low-Voltage Standardization

Overall score: 6.88/10
Classification: pqs_hook broadly; proto_pvp for named operators, GCs, property managers, or MSP/AV partners.

Existentiality: 6.0/10
For retail and service operators, low-voltage reliability affects staff accountability, POS-area visibility, entrances, stockrooms, Wi-Fi/network consistency, and remote support. For referral partners, missed low-voltage scope can create project friction and punch-list pain.

Timing: 6.5/10
Timing appears when public sources show new stores, multi-location growth, construction portfolios, tenant fit-outs, or project management services. Gardner White, Belle Tire, Emagine, McLaughlin's, and local GCs/property managers all provide public fit signals. Sources include axonix-src-gardner-white-stores-2026-05-17, axonix-src-belle-tire-home-2026-05-17, axonix-src-emagine-theatres-2026-05-17, axonix-src-mclaughlins-home-2026-05-17, axonix-src-walbridge-one-campus-2026-05-17.

Data availability: 7.5/10
Store locators, project portfolios, permit records, business directories, property pages, GC portfolios, and municipal planning documents can identify named accounts.

Practical outbound usability: 7.5/10
The message can focus on repeatable site standards, closeout packages, and low-voltage scope coordination. It can also route through GCs, property managers, electrical contractors, or MSPs.

Example safe angle:
pqs_hook: "When a multi-site operator adds or remodels locations, the expensive part is not the camera. It is keeping access, cabling, PoE, Wi-Fi, and handoff standards consistent across sites."

Why this beats generic targeting:
It finds the world through location pages, project pages, permits, and property portfolios rather than filtering a generic list for "retail."

Wedge Comparison

Source References

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