Advisory / Audits
0–360 Audit
Degrees of coverage, not days of consulting. You choose how much of the picture you need; every tier ends in the same thing — a prioritized action plan.
The numbers are degrees, not days
Each tier is named like a compass: it covers a wider arc of how you build and run technology. The 45 takes one week. Wider tiers take longer because they cover more ground; the number never means days, and none of them is a long engagement.
The tiers
| Tier | Coverage | Duration |
|---|---|---|
| 45 | Rapid review: architecture and codebase health, the most expensive risks named | one week |
| 90 | The 45, plus delivery process and infrastructure spend | scoped on the call |
| 180 | The 90, plus security posture, data architecture and AI readiness | scoped on the call |
| 360 | The 180, plus team structure and organization — the full arc | scoped on the call |
Wider tiers are quoted once we know your estate’s size — a 90 on a five-person platform is not a 90 on a two-hundred-engineer one. The quote is fixed before we start.
How to choose
- A fast, honest read before a decision: the 45. One week, the major risks ranked.
- The bill and the roadmap both feel wrong: the 90. How you deliver and what you spend usually explain each other.
- The board is asking about security, data or AI: the 180. Engineering answers instead of slide decks.
- You suspect the organization, not the technology: the 360. The full sweep, including the people and structures that produce the systems.
Tell us the symptom on the scoping call and we will point you to the smallest tier that answers it.
What happens in every tier
We read code and architecture directly, not just interview decks. We watch the delivery pipeline as it actually runs. And findings come in business terms: what each risk costs, what fixing it takes, what happens if you do nothing.
