Process

Five stages. Every one produces a document you own.

The most common complaint about infrastructure vendors is not technical incompetence — it is that nobody knows what is happening or when it will be finished. So here is the whole shape of an engagement, including the parts where we need something from you.

Discover

1–2 weeks

We read your architecture, not your marketing deck.

You receive

Current-state risk map (including single points of failure)
Baseline measurements: latency, IOPS, GPU utilisation, cost
Prioritised findings with effort/impact

We need from you

Read-only access, or someone to run a handful of commands
A name for each system owner we will disturb
Two hours of an engineer's time for the walkthrough

Design

1–3 weeks

Every decision gets written down, with the alternative we rejected and why.

You receive

Reference architecture
Failure-domain analysis
RTO/RPO targets you can hold us to
Bill of materials with licence comparison

We need from you

Decisions from whoever owns budget and risk
Your compliance constraints, stated plainly
Notification of any change freeze you have

Build

2–10 weeks

Everything is described in code. Nothing is configured by hand at 2am.

You receive

Ansible / Terraform / GitOps repository
Cluster built to the approved design
Handover runbooks
Team walkthrough session

We need from you

Change windows, or agreement that we work during business hours
A CI/CD target if you want the code in your own repo
A person to accept the handover

Harden

1–2 weeks

We break it on purpose so it doesn't break by accident.

You receive

Chaos drill report: real failover, real timings
Restore-from-backup proof, timed
CIS baseline scan results
Remaining risk register — the honest one

We need from you

Permission to actually break it, once, in a window
An application owner on standby during the drill
Agreement on what counts as a failure

Operate

Ongoing

The part most vendors skip.

You receive

7×24 on-call with named engineers
Quarterly failover + restore drills
Capacity and cost review each quarter
Patch and upgrade windows you approve

We need from you

An escalation path that reaches someone who can decide
A change calendar so we do not patch during your peak
A quarterly review where you tell us what is annoying you

Before all of that

What happens after you press send

Within one business day — an engineer replies. Not an autoresponder, not a calendar link, an actual reply from someone who read what you wrote.
Within three days — a 30-minute call. We ask about failure domains, what broke recently, and what you are actually trying to avoid. No slide deck.
Within one week — a written scope with a price range, the assumptions behind it, and the things that would change it.
Then you decide. If the answer is no, you keep the scope document. It is a decent architecture review on its own.

No pressure We do not do discovery calls that turn into a pitch for a licence, and we do not follow up repeatedly. If you want another conversation, you start it.

Start with the review call

Thirty minutes. Bring the architecture or just the symptom. Worst case, you leave with a clearer idea of what you are dealing with.

Book a 30-min review See pricing

botonwa@gmail.com · +86 130 5181 3099