The studio has engineers because the alternative is designing things whose cost we cannot estimate. They are in the room from the first week, and the most valuable thing they do early is say that something is either much cheaper or much more expensive than it looks.

We work in native mobile, in typed JavaScript on the web, in Python and Go on the server, and occasionally close to hardware when a client instrument requires it. We are not attached to any of it. We choose for the maintenance burden the client will carry, not for what is interesting to write, and we will argue against a stack we like if the client cannot hire for it.

Everything ships with tests, a deployment path the client controls, and documentation written for the engineer who inherits it. The work is not finished when it launches; it is finished when someone else has changed it successfully.