Every Client Wants an AI Chatbot Now. What That Means for Freelancers.

There is a pattern every freelance developer recognizes: clients arrive with a request that is less about solving a problem and more about matching a perceived norm. For years, that request was the carousel. Now it is the AI chatbot.

The shift is documented in the author's own client work. The carousel was never really about content strategy — it was a signal. Clients wanted to look current. The chatbot request operates the same way. Most clients cannot articulate what the bot should do, what data it should have access to, or how success gets measured. They know competitors have one.

For engineers and technical founders, this creates a specific kind of friction. Carousels were expensive in UX terms but cheap to deliver. A React component, a content array, done. Chatbots carry real cost: LLM API spend, retrieval infrastructure if you want grounded responses, ongoing prompt maintenance, and edge-case handling that never fully resolves.

The analogy breaks in one important way. A broken carousel degrades the experience. A broken or poorly-scoped chatbot actively misleads users and can expose the client to reputational or legal risk. The stakes of the default request got materially higher.

The practical implication is that scoping discipline matters more than it used to. Delivering a chatbot that wraps a general-purpose LLM with no grounding is technically easy and strategically indefensible. The better deliverable is a narrow, well-scoped tool — FAQ retrieval over a defined knowledge base, support triage with explicit fallback — where the boundaries are part of the design.

The pattern will repeat. At some point another default request replaces chatbots. The skill is recognizing when a client request is a signal about perception rather than a specification for a solution, and pricing and scoping accordingly.

Source