Why does the first pilot matter so much?
Your first automation sets your team's opinion of AI for the next year. If it's useful and trustworthy, people ask for the next one. If it's flaky or embarrassing, everyone quietly goes back to spreadsheets. So the first pilot should be chosen for likelihood of success, not for how impressive it sounds.
What makes a good first pilot?
Score each candidate against five criteria (or use our interactive pilot scorecard):
- Repetitive. It happens many times a week, so the time saved adds up.
- Rule-based. Most cases follow a pattern a new employee could learn in a day.
- Low-risk. Mistakes can be caught before a customer is harmed, or are easy to reverse.
- Measurable. You can count something before and after: response time, hours spent, leads followed up.
- Owned. One named person on your team cares about it and will review the output.
Which workflows usually make good first pilots?
- Capturing WhatsApp or website enquiries into a CRM or sheet with a follow-up task
- Answering order or appointment status questions from a live system
- Invoice and payment reminders with an approval step for exceptions
- Tagging and routing incoming support tickets
- Drafting replies to common questions from approved help content
Which workflows make poor first pilots?
- High-stakes decisions with no clear rules: credit, medical advice, legal positions
- Processes that happen a few times a month
- Processes nobody agrees on yet; automate a broken process and you get broken results faster
- Anything requiring five or more integrations before it does anything useful
How do you write a one-page pilot scope?
- Trigger: what starts the workflow (for example, a new WhatsApp message).
- Inputs: what data the workflow uses.
- Steps: what the automation does, in order.
- Outputs: what is created or sent.
- Stop rule: alone / with approval / hard stops / handover. See our template.
- Success measure: what you'll check after a few weeks.
- Owner: who reviews it.
What happens after the pilot?
You decide based on evidence: keep it as is, tune it, expand it to a second workflow, or stop. Stopping is a legitimate outcome, because a small scoped pilot that teaches you something is far cheaper than a big rollout that fails. Read our full pilot process.
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.