Loading —
Loading —
Process — five phases, in order
Nine years and eighty-odd projects have worn our process down to five phases. None of them are optional, and none of them are secret. The order matters more than the names.
1–2 weeks
We learn your business before we have opinions about it.
Every engagement starts in your world, not ours: your sales calls, your factory floor, your support inbox, your tender documents. We interview the people who buy from you and the people who almost did. We read what your competitors publish and what your customers actually search for.
The phase ends with a written brief we both sign. If we can't agree on what the work is for, we stop here — it's the cheapest place to find out.
2–3 weeks
Strategy in plain sentences, agreed before anything is designed.
Positioning is a set of choices about who you're for and what they should believe. We write it as plain, testable sentences — no quadrant diagrams, no brand onions. Messaging, information architecture, and content strategy follow from it.
This document becomes the arbiter for every design decision after it. When a review stalls, we go back to the sentences, not to taste.
4–8 weeks
Identity and interface designed as one system, shown in context.
We don't present three logo options on white slides. We design one system — type, colour, layout, motion, voice — and show it doing its actual job: on the spec sheet, in the checkout, at the bus stop, on the phone your customers really use.
Reviews happen weekly and in working form. You'll see rough work early, because course-correcting at week two costs nothing and at week eight costs the schedule.
4–8 weeks
Design and build in-house, tested against a performance budget.
Websites and products are built by the same studio that designed them. Everything ships against a written budget for performance and accessibility — page weight, load time, contrast, keyboard coverage — checked in review, not discovered after launch.
Print and packaging go through production supervision: we're at the press check, because that's where good work is most often quietly ruined.
1–2 weeks, then retained
Documentation, training, and a measured launch — not a file dump.
Handover means your team can run the work without us: guidelines as a living site, a documented codebase, CMS training, and a launch checklist we execute together. We measure the outcomes we promised in phase one and report them honestly, including the ones that missed.
Most clients keep a retainer for the sharp-tool work; some come back a year later with the next problem. Either is a good ending.
The process is only as good as what it shipped
See the outcomes →
Eight to ten projects a year. Currently scheduling work for next quarter.
Start something →newwork@foundrynorth.example · +44 161 496 0233