A small-business website connecting an enquiry to a CRM, calendar and follow-up workflow
|

Are Websites Dying in the Age of AI? For Small Businesses, the Opposite Is True

By Vadym Leonov, owner and lead developer at LeonovDesign · 18-minute read

For a small-business owner, a new website enquiry should feel like good news. Too often, it arrives as homework.

Copy the details into the CRM. Ask which suburb the customer is in. Request photos. Find a suitable time. Send the same explanation you sent yesterday. Chase the confirmation. Follow up when the reply disappears.

The lead came through the website. The work did not.

A small-business website connecting an enquiry to a CRM, calendar and follow-up workflow
A website is no longer a page you look at. It is the layer between a customer’s question and the systems that answer it.

Now add AI to the conversation and you hear a different story: customers will ask an assistant, the assistant will answer, and websites will become irrelevant. It sounds plausible — if a website is only five pages and a contact form.

But that is an old job description for a website.

The short answer

Websites are not dying. Static websites that only display information are becoming less useful. A modern small-business website is a trusted public source, a place where customers take action, and the connection between your CRM, calendar, payments, analytics and day-to-day processes.

AI has made a basic page easier to produce, and it has widened the range of work software can handle. Forms, CRM connections, booking rules and automatic reminders existed long before generative AI. Now software can also interpret a free-text enquiry, classify or translate it, summarise it for staff and search an approved knowledge base. As the page itself becomes a commodity, the accurate information, proof, integrations and business thinking behind it become more valuable.

The Small-Business Problem Is Not a Lack of Technology

Most small-business owners I meet do not need another dashboard. They need fewer loose ends.

An enquiry arrives in one inbox. A booking lives in another app. A quote sits in a document. A staff member keeps a private spreadsheet because the CRM is missing half the details. The owner remembers to follow up because nobody else knows the lead exists.

Each step looks small. Together, they break the day into pieces.

That is the hidden cost of a disconnected business: not only the minutes spent copying information, but the attention lost whenever a person has to stop useful work, reconstruct the situation and decide what happens next.

Small businesses rarely have a shortage of work. They have a shortage of uninterrupted attention.

So the better question is not, “Will AI replace my website?” It is: can my website stop creating admin and start carrying part of the process?

A website that creates a lead and six manual tasks is only half-built.

Why the “Websites Are Dying” Story Feels Believable

There is a real change underneath the dramatic headline.

People ask ChatGPT to compare services. Google places an AI-generated summary above its familiar list of results. A customer can find a local business through Maps, Instagram, a marketplace or an AI assistant without visiting its homepage first. AI website builders produce a respectable-looking page in an afternoon.

And yes, some searches now end without a click.

In March 2025, Pew Research Center tracked 900 US adults across 68,879 Google searches. When an AI summary appeared, people clicked a traditional result on 8% of visits, compared with 15% without one. Just 1% clicked a source inside the summary. That is one US study, not a forecast for every search — but the shift is real. Read the Pew Research Center study.

So the concern is reasonable. The conclusion is not.

Fewer clicks to generic informational pages do not make a business website useless. They make generic informational pages less defensible. A customer may get a quick answer elsewhere, but the business still needs:

  • an authoritative place to publish current facts;
  • evidence that its claims are real;
  • a controlled path to enquire, book, buy, upload, sign or pay;
  • a way to record consent and customer intent;
  • a connection to the systems that deliver the service; and
  • a reliable way to measure what happened.

The mistake is treating discovery, authority and action as the same thing.

What Is Actually Dying: the Passive Brochure Website

The old brochure website had a simple job. It showed a logo, a few services, a team photo and a phone number. If it looked polished, everyone considered the project finished.

That model is losing value, and it should. A passive brochure usually has:

  • generic service copy that could belong to any competitor;
  • vague claims with little evidence;
  • a contact form that turns a customer into an unstructured email;
  • information that goes stale because updates are difficult;
  • no useful connection to the CRM, booking system or payment flow;
  • no clear attribution for where a lead came from; and
  • no plan for what happens after “Thank you for your enquiry”.

The problem is not that the site has only five pages. Some businesses genuinely need a simple website, and adding complexity for its own sake only creates more maintenance.

Simple is not the problem. Passive is.

The modern alternative is not a website covered in AI buttons. It is a website designed around what the customer needs to do and the business process behind it.

AI Still Needs Somewhere to Get the Truth

An AI assistant does not know your business by intuition. It works with information it can retrieve from the web, connected services and other available sources: directories, reviews, social networks, third-party articles. Your website is the source you can most directly control.

