Webbfox Delivery Fundamentals
An overview of how Webbfox delivers web projects — from discovery through launch and beyond. What to expect at each phase and how handover works.
How We Deliver Projects
Every Webbfox engagement follows a structured delivery model designed to reduce surprises and keep your team informed. Whether you're building a new site or reworking an existing one, the process moves through five phases: discovery, structure, build, launch, and improve.
This isn't a rigid waterfall. Phases overlap, and we adapt based on project complexity. But the sequence gives both teams a shared language for where things stand at any point.
The Five Phases
1. Discovery
We start by understanding your business, your audience, and the problem the site needs to solve. This includes stakeholder interviews, competitive review, and technical scoping. Discovery typically produces a brief, a sitemap, and a rough timeline.
2. Structure
With the brief agreed, we define the information architecture, content requirements, and key user flows. You'll see wireframes or low-fidelity layouts at this stage — enough to validate direction before visual design begins.
3. Build
Design and development run in parallel where possible. We work in short iterations, sharing progress through a staging environment you can access at any time. Feedback is collected in structured rounds to keep things moving.
4. Launch
Before go-live, we run through a pre-launch checklist covering performance, accessibility, SEO basics, analytics, and redirects. Launch is coordinated with your team — we handle the technical cutover and monitor for issues in the first 48 hours.
5. Improve
Websites aren't finished at launch. We offer ongoing support plans for clients who want continued optimisation, content updates, or feature additions. Many of our best results come from post-launch iteration informed by real traffic data.
How Handover Works
At the end of a project, you receive full access to your codebase, hosting environment, and CMS. We provide a handover document covering site architecture, credentials, third-party integrations, and maintenance notes.
If your team manages the site going forward, we're happy to do a walkthrough session to cover the essentials. If you'd prefer ongoing support, check our pricing plans.
What We Expect From You
The model works best when both sides stay engaged. That means timely feedback, access to the right stakeholders, and realistic content timelines. We'll flag risks early — and we expect the same in return.
For a detailed look at how kickoff works, see Getting Started with Webbfox.