01
A list of automations
Write down everything that runs by itself: forms, data transfers, robots. Next to each, name the person responsible.
Three steps with no cost and no us. Often that alone cuts the losses noticeably.
Write down everything that runs by itself: forms, data transfers, robots. Next to each, name the person responsible.
Once a week send a test enquiry through the website and check that it reached the CRM. Five minutes, and you will catch half of the breaks.
If not one enquiry arrives in a working day, check the form. The quiet may be a break.
Automations break quietly: they have no window that shows something has gone wrong. While nobody looks, a break lives for days, and the enquiries lost in that time do not come back.
You already run several automations: the website form, passing enquiries to the CRM, Bitrix24 robots. One of them breaks without a sound, or enquiries stop reaching it. It is noticed days later, from a client's complaint or a strangely empty report.
An automation works until it stops. When it stops there is no call, no email, no red light.
Press "Show how it works": six steps, one at a time.
| Automation | What is known |
|---|---|
| Website form to CRM | last enquiry 5 days ago |
| Export to 1C | nobody checked |
| Reminder robot | running, but unknown |
Found out when a client asked why nobody replied.
We change nothing in your processes. A short mark is added to each automation to say that it ran.
For each one we know in advance how often it should leave a mark.
| Automation | Last mark | Expected |
|---|---|---|
| Website form to CRM | today 09:12 | hourly |
| Reminder robot | yesterday 18:00 | daily |
| Export to 1C | 4 days ago | daily |
This is a plain rule, the same every time: a mark was expected daily, and there has been none for four days. No AI is needed here.
The rule works around the clock and never gets distracted.
Sometimes an automation is "alive" but enquiries no longer reach it. So we also compare how many enquiries arrive with your usual numbers.
Two days in a row of zero, when ten to fifteen is normal, is a reason for an alert.
| Day | Enquiries |
|---|---|
| Mon | 12 |
| Tue | 15 |
| Wed | 11 |
| Thu | 0 |
| Fri | 0 |
38 enquiries in three days, then zero two days in a row.
This is the only optional step. A technical error message becomes a couple of clear sentences: what broke and where to look.
It only explains. It cannot fix anything.
| What the system printed | Access error, key expired |
| What AI will say | The export to 1C failed because the access has expired. Sign in to the account again and renew the key. |
It goes to a specific employee you named in advance. A shared chat, where everyone assumes someone else will answer, is not needed for this. One break, one alert.
The system restarts nothing and fixes nothing by itself. A person decides what to do: fix it, call us, or mark it as expected.
One sheet: which automations ran without a failure, which broke and how long they were silent. The weak spot is visible at once.
If the same automation breaks every week, it is time to look into the cause.
| Automation | Failures | Silent for |
|---|---|---|
| Website form to CRM | 0 | none |
| Reminder robot | 1 | 2 h |
| Export to 1C | 1 | 4 days |
2 failures in the week. needs a cause Export to 1C
Example on made-up data: the companies, goods and prices are invented for the demo.
Put in your own numbers: this is your calculation.
Not a public offer. The exact price is set after the first call. More on pricing ›
No. The alert arrives by email or in your work messenger like any message. There is nothing to open.
Fixes are part of ongoing support. What to change and when is decided by your person, and we restart nothing without you.
Watching is part of ongoing support: from ₽20,000 a month, a reply within one business day, no 24/7 promises. The exact price depends on the number of automations and is fixed after a call.
A cheap bot answers questions, and that is all. We build AI into your work: the enquiry lands in your CRM by itself, gets an owner, and the result shows in your reports. Scope and price are fixed before we start, there is a 30-day warranty after launch, and we stay in touch.
You do. The data, the subscriptions, the accounts and the system itself are in your name. We host nothing and own nothing: we set everything up in your services, under your accounts, and leave. You pay for the subscriptions directly, with no mark-up from us. For the first 30 days after launch, fixes are free. After that, if anything needs fixing or extending, we come back when you ask and reply within one business day.
A client wrote through the website, email or a messenger — and nobody answered.
Every week someone spends half a day merging figures from five spreadsheets into one report.
You bought Bitrix24, but managers keep clients in a notebook and in their heads.
A client is waiting for a call, and the manager forgot or ran out of time.
Staff and clients ask the same things, and the same person always answers.
A commercial proposal is stitched together from three old files over half a day.
Invoices, acts and contracts are checked by eye, and mistakes still slip through.
You sent a proposal, the customer never replied, and it was forgotten.
Suppliers send quotes as PDFs, and a manager retypes them into a spreadsheet by hand.
A client asks for a price, and a manager writes to suppliers one by one and waits days for replies.
An accountant retypes every supplier invoice into 1C: it takes time, and typos creep in.
A deal was won but no invoice went out. An invoice is overdue and nobody noticed.
The review is 30 minutes and free. Within 2 working days you get one page: what to automate first and what it costs. If you don't need automation, we'll say so.
Designs and implements AI systems for companies' day-to-day operations. Author of "Thumbs Up Russia" (2023). Master's student at Siberian Federal University.