Step 1. Find where money leaks
Draw the path of a client from first contact to payment. Where do enquiries come from: phone, messengers, website, social media? Who answers each channel? Where do people wait, get lost or ask the same thing twice?
Usually two or three weak spots become obvious within an hour. Those are your candidates, not the tasks that are simply annoying.
Step 2. Describe the process as it is
Write down how things actually work today, not how they should work. Who receives an enquiry, what they reply, where they record it, who gets it next.
- Which questions clients ask most often.
- Which answers are always the same.
- Where a person makes a real decision and where they just copy data.
Automation copies a process. If the process is unclear on paper, it will stay unclear in software.
Step 3. Choose one automation with a fast effect
Do not start with a big CRM migration or a full rebuild. Choose one task that runs often, follows clear rules and directly affects revenue.
For businesses with a steady flow of enquiries this is usually first contact: answering calls and messages, booking clients and passing complex cases to people. The effect is easy to see, because every enquiry either got an answer or did not.
Other good first candidates:
- Moving requests from the website and messengers into one table or CRM.
- Booking reminders and confirmations.
- A daily summary of new requests for the manager in Telegram.
Step 4. Prepare the data
Automation is only as good as what it knows. Before launch, gather:
- Services and current prices.
- Answers to frequent questions.
- Working hours and booking rules.
- Who handles which cases, and how to reach them.
- Access to the calendar, CRM or tables the system will use.
If you have no CRM, that is not a blocker. Google Sheets is a perfectly good starting point, and you can move to a CRM later.
Step 5. Launch, measure, expand
Launch on real traffic and watch the first weeks closely. Read conversations, check where the system hands over to people and why, and fix the knowledge base.
Decide in advance what you will measure: the share of enquiries answered, the number of bookings, the time to reply. Compare with what you counted before launch. Only when the first automation works steadily, take the next one from your list.
Common mistakes
- Automating everything at once and drowning in edge cases.
- Choosing a tool before understanding the process.
- Launching without a clear path to a person.
- Not assigning anyone to keep the knowledge base current.
- Measuring nothing, then judging by feeling.
How we start with clients
We begin with a free AI audit: we look at where your enquiries come from and where they are lost, and suggest the first step with the fastest effect. Then we build a free personal demo on your own services, prices and language, and fix the scope and price in writing before launch. After launch, we either support the system with monitoring and monthly reports or hand it over with documentation.
We work across the full cycle, from client service to sales, marketing, CRM and internal processes, and build websites, apps and internal tools with AI inside. Our own site is an example: three languages, an AI manager, a CRM and requests delivered to Telegram.
What not to automate yet
Some tasks are better left to people, at least at the start: decisions about discounts and exceptions, complaints, sensitive conversations and anything that happens once a month. Automating rare or emotional tasks costs more than it saves. Keep them human and give the person a good brief instead.
Who owns it on your side
Even with full support from an agency, one person in your team should own the automation: approve answers, report changes in prices or services and read the monthly report. It takes little time, but without an owner even a good system slowly drifts away from the real business.
A good sign that you are ready: you can name the one process that costs you the most today, and the person who will own its automation.
How long does the first automation take?
It depends on scope and integrations. We fix the scope, the price and the plan in writing after the audit, before any work begins.
Do I need a developer on my team?
Not with support: we run the system for you. With a one-time handover, it helps to have someone technical, or a contractor, to maintain it.
We have no CRM. Can we still start?
Yes. Many businesses start with Google Sheets and Telegram, and add a CRM once the process is stable.