01 — Make something new
From a goal to something specific enough to build
Most projects are agreed with vagueness, creating unexpected cost. We shape the scope with you until the thing to build is specific enough to commit to, and you decide whether to build it after that — not before.
What we take on
A goal with something in the way of it. That might arrive as an idea, as a process that has stopped scaling, or as a report that takes days to assemble and is out of date by the time it lands.
You do not need to have concluded that you need software. Part of the work is finding out whether you do, and saying so if you do not.
How product work runs
Four stages
Each stage ends in something you receive and can read. Nothing here is a fixed timetable, because the shape of the problem sets the pace — but the order does not change, and neither does what you get at each point.
You agree the build budget only after discovery has produced a written definition of what would be built and why. That definition is yours: if you stop there, you keep it and can take it anywhere.
-
01 Discovery
A shared, written understanding of the goal, the obstacle in front of it, and the realistic options — including the option of doing nothing. Discovery is a paid, separately agreed phase: its budget is set before work begins and scaled to the depth you want, so you are never asked to fund a build to find out what the build should be.
-
02 Sharpen
A definition specific enough to plan against. When applicable, a clickable wireframe for part of the system is produced, so you can see something tangible and we can sharpen the definition.
-
03 Build
Working increments you can use, in an order agreed with you, so progress is something you see rather than something you are told about.
-
04 Run
A SaaS system in service with the knowledge to operate it written down alongside it, that we maintain.