Q2 marked our HCMC studio expansion — 18 new engineers onboarded across web and mobile squads.
Three enterprise clients went live: a B2B marketplace, a fintech onboarding flow, and a healthcare scheduling platform.
Studio and capacity announcements matter to clients planning roadmap timing — we share what changed in delivery capacity, not only press-release headlines.
Every milestone ships with a short written retro shared with partners so lessons travel across accounts.
Each go-live followed the same playbook: staged traffic ramp, war-room channel for
72 hours, and a written retro shared with client stakeholders within a week.
Go-live playbooks are repeatable: staged traffic, war-room channel, explicit rollback owner, and a 72-hour hypercare window.
Client NPS moves when communication is predictable — weekly written updates beat surprise calls when blockers appear.
We are investing next in internal tooling: automated Lighthouse CI gates, shared Prisma
migration playbooks, and a design token pipeline that syncs Figma to Tailwind.
Internal tooling investments (CI gates, migration playbooks, token pipelines) pay off across every account — we prioritize platform work that removes toil from squads.
Hiring and onboarding are part of delivery capacity — ramp time is scheduled, not assumed.
Client NPS for the quarter landed at 72 — our highest yet — driven
by predictable delivery cadence and transparent written updates.
Community and university partnerships feed internship pipelines we convert to full-time offers each quarter.
Regional expansion decisions weigh timezone overlap, talent depth, and attrition — not only real estate cost.
Thank you to every partner who trusted us
with production workloads this quarter.
Thank-you notes to partners are operational, not ceremonial — trust compounds into referrals and extension work.
Forward-looking roadmaps name what we will not build so expectations stay aligned.
The table below summarizes the reference points we review with client stakeholders before sign-off. Use it as a shared vocabulary in sprint planning and release reviews.
Quarter delivery snapshot
| Milestone | Region | Status | Client impact |
|---|---|---|---|
| Studio expansion | HCMC + Da Nang | Complete | Higher APAC overlap |
| Enterprise go-lives | US + APAC | Shipped | 3 production launches |
| Internal tooling | Global | In progress | CI + migration kits |
| Next-quarter roadmap | Global | Planning | Shared with partners |
| Hiring pipeline | Vietnam | Active | 18 engineers onboarded |
| NPS / feedback | Global | Reviewed | 72 quarterly score |
Run through this checklist in order — skipping steps because of deadline pressure is how regressions reach production. Assign an owner for each item before you schedule a launch window.
Pre-launch gates
- Share release notes with client stakeholders.
- Update public-facing timelines if milestones shifted.
- Log lessons learned while context is fresh.
- Confirm support runbooks reflect new capacity.
- Publish internal retro summary for delivery squads.
- Refresh careers and contact pages if capacity changed.
