©Code byMilanParmar

The Chat Company: an AI chatbot SaaS handling 100K+ messages a day for 30+ businesses

The Chat Company lets a business add an AI chatbot to its website without building any AI itself. They enter their URL, pick the pages the bot should learn, style the chat window, and paste one script tag. When I took it over, it was a buggy AI-generated demo. I kept about 20%, rewrote the other 80%, and built the full product on that in nine weeks. It now serves 30+ businesses, handles 100K+ messages a day, and replies about 3x faster than typical chatbot platforms.

Category
AI
Industry
AI / SaaS
Type
AI chatbot SaaS
Year
2026

At a glance

Client
The Chat Company, an AI chatbot SaaS
The problem
The founder had a buggy, AI-generated demo. It showed the idea, but it couldn't serve real businesses: a chatbot that answers from their website, matches their brand, and installs anywhere.
What I built
Kept about 20% of the demo and rewrote the rest: a multi-tenant SaaS with a website crawler, RAG answer engine on OpenAI, a one-script widget, a live visual customizer, conversation analytics, and a support desk.
The result
30+ businesses use it, and it handles 100K+ messages a day. Replies are about 3x faster than typical chatbot platforms. Installs on WordPress, Shopify, or any HTML site with one script tag.
Timeline
9 weeks
Budget
$20,000

The problem: AI chatbots that don't know your business

A generic AI chatbot answers from what it learned on the internet, not from your pricing, your services, or your policies. Building one that answers from your own content usually means hiring AI engineers and running servers, which small and mid-sized businesses won't do.

The Chat Company needed to make that a quick self-serve setup: point it at a website, and get a chatbot that knows the business, looks like the brand, and installs anywhere.

Taking over an AI-generated demo: what I kept and what I rewrote

When I started, The Chat Company was a first version the founder and another developer had generated with AI tools as a demo. It showed the idea well enough to pitch, but it was buggy and wasn't built for real customers.

I reviewed all of it, kept about 20% (the general backend code that worked), and rewrote the other 80%. Then I built the rest of the product on that foundation. Nine weeks later it was a working SaaS, and it now serves 30+ businesses.

How a business sets up an AI chatbot for its website

The whole onboarding runs as a step-by-step flow that remembers where each business left off, so a slow crawl or a closed tab never means starting again.

  1. 01

    Enter the website URL

    The crawler maps every page on the domain.

  2. 02

    Pick the pages

    The business chooses what the bot should learn.

  3. 03

    The bot learns them

    Pages are scraped, split into chunks, and indexed for search.

  4. 04

    Style the chat window

    Pick one of 56 templates and adjust it live.

  5. 05

    Paste one script tag

    Works on WordPress, Shopify, or plain HTML.

RAG: making the chatbot answer from the website, not guesswork

RAG (retrieval-augmented generation) means the bot looks up the relevant parts of your content before it answers. Each page is split into chunks of about 500 characters that overlap slightly, so no sentence loses its meaning at the edges. For every question, the five most relevant chunks are pulled and given to the model as context.

Two safeguards matter in production. Every search is filtered by business, so one customer's content can never show up in another customer's chatbot. And if the lookup is slow or fails, the chat still answers instead of breaking.

  1. 01

    A visitor asks a question

  2. 02

    The five most relevant chunks of that business's content are found

  3. 03

    They're added to the prompt as context

  4. 04

    The model streams an answer grounded in the website

One script tag that works on any website

The chat widget is a single JavaScript file with its styles built in. It loads the business's settings, streams answers, and tracks sessions, without touching the rest of the site. That's why it installs the same way on WordPress, Shopify, or a hand-coded HTML page.

Businesses style it in a live customizer: 56 templates, plus controls for colours, fonts, message bubbles, the launcher button, position, and pop-up behaviour. Every change shows instantly in a preview next to the controls.

Chatbot analytics: seeing what visitors actually ask

The dashboard shows sessions, messages, unique users, token usage, and a replay of every conversation. For a business, that's a list of the questions its website doesn't answer well. For the product, token tracking and capped conversation length keep AI costs predictable.

The knowledge base view shows exactly which pages and chunks the bot has learned. The screenshot below is from Authentic Urban, the D2C store I also built.

Inside The Chat Company

  • Homepage

    The marketing site sells the chatbot as a pipeline tool, then drops into pricing, FAQ, and the live widget.

  • Dashboard

    The dashboard tracks messages, tokens, users, and individual chat sessions from one place.

  • Knowledge Base

    Scraped pages, company knowledge, and indexed chunks sit together so you can see what the chatbot actually knows.

1 / 3

Results

  • 30+

    businesses using it

  • 100K+

    messages handled every day

  • ~3x

    faster replies than typical chatbot platforms

  • 9 weeks

    from start to launch

Key decisions

  1. 01

    Filter every search by customer

    One business's content must never appear in another's chatbot. Filtering at the search layer makes that a hard guarantee, not a hope.

    Trade-off: Every lookup has to carry the customer's identity.

  2. 02

    Ship the widget as one self-contained file

    Installation had to be one step on any platform. A single file with its own styles doesn't depend on the host site's code.

    Trade-off: The widget carries its own styles, so it's a little larger.

  3. 03

    Cap conversation history and answer length

    Long conversations send more text to the model every turn. Capping them keeps each customer's AI bill predictable.

    Trade-off: Very old messages in a long chat are forgotten.

  4. 04

    Onboarding as a resumable step-by-step flow

    Crawling and indexing take time and can fail. Saving each step means a business always picks up where it left off.

FAQs

Can you fix an app that was built with AI tools?

Yes. AI tools are good at getting a demo working quickly, but the code usually isn't ready for real users. I review what's there, keep what works, and rewrite the rest. On The Chat Company that meant keeping about 20% and rewriting 80%, then building the full product on top.

What is a RAG chatbot?

A RAG (retrieval-augmented generation) chatbot looks up relevant parts of your own content before it answers, then gives that content to the AI model as context. The result is answers based on your website and documents rather than general internet knowledge, and far fewer made-up answers.

Can an AI chatbot be trained on my website?

Yes. Strictly, the model isn't retrained; your pages are crawled, split into chunks, and indexed so the chatbot can search them for every question. That's cheaper and faster than training a model, and updating the bot is as simple as re-crawling the pages.

How do you keep each customer's data separate in an AI SaaS?

Tag every stored chunk with the customer it belongs to, and filter every search by that tag. Do the same for sessions, messages, and settings, and check ownership on every protected operation. Isolation has to live in the data layer, not just the interface.

How do you keep AI chatbot costs under control?

Send the model less text. Retrieve only the few most relevant chunks, cap how much conversation history goes into each request, limit answer length, and use a smaller model where it's good enough. Tracking tokens per customer shows where costs actually come from.