That matters because the details customers ask about are rarely abstract:

  • Which suburbs do you service?
  • Do you handle this type of job?
  • What does the process involve?
  • What is included in the price?
  • Can I book next week?
  • Do you have evidence of similar work?
  • What happens to the information I submit?

If your own site is vague, stale or contradictory, an AI system cannot reliably fill in the blanks for you. It may find an old directory listing, an incomplete social profile or a third-party description you did not write.

Google’s current guidance is unusually clear on this point. Its generative AI features use core Search systems to retrieve relevant, up-to-date pages from the Google index and ground answers in web sources. Google also says normal SEO remains relevant: useful original content, crawlable pages and a clear technical structure still matter. See Google’s guide to generative AI search.

OpenAI makes a similar practical point. Any public website can appear in ChatGPT Search, and publishers who want their content discovered, cited and linked should allow its search crawler, OAI-SearchBot. OpenAI is also clear that there is no way to guarantee top placement. See OpenAI’s publisher guidance and ChatGPT Search guidance.

AI does not remove the need for a source of truth. It raises the cost of not having one.

The Homepage Is Not the Treasure. The System Behind It Is.

People talk about a website as an asset, but the valuable part is not the collection of pixels on the homepage. The real asset is what a good website accumulates and connects over time:

  • a recognised domain and a consistent public identity;
  • clear explanations of the business’s expertise;
  • original photos, projects, reviews and case studies;
  • useful pages that earn links and search visibility;
  • tested routes from a customer question to a sensible action;
  • measurements based on data customers agreed to share;
  • structured customer data flowing into the right system;
  • business rules for qualification, routing and follow-up; and
  • a maintained knowledge base that staff and customer-facing AI can use.

Social media, marketplaces, Google Business Profile and AI assistants are valuable ways to reach people. Use them. But their rules, formats and reach belong to somebody else.

Your website is where those channels hand a customer into a process your business controls. The value is not in owning pages. It is in controlling the route from question to outcome.

That is why a good website becomes one of a small business’s most valuable digital assets. It carries knowledge, reputation and processes that improve with use. A social post usually has a short life. A maintained website builds on the work done last month and last year.

We explored this ownership idea in more detail in Why Every Melbourne Business Needs a Website. AI does not weaken the argument. It adds a new audience for the information you own: machines acting on behalf of customers.

The Website’s New Job Description

Here is the change in plain English.

Old brochure websiteConnected business website
Lists servicesExplains services clearly to people and machines
Sends a form to an inboxCollects useful details and creates a complete CRM record
Displays a phone numberRoutes each customer to the right next step
Answers a few generic questionsGives customers approved, current answers
Shows a galleryConnects proof to a service, location and outcome
Ends at a thank-you pageConfirms, assigns, books, tracks and follows up
Counts visitsTracks qualified enquiries, bookings and sales
Works as a destinationMoves the customer and the team to the next step

This is what we mean at LeonovDesign when we say a website should work for the business, not merely announce that the business exists.

One Enquiry, Before and After

Consider a hypothetical roofing company in Melbourne. A customer notices a leak at 8:40 pm and sends, “Can you give me a quote?”

Small-business owner reading a website enquiry that still has to be copied into a CRM by hand
The same enquiry can arrive as a loose email or as a complete, routed record. The difference is design, not luck.

With a disconnected website

The message lands in an inbox. The next morning, somebody asks for the address, roof type, urgency and photos. The customer replies with two of the four. A staff member checks the service area, copies the details into the CRM, asks for the missing photo and offers a time. Three more messages follow. Nobody records whether the customer came from Google, an ad or a referral.

The website generated interest. The team still had to turn that interest into usable information by hand.

With a connected website

The site asks only the questions needed for that kind of job:

  1. It collects the postcode, roof type, urgency, contact details and photos with clear consent.
  2. A fixed rule checks whether the address falls inside the service area.
  3. The enquiry source and complete job details enter the CRM.
  4. The customer receives an accurate explanation of what happens next.
  5. If the job meets the business’s criteria, the customer can choose an inspection time.
  6. The right staff member receives a task, not a loose email.
  7. AI may summarise the submission for the team, while pricing and commitments stay controlled by business rules or a person.

If the form is incomplete, the job is unusual or the customer would rather call, the site should preserve what it can and offer a clear route to a person. It should not guess its way to a quote.

The customer gets clarity. The team gets a usable record. Nobody has to move the same information by hand. That is website automation at its best: not a talking robot added for decoration, but a clean handoff from customer intent to the people who can help.

