How we workHOW WE WORKStraight through. Measured.THE SAME WORK, UNTANGLED01 · Day 1First readYou write one sentence. An engineer replies with what we heard.02 · Day 2–3A callThirty minutes to understand the work and who it touches.03 · Week 1Scope and SOWOne fixed fee, or a monthly plan. Baseline captured.04 · Weeks 2–4Build with your teamOn your systems. People decide every exception.05 · 30 daysHypercareDaily checks, fast fixes, measured again.06 · AfterExtended teamYour engineer works the top of your priority board.Three kinds of hands on the work.Every step of every project says who did it. Nobody confirms their own work, and the software never decides anything a person is accountable for.YOUR PEOPLEDecide.Choose what gets worked firstApprove scope, stage changes and every exceptionConfirm results, with finance signing offOUR ENGINEERSBuild.Walk the work with the people who do itBuild on your systems, in your environmentStay for 30 days of hypercare after launchTHE ASSISTANTProposes.Routes and summarises what you raiseDrafts replies and first reads for a person to checkNever approves, decides or confirms a resultHand us the first knot.One sentence is enough. An engineer replies within a working day, then gets on a call with you.Get a first read

How we work

Three kinds of hands on the work.

Every step of every project says who did it. Nobody confirms their own work, and the software never decides anything a person is accountable for.

{{ h.who }}{{ h.t }}

{{ x }}

Hand us the first knot.

One sentence is enough. An engineer replies within a working day, then gets on a call with you.

Get a first read