Guide / Preparation

Checklist before you book a system health check

Prepare eight things: symptoms, access, numbers, devices, cost pressure, risk windows, a decision owner and what useful looks like. Then the 1–2 week system health check goes into finding causes, not chasing access.

Short answer: you need eight things. Symptoms in plain words, access you can grant, numbers you already have, real devices, a risk window, one decision owner, what useful looks like, and a view on cost pressure. With these ready, a system health check starts on day one.

Most delays in a review come from waiting for access, not from the technical work. This page lists what to gather first. You can print it or copy it into a message to us.

The eight things to prepare

Check each one before the review

  1. Symptoms in plain wordsWhat users or staff see, since when, and how often. For example: checkout spins in the evening.
  2. Access you can grantA staging environment or view-only production access, analytics, error reports and the hosting console. Note what you cannot share yet.
  3. Numbers you already havePage load, API speed, error rate and the monthly hosting bill. Rough ranges are fine.
  4. Real devices and networksThe phones, tablets and browsers your customers and staff actually use.
  5. Cost pressureWhether finance is asking about cloud spend, and which part grew recently.
  6. Risk windowsUpcoming promotions, launches or peak seasons.
  7. Decision ownerWho approves access, scope and the next step after the review.
  8. What useful looks likeA ranked fix list, a yes or no on a rewrite, or a running-cost picture for leadership.

What the review looks like

We record baselines on the paths that matter to you. Then we send back a ranked list of causes, each with evidence and a fixed quote to fix it. The whole review takes one to two weeks once access is ready.

Three steps from left to right: prepare symptoms and access, review the paths that matter, receive a ranked fix list.
Figure 1Prepare on your side, review on ours, then a ranked list comes back.

If access will take weeks

Tell us early. We propose a staged plan instead of a stalled calendar, and the clock starts when access is ready.

Frequently asked questions

What should I prepare before a system health check?

Eight things: symptoms in plain words, access you can grant, numbers you already have, real devices and networks, cost pressure, risk windows, a decision owner and what useful looks like.

What access do I need to grant?

A staging environment or view-only production access, analytics, error reports and the hosting console. Note what you cannot share yet.

Do I need exact numbers?

No. Page load, API speed, error rate and the monthly hosting bill are enough as rough ranges.

What if access will take weeks?

Tell us early. We propose a staged plan instead of a stalled calendar, and the clock starts when access is ready.

What can I get out of a system health check?

A ranked fix list, a yes or no on a rewrite, or a running-cost picture for leadership. Tell us which one is useful to you.

How long does it take and what does it cost?

1–2 weeks and 12M VND, excluding VAT. It is deducted from a Fix Package. The scope and the cost are in writing before your first payment.

Can I talk to someone first?

Yes. Book a free 30-minute call. You speak with our Founder or Solution Architect. We reply within one business day.