Process
How projects actually happen.
Every project follows the same structure: research, design, build, test, launch, handover. The timeline varies. The principles don't.
01 · The approach
No surprises.
The process below isn't an idealised flowchart. It's the actual sequence we follow, refined across nine years of creative and development work — from small brand identities to complex custom platforms and full web applications.
The goal is simple: no surprises. At every stage you know what's happening, what's next, what we need from you, and what you'll see at the end. Every project has its own shape — we'll give you an honest plan before you sign anything, including how we sequence the work so nothing slips.
02 · The stages
From first call to live site.
Six stages, six checkpoints. Same structure on every project — even if the scope and shape vary.
01
Discovery & strategy
We start by understanding the project properly. Audit what already exists, talk to the team who'll use or administer the product, map the actual user needs, identify technical and operational constraints. Larger projects get competitor analysis and a content audit before any design work begins.
You get at the end
- A written project brief
- Scope and priority recommendations
- A proposed information architecture
- A clear plan for the rest of the project
Checkpoint
We review the brief together. You confirm the direction before we move forward.
02
Design direction
Before building the whole site, we design a single representative page — usually the homepage — at full fidelity. This is where the visual language is established: typography, colour system, spacing, interaction style, tone. We use this page to validate the direction before any code is written.
You get at the end
- A fully designed homepage (desktop + mobile)
- A draft design system
- A written rationale for every choice
Checkpoint
We present the design direction. You approve it. Changes after this point affect the plan — not a warning, just a fact.
03
Development foundation
Clean, purpose-built code on the stack we chose during Discovery. The structural foundations come first — design tokens, base templates, navigation, typography, core components. At this stage the product doesn't look like much, but the engine is being assembled.
You get at the end
- A working foundation on staging
- A development preview URL
Checkpoint
A short technical review to confirm the foundation is solid before content build-out.
04
Content types & components
The bulk of the build. Data structures, templates, and core components assembled. Application logic implemented. Whether it's a content-driven site, a client portal, a CRM, or a custom platform — this is where the product takes shape. Migrations, integrations, forms, dashboards, custom features — all built here.
You get at the end
- A fully populated, functional site on staging
- Every page template working
- Every custom feature implemented
- All content migrated
Checkpoint
Structured review of the full site. You walk through every page, note everything. We fix it.
05
Accessibility, performance & QA
This is the part most projects skip and regret. We audit accessibility manually — keyboard navigation, screen reader testing, contrast, alt text, semantic HTML. We test performance on real devices and real network conditions, not just desktop Chrome on fibre. We check every relevant browser. We fix what we find.
You get at the end
- A WCAG 2.2 AA compliance statement
- Lighthouse ≥ 90 across Performance, Accessibility, Best Practices, SEO
- Cross-browser and cross-device verification
- A final QA report
Checkpoint
Green light to launch.
06
Launch & handover
We migrate staging to production, set up redirects, verify SSL, configure analytics, submit sitemaps, and switch everything live. Then we spend time with your team showing them how to administer the site, so they can run it from day one — no ongoing dependency on us required.
You get at the end
- A live, fully-working site at your domain
- A documented handover guide tailored to your site
- Admin credentials transferred to your team
- 30 days of post-launch support included
Checkpoint
Site is live, team is trained, the support window begins.
03 · After launch
The 30-day support window.
After launch, every project includes 30 days of support at no additional cost. This covers any bugs, adjustments, or minor changes that surface once the site is actually in use. It does not cover new features or major changes of direction — those become separate scoped work.
After the 30 days, your team takes over completely. The site is built to be administered internally, not to create ongoing dependency on us. If you want us involved in bigger changes later, we're available for that as separate scoped work.
04 · How we price
Priced honestly.
Every project is quoted individually after Discovery. We don't have a rate card with packages — that model produces generic results because it's designed to be sold at volume. We sell fewer projects, priced honestly, built properly.
- We quote on scope, not on hours. Once we've agreed a price, we won't surprise you with extras unless you ask for something outside the original scope.
- We're transparent about what's included and what isn't.
- Payment is usually structured in tranches — a deposit at contract signing, a mid-project tranche at design approval, the balance at delivery. The split is flexible.
- If you have a budget in mind, tell us. We'll tell you honestly what's possible within it, or what would need to change to fit.
05 · Start
Ready for stage 01?
Send a short note describing what you're working on. We reply within 24 hours, and we'll tell you honestly whether we're the right fit — even if we're not.