Chatbot Development, Stage by Stage: How Long Each Step Takes and Where the Hours Really Go (Free Effort Estimator)
Chatbot development is usually planned as a coding job, then turns out to be a writing job. Most of the hours go into deciding what the bot should answer, writing those answers, checking them with the person who knows the facts, and testing them with real questions. This guide walks through the seven stages of building a website bot for a small business, what each stage produces, how long it typically takes on a hosted tool versus custom code, and the traps that stretch a two-week project into three months. A free estimator turns your own numbers into a stage-by-stage plan.
โก In short
- There are seven stages: discovery, content, flows, setup, connections, testing and tuning.
- On a hosted tool, writing and checking answers is usually the biggest single block of time.
- Coding your own adds the chat window, server, inbox, alerts, hosting and security, often hundreds of hours.
- Plan in hours per week you can really give it. The estimator below turns that into a calendar.

The shape of the work
Why the estimate is usually wrong
Ask a business owner how long it takes to build a bot and you’ll hear “a weekend” or “a few months”, depending on whether they picture a drag-and-drop tool or a developer writing code. Both answers miss the same thing: the part that takes longest is rarely the technology.
A website bot is useful only if it gives correct, specific answers to the questions your customers really ask. Collecting those questions, writing answers, getting prices and policies confirmed, and testing the result is work no tool can do for you. It’s also the work that tends to be squeezed into the last two days before launch, which is why so many bots go live answering “Sorry, I didn’t understand that”.
Thinking in stages helps. Each stage has a clear output you can check, so you know whether you’re on track. It also shows where a developer is genuinely needed and where they’d be paid to wait for your content.
The stages below apply whether you use a hosted product such as LiveChatBot, a different builder, or your own code. The hours change a lot between those routes; the order doesn’t.
The seven stages
What each one produces
A ranked list of the questions people ask, taken from real messages, plus the list of things the bot must never answer alone.
One checked answer per question: the fact, any condition, and the next step.
The greeting, menus and proactive messages, drawn on paper first, then built.
Widget installed, styled, opening hours and away form set, team invited.
Chats or tickets flowing to the places your team already works.
A pass through every answer and flow with real phrasing, on a phone.
A month of reading chats and fixing the gaps they reveal.
Stages 1 and 2
Discovery and content: the part that decides quality
Discovery means reading the last 50 to 100 customer messages and writing the reason behind each one. You’ll usually find five to eight reasons that cover most messages, and a long tail of rarer ones. Also list what the bot must hand to a person: complaints, refunds, custom quotes, anything medical, legal or financial. On a hosted tool this takes two to four hours. Developers building a custom bot often skip it and pay for that later.
Content is writing one answer per question. Each answer gives the fact, mentions any condition, and offers a next step: “We deliver across Pune in 2 days. Orders above โน999 ship free. Want to see delivery areas?” Budget about fifteen to twenty minutes per answer including a check by whoever owns the fact (the accountant for fees, the manager for timings). Thirty answers is roughly a day of focused work.
Add time if you serve customers in more than one language. LiveChatBot can detect the visitor’s language and translate welcome messages, but someone who speaks the language should still read the key answers once.
Write the answers as saved replies. In LiveChatBot the free keyword bot answers typed questions from saved replies, your team reuses the same wording by hand, and the AI Agent can learn from the same knowledge. One set of answers serves all three; see saved replies and training your AI chatbot.
Stages 3 and 4
Flows and setup: faster than you’d think
Flows are the greeting, button menus and proactive messages. Draw them on paper first: which buttons appear, what each leads to, where a person steps in. Once the plan is settled, building a simple flow takes under an hour in a visual builder. LiveChatBot’s Flows include templates and can target visitors by page, traffic source, country, device, browser language, number of visits, lead score or whether you already have their contact details, with up to six conditions. The flow guide shows each block.
Setup is installing the widget and choosing its settings: colour, position, team name and avatar, welcome text, opening hours and the away form that collects an email or phone number when nobody’s online. Installation is a copy-paste of one code snippet, or the WordPress plugin, Joomla extension, or React and Vue plugins. On Shopify, Wix and Squarespace you paste the code. Expect about an hour, including inviting your team and installing the Android app on their phones.
On a custom build these two stages are where the big numbers live. You’d be writing the chat window, a server to receive messages, storage, an inbox for your team, notifications, an admin screen for flows, and the logic that decides which message to show whom. That’s real software, and it needs ongoing maintenance.
Free tool
Estimate your chatbot development hours
Enter how many answers and flows you need, how many languages and which connections. The estimator splits the work into stages for a hosted tool and for custom code, and turns the hours into weeks.
Describe the bot you want to build. The estimator gives planning hours per stage for two routes: setting up a hosted tool, and coding your own.
Connections
Runs only in your browser; nothing is sent or saved. The hours are planning assumptions shown in the result, not measurements. Change the inputs to match your situation.
Stage 5
Connections: where a developer earns their fee
Many small businesses need no connections at all. The team answers in the inbox, offline messages become tickets, and that’s the whole system. Add connections only when someone is currently copying information by hand.
Common examples, from simplest to hardest:
- Sending leads or tickets to a sheet or email. With Zapier this is usually an afternoon, no code needed.
- Webhooks to your own system. LiveChatBot sends webhooks when a ticket is created or solved. A developer can catch these and update your records in a few hours.
- Passing logged-in customer names into chat. The JavaScript API (window.LiveChatBot with setVisitor) lets your site tell the chat who the visitor is. A small task for whoever maintains your site.
- A two-way link with a CRM or order system. Reading order status from your system and writing chat details back takes real development time on any platform. Ask for a fixed quote for this task alone.
The REST API covers other cases. LiveChatBot’s developer documentation isn’t public yet, so ask our team for it before you brief a developer. The integrations page lists what’s available.
Stage 6
Testing: the stage everyone shortens
Testing a bot means asking it questions the way customers do, not the way you wrote the answers. Customers misspell, mix languages, ask two things at once and leave out the key detail. “deliver koregaon park tmrw?” is a real question.
A practical test pass has four parts:
- Every answer, reworded. Ask each question in two different ways and check the right answer comes back.
- Every flow, on a phone. Tap through every button path on a real phone, not a desktop browser. Check labels don’t wrap and every path ends somewhere.
- The handover. Send a message that needs a person and check someone on your team actually gets the alert, on the Android app as well as the dashboard.
- Out of hours. Test the away form after closing time and check the message turns up for the next shift.
Budget two to four hours for a typical small-business bot, plus half an hour per flow. For a custom build, double it: you’re testing your own code as well as your content.
Write down the test questions. You’ll reuse the same list after every change to prices, policies or flows, and the second pass takes a fraction of the time.
Stage 7
Tuning: the first month decides whether it sticks
Launch is the start of the useful feedback, not the end of the project. For the first month, read every chat once a day, or every few days if volumes are low. You’re looking for three things.
Questions the bot couldn’t answer. Each one that comes up twice deserves a new saved reply. This is the fastest way the bot improves.
Answers that didn’t land. If people ask a follow-up straight after an answer, the answer probably left something out. Add the missing detail.
Places people gave up. A visitor who taps two buttons and leaves found the menu confusing. Simplify that branch.
Set aside about an hour a week for this during month one, then fifteen minutes a week after that. This tuning time is the most valuable part of the whole chatbot development effort, because it’s driven by real customers rather than guesses.
If you went the custom route, tuning also includes bug fixes, dependency updates and server maintenance. Those hours don’t stop after month one; plan for them every month for as long as the bot runs.
Common traps
What turns two weeks into three months
Code before content
Building the tool first and writing answers last. The bot launches empty and gets a bad first impression.
No fact owner
Nobody is responsible for confirming prices and policies, so answers wait for weeks or go live wrong.
Every feature at once
Ten flows, five languages and a CRM link in version one. Launch with the top reasons, add the rest monthly.
Desktop-only testing
Most visitors are on phones. A menu that looks fine on a laptop can be unusable on a small screen.
No tuning time
The bot launches and nobody reads the chats. Gaps stay open and visitors stop trusting it.
Custom without upkeep
A home-built bot with no budget for updates slowly breaks as browsers and libraries change.
Choosing the route
When custom code makes sense
For most small businesses, a hosted tool is the sensible choice. The chat window, inbox, alerts, apps and security are already built and maintained, and your hours go into the content that makes the bot useful. LiveChatBot’s free plan covers two websites and 100 visitors per website each month, with visitor packs (100 for โน99, 500 for โน299, 1,000 for โน499) that never expire, and no per-seat charges; see pricing.
Custom code makes sense in narrower cases: the bot is part of your own software product, it must run entirely on your own servers for a contractual reason, or it needs deep two-way access to internal systems that no hosted tool can reach. Even then, many teams start on a hosted tool to learn what customers ask before investing months of developer time.
If you’re unsure, our make-vs-buy guide goes deeper. Whichever route you pick, start chatbot development with Stage 1 this week: the question list is useful on any platform, and it’s the stage that most improves the final result.
Frequently asked questions
How long does chatbot development take for a small business?
On a hosted tool, a typical bot with 30 answers and a few flows takes roughly 20 to 30 hours spread over two to four weeks, most of it writing and checking answers. Coding your own usually takes many times longer.
What is the most time-consuming stage?
Writing and checking answers. Each needs the fact, any condition and a next step, confirmed by whoever owns that information.
Do I need a developer?
Not for a hosted tool’s basics. A developer helps with webhooks, passing logged-in customer details, or a two-way CRM or order-system link.
Can I launch with only a few answers?
Yes. Launch with answers for your top five to eight reasons and a clear route to a person, then add answers each week from real chats.
What happens after launch?
Tuning. Read chats for a month, add answers for repeated questions, fix answers that cause follow-ups and simplify menus where people give up.
Keep reading
Related guides
Chatbot Design Blueprint: Sketch Your Bot’s Menu Tree on Paper and Catch Problems Before You Build
Spend your hours on answers, not infrastructure
Set up the widget, inbox and flows in an hour and put the rest of your time into content. Start free on livechatbot.in.