Guide
When should you move from WordPress to a Headless CMS?
WordPress is a great starting point. It's familiar, flexible, and has a plugin for just about everything. For a lot of businesses, it doe...
The Blog
What to expect when you hire a web development partner
Guide
If you've never commissioned a website before, or if the last time went badly, the whole process can feel like a black box. You hand over money, have a few meetings, and weeks later someone shows you something that may or may not resemble what you discussed.
It doesn't have to work that way. A well-run web project has a clear structure, predictable milestones, and no surprises. Here's what a good engagement typically looks like, so you know what to expect and what to push back on if things feel off.
- 01Discovery and scoping
Before any design or development starts, a good partner will spend time understanding your business, your goals, and what the website actually needs to do.
This usually involves a combination of conversations, document review, and research. The output is a scope document, a clear description of what's being built, why, and how long it will take.
This stage typically takes 1–3 weeks, depending on the complexity of the project. Some agencies skip it or rush through it. That's a red flag. Discovery is where misunderstandings get caught early, before they become expensive.
What you should see at the end of this stage: a written scope, a timeline with milestones, and a fixed or well-defined budget. If you're getting a vague proposal with no detail, ask questions before signing anything.
- 02Design
Design isn't just about making things look good, it's about structuring information so visitors can find what they need and take the action you want them to take.
Most projects start with wireframes, simplified layouts that show page structure without colours or images. This is where you'll see navigation, content hierarchy, and page flow. It's much easier to move things around at this stage than after everything's been designed in full colour.
After wireframes are approved, visual design is applied. You'll typically see 2–3 key pages designed in full detail, and once you approve the direction, the remaining pages follow the established style.
A good partner will limit design revisions to a structured process, not because they don't want your feedback, but because endless revision cycles delay the project and increase cost without improving the outcome.
- 03Development
This is where the site gets built. Depending on the project, this could take anywhere from 3 to 12 weeks.
During development, you should expect regular check-ins, not daily updates on technical details, but weekly or fortnightly demonstrations of working progress. You should be able to see the site taking shape at each milestone, not just at the end.
A good development process includes a staging environment, a private version of the site where you can review progress, test functionality, and flag issues before anything goes live. If your developer only shows you the site on launch day, that's a problem.
For more detail on how structured delivery works and why it matters, see our project delivery approach.
- 04Content and testing
Content is where most projects stall. Design and development can run to schedule, but if the content isn't ready, the copy, the images, the case studies, the launch date slips.
The best approach is to treat content as a parallel workstream from the start, not something to "fill in at the end." Your partner should be helping you plan content requirements early in the project and flagging deadlines well in advance.
Testing should cover functionality (does everything work?), responsiveness (does it work on mobile?), performance (is it fast?), and accessibility (can everyone use it?). Ask your partner what their testing process looks like. If the answer is vague, that's a concern.
- 05Launch and handover
Launch should feel calm, not chaotic. If the project has been well-managed, launch day is just the final step in a series of planned milestones, not a scramble to fix last-minute issues.
A proper handover includes documentation on how to use the CMS, training for your team on making content updates, and a clear understanding of what's included in post-launch support.
Ask these questions before launch: Who do I call if something breaks? What changes are included in the post-launch period? What happens after the support period ends?
Signs
Red flags to watch for
Over the years, we've seen patterns in projects that go badly. Here are the warning signs:
- 01No written scope.
If there's no document describing what's being built, there's no shared understanding, and no way to hold anyone accountable when things go wrong.
- 02No milestone check-ins.
If you don't see the site until it's "done," you have no opportunity to catch problems early. Milestone-based delivery is the minimum standard.
- 03Unclear pricing.
Fixed price with a clear scope is fine. Hourly with a well-defined estimate is fine. "It depends" with no detail is not fine.
- 04No post-launch plan.
A website needs ongoing maintenance, updates, and occasional fixes. If your partner doesn't offer any form of post-launch support, ask who will handle this.
A good web development partner makes the process feel collaborative and predictable. You should never feel in the dark about what's happening, what's coming next, or what you're paying for.
If your last experience felt stressful, chaotic, or opaque, it wasn't because "that's just how web projects work." It's because the process wasn't right.