In short
Optional, after day 90. Maintenance and extended builds whenever you want them. Never required. Your team already owns and runs the system.
By day 90 your team owns the system and runs it. Everything after that is optional. Never required.
Maintenance means we watch what ran and report only when it matters, keep the instructions sharp, tighten a validator every time something ships wrong, and move the files to the better model or harness when one appears.
Extended builds mean a bigger job than your team wants to ask for on its own: a new department, a new tool, a new system. We scope it on a call and build it inside the system you already own.
You can run on our infrastructure, one bill, nothing to babysit, or in your own accounts. Either way the files are yours.
Example
What it looks like.
A month of maintenance after day 90: one validator tightened after a bad render, a model upgrade absorbed, and one message to the owner, about a decision only she could make.Related
Read next.
- Ninety-day transformationA fixed three months, in and out. Build in month one, live by day 30. Adopt in month two. Own in month three, when we hand over the keys, the instructions and the files.Read the definition
- source filesWhat a design studio hands over when the work is done. Here: the instruction files, the documentation, the code, the repository, the keys. All yours, in your accounts.Read the definition
- railsOur hosting, email, backend, and models, run for you. One bill, nothing to babysit, always on current software. Your files stay portable.Read the definition
- portabilityYour agents are files. They move to any harness, any model, any host. Leaving is copying a folder.Read the definition