In short
A 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.
Every engagement is the same ninety days. Days 1 to 30, build: we build the whole system inside the software you already run, and it is live by day 30. Days 31 to 60, adopt: your team uses it every day while we sit beside them, fix what breaks and add what they ask for. Days 61 to 90, own: we step back from active building, your team runs it and asks it for new features on their own, and we hand over the keys, the instructions and the files.
There is no separate study first. The map of how your business works, which tools you actually use, which process routes through a person, what to own next, comes out of building it. You hear the full price of the ninety days on a call, before day one.
The end state always happens: your team owns it and runs it. After day 90, maintenance and extended builds are there whenever you want them. Never required.
Example
What it looks like.
Ninety days, start to finish: connect the people to their systems, put the whole system live by day 30, sit beside the team while they use it every day, then hand over the keys, the instructions and the files on day 90.Related
Read next.
- Extended maintenanceOptional, after day 90. Maintenance and extended builds whenever you want them. Never required. Your team already owns and runs the system.Read the definition
- prototypeReal software, small in scope, that a subject-matter expert can run today. Not a mockup, not a slide. The unit of the first month.Read the definition
- connectorA link between an agent and a real system: email, calendar, files, the CRM, the site. Connecting your people to their systems is one of the first things we do in month one.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