A calm, six-step process. No surprises.
We work in phases you can see, with weekly check-ins, no jargon and a written trail at every step. If a phase feels wrong, we say so, and fix it before building on top of it.
Understand
We listen. Your mission, your people, your pressures come first.
Typical duration: 1–2 weeks
Before we mention a single tool, we spend time understanding what your organisation actually does day to day, who it serves, and what the technology needs to make possible. No slide deck. No jargon. A conversation.
What happens
- A one-hour conversation with the people doing the work
- A walk-through of the current tools and their pain points
- A shared picture of what "good" looks like for your team
Assess
Where you are, what would help, what should stay as it is.
Typical duration: 1–2 weeks
We map the current state (websites, systems, processes, data) and identify the biggest wins first. Sometimes the answer is a small automation. Sometimes it is a new website. Sometimes it is doing nothing yet. We tell you either way.
What happens
- A written assessment with plain-English recommendations
- Rough effort and cost bands for each option
- A prioritised roadmap you can share with a board
Design
A shape for the solution, sketched with you, not to you.
Typical duration: 2–4 weeks
Whether we are building a website, a system or an automation, we sketch it early and check it with the people who will use it. Nothing is precious. It is easier to change a wireframe than a live system.
What happens
- Wireframes, flows and visual design where relevant
- Content structure and journey mapping
- Sign-off on scope before build starts
Build
Websites, systems and automation in iterative steps you can see.
Typical duration: 4–12 weeks
We build in small, reviewable slices. You see progress every week. If something needs to change, we change it while it is cheap to. We use modern tooling (Next.js, TypeScript, Postgres, Vercel) so what we build lasts.
What happens
- Weekly demos and check-ins
- A staging environment you can share
- Accessibility, performance and security baked in
Launch
Onboarding, migration, documentation and training for your team.
Typical duration: 1–2 weeks
A launch is not just a switch flip. We migrate content and data carefully, train the people who will use the system, write documentation your team can find later, and stand by while things bed in.
What happens
- Data migration and content transfer
- Team training and written how-to guides
- Two weeks of active hand-holding after go-live
Support
Ongoing partnership so the technology keeps working for you.
Typical duration: Ongoing
Most of our clients stay with us. Monthly support covers maintenance, small improvements, a second opinion when you need one, and someone to call if something breaks. Predictable cost, no scramble.
What happens
- Monthly maintenance and updates
- Priority response on urgent issues
- Ongoing improvements and small features