How we work · Operating model
How we run systems that can't fail on the day.
The operating model behind our production engagements — how we make decisions, ship changes, rehearse high-stakes days, and handle client data. Written down so you can hold us to it.
01Decisions are written down
Before a significant change reaches production, we write a short decision record: the problem, the options we considered, what we chose and why, and what would make us revisit it.
The records live with the code, so anyone who joins later — on your team or ours — can see why the system looks the way it does. This website works the same way: its architecture decisions are recorded as numbered ADRs.
02Every change has evidence and a way back
A change isn't finished when it deploys. We capture before-and-after evidence — response times, error rates, the query that proves the number — and write down the exact steps to undo it before it goes out.
If something regresses, rolling back is a routine step, not an emergency meeting.
03High-stakes days are rehearsed
For launch days, sale events, and cut-overs, we run an automated preflight checklist and a full rehearsal of the day from a single command, then keep automated watchers running through the final hours.
By the time real traffic arrives, the day has already happened at least once. See it on iStudio's pre-order platform, six iPhone launch cycles in.
04We watch what users actually hit
Monitoring is per route, including requests turned away before they reach application code — so a problem at the edge shows up as quickly as a bug in our own code.
Launch days run on an on-call playbook: who watches what, where the thresholds sit, and who is allowed to decide.
05Commercial calls stay with you
Pricing, stock allocation, queue policy, what to tell customers — these are business decisions. When one comes up, we bring the options, the data behind each, and our recommendation. Your team decides.
Our job is to make the decision fast and well-informed, not to make it for you.
06Your data and your story
- Production figures we report are read with read-only access, and we keep the query so the number can be re-checked.
- Client figures and quotes on this site are published only with the client's written approval.
- Personal data is handled under Thailand's PDPA — see our Privacy Policy.
07How an engagement starts
Most engagements move through four stages: discovery, ideation, testing, and execution (see the steps).
If you have a launch or cut-over date coming up, the simplest way in is a launch-readiness review: we look at the system, the traffic you expect, and the runbook for the day, and hand back a prioritised list of what to fix first.