Method
We would rather show you our checklist than our trophies.
We have no awards to list, so here is what we actually check.
Frame
Who uses it, what must work on day one, what can wait. Written down in a page or two.
Sketch
Rough flows before visual polish. Cheap to change, so we change them.
Build
Small working increments you can try, not a reveal at the end.
Check
The criteria below, on real devices and widths.
Release
Launch steps, a rollback note, and a clear handover.
Quality criteria
Tick through them for your own project. This list is stored nowhere.
0 of 8 checked
Questions about how we work
Do you give fixed prices?
Only once scope is written down and agreed. Early conversations are about what to build, not a number.
Can we start small?
Yes. A narrow first release is often the most useful way to learn what matters.
Who owns the work?
Ownership and licensing are set out in the written agreement for each project; ask us to explain anything that is unclear.
What if something breaks after launch?
Agree a support arrangement before launch, so it is clear who does what. See IT support.