Why are most "chatbot vs staff" comparisons misleading?
Many agency pages show a big headline saving, comparing a bot's monthly fee with a full salary. That comparison assumes the bot does everything the person did. It rarely does. Bots handle repetitive, rule-based work well; people handle judgement, empathy, exceptions and selling. The honest question isn't "bot or person?" but "which parts of this job should a bot do so our people can do the rest better?"
What does an extra hire really cost?
List the full cost, not just salary:
- Salary and statutory contributions
- Recruitment time and any agency fees
- Training and ramp-up time
- Equipment, software seats and office space
- Supervision and management time
- Cover for leave and attrition
Use your own figures; they vary widely by city, role and seniority.
What does automation really cost?
- One-time build (see our cost guide)
- Monthly running costs: WhatsApp messaging, AI usage, hosting and platform fees
- Maintenance: updating FAQs, templates and prompts
- Staff time reviewing drafts and handling escalations, which is real and should be counted
Which tasks suit automation, and which suit people?
| Usually automate | Usually keep with people |
|---|---|
| Answering repeat questions from approved content | Complaints and emotional conversations |
| Order and appointment status | Refunds, discounts and exceptions |
| Capturing lead details into a CRM | Negotiation and closing |
| Reminders and follow-ups | Medical, legal or financial advice |
| Tagging and routing tickets | Decisions with no clear rule |
How do you run the comparison with your own numbers?
- Count how many messages or tasks of each type arrive per week.
- Estimate minutes per task and which share is truly repetitive.
- Put those numbers into our time-saved calculator to see hours per month.
- Compare that with what a hire would cost you in full, and what automation would cost to build and run.
- Remember the third option: automate the repetitive share and keep or hire people for the judgement work.
What happens to customer experience?
A bot that answers instantly at 11 pm is good service; a bot that loops and refuses to hand over is bad service. Design matters more than the choice. Every agent we build has a stop rule and a fast path to a person.
How do we apply this in client work?
Everything on this page feeds into how we run pilots. We start with a consultation to understand the process and the people involved, then write a one-page scope: the trigger, inputs, steps, outputs, a success measure and a stop rule that says what the agent may do alone, what needs approval and when it must hand over. We build inside the tools you already use, test on real or realistic cases including awkward ones, and review the results with your team before anyone talks about expanding.
We keep a few habits on every project: we never publish invented results, we label examples as illustrations, we list third-party costs separately, and we say so plainly when something isn't worth automating yet. If that sounds like the kind of partner you want, read the pilot process or message us on WhatsApp.
What should you prepare before talking to us?
You don't need a technical brief. A useful first conversation needs only a few things, and gathering them is valuable even if you never work with us:
- The process in plain words: what triggers it, who does what, and where it usually goes wrong.
- Rough volumes: how many messages, orders, tickets or invoices per week. A one-week tally is enough.
- Your tools: WhatsApp app or API, CRM, sheets, accounting or helpdesk software, including versions or plans where you know them.
- Three real examples: typical messages or cases, plus one awkward one, with personal details removed.
- What must never happen: the mistakes that would hurt most. These become the first lines of your stop rule.
- An owner: the person who will review the workflow once it runs.
Send these on WhatsApp or by email, or run the pilot scorecard first.
How does a pilot with us work?
Every engagement follows the same four steps. Consult: you walk us through the process, the tools and where it breaks. Pick the pilot: we choose one workflow and write down its inputs, outputs, tools, stop rule and success measure. Ship: we build it into the tools you already use and test it on real cases. Review: your team checks what the agent did and what it escalated, then decides whether to tune it, expand it or stop. Read the full pilot process.