Instrumentation playbook: measuring “strategic unavailability”


Meeting Mirage and 404-as-a-Service run on instrumentation from day one. Here’s what we measure and why.

Core metrics

  • Deflection rate: % of booking attempts rerouted to Mirage meetings. Our benchmark is >90% without angering teammates.
  • Coverage: % of working hours marked Busy with believable events.
  • Rage-clicks: From 404-as-a-Service. If rage climbs, we dial down the spice.
  • Uptime: 99.9% target for calendar writes and 404 rendering.

Guardrails

We cap meeting density so your calendar remains plausible. We also rotate themes to avoid suspicion and surface a weekly report you can share with management (“Strategic Availability Summary”).

Stack

Astro frontends, edge functions for 404 interception, webhook-driven calendar writes, and a Postgres + DuckDB lane for analytics. Every event carries metadata so we can trace which theme, persona, and escalation rule won.

Next up

We’re adding per-role baselines (sales vs. engineering vs. leadership) and privacy-friendly analytics for regulated teams. Want to help shape it? Register and pick the Pro plan—we’ll route you into the beta list.