What a seven-day health-check will not tell you

In about a week of focused work, a useful health-check confirms access, captures a baseline on the paths that matter, and returns a ranked list of suspects: latency, memory, stability, and sometimes run-cost drivers. Exact inputs and outputs live in the statement of work. The point is to decide the next spend with evidence: targeted fixes, a deeper Surgery engagement, a delivery roadmap, or a stop if the system is healthy enough. Use the checklist guide to prepare symptoms, devices, baselines, and owners before Contact.

A short window will not map every edge case in a large catalog, every regional network condition, or every seasonal peak you have not yet hit. It will not replace continuous monitoring, load testing at full campaign scale, or a security audit. It will not invent findings from marketing screenshots when staging and analytics access are blocked. If finance needs a multi-year capacity plan, that is a different engagement. If product wants a redesign brief, that is Delivery or Lab, not a performance readout dressed up as strategy.

The check is enough when leadership only needs a ranked fix list and a go/no-go on rewrite, when the hottest path is clear, and when access arrives quickly. It is enough when the likely work is a handful of targeted changes with before/after metrics you can show internally. It is also enough when the honest answer is “not a performance problem” and the real need is product delivery or AI automation. Saying that early is part of the value.

Move to Surgery when the readout shows systemic issues across multiple surfaces, when crash or latency risk sits on a revenue or reputation window, or when run-cost waste and performance share the same root causes and need a sequenced fix program. Surgery means agreed targets, named owners, and measurable before/after reporting. A rewrite enters the conversation only when measurement and commercial impact support it. The health-check exists to make that call with evidence, not opinion.

Name the user path, device, and time of day where pain shows up. Share crash reports, hosting invoices, or approximate baselines if you have them. Name who can approve access and the next engagement. If access will take weeks, say so; we can propose a staged plan instead of a stalled calendar. Pair this insight with the Work page when stakeholders ask whether we have shipped under campaign and catalog pressure before.

Will the health-check recommend a rewrite?

Only when measurement and risk support it. Many engagements start with targeted fixes on the hottest paths. The check is designed to prevent rewrite-by-default.

Can it explain rising hosting spend?

When cloud or hosting signals are in scope and visible, yes as ranked suspects engineering can act on. It is not a generic FinOps slide deck.

How do we start?

Send checklist notes via Contact with the health-check intent. We reply with fit, access needs, and calendar options.