Start with the process that hurts the most: the one eating your team's hours or drawing the most customer complaints, not the most complex or most visible one. That process already carries internal pressure, so the team pushes for the change instead of resisting it.
In short:
- Pick the process with the most friction, not the most visible one.
- Split it: the repetitive half gets automated, the rest stays with your team.
- Two paths: an existing product live in days, or a custom build of four to twelve weeks.
- Before the call, settle invoicing, language, and how much contact runs through WhatsApp.
Three things to settle before you pick a process
- Invoicing.Invoicing here runs on CFDI 4.0, in force since January 2022, and the tax authority publishes a free service to issue version 4.0 invoices. Read Mexico's e-invoice rules for foreign-run companiesbefore you decide where it lands.
- Language.Our 30-minute call is in Spanish, with a person. Pick who joins from your side: the one who runs the process day to day.
- WhatsApp.Check how much of your customer contact already runs through WhatsApp, and bring that count to the call.
How to spot the process that hurts most
This is the question we hear most on the first call, with several processes competing at once. Judge it by three signs, not by how complicated it looks.
| Signal | What to look at | What to count |
|---|---|---|
| Friction | The task your team puts off | Hours a week it takes |
| Customer complaints | What repeats in support, sales and collections | Complaints last month that point at it |
| Frequency | How often the task runs | Times per week |
Asking beats guessing. Put four questions to the people doing the work:
- Which task eats the most hours in a normal week?
- Which questions come in over and over on WhatsApp or by phone?
- What gets typed into one system and then retyped into another?
- Which reminders and recurring reports still go out by hand?
When more than one person names the same task unprompted, start there.
Then split that process before anyone builds anything. The half that repeats the same way every time gets automated: frequent questions, a standard order flow, an invoice from data already captured. The half that needs a decision stays with your team: a case outside the pattern, an exception, a discount.
Ready-made product or custom build: how big the first project should be
Path A turns on a product that already exists, in days. Path B is a custom build for that one process, four to twelve weeks as a range, not a promised date. One well-defined process, finished and measured, gives you more than a project that takes a year.
Path A fits when your process looks like something already solved; keep path B for what is genuinely different. We compare cost, data control and timelines in custom software or SaaS: how to decide.
What to measure in the first weeks
- Compare how long the process took before and how long it takes now.
- Count the manual corrections your team had to make.
- Ask the team whether they felt the change, not just the numbers.
We break this down for automatic collections for small businesses in Mexicoand taking restaurant orders on WhatsApp, step by step.
Who to involve on your side
- The person who runs the process day to day: ask them for the exceptions.
- Whoever can approve the change without a second meeting.
The next step is a free 30-minute call, in Spanish and with real people, not a bot. It does not end with a fixed quote: it ends with a map of what an existing product already solves, what would have to be built, and what is not worth touching yet.
Frequently asked questions
Will the 30-minute call be in English?
No. The call runs 30 minutes, at no cost and with no commitment, in Spanish and with a person, not a bot. If your side does not work in Spanish, bring someone who does.
Does invoicing have to be in the first project?
Only if that is where the friction is. Invoicing in Mexico runs on CFDI 4.0, so settle early whether it belongs in the first project or the second. If the complaints come from somewhere else, start there.
How do I know the first project is done?
When it has been measured, not just delivered. Before you commit to the second process, check how long the first one takes now and how many manual corrections your team made. That tells you whether the next pick is a different process or the same one, scoped tighter.
Already know which process hurts the most? See how a custom software project starts with that process instead of everything at once.
Want your customers to get an answer even when nobody is at the phone? See how WhatsApp automation for your business works: what it includes, what it costs and how long it takes.
