Index / Method
How the work actually happens.
Short cycles, real working software early, decisions written down, and no surprises at the invoice.
Shape
Working sessions with the people who own and use the process. Output: a written brief, a map of the systems involved, a first list of features ranked by value, and open questions. Paid as a small fixed-price piece of work, useful even if you take it elsewhere.
Sketch
Designs of the screens that matter most, clickable and tested with users. Wording, layout and flow are settled here. Output: approved designs and a build estimate in stages.
Build
Development in cycles of one or two weeks. At the end of each, a working version on a test site and a short note of what changed, what is next and any decision we need from you.
Launch
Data migration if needed, a rehearsal, a planned go-live at a quiet moment, and training sessions for your team. We stay close for the first weeks.
Care
An agreed arrangement for updates, fixes and small improvements. See care and support.
How we estimate
We estimate in ranges, not single numbers, because software has genuine uncertainty. Each estimate lists the assumptions it rests on. If an assumption turns out wrong, we tell you straight away and agree what to do before spending more.
What we need from you
A decision-maker who can give answers within a few days, access to the people who will use the tool, sample data early, and honesty when something we built is not right. That last one matters most.