Does your website actually need AI? A plain answer for businesses being pitched one

If you run a business with a website, someone has recently tried to sell you AI for it — a chatbot, an "agent," an assistant that will supposedly answer customers while you sleep. The pitch is rarely dishonest, but it's rarely specific either. So here is the specific version, from a studio that builds AI-assisted features when they're warranted and refuses them when they're not.

Start with the distinction the sales deck skips. A true agent takes actions on your behalf — books a slot, updates a record, sends a follow-up — without a human confirming every step. An assistant helps a visitor find what they need faster: smarter search across a catalogue, a booking flow that asks fewer redundant questions, an internal tool that summarises a spreadsheet instead of someone reading it line by line. Most businesses being pitched an "agent" would be better served by the assistant — or by neither.

The neither case matters more than vendors admit. A board-election portal doesn't need a chatbot; it needs a voting flow so unambiguous that no member ever has a question to ask. A bakery's e-commerce site doesn't need a conversational agent; it needs commissions and payments to just work. In both of those real projects, the honest AI recommendation was zero — and the budget went to the things visitors actually touch.

Where AI features genuinely earn their place is narrower and more useful than the marketing suggests: search that understands "the navy dress from the spring lookbook" instead of demanding exact keywords, a booking assistant that reads a real calendar and proposes real slots instead of a static form, an admin dashboard that turns a week of member-renewal data into three sentences someone can act on. Notice the pattern — each one removes a specific, nameable friction. None of them is "AI" for its own sake.

There's also a cost the pitch leaves out: an AI feature is a running system, not a one-time install. It needs monitoring, its answers need reviewing, and when it gets something wrong it does so in your brand's voice, to your customer. If a vendor can't tell you who checks its output and what happens when it's wrong, the feature isn't finished — it's just deployed.

The test we apply before anything AI-labelled ships on a client project: would a visitor or a staff member actually notice it saved them time this week? If yes, it earns its maintenance cost. If the honest answer is "it makes the site sound current," it doesn't ship — because six months from now, nothing dates a site faster than an abandoned chatbot nobody trained.

So, does your website need AI? If you can name the friction it removes, possibly — and it's worth a scoping conversation. If you can't name it yet, spend the money on speed, clarity, and content first. Those convert visitors every single day, no model required.