Scope before code
A written definition of what is being built, what is not, and what done means, agreed and priced before anything starts. Changes carry a number.
The studio
Software is a system inside other systems.
Which is why the work starts with the scope and ends with a handover, not with a launch.
A software and design studio
XYZ Makes LLC builds software, and the things around software. Native applications for Apple platforms, web platforms and the systems behind them, original writing and video, and practical advisory for teams putting AI into work they already do.
The pipeline that produces the video produced this site’s design tokens, and the iOS applications read the same tokens. The four lines share machinery.
Engagements are scoped, priced and dated before they begin.
How the work runs
01
02
Something running early
A prototype in the first weeks. Opinions about a picture of software are worth very little.
03
Weekly, visibly
Increments you can look at, on a schedule.
04
Built to be handed over
Documentation, access and code written for whoever maintains it next. A studio that makes itself hard to leave has sold you a hostage.
The stack, and why
Applications are Swift and SwiftUI, shipped through TestFlight before anyone else sees them. Sites are static by default — Astro, rendered ahead of time, served from an edge network, with motion added where it earns its place and nowhere else.
Colour, type and the mark live in one repository the site and the applications both read. A script checks the palette against WCAG AA on every surface it can land on, in both colour schemes, and fails the build.
Start with the problem, not the solution.
Describe what you are trying to ship and what is in the way. You will get a scope and a price, or a straight answer that this is not the right studio.