Starting a new website project is exciting. It’s an opportunity to refresh your brand, improve the user experience, and create a platform that better supports your organisation’s goals.
But after working on hundreds of website projects over the years, we’ve noticed a common theme.
No matter the size of the organisation or the scope of the project, there are always a few things clients discover along the way and wish they’d known from the beginning.
If you’re considering a new website, here are some of the biggest lessons we’ve learned.
A website project is mostly about content
When people think about a website project, they often picture design concepts, colour palettes, and exciting new functionality.
In reality, content is usually the biggest challenge.
Gathering existing content, identifying gaps, rewriting pages, obtaining approvals, sourcing images, and deciding what stays and what goes can take significantly longer than the design and development itself.
A great website isn’t built around a beautiful design. It’s built around clear messaging and useful content that helps visitors achieve what they came to do.
The earlier you start thinking about content, the smoother your project is likely to be.
Internal approvals often take longer than development
Many organisations are surprised by how quickly design and development can move.
What often slows projects down is decision-making.
Feedback needs to be collected. Stakeholders need to review concepts. Internal teams need to agree on priorities. Content requires approval. Sometimes the same decision gets revisited multiple times.
None of this is unusual, but it can have a significant impact on timelines.
Establishing clear project ownership and approval processes from the start can make a huge difference to the success of a website project.
Your homepage isn’t the most important page
The homepage is often where organisations focus most of their attention.
While it is important, many visitors will never see it.
People arrive on websites through Google searches, social media links, email campaigns, blog articles, service pages and landing pages. In many cases, their first interaction with your organisation happens somewhere deep within the site.
Every page should provide context, answer questions and guide visitors towards a clear next step.
A successful website isn’t built around a great homepage. It’s built around a great experience from any entry point.
More features don’t always create a better website
It’s easy to fall into the trap of creating a long wishlist of features and functionality.
But successful websites aren’t defined by how much they do. They’re defined by how effectively they solve problems.
Before adding a feature, it’s worth asking a simple question:
What problem are we trying to solve?
Often the simplest solution delivers the best outcome for both visitors and content managers.
Launch day is just the beginning
Many organisations view a website launch as the finish line.
In reality, it’s the starting point.
Websites require ongoing care and attention. Software needs updating. Content needs refreshing. Security patches need to be applied. Analytics should be reviewed. User behaviour should be monitored.
Just like a house or a car, a website performs best when it’s maintained regularly.
The most successful websites aren’t the ones that launch perfectly. They’re the ones that continue to improve over time.
Not every page deserves equal attention
One of the biggest mistakes we see is organisations treating every page as equally important.
The reality is that some pages will receive significantly more traffic than others. Some pages directly support enquiries, sales or conversions. Others exist primarily for reference.
Understanding which content matters most allows you to focus your time, energy and budget where it will have the greatest impact.
Analytics and user insights can be incredibly valuable in helping guide these decisions.
The cheapest option is rarely the cheapest option
A website is a long-term investment.
Choosing a platform, solution or supplier based purely on price can often lead to higher costs later through security issues, performance problems, limited flexibility or the need for an earlier rebuild.
The goal shouldn’t be finding the cheapest solution.
It should be finding the solution that delivers the best long-term value for your organisation and your audience.
Technology alone won’t solve every problem
A new website can do amazing things, but it isn’t a magic wand.
It won’t automatically improve your marketing. It won’t fix unclear messaging. It won’t solve internal process issues. And it won’t create great content on its own.
The most successful website projects combine strategy, content, design, development and ongoing optimisation.
When all of these elements work together, the technology becomes a powerful tool rather than the entire solution.
Final thoughts
After hundreds of website projects, we’ve learned that the biggest challenges are rarely technical.
They’re usually content, communication and decision-making.
The organisations that achieve the best outcomes are the ones that invest time upfront in understanding their audience, defining their goals, preparing their content and making decisions efficiently throughout the project.
Get those foundations right, and the rest of the project becomes much easier.
If you’re planning a website project and aren’t sure where to start, we’d love to help.
Michael Scruse
Michael brings a rare blend of technical, web and sales expertise to every project, backed by over 30 years of experience in the IT industry.
He’s also a qualified chef, though these days his culinary skills are mostly reserved for the home kitchen. A self-confessed history buff, Michael is currently deep into researching his own family tree.