The 5-Year Website is Dead and Why Businesses Need Living Growth Systems Instead
Ben Crowther is the founder of Crow Flies Growth Systems and co-founder of Aiden Solutions. He helps businesses replace static websites and fragmented marketing with AI-powered growth systems built to convert, support and scale.
Businesses can spend heavily on a new website, then leave it largely unchanged until the next rebuild. Ben Crowther argues for a more useful approach: a connected system that improves as the business learns what customers need.
I think the five-year website has had its day. By that, I mean the habit of building a website, launching it, then barely touching it until somebody decides it looks old.
You spend a decent chunk of money. Everyone is excited for a few weeks. Then the website slips down the list until, four or five years later, you start the whole exercise again.
The website itself still has a job to do. In plenty of businesses, it could be doing a much better one.
With the right information and connections, it can help customers find answers, narrow down options, prepare an enquiry and reach the right person. It can also pass useful information into the systems your team already uses.
Once you start thinking about it that way, launch day should be the beginning of the work. It shouldn't be the best it ever gets.
Ask what business customers need
A clear, well-built website with useful information and an easy way to get in touch is still valuable. I don't think every business needs a complicated platform.
But I'd put a different question at the start of a website project. Before asking how many pages we need, ask what somebody needs to be able to do here.
Choose a product? Understand a service? Find out whether you cover their area? Give you enough information to prepare a sensible quote?
That changes the brief. You might still end up with Home, About, Services and Contact. Fine. Those pages should help a customer move forward, rather than simply tick off the sitemap.
Use the knowledge you have
A business can have experienced staff, years of customer conversations, technical documents and a detailed product catalogue. Then somebody visits its website and gets six marketing pages and a contact form.
There's a fairly obvious gap there.
Take a customer looking for equipment for a touring vehicle. They may know what they drive, what they carry and how they use it. They probably don't know how your catalogue is organised.
A useful website could collect that context, point them towards relevant information and flag what needs checking with a qualified person. It shouldn't confidently recommend a safety-critical setup because a language model produced a convincing answer.
The starting point is the information your business is comfortable making available. Keep it accurate, current and clearly separated from confidential material. Work out who owns it and who checks it.
Without that work, adding AI mostly gives an incomplete website a more talkative interface.
Search is raising expectations
Google began rolling out AI Mode in Australia in October 2025. In its announcement, Google said early testers were asking questions nearly three times the length of traditional search queries.
That is Google's report about its own users, not proof that everyone wants a conversation with every website. But it is a useful signal.
Compare "accountant Penrith" with "I run a building company in Western Sydney and keep finding out my tax position too late. What sort of accountant should I be looking for?"
The second question gives a business much more to work with.
I expect people who get useful answers that way to become less patient with websites that make them hunt through menus. Some will still prefer browsing or picking up the phone. Give them a clear route too.
Look behind the chatbot
I suspect we'll see plenty of websites add a chatbot, put a little sparkle next to it and call the job done.
The useful questions sit behind the interface. What information can it use? What happens when it doesn't know? Can the customer reach a person? What is it actually allowed to do?
Imagine someone arrives at 9.30 pm with a service enquiry. A properly configured system could answer routine questions from approved information, collect the details your team needs and create a lead in your customer relationship management system.
It could include a conversation summary and route the enquiry to the right person. The next morning, that person has something useful to work with instead of starting again.
That's an example of what can be built, not a promise that any chatbot does it out of the box. The connections need testing. The customer needs to know what happens next. A failed handover needs to be visible.
And answering a question is different from committing the business to a price, booking or technical recommendation. Decide where approval is required before giving a system the ability to act.
Start with frustrating work
The Australian Bureau of Statistics put reported AI use at 12% in its 2024-25 survey of employing businesses. That tells us something about adoption. It doesn't tell us whether the businesses improved.
You can buy another subscription and still have the same problem. You can also make a bad process faster.
I'd start by looking at where customers or staff get stuck. Which questions keep coming up? Where are people entering information twice? Where does an enquiry sit because nobody is sure who owns it?
Then choose the simplest useful fix. It might be AI. It might be ordinary automation, a better form or rewriting a terrible page.
AI isn't a religion. Use it where it makes sense.
Connect the next step
A website's job shouldn't automatically end when somebody presses Submit.
If the customer then gets asked the same questions again, waits while information is copied between systems and has to chase a reply, the experience still needs work.
This is where I think the traditional agency model can get in the way. Websites, search, content, advertising and CRM are often sold and managed separately. The customer has no interest in how we've divided up the invoice.
They find the business, decide whether it looks credible, make contact and judge what happens next.
I use the term living growth system for the connected work behind that experience: the website, useful business information, lead handling, follow-up and the people responsible for it.
You don't need to replace everything at once. Connect the part that is causing a real problem, then decide whether the next improvement is worth doing.
Improve after the launch
This is the part that matters most to me. Six months after launch, the website should be more useful than it was on day one.
That improvement won't happen because somebody calls it intelligent. Someone has to review the questions customers ask, fix weak answers, remove old information and check that enquiries reach the right place.
I'd give that work an owner, a realistic budget and a regular place in the calendar. A monthly review is a sensible starting point for many businesses, with urgent corrections handled sooner.
Look at a few measures that match the problem you're fixing. Are customers completing the enquiry? Are the details useful? How long does a human response take? Is the team spending less time re-entering information?
Measure against where you started. If a new feature creates more confusion or extra work, change it or remove it.
Continuous improvement also doesn't mean endless tinkering. Keep what works. A rebuild may still be justified when the existing platform is insecure, difficult to maintain or genuinely holding the business back. Its birthday alone isn't a compelling reason.
Keep people involved
I want good salespeople spending time on useful conversations. I want technical experts handling the questions that need their judgement. I don't want either of them stuck repeating information a customer could already have been given.
Keep a straightforward way to reach a person. Make the handover carry the context, so customers don't have to explain themselves all over again. Review mistakes rather than assuming a confident answer was a correct one.
The system needs to support the people doing the work. Otherwise you've just given them something else to manage.
Follow one customer journey
Before commissioning your next website, follow one enquiry from the customer's first question to the point where someone in the business takes responsibility for it.
Write down where the customer gets stuck, what information is missing and what your team has to do manually. Pick one problem, agree what better would look like and fix it. Then check whether it helped.
You may discover that the website needs rebuilding. You may discover that the existing one needs better information and a few sensible connections.
Either way, you'll have a better brief than "make it look more modern".
That's what I mean by moving beyond the five-year website. Build something useful, keep it accurate and give it the attention it needs to improve.
Launch it. Just don't abandon it.
Read more from Ben Crowther
Ben Crowther, Founder of Crow Flies Growth Systems & Co-Founder of Aiden Solutions
Ben Crowther is an Australian entrepreneur, marketing strategist and artificial intelligence (AI) advocate focused on how technology is changing the way businesses attract, convert and support customers. He is the founder of Crow Flies Growth Systems and co-founder of Aiden Solutions, a knowledge and customer support platform powered by AI. His work combines digital strategy, search engine optimisation (SEO), answer engine optimisation (AEO), generative engine optimisation (GEO), automation and conversational AI to turn traditional websites into active business systems.
Ben is particularly interested in the shift from static online brochures toward intelligent digital experiences that can sell, answer questions and support customers around the clock. Through his writing, he explores AI, entrepreneurship, marketing and the future of digital business.
