The build is thirty minutes. Everything else on this timeline is your own preparation and review, and that is where the whole difference in quality sits. The idea that AI deployment takes months comes from enterprise software projects that genuinely do — a purpose-built system for a small business is a different animal, and pretending otherwise sells consulting rather than results.
What actually happens on our side?
Thirty minutes, Monday to Friday, 08:00 to 16:30 SAST, South African public holidays excluded. You send the material, we train and test it, you review it, it goes live. Sign up outside that window and it lands at 08:30 the next business day. The one exception is a website build, which is a real build and runs two to thirty days depending on scope.
So the five days below are not a queue. They are a sequence for getting it right.
The five days
| Day | Who | What happens |
|---|---|---|
| 1 — Decide | You | Pick one job with a number attached. Write down what it currently costs you. This number is what you will judge everything against |
| 2 — Gather | You | Prices, hours, service areas, the 20 questions you actually get, what you do NOT do, your escalation rules, three replies you were happy with |
| 3 — Build | Us | Thirty minutes. Trained on your material, refusals configured, tested internally before you see it |
| 4 — Break it | You | An hour trying to make it fail. Off-topic questions, rude questions, price questions asked sideways, "are you a person" |
| 5 — Live, quietly | Both | Switch on without announcing it. Read every conversation for the first few days and correct what it got wrong |
Which day gets skipped, and what it costs
Day 2 and Day 4, always. Day 2 gets skipped because writing down your own prices and policies is dull, and the result is a bot that knows what your homepage says and nothing more. Day 4 gets skipped because the demo answers looked fine, and the result is discovering an invented answer from a customer rather than from your own testing.
Both are an hour or two. Both are the difference between a system you trust and one you quietly stop pointing people at.
What does "live" actually mean on day 5?
For a website chatbot, a single script line on your site — nothing installed, nothing to maintain, and it works the same on WordPress, Wix, Shopify or a hand-built page. If somebody else looks after your website, you can send them the line rather than giving anybody access.
Going live quietly matters more than it sounds. The first two days of real traffic produce the corrections that no amount of internal testing finds, and you would rather make those before the people whose opinion matters have seen it.
What happens after day 5?
- Week two: read the log. Every question it could not answer is either a gap in the material or something that should be on your website.
- Month one: compare against the number you wrote on day 1. That is the whole evaluation.
- Ongoing: update it the same day a price or a policy changes. A bot quoting last quarter's price is worse than no bot.
Why does this not take three months?
Because nothing here requires integrating with your ERP, migrating data, or changing how anybody works. A chatbot answering enquiries on your website touches nothing else in your business — which is precisely why it is the sensible first thing to automate, and why the long project plan you may have been quoted was for a different kind of work.
Nothing here is waiting on us. Every day on this list except day 3 is you deciding what your business says and then checking that the thing says it.
What does it cost to start?
A Website Chatbot is R299 a month plus a R250 once-off setup fee — R549 at checkout, cancellable at the end of any paid month. There is a free trial, so days 3 to 5 can happen before any money changes hands.