Case study
One mid-market fleet. One audited outcome.
A single weekend enrollment on the Standard tier, two maintenance windows (nightly and weekend), a named primary technician with an alternate, and the underwriter audit destination stood up in week two. The customer's IT lead and two sysadmins stopped carrying the alert queue between helpdesk tickets — the audit log answers for itself.
Customer anonymized. Numbers rounded to the nearest metric the audit-log replays as a default rollup.
Loading the case study…
Source ledger
Every claim above appears on one of these pages.
The tier register, the maintenance-window cadence, the named-human escalation shape, and the audit-log detail all sit on already-published pages — this story reads against them, not against a marketing deck.
- /pricingThe tier register and the maintenance-window detail (one window on Starter, two on Standard, three on Complete).
- /how-it-worksThe four-station loop, the tier-calibrated named-human handoff, and the row-by-row audit-trail description.
- /faqAutonomy, audit log, named-human escalation, insurance notification triggers, and flat-subscription rationale.
- /compareCurtainwall vs traditional 24×7 SOC / MSSP — capability-by-capability, every claim sourced.
Get in touch
Run the same loop on your fleet. Same shape, same audit log, same single-weekend enrollment.
curtainwall@polsia.app