Useful Website Automations, Not Automation Theatre

The goal is not a website with AI. The goal is a business with fewer broken handoffs. These are the automations that usually deserve attention first.

Qualify and route enquiries

A good form changes according to the service a person selects. It gathers the few details needed to assess the enquiry, checks simple eligibility rules and sends a complete record to the correct CRM pipeline or team member. That does not mean rejecting every unusual job automatically. It means routine enquiries arrive in a usable shape, while exceptions are flagged for a person.

Booking and reminders

The website can offer the right appointment type, read genuine availability, add a sensible travel buffer, confirm the booking and send reminders. It can also make rescheduling easy instead of starting another email chain.

Quote, deposit and onboarding handoffs

Once an agreed condition is met, the site can trigger the next document, request a deposit, send an onboarding checklist or create an internal task. Fixed calculations can be automated. Complex pricing should stay reviewable.

Grounded customer support

An AI assistant can answer repeat questions from an approved knowledge base: service areas, preparation instructions, opening hours, warranty steps or what to bring to an appointment. When the answer is uncertain, sensitive or outside scope, it should hand the conversation to a person. For practical examples, see our guide to AI chatbot use cases for small-business websites.

Cleaner CRM records and useful summaries

A connected form can create one complete customer record, preserve marketing attribution, assign an owner and set the next task. AI can classify or summarise a long submission so staff see the important points first. Your CRM should not discover a customer three emails late.

Follow-up after the work

The system can send care instructions, check whether the customer needs help, request a review, schedule a maintenance reminder or invite an appropriate repeat booking. This is where small improvements compound. A single reminder is not impressive. A reliable process that prevents hundreds of forgotten reminders is.

Use Code for Rules, AI for Language and People for Judgement

Not every task needs AI. Many of the best website automations are ordinary rules executed reliably. This is the framework we use when thinking through a workflow.

Best handled by fixed rules or codeWell suited to carefully constrained AIKeep a person responsible
Required fields and validationSummarising a long enquiryFinal quotes for unusual work
Service-area checksClassifying the type of requestComplaints and sensitive conversations
Calendar availabilityDrafting a reply for reviewContractual commitments
Fixed calculationsSearching an approved knowledge baseRegulated or high-stakes advice
Consent recordsExtracting details from free textExceptions that affect safety or trust
Routing and status changesTranslating or rephrasing informationDecisions that need accountability

Use code for rules, AI for language and people for judgement. That line prevents two common mistakes: using an unpredictable model for a decision that should follow a fixed rule, and paying a person to repeat a mechanical task that software can handle safely. Automate the relay, not the relationship.

Why the CRM Connection Matters So Much

A website form and a CRM are not the same thing.

The website sees the moment of intent. It knows what page the visitor used, which service they selected, what information they supplied and what consent they gave. The CRM is where the business tracks the relationship: who owns the lead, what stage it is in, what was promised and what must happen next.

When the two are disconnected, context leaks away. Someone copies a name but forgets the source. A photo stays in the inbox. A booking is confirmed but the deal stage never changes. Marketing reports a “conversion” while the sales team knows the enquiry was irrelevant.

A proper website-to-CRM integration can:

  • create or update the correct contact without duplicates;
  • attach the service, location, budget range, files and consent record;
  • preserve campaign and landing-page attribution;
  • assign the enquiry using clear business rules;
  • create a follow-up task with a deadline;
  • trigger a relevant email or SMS; and
  • feed the final outcome back into reporting.

The most valuable button on a website may be the one that stops a name being copied into a spreadsheet.

A Modern Website Has Visitors Who Are Not Human

Search crawlers have visited websites for decades. AI is adding a more active kind of machine visitor: an agent that may compare providers, complete a form or help a user make a booking.

This does not require a science-fiction rebuild. It requires solid web design. Google’s web.dev guidance explains that browser agents may interpret a page through screenshots, HTML and the accessibility tree. Clear buttons, proper links, labelled fields, stable layouts and semantic structure make actions easier for agents to understand. Conveniently, those same choices make a website better for people using keyboards, screen readers or small mobile screens. Read the agent-friendly website guidance.

An AI-ready website is a site whose facts and actions are clear, crawlable, accessible and current. It gives people and machines reliable information, gives customers a safe way to act, and passes the resulting data into the systems the business actually uses. It is not a separate species of website.

How to Make a Website Easier for Search Engines and AI Systems to Understand

