Engagement cycle

This page is for teams deciding whether a full cluster reliability assessment, a shorter incident pattern review, or a recurring briefing fits their moment. The sequence below describes the flagship assessment; lighter offerings compress the same stages.

1. Scoping call

   We confirm the application cluster boundary, the decision the report must support, access constraints, and whether on-site days in Sydney help. You leave with a written estimate, not a verbal promise.

2. Access briefing

   Your technical contact grants read-only evidence: metrics exports, incident archive, deploy notes, dependency list. We refuse write credentials to production.

3. Evidence & application analytics

   We map failure modes, recovery paths, and which signals predict trouble. Time is spent in notes and traces, not in decorating slides.

4. Draft findings

   Your technical contact sees a draft for factual correction — not for softening consequences. Disputed items are marked for the owner reading.

5. Owner reading

   A closed session with decision owners. We walk through the reliability report, answer challenges, and lock the action ranking.

6. Final delivery

   Signed PDF report, one-page executive brief, and a short clarification window. Remediation remains yours unless you commission further work.

What you prepare

• Named technical contact and decision owner
• Ninety days of incidents where available
• Honest map of what sits inside vs outside the cluster under review

What we need from leadership

Permission to write uncomfortable findings. A report that cannot name a real risk is not worth the fee.

Ready to start?

Browse assessments or request a scoping call.