How does the scorecard work?
Each question reflects one of the criteria we use when picking first pilots with clients: frequency (how often it happens), rules (how teachable it is), risk (what a mistake costs), input (how structured the data is), systems (how many tools are involved), measurability, ownership and agreement on how the process should work. Each answer scores 0 to 3, and the total is shown out of 100.
The score is a rule of thumb, not a verdict. A low score doesn't mean "never automate". It usually means "not as a first pilot" or "fix the process first".
What do the results mean?
- 75 and above: strong first-pilot candidate. Repetitive, rule-based and low-risk. Write a one-page scope with a stop rule and pilot it.
- 50 to 74: promising, with caveats. Reduce the scope, for example automate drafting or routing only, with people approving.
- Below 50: not a first pilot yet. Document or simplify the process first, or pick a more repetitive, lower-risk workflow.
The result lists your weak spots, the questions where you scored lowest, so you know what to fix.
Why do risk and agreement matter so much?
Automation amplifies whatever process it's given. If people disagree on how something should work, an agent will apply that confusion faster. If mistakes are costly, the automation needs approval steps that reduce the time saved. That's why we score both explicitly. Read what AI agents can't do.
What should you do after scoring?
- Score two or three candidate processes and compare.
- Estimate the time involved with the time-saved calculator.
- Read how to choose your first pilot and draft a one-page scope.
- Send us your result on WhatsApp for a second opinion. The result screen has a button that pre-fills the message.
Which processes do people usually score?
Common candidates include WhatsApp enquiry handling, lead entry into a CRM, order status replies, appointment reminders, invoice and payment reminders, ticket triage, vendor invoice processing and weekly reporting. Score the two or three that annoy your team most. The comparison is often more useful than any single score.
Example: how two processes compare
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.