How we work
How we work
What separates a considered solution from an arbitrary one is the work done before and around the code. With us, mapping, analysis and documentation are part of the delivery, not something that happens behind the scenes. Every step leaves something tangible: a document, a sketch, a measurement, a decision.
Map
We start with the organisation, not the order. Who does what today, where does the time go, where do the errors occur, and who will actually use the solution? We talk to the people who do the work, not only the person placing the order, and look at competitors and the market where relevant. If a solution already exists, we review it properly: performance, accessibility, visibility, contact flow. You get the findings presented so you can verify them yourself.
Sort
Findings only become useful once they are sorted. We separate problem from symptom and urgent from can-wait, and point out what should not be built at all. Sometimes the right advice is to leave it alone. When it is, we say so.
Sketch
From vague wish to something you can look at. We make sketches or a clickable prototype before anything is built, while changes are still cheap. You should be able to point at what’s wrong before it is coded, not after.
Build in small steps
We build in short stages with visible progress and demos along the way. Nothing disappears into a dark room for three months. You see what is happening, and can adjust course while it is still easy.
Responsible by default
Privacy, accessibility and security are assessed at the start, not at launch. Early on, we establish what data the solution needs, who must be able to use it, and which rules apply to your particular use – so the regulated parts are handled in the plan, not discovered in the final week before launch.
Measure and document
We measure what we promised: performance, accessibility and function. We write the result down with a date. The documentation is written so you can understand, operate and develop the solution afterwards. Including with a supplier other than us.
Insight as a standalone delivery
The mapping can be bought on its own, as a discovery project. You end up with a document describing the need, the priorities, the risks and a proposed solution, written to be usable no matter who builds next. Some only need that to move forward. That is a perfectly good outcome in our book.
We don’t take every project
Some projects require licences, specialist expertise or risk assessments we cannot responsibly carry out. When that is the case, we say so early – and gladly point you towards someone who can help. That is better for everyone than us having a go.
Measured, not claimed
This website is an example
The site you are reading is built to the same standards we apply in client projects. No analytics or tracking loads before you choose to consent. Open your browser’s developer tools and see for yourself. The site has been reviewed against WCAG 2.1 AA with a written test log, its performance is measured and documented with dates, and the contact form stores nothing: your message is sent to us as an email, and that is all.
Would you like the same documentation for your own solution? This is how we work.