In many companies, work lives in several places at once. Orders arrive by email, shifts are planned in Excel, reports are posted to messenger groups, and payroll is calculated by one person who knows all the formulas. While the business is small, this works. As the number of employees, branches or orders grows, the mistakes, delays and lost data begin.
This article explains how manual work is replaced with one system, where to start, and how such a project actually runs.
Signs it is time to automate
The most common ones:
- The same data is entered in two or more places, for example first in a spreadsheet and then in accounting software.
- Management gets accurate numbers only at the end of the month, when someone compiles a report by hand.
- Important decisions and tasks get lost among hundreds of messenger messages.
- Payroll or bonus calculations cause disputes because nobody can see how the numbers were reached.
- A process depends on one person, and when they are on leave, work stops.
If two or three of these sound familiar, manual work already costs more than it seems. Lost hours and errors do not show up in any report, but they repeat every month.
Which processes to automate first
Automating everything at once is a mistake. It is better to pick one or two processes that meet three conditions: they repeat daily, they take a lot of time, and they often produce errors. Usually these are:
| Process | How it works now | How it works in a system |
|---|
| Taking orders | email, calls, messengers | the order appears in the system instantly and notifies the right person |
| Manual data entry | an operator retypes data from a PDF or an email | the system reads the document and fills in the fields itself |
| Shifts and attendance | Excel, photos in a group chat | schedule and attendance in one place, on the phone |
| Payroll and bonuses | spreadsheet formulas, manual checks | automatic calculation from real data, transparent to every employee |
| Reports | compiled by hand at month end | numbers visible at any moment |
A key rule: automate what creates data first, then what uses it. If orders still come in through ten different channels, even a beautiful report will not be accurate.
Off-the-shelf CRM or a custom system?
Ready-made services work well for standard processes, such as a simple sales pipeline. The trouble starts when your process is not standard: payroll follows your own rules, data has to come from 1C, and staff have dozens of different roles. Then the company starts adapting to the software instead of the other way round. A custom system is built around how you actually work and connects to the tools you already use.
How a project runs
1. Audit
The first step is studying the processes. We talk not only to managers but to the people who work in the spreadsheets every day. The result is a plain description: what happens now, where time is lost, and what to automate first. Scope, timeline and cost are fixed in writing at this stage.
2. First working version
The first working version is ready in 3–5 weeks. It covers the one or two most important processes, not everything. We want staff using the system with real data as early as possible, because that is the only way to learn what is genuinely convenient.
3. Step-by-step rollout
The system then grows step by step: new modules, new roles, integrations. Each stage is checked and accepted separately. This keeps risk low: if something needs to change, we change one module, not the whole system. Projects like this often take several months on the market before the first result; a staged approach delivers value from the first month.
Real examples
A retail chain with 140 stores. At ProMobile, schedules, sales reports, payroll and stock levels lived in spreadsheets, and communication ran through calls and messenger groups. Today everything is in one app (iOS, Android and a web admin panel) used daily by more than 200 employees across 19 roles. Payroll is calculated automatically from sales, attendance and an efficiency score, and internal chat messages are delivered in under 1 second.
Freight. For CargoFlow, a Russian freight company, the system reads PDF orders arriving by email (with OCR, i.e. recognising text in a document), extracts the data, links drivers and vehicles, calculates the route and the drivers' pay automatically, and produces Excel reports. Dispatchers no longer enter orders by hand.
No double entry. The 1001 Manruq mobile app has an online shop and a QR bonus card, and thanks to the 1C integration nobody enters the same data twice.
Orders straight to Telegram. On the Mangal-Elit and Fasad.am websites, every order reaches Telegram instantly. It is the simplest form of automation, and a very effective one: no request gets lost in an inbox.
What changes after automation
- One source of truth. Everyone sees the same numbers, and arguments about "which spreadsheet is right" stop.
- Transparency. Employees see what their pay is made of; managers see what happens in every branch.
- Speed. An order is processed in minutes, not hours.
- Scale. Adding a store or an employee does not require a new spreadsheet and a new person to maintain it.
Price ranges in 2026
| Project type | Example | Timeline | Approximate cost |
|---|
| One process automated | orders from email or Telegram into a system, reports | 2–3 weeks | 500 000 – 1 200 000 ֏ |
| First working version of an internal system | CRM or ERP for one department | 3–5 weeks | 1 500 000 – 5 000 000 ֏ |
| Company-wide system | mobile app, roles, integrations | from 8 weeks | from 8 000 000 ֏ |
These figures are approximate. We give the exact price and deadline after a free estimate within 2–3 days, fix them in writing, and they do not change. You can pay once you have received the complete working system and confirmed that everything matches your requirements. Larger projects can also be split into stages, each accepted separately.
What drives the price
- Number of processes. Automating one process is far simpler than bringing the whole company into one system.
- Roles and permissions. More roles mean more screens, rules and checks.
- Integrations. 1C, email, Telegram, accounting: each connection is separate work.
- Mobile app. If staff need an iOS and Android app, the scope grows.
- Migrating old data. Depends on how many spreadsheets there are and what state they are in.
How we work
We sign an NDA before discussing details. Scope, timeline and cost are fixed in writing before work starts. You pay only after you have received the complete working system and confirmed that everything matches your requirements; on larger projects, by accepted stages. Design revisions are unlimited at the design stage. At handover you receive technical documentation listing the languages and versions used, and the source code belongs to you. We follow international development standards and provide a warranty and long-term support.
Frequently asked questions
How long does business automation take?
The first working version is ready in 3–5 weeks, then the system is rolled out in stages. The full timeline depends on how many processes are involved.
How much does a custom CRM or automation system cost?
Automating one process costs roughly 500 000 – 1 200 000 ֏, a first version of a system for one department 1 500 000 – 5 000 000 ֏, and a company-wide system from 8 000 000 ֏. The exact price is fixed in writing after a free estimate and does not change.
Can a new system work with 1C or the software we already use?
Yes. Integration is usually the core of automation, because it is what removes double entry.
Will our staff manage to learn the new system?
A good system is simpler than the spreadsheets it replaces. Each role sees only what it needs, and a staged rollout lets people learn gradually.
What happens to the data we already have in Excel?
It is migrated into the new system during rollout, so no history is lost.
Remember: you pay only when you have received the complete working system and made sure it meets your requirements. Describe your process via the contacts page or read more about business automation and custom software development.