Back to FAQ Hub
FAQ Category

Team & Communication

Who works on your project, time-zone overlap, language fluency, and the engagement model that makes async-first delivery work.

Overview

Working with an offshore team succeeds or fails on communication structure. DevStudio staffs a stable, named team and runs async-first so progress does not depend on overlapping office hours. This page covers exactly who is on your project, how time-zone overlap is used, the team English fluency, and the documented escalation path you get on day one.

Key things to know about the team

A stable, named team

You get a named tech lead (the one throat to choke), 1-2 senior engineers, and a 0.25 FTE engagement sponsor for QA and escalation. No rotating bench; tech-lead changes require notice and your written approval.

Async-first across UTC+8

Based in Hangzhou (UTC+8), the team provides 1-3 hours of overlap for US buyers and runs on architecture decision records, written changelogs, async demo videos, and weekly written status.

Documented escalation from day one

A named escalation path is set on day one — tech lead first (24-hour SLA), engagement sponsor second (48-hour SLA), with an on-call rotation before any production launch.

Frequently Asked Questions

Who is on my project team?
A named tech lead (the one throat to choke), 1-2 senior engineers, and a 0.25 FTE engagement sponsor for QA and escalation. The team is stable for the duration of the engagement — we do not staff with a rotating bench. Tech lead changes require 2 weeks notice and your written approval.
What time zone are you in and how does overlap work?
We are based in Hangzhou, China (UTC+8). For US buyers, our morning is your evening, providing 1-3 hours of overlap. We operate async-first: architecture decision records, written changelog per sprint, asynchronous demo videos, weekly written status. Synchronous overlap is reserved for kickoff, architecture review, demo, and escalation.
How fluent is the English on the team?
Tech lead and at least one client-facing engineer are fluent in written and spoken English. The full engineering team writes English in commits, PRs, written changelog, and ADRs. Synchronous calls are conducted in English with the tech lead.
How do daily standups work across time zones?
Two patterns. Async standup written in your shared Slack channel before vendor team logs off (your morning). Or weekly synchronous status with mid-week async written check-in. Most engagements settle on weekly synchronous + daily async after the first sprint.
Who do I escalate to if there is a problem?
Named escalation path documented at Day 1: tech lead first (24-hour SLA), engagement sponsor second (48-hour SLA). For production-impacting incidents, an on-call rotation with paging is established before launch.

Related guides

Custom Software Development

How engagements are staffed and delivered.

 How to Choose an AI Outsourcing Team

What to vet before signing with any vendor.

 Engagement Process FAQ

How an engagement starts and runs week to week.

 Delivery & Handover FAQ

Escalation, on-call, and the QA window.

Other FAQ Categories

Cost & Pricing

Project rates, Paid Scoping, payment milestones.

 Timeline & Delivery

5-phase delivery, milestones, post-launch.

 Technical Approach

Architecture, RAG vs fine-tuning, security.

 Team & Communication

Time zones, escalation, async-first delivery.

 Engagement Process

Discovery, Paid Scoping, change requests.

 Delivery & Handover

Source code ownership, 6-month QA, model upgrades.