Install crews work with gloves, ladders, and impatient homeowners. Dense PDFs and generic admin portals generate misconfigurations that surface weeks later as expensive callbacks.
Research on the van
We interviewed installers on real jobs to watch where thumbs hesitated, where connectivity dropped, and where "skip" buttons tempted shortcuts. That shaped offline-tolerant checklists with explicit acknowledgement steps on safety-critical items.
Configurator tied to rules
Hardware SKUs carried compatibility and dependency rules so illegal combinations surfaced before dispatch, not mid-install. Errors from APIs translated into plain-language recovery paths — retry, alternate SKU, call dispatch — instead of opaque codes.
Knowledge base people actually search
Short articles with schematic thumbnails replaced fifty-page manuals for common faults. Search success rose once titles matched how techs phrase problems aloud.
QA phase honesty
Late-stage hardening focused on dispatcher alignment: shared status vocabulary between field app and ops dashboards so nobody argued about what "complete" meant.
Metrics
Indexed setup-time improvement, misconfiguration-theme reduction, and documentation search success tell the story without exposing hardware margins.