Our Web Development Process, From First Call to Launch and Beyond
A clear process is the difference between a project that runs smoothly and one that drifts. Our web development process follows the same seven stages whether we're building a website, a platform, an app or an AI tool, so you always know what's happening, what comes next and what we need from you.
The seven stages
1. Discovery
We start by understanding your business: who your customers are, what they need to do, what's working today and what isn't. We look at your existing website, tools and data, and talk to the people who'll use what we build.
What you get: a shared understanding of the goals and how success will be measured.
What we need from you: time with the right people and access to existing systems.
2. Planning and scope
We turn what we've learned into a plan: the pages or features, how they fit together, the technology, and what's in and out of scope for this phase. Anything that can wait for a later release is noted, not lost.
What you get: a written scope and plan you approve before work starts.
What we need from you: decisions on priorities.
3. Design
We design the structure and screens: user flows, wireframes and then a clickable prototype you can try on your own devices. Changing a design is far cheaper than changing code, so this is where we invite the most feedback. Where it helps, we test with real users.
What you get: approved designs for the screens and flows.
What we need from you: feedback and sign-off.
4. Build
We develop in short cycles, sharing working progress regularly rather than disappearing until launch. You review real features as they're finished, which means problems surface early and course corrections are small.
What you get: regular demos of working software.
What we need from you: content, feedback on each cycle, and quick answers to questions.
5. Testing
Before launch, we test on real devices and browsers, check speed against Google's Core Web Vitals, review accessibility against the WCAG guidelines, and check security and data handling. For redesigns, we also check redirects so search visibility isn't lost.
What you get: a site, app or tool that's ready for real users.
What we need from you: a final review.
6. Launch
We launch carefully, monitor closely in the first days, and fix anything that comes up. App launches include store submission and review. We walk your team through how everything works.
What you get: a live product and a handover.
What we need from you: availability around launch day.
7. Care and growth
After launch, we can stay on to maintain, improve and market what we've built: updates, monitoring, new features, SEO and campaigns. Or your own team can take over, using the code and documentation we hand over.
What you get: a choice of ongoing support or a clean handover.
How the process adapts
| Project type | What changes |
|---|---|
| New website | More time in discovery and design on structure and messaging |
| Website redesign | An audit of the current site and a redirect plan come first |
| Custom platform or SaaS | Data model and architecture are planned before screens |
| Mobile app | Store guidelines are checked early; launch includes store review |
| AI project | A small proof of concept on real examples comes before the full build |
| Marketing and SEO | Measurement is set up first; work runs in ongoing cycles rather than to a launch |
What you can expect from us
- Plain language. We explain decisions without jargon.
- No surprises. Changes to scope are discussed and agreed before they happen.
- Visible progress. You see real work regularly, not just status updates.
- Honest advice. If something isn't worth building, we'll say so.
Timelines and pricing
Timelines and pricing depend on scope, so contact us for an estimate. The discovery and planning stages are where that estimate becomes firm.
Frequently asked questions
Most involved during discovery, design reviews and at the end of each build cycle. In between, a quick answer to questions keeps things moving.
Yes. Changes are easiest during design. Later changes are discussed and agreed before they're made, so you always know the impact.
We work in short, iterative cycles with regular demos, which is the core of agile delivery. We adapt the exact format to your team.
You can keep us on for maintenance, improvements and marketing, or take the project in-house using the code and documentation we hand over.
Ready to start?
The first step is a conversation. Tell us what you have in mind and we'll come back with a clear next step.