If you build websites, you already have the hard part covered. You have clients, they trust you with their online presence, and you're the person they call when something needs fixing. Adding a chatbot to that relationship takes two to three hours and turns a one-off project into a monthly payment.
The setup isn't the hard part. The tricky bit is structuring it so the client sees value on their own and you're not writing weekly "here's what the bot did" summaries.
Why clients pay for this
A static website waits for someone to fill in a contact form. A chatbot responds.
For a small business, the practical benefit is capture. Someone visits the site at 10pm with a question, the bot answers it, and the client has a lead in the morning instead of a missed inquiry. For a dentist, that might be "are you taking new patients?" For a restaurant, it's "do you have a table on Saturday?" For a real estate agent, it's someone asking about a specific listing.
Clients don't pay for chatbots because they understand AI. They pay because they're losing enquiries to competitors whose websites actually respond.
The mistake freelancers make is treating the bot as a one-time deliverable. You build it, hand it over, and stop charging. The better approach is to retain ownership of the dashboard and bill monthly for keeping it running and accurate.
What you're actually building
A chatbot on Octively has three parts: the bot itself, the embed on the client's site, and the portal where the client checks their results. The full setup takes under two hours for a typical client site.
Step 1: Create and configure the bot
You set up the bot in a dashboard. Give it a name, write a short description of the client's business, and add the information it should know: services, prices, hours, location, and the ten or fifteen questions customers ask most often.
No code involved. The bot works from what you give it. A few paragraphs about the business plus common Q&A pairs gets you to a working bot. You refine it over the first few weeks as you see what people actually ask.
Step 2: Add it to the site
Once the bot is configured, you get a one-line embed script. That script goes into the site's footer.
On WordPress, that's a footer code field in your theme settings or a free plugin like Insert Headers and Footers. On Webflow, it's Site Settings, Custom Code, Footer Code section. On Shopify, it goes into the theme's footer template. On Squarespace, there's an embed block. On plain HTML, paste it before the closing body tag.
The bot appears on the site immediately. No deployment pipeline, no caching to clear.
Step 3: Set up the client portal
The last step is creating a client account and inviting them to their own portal. They get a link, set a password, and from that point on they can see their full conversation history and lead list without contacting you.
This step saves more time than any other. Once the client has their own login, the "how's the bot doing?" question becomes one reply: "here's your portal link." After that, they check themselves.
Keeping the bot useful over time
Bots drift. A client updates their prices. They add a new service. They move location. Every couple of months, it's worth spending twenty minutes going through recent conversations to see what the bot handles well and where it's getting stuck or giving outdated answers.
That review is also the easiest thing to build into a retainer. You're not just charging for the tool to stay running. You're charging for someone to actually watch it and keep it accurate. Most small business owners can't do that themselves and don't want to learn.
How to price the service
Two structures work well.
The first is a setup fee plus a monthly retainer. You charge a one-time amount (₨15,000-₨25,000 or around $100-$200) to build and configure the bot, then a monthly fee for hosting, monitoring, and keeping it current. The monthly fee is where most of the money comes from over a year.
The second is a retainer only, with a higher monthly rate that folds in the setup work. This is easier to sell to a hesitant client because it sounds like a smaller commitment, even if the total cost over six months is similar.
Either way, your platform cost needs to stay well below what you charge. On a ₨2,500 plan, even a single client at ₨10,000 a month leaves solid margin.
What to actually charge
For a managed chatbot with a client portal, ₨10,000 to ₨20,000 a month is a realistic retainer in Pakistan. Internationally, $79 to $149 covers similar ground.
The client isn't paying for the bot alone. They're paying for someone who configured it correctly, keeps it accurate, and is reachable if something goes wrong. That's the service. The chatbot is what delivers it.
Five clients at ₨15,000 each is ₨75,000 a month from a service that takes maybe two to three hours total to maintain once it's running. That math is why freelancers who figure this out tend to keep doing it.
Finding the first client
The first one doesn't require any pitching. You probably have a client right now whose website has a contact form and nothing else. A bakery, a physio, a tutoring centre, a local estate agent. Someone whose business would genuinely benefit from answering questions at 2am.
Build it for them on the free plan. Show them the portal after a week. Charge a monthly fee once they've seen a few real conversations come through.
The second and third clients come from the first. Small business owners talk to each other. When a client mentions their website started generating enquiries overnight, someone nearby will ask who set it up.
Frequently Asked Questions
Try it on your next client project
Free plan — no credit card required.