By Saurav · saavos
[!TLDR] A chatbot for small business costs $0–$49/month on a managed platform, takes 20–60 minutes to set up, and pays for itself by deflecting 15–40 repeat support questions a month. The ROI is real but narrow: it works if you train it on factual pages (pricing, FAQ, shipping policy) and leave it alone for 30 days. It fails if you train it on blog posts, skip the fallback message, or expect it to generate leads before it's handling support. For most small businesses in 2026, "buy a $25/month tool" beats "build your own" by roughly 30 months of subscription cost.
What is a chatbot for small business?
A small-business chatbot is a widget on your site that answers visitor questions automatically, without you needing to be online. In 2026, nearly all of them use retrieval-augmented generation (RAG): you give the bot a URL or a PDF, it reads your content, and it draws answers from that content in real time. No scripted decision trees. No manually typed Q&A pairs.
The practical shape of it: a visitor lands on your pricing page at 11pm on a Sunday, types "do you ship to Canada?" and gets an accurate answer in 2 seconds, pulled from your shipping policy. Without the chatbot, that visitor either bounces or sends you an email you won't see until Monday morning.
That's the core job. Not magic. Not "AI that sells for you while you sleep." A fast, accurate answer to a question you've already answered somewhere on your site.
Who actually needs one?
Not every small business does. Here's a quick diagnostic.
You probably benefit if:
- You get 5 or more repeat support questions a week (the same handful of questions, over and over)
- Your site gets enough traffic that visitors arrive when you're not at the desk
- Your support questions are factual and answerable from your existing content
You probably don't need one yet if:
- Your support volume is under 10 questions a month (a FAQ page does the same job for free)
- Your product is complex enough that most questions require a conversation with you specifically
- You're pre-launch and don't know what your visitors actually ask
The sweet spot is a small business or indie SaaS doing 300+ monthly visitors, with a consistent set of inbound questions about pricing, policies, or product features. At that volume, a $25/month chatbot earns its keep.
How much does a chatbot for small business cost?
The 2026 market breaks into three tiers. Real numbers, not ranges padded for SEO.
Preview ($0/month) Most major platforms offer a forever-free plan. Typical limits: 1 bot, 50–100 conversations per month, smaller AI models (Claude Haiku, GPT-4o-mini). Good for testing whether a chatbot is even worth pursuing for your business. Not enough for a site with real traffic.
saavos's no-card preview: 1 bot, 3 source documents, dashboard preview. Uses Claude Haiku. No credit card required.
Starter tier ($19–$29/month) This is where most small businesses land. At this price point you get 1,000–2,000 conversations per month, access to better models (Claude Sonnet, GPT-4o), and 5–25 source documents. For a small business getting 500–2,000 monthly visitors, this covers the full conversation volume.
saavos Solo: $9/month, 1 bot, 10 sources, 1,000 messages, Claude Sonnet.
Pro tier ($49–$99/month) Relevant when you're running multiple sites, have more than 25 source documents, or are approaching 3,000+ monthly conversations. The price jump from Starter to Pro is often about the number of bots or sources, not message volume. Most single-site small businesses never hit this tier.
What to avoid: Per-resolution pricing (Intercom charges $0.99 per resolved conversation — on a 500-visitor site that adds up fast). Overage fees above the message quota that charge 2–3x the per-message rate without warning. Both are landmines if your traffic spikes.
For a full breakdown of what different platforms charge and what the fine print actually says, see AI chatbot pricing comparison for 2026.
What does a chatbot actually do for your business?
Three jobs. In order of how reliably they pay off.
1. Deflect repeat support questions. Roughly 40–70% of small business support questions are repeats: "what are your hours," "do you offer refunds," "how long does shipping take," "what's included in the Builder plan." A well-trained chatbot answers all of these without you touching the inbox. Reducing customer support tickets with an AI chatbot goes deep on the measurement side if you want to track it.
2. Catch visitors who bounce before contacting you. A visitor who can't find your return policy or shipping cost in 20 seconds usually leaves. They don't email you; they're just gone. A chatbot that answers instantly salvages a portion of that traffic. The conversion math here is harder to measure but the behavior is consistent: faster answers keep people on-site longer.
3. Handle after-hours coverage. You're not online at midnight. Your chatbot is. For a coffee-shop owner whose website takes catering inquiries, or a Shopify store running international orders, the time-zone gap alone justifies the monthly cost.
What a chatbot does NOT do reliably:
- Complex bookings or multi-step scheduling (use Calendly or a form)
- Payment collection (use Stripe Payment Links)
- Emotional customer complaints (route to a human immediately)
- Sales conversations that require nuance or negotiation
For the first 90 days, keep your chatbot in lane: factual answers, fast. Everything else is scope creep that will make the bot worse, not better.
How to choose the best chatbot for your small business
There's no single "best." The right tool depends on your platform, your budget, and your support volume. Here's how to think through it.
For Shopify stores: You want a chatbot that can ingest your product catalog or FAQs without manual copy-paste. saavos works via URL crawl; Tidio has a native Shopify integration with live chat layered on top. If you want live chat plus AI in one tool, Tidio wins. If you want pure AI with lower cost, saavos or Chatbase. See the Shopify chatbot setup guide for 2026 for a step-by-step walk.
For Webflow sites: Any tool that deploys via a script tag works fine with Webflow. The main thing to watch is widget z-index conflicts with Webflow's sticky nav. saavos's embed script handles this automatically; some cheaper tools don't. Full setup walkthrough: how to embed a chatbot on Webflow without code.
For general small business sites (WordPress, Squarespace, custom HTML): The script tag method works across all of them. Five minutes of setup.
For SaaS founders: The priorities shift slightly -- you care more about in-app deployment and integration with your help docs than basic FAQ coverage. Best AI chatbot for SaaS in 2026 covers that case in detail.
What to look for in any platform:
- Transparent message quotas (not "unlimited" in the headline and asterisked in the terms)
- Conversation logs you can actually read (not just aggregate stats)
- A real fallback message when the bot doesn't know something
- No per-resolution billing unless your volume is very predictable
The full vendor-pressure checklist is in 12 questions to ask AI chatbot vendors before you sign.
How to set up a chatbot for your small business website
The five-step version, platform-agnostic.
Step 1: Pick your training sources. Not your whole website. Your pricing page, your FAQ, your shipping or returns policy, your product spec pages. Three to five tightly-scoped documents outperform a 50-page crawl of everything. The wider the training set, the more likely the bot pulls from off-topic or outdated content.
Step 2: Create an account and paste your URL. Every major platform supports URL ingestion. Paste your pricing page. Paste your FAQ. Let it process -- usually 2–5 minutes. Confirm the ingestion worked by asking the bot a question you know the answer to.
Step 3: Write a fallback message. This is the most skipped step. Every chatbot needs to know what to say when it can't answer. Good fallback: "I'm not sure about that one -- email us at [support@yourbusiness.com] and we'll reply within one business day." A visible dead-end beats a hallucinated answer every time.
Step 4: Embed on your site.
Copy the script tag, paste it before the closing </body> tag in your site's HTML. On Webflow, that's in Project Settings → Custom Code. On Shopify, it's in the theme's theme.liquid file. Takes 3 minutes.
Step 5: Test on a real phone before you declare it live. Open your site on an actual mobile device. Check the launcher button position -- does it overlap your cookie banner? Your sticky footer? Your "add to cart" button? This is where half the chatbot launches quietly fail.
After setup, block 30 minutes at the end of week 1 to read every conversation the bot had. You'll immediately see which questions it missed, which answers were too long, and which visitor questions you didn't anticipate. Fix those. Don't wait for month 3.
The ROI math: a worked example
A local gym has a website that fields 600 monthly visitors. About 3% contact the owner directly -- that's 18 support questions a month. The questions: opening hours, membership pricing, trial class booking, parking, and whether they allow drop-ins. All five are on the website, but visitors either can't find them or can't be bothered.
Handling each question takes 4 minutes. That's 72 minutes a month in inbox time.
A $19/month chatbot deflecting 65% of those questions saves 47 minutes a month. At $50/hour labor value, that's $39 in time recovered. The chatbot costs $19. The first month it pays for itself, and every month after that is upside.
The math is more compelling for a SaaS founder at $150/hour. Same volume, 47 minutes saved = $117/month in time. A $19 tool with $98 in net monthly value.
A detailed version of this math, including the break-even table and what changes at different traffic volumes, is in AI chatbot for small business: the ROI guide.
Common mistakes that kill results in the first 30 days
Training on blog posts instead of factual pages. Your "10 tips for better sleep" blog post is terrible retrieval material. Your "Shipping policy" page is perfect. Train narrow, on factual sources. This is the single biggest predictor of chatbot quality.
Skipping the fallback. A bot without a fallback will hallucinate. It will confidently say things that are not in its training set. Always configure the "I don't know" response.
No human exit path. When the bot can't help, the visitor needs somewhere to go. A visible email address or a link to a contact form. Make it obvious, not buried.
Deploying without a mobile check. Most small business site traffic is mobile. Test it on your phone. Then test it on your phone again.
Treating it as "set and forget." The bot in week 8 should be better than the bot in week 1. That only happens if you read the conversation logs. Read them. They're more interesting than you expect.
Try it
If you want to see whether a chatbot makes sense for your site before committing, the no-card preview is the right starting point. Paste one page, ask it 10 questions, check whether it gets them right. That 10-minute test tells you more than any comparison article.
Preview saavos. No credit card required. Or if you want to see how the pricing stacks up against Chatbase, Tidio, and Intercom before deciding, the AI chatbot pricing comparison has the current numbers.