There is no button that guarantees a citation in ChatGPT or an appearance in Google AI Overviews. Anyone selling that guarantee is selling confidence they do not own. There is, however, a sensible body of work that helps humans and machines understand a business.

Publish facts, not fog

State what you do, who it is for, where you work and what happens next. Keep opening hours, contact details, service areas, policies and pricing signals consistent wherever they appear. “We deliver innovative solutions” tells nobody anything. “We build and support fast websites for Melbourne small businesses” can be understood, checked and quoted.

Answer real questions directly

Use customer language in headings and give the answer before the long explanation. A clear FAQ is useful because it reflects how people speak, not because FAQ markup is a magic ranking trick.

Add evidence that cannot be generated from a prompt

Original case studies, project photos, measured results, limitations, methods and first-hand explanations are harder to copy and more useful than another summary of common advice.

On our Keilor Park Soccer Club rebuild, for example, we published the old and new page weight, load time, technical changes and analytics screenshots instead of hiding behind a vague “great result”. The case study reports a 280% traffic increase in 30 days. That is a first-party result from one project, not a promise about the next one. The point is to show the work and its context.

Make the page technically clear

Use descriptive titles, logical headings, crawlable text, canonical URLs, useful internal links, sensible image descriptions and semantic HTML. Add accurate structured data where it matches what a visitor can see. Keep forms accessible and important actions available without a maze of pop-ups.

Show who wrote the content and when

A named author, relevant experience, publication date, genuine update date and source links help a reader judge the page. They also make the origin of a claim easier for another system to identify.

Allow the crawlers you want

Crawler access is a business choice, not a compulsory setting. If you want visibility in ChatGPT Search, check that OAI-SearchBot is allowed by your robots.txt file, firewall and content-delivery network. OpenAI treats its search crawler separately from GPTBot, which is associated with potential model training, so the decision does not have to be all or nothing.

Ignore “secret AI SEO” tricks

Google says you do not need special AI markup, artificial content “chunks” or an llms.txt file to appear in its generative search features. It also says structured data is not a special requirement for AI search, although accurate markup remains useful for established search features. The durable work is still good information, sound SEO and a usable site — not a file created to impress a crawler.

For a broader practical guide, read AI for Small Business: The Website as Your Source of Truth.

What Should Not Be Automated

Automation becomes expensive when it handles the easy path quickly and fails badly at the edges. A faster mistake is still a mistake.

Keep human review wherever the business is making a sensitive promise, exercising judgement or accepting meaningful risk. That often includes unusual or high-value quotes; complaints and vulnerable customers; safety-critical instructions; legal, medical, financial or other regulated advice; contractual changes; uncertain identity or payment issues; and anything the system cannot explain or confidently route.

Good automation also needs basic discipline:

  • collect only the data the workflow needs;
  • explain why it is being collected;
  • restrict access to customer information;
  • use approved, secure integrations;
  • do not paste sensitive records into an unapproved AI tool;
  • log important actions and failures;
  • give customers a visible route to a person; and
  • review the workflow when the business changes.

Australian businesses should check how the Privacy Act and Australian Privacy Principles apply to them and to the personal information they handle. Many small businesses with annual turnover of A$3 million or less are not covered, but important exceptions apply. Check the OAIC’s small-business guidance and its guidance on commercially available AI products. This is general information, not legal advice.

Automated marketing does not remove responsibility either. Consent, sender identification and a working unsubscribe option still matter. See the ACMA’s spam guidance. Responsible automation is not “set and forget”. It is a maintained part of the business.

Judge the Website by Handoffs, Not Vanity

Traffic matters, but it is not the whole job. A page can attract thousands of visits and create little value. A low-volume service page can produce the right enquiry, collect everything the team needs and save several rounds of admin.

Useful measures include time to the first useful response; percentage of enquiries with complete information; qualified enquiry rate; enquiry-to-booking completion; manual touches required per enquiry; appointment reschedules and no-shows; completeness of CRM records; time spent moving information between tools; and pipeline or revenue influenced by the workflow.

Traffic tells you who arrived. Handoffs tell you whether the website helped.

Annual hours spent = minutes per task × times repeated per week × 52 ÷ 60

A ten-minute task repeated for 20 enquiries a week adds up to about 173 hours a year. That does not mean automation will recover every hour. It gives you a number to investigate — and a way to compare the cost of a sensible integration with the work already being paid for in staff time, delay and missed follow-up.

When Automation Is Worth Paying For, and When It Is Not

Automation is usually worth investigating when a task happens often, follows stable rules, creates costly delays or errors, and connects tools that can exchange data reliably.

