Specs in.
Software out.

Async software development is a delivery model where all communication between client and engineering team happens through written artifacts — specs, change orders, written design reviews, and recorded screen walkthroughs. There are no live meetings, no standups, no real-time calls. Decisions are made in writing, leaving a durable audit trail.

Three reasons. First, no meeting overhead — engineers spend hours coding, not sitting in calls. Second, no time-zone friction — work happens whenever, without waiting for overlap windows. Third, written specs force precision — ambiguity that a meeting would have papered over surfaces immediately, before code is written against the wrong assumption.

No. Alignment happens through the written brief and the written deliverable. The client sends specs; the studio sends a confirmation in writing with timeline, scope, and price. Mid-sprint, the client receives written status updates with screenshots. On delivery, the client receives source files plus a recorded video walkthrough they can watch on their schedule. Calls add no information that writing doesn't.

Send it in writing — usually email or the client portal. The studio replies in writing within one business day. If the question is a scope change, it goes through a written change order process. If it's a clarification, the answer is appended to the spec, where it lives forever instead of being lost in a Slack scroll-back.

Yes — and it's especially good for them. Complex projects accumulate decision debt: who decided what, when, and why. Async forces every decision into writing, which makes complex projects auditable, transferrable, and resilient to team turnover. Traditional sync engagements lose half of their decision context within six months.

Founders who genuinely want to learn alongside the engineering team — who want to sit in design reviews, watch architecture debates, and absorb technical context. Async optimizes for the studio's productivity, not for the client's education. If education is a primary goal, embedded sync engagements are a better fit (and cost 2–3× more).

Every sprint at Amatrix Studio is async by default. The intake is a written form. Confirmation is a written reply within 24 hours. Mid-sprint updates are written. Final delivery is source files in a ZIP plus a recorded screen walkthrough. There are no scheduled calls, ever — and the studio doesn't offer them as an option.