Back to blog

    How to choose a chatbot development company in Pakistan

    Page one for this search is three directories and a row of companies explaining why they are the best one. Here are the nine questions that actually separate them, written so they work on us too.

    Published: 12 September 202610 min read

    The short answer

    Ask one question early: what happens when the bot cannot answer? Everything you need to know about how a company builds is contained in how precisely they answer it. Vagueness there predicts vagueness everywhere.

    The rest of this page is eight more questions like it. They are the same ones we expect to be asked before somebody commissions custom chatbot development from us, and we have included the answers that should make you walk away, including when they are ours.

    Nine questions, and what each answer reveals

    Run these on every company on your shortlist. Ask them on a call rather than by email, because the hesitation before an answer is often more informative than the answer.

    1

    What happens when the bot cannot answer?

    This is the fastest filter there is. Every bot fails on something. What matters is what the customer sees in that moment.

    What you want to hear: A named handover: the conversation moves to a human inbox, the customer is told, and somebody is responsible for picking it up inside a stated window.

    What should worry you: “It won’t happen, our AI handles everything.” It will happen, usually in week one, and a bot that loops back to a menu loses you the enquiry.

    2

    What does Meta charge on top of your fee?

    WhatsApp fees are billed by Meta directly, per message delivered. A company that does not mention them either does not run WhatsApp builds or is hiding the number.

    What you want to hear: A category-by-category answer, and a note that rates change quarterly. Bonus points if they know Pakistan is priced in US dollars.

    What should worry you: “Unlimited messages included.” Nobody can include what Meta bills you for. The cost is being hidden, not removed.

    3

    Who updates it when my prices change?

    Products change, prices change, policies change. A bot nobody maintains starts giving wrong answers within a couple of months, and wrong answers are worse than no bot.

    What you want to hear: A named maintenance arrangement with a monthly fee attached. Somebody owns it after launch.

    What should worry you: A one-off build price with no mention of what happens afterwards. You are buying a snapshot, not a system.

    4

    Can I see it working before I pay the balance?

    Chatbots demo beautifully and break on real phrasing. You want to test it on your own awkward questions, in Urdu and English, before the money moves.

    What you want to hear: A staging number or test environment you can message yourself, with your own content loaded.

    What should worry you: A video walkthrough of somebody else’s bot, or a demo you are not allowed to type into.

    5

    Whose WhatsApp Business account is it?

    If the number and the Meta Business account sit under the agency’s name, you cannot leave without losing the asset and the conversation history.

    What you want to hear: The WABA and the phone number are registered to your business. The agency has access, not ownership.

    What should worry you: Vagueness, or “we manage all that for you.” Ask again, and get the answer in writing.

    6

    What does the bot connect to?

    A bot that only answers questions is a cheaper build than one that checks stock or books a slot. Confusing the two is how quotes go wrong in both directions.

    What you want to hear: Specific system names and a clear statement about which have ready connectors and which need custom work.

    What should worry you: “It integrates with everything.” A custom ERP with no API integrates with nothing without somebody writing that integration.

    7

    Does it handle Urdu, and how?

    Most Pakistani customers write Roman Urdu, mixed with English, with spelling nobody standardised. This is the single most common cause of a bot feeling stupid.

    What you want to hear: A direct answer about Roman Urdu specifically, ideally with a test you can run yourself.

    What should worry you: “Yes, it supports 100+ languages.” Language support in a model is not the same as handling how your customers actually type.

    8

    Can you show me a build you did that failed?

    Anybody can show you a success. A company that can describe a project that went wrong, and what they changed afterwards, has done enough work to have scars.

    What you want to hear: A specific story with a lesson attached, even an anonymised one.

    What should worry you: “All our clients are happy.” Nobody has a hundred percent record, and pretending otherwise tells you how they will handle your problem.

    9

    What would make you tell me not to buy this?

    The most useful answer in the whole conversation. A company that cannot name a scenario where you are the wrong customer will sell to anyone.

    What you want to hear: A real disqualifier: low volume, no written process, systems with no way in.

    What should worry you: A pause, then a reason why you are perfect for it.

    Spotting a reseller in developer’s clothes

    Plenty of companies in this market buy access to a chatbot platform, add a setup fee, and sell it as a custom build. That is a legitimate business, and it is not what you think you are buying when somebody says development. Five tells:

    1

    The proposal describes a dashboard rather than your business. If the features list could be pasted into any other client’s proposal unchanged, you are buying software access with a setup call attached.

    2

    Pricing is per-agent or per-contact rather than per-build. That is a platform’s pricing model showing through the agency’s invoice.

    3

    They cannot explain what happens to your data or where the conversation history lives.

    4

    Scoping takes ten minutes. Real scoping is uncomfortable, because somebody has to make you describe what a valid order actually looks like.

    5

    The word custom appears everywhere and nothing in the proposal is specific to you.

    None of this means the price is wrong. It means you should compare it against what platform access costs on its own, which is the comparison we set out in what a chatbot actually costs in Pakistan.

    What a real scoping conversation covers

    You can judge a company by how uncomfortable their scoping call is. A good one makes you do homework. It should get through most of this before anybody quotes:

    Your actual messages

    A fortnight of real chat history, read properly. Not a summary of what you think customers ask, because the two are never the same.

    The edge cases

    Refunds, complaints, the customer who wants a discount. The awkward conversations decide whether the bot helps or embarrasses you.

    Who is on the other end

    Named people, working hours, and what happens at 11pm on a Sunday. Handover design is most of the value in a build.

    What counts as done

    A written definition of success before the build starts. Otherwise the project ends when everyone gets tired rather than when it works.

    When the answer is don’t hire anyone yet

    We turn down projects for these reasons most months, and any company worth hiring will tell you the same thing rather than take the deposit.

    Under roughly a dozen enquiries a day. A person answering properly beats anything automated at that volume, and the build will not pay for itself.

    Nobody has written down how the process works. If three staff handle the same request three different ways, that has to be settled before a bot can be told what correct looks like.

    The real problem is that nobody follows up. Automating the first reply does not fix a pipeline where leads go cold on day three.

    You are between systems. If your store or CRM is being replaced in two months, build after the migration, not before.

    Where we sit, including the unflattering part

    We build custom chatbots and AI agents for Pakistani businesses on WhatsApp, Instagram and Messenger. Rs. 49,999 for a standard build, Rs. 9,999 a month to keep it running and current. Meta bills you for messages directly, at its own published rates, and we pass nothing on top of that.

    We are the wrong choice if you want to log into a dashboard and build flows yourself, because we do not sell that. We are also the wrong choice below about a dozen enquiries a day, and we will say so on the call rather than after the invoice. Our WhatsApp builds are the bulk of what we do, and the constraints we design around are Meta’s, not ours.

    Run the nine questions on us the same way you would on anyone else. Book a scoping call and bring your awkward ones. If the honest answer is that you should not be buying this yet, that is what you will get, and it costs you nothing to find out.

    Questions people ask before hiring

    How do I choose a chatbot development company in Pakistan?

    Judge them on the answers to a handful of specific questions rather than on the portfolio. The most revealing are what happens when the bot cannot answer, what Meta charges on top of their fee, who maintains it after launch, and whose WhatsApp Business account the number sits under. A company that answers those four precisely is doing real builds. A company that deflects on any of them is reselling platform access.

    How much does it cost to develop a chatbot in Pakistan?

    It depends on what you are buying: a self-serve subscription tool, a freelancer's one-off build, or a built and maintained service are three different products at three different prices. Ours is Rs. 49,999 once and Rs. 9,999 a month, with Meta's message fees billed to you separately by Meta. We have written up the full comparison, including the ranges for the other two routes.

    Which companies develop chatbots in Pakistan?

    Several, and the honest answer is that the directory listings you find on page one are not a ranking of quality. Clutch, GoodFirms and Upwork sort by review volume and profile completeness, not by whether the build survives contact with real customers. Use the questions above on any shortlist, including ours.

    Should I hire a freelancer or an agency for a chatbot?

    A freelancer is fine for something small and static that will not change. The risk is not the build quality, it is what happens three months later when your prices change or Meta changes a rule and the freelancer has moved on. If the bot is answering customers every day, somebody needs to own it continuously.

    What questions should I ask a chatbot developer before signing?

    Nine are worth asking, and they are laid out in full above. If you only have time for three: what happens when the bot cannot answer, who updates it when my prices change, and what would make you tell me not to buy this. The third one separates consultants from salespeople faster than anything else.

    How long does a chatbot build take in Pakistan?

    A standard single-channel build is a matter of weeks rather than months, and most of that time is not engineering. It is getting your content, prices and policies written down accurately, and agreeing what the bot should do when it is unsure. Projects that run long almost always run long on that, not on the technology.

    Do I own the chatbot after it is built?

    You should own the conversation design, the content and the data, and the WhatsApp Business account and number should be registered to your business rather than the agency's. What nobody sells outright is the messaging channel itself, because WhatsApp, Instagram and Messenger run on Meta's infrastructure with Meta's fees whoever you buy from.

    Is Botsify or a local agency better for a Pakistani business?

    They are different purchases. A platform gives you tools and expects you to build the conversation yourself; a development company designs and builds it for you and keeps it current. Neither is better in the abstract. The question is whether anyone on your team has the time and inclination to own a bot as an ongoing job.

    Read next

    Thinking about building one?

    Tell us the messages your team answers over and over. We will tell you which parts a chatbot should take, which parts it should not, and what it would cost \u2014 Rs. 49,999 to build, Rs. 9,999 a month to run.

    Live in 24 to 48 hours
    English and Urdu
    Fixed price before you commit