It may not be worth it when enquiry volume is low, the process changes every week, most cases are exceptions, or a person can complete the task faster than the system can be maintained. Integrations also need an owner. APIs change, permissions expire, staff alter the process and messages go out of date.

The honest goal is not maximum automation. It is the smallest maintained system that removes a real point of friction.

How to Turn an Existing Website Into a Working Part of the Business

You may not need a new site. Often, the right first step is to connect or improve the one you have. Start with one customer process:

  1. Choose a frequent process. Enquiry qualification, appointment booking, deposit collection or follow-up are good candidates.
  2. Map the real handoffs. Write down every question, decision, copy-and-paste step and place where information waits.
  3. Choose the source of truth. Decide whether each fact belongs in the website, CRM, calendar, accounting system or another maintained tool.
  4. Fix the information and intake. Make the page clear and collect only what the next step needs.
  5. Connect the important system. Do not add five integrations when one CRM or booking connection solves the real problem.
  6. Automate fixed rules first. They are easier to test and explain.
  7. Add AI for a defined role. Give it approved information, limits and a human fallback.
  8. Measure the result. Watch both customer completion and the team’s manual work, then adjust.

Do not begin by asking, “Where can we add AI?” Begin by asking, “Where does information get lost, delayed or copied?”

So, Are Websites Becoming Obsolete?

No. Their old job description is.

Some customers will start with an AI answer, Maps or social media rather than your homepage. That makes the website less important as a compulsory first stop — and more important as the dependable layer underneath every route.

It is where you publish the facts, show the proof, collect the right information and move it into the systems your team uses. At the end of a long day, you should not receive another loose message to decipher. You should receive a usable record and a clear next action.

That is why a useful website is becoming more valuable, not less. The treasure is not the homepage alone. It is the business knowledge, trust and working connections behind it. AI can extend that system; it cannot replace the foundation.

Tell Vadym which task you want off your plate

If your website still turns every enquiry into admin, send Vadym the task you repeat most — qualifying leads, arranging appointments, taking deposits, sending reminders or keeping the CRM current. He will tell you what the website can sensibly handle, what should stay human, and whether the integration is worth maintaining. If it is not worth automating, he will say so.

Vadym works directly with small businesses in Melbourne and across Australia.

Frequently Asked Questions

No. AI is changing how people discover and compare businesses, and it may reduce clicks for some informational searches. But an assistant cannot replace the business’s own source of current facts, proof, policies and customer actions. Passive brochure sites are becoming less useful; websites connected to booking, payments, CRM and follow-up are becoming more valuable.

Yes, if you want a channel you control and a dependable route from attention to action. Social media and Google Business Profile are valuable for discovery, reviews, directions and conversation. Your website can do the deeper work: explain the service, show original proof, qualify an enquiry, record consent, accept a booking or payment, update your CRM and measure the result.

AI summaries can reduce clicks for some searches, especially when a short answer satisfies the question. That does not make every customer decision click-free. People still need to verify providers, inspect evidence and complete actions. The practical response is to publish information worth citing and make high-intent actions clear, rather than measuring success by page views alone.

They may use public web pages, search indexes, business listings, reviews, social platforms and connected data sources. A website is the public source the business can most directly maintain. Publish original information, answer real questions, show the author and update date, cite reliable sources and keep the page crawlable. These steps improve clarity and eligibility; they do not guarantee a ranking or citation.

A website can qualify and route leads, create CRM records, preserve attribution, offer relevant booking times, send confirmations and reminders, collect deposits, deliver onboarding information and trigger follow-up. AI can also summarise enquiries or answer routine questions from approved content. The right starting point is one frequent process with a clear rule and a measurable cost.

A website-to-CRM integration stops customer details and context being copied by hand. It can create a complete lead record, store the enquiry source, attach files and consent, assign the right owner, set a follow-up task and update reporting. The benefit is not the integration itself; it is a cleaner handoff and less lost information.

No. A chatbot is useful when customers ask repeat questions, the business maintains an approved knowledge source, and there is a clear handoff to a person. If a simpler form, booking flow or improved service page solves the problem more reliably, use that. Complexity should earn its place.

Not as a collection of secret hacks. Google says its generative search features still use core Search systems and normal SEO foundations, and it does not use llms.txt. Accurate structured data can support established search features, but it does not guarantee AI citations; Google also limits FAQ rich results mainly to authoritative government and health sites. Focus on useful original content, clear structure, accessibility and correct crawler access. See Google’s guidance on generative AI search and FAQ rich results.

Sources

Similar Posts