In short. Integrating two systems — say, a bot and a CRM or a website and a Google Sheet — costs 6 000–25 000 ₴, a bot with a CRM integration 5 000–20 000 ₴, an automation on n8n or Make 3 000–15 000 ₴. The main multiplier of price and timeline is the quality of the other system's API: with documentation the estimate is quick, without it the spread grows.
A manager copies requests from the chat into the CRM by hand, some get lost, the client does not know the order status, and the reports are put together in a spreadsheet in the evenings. An integration removes that manual work: data moves between the systems on its own. Below is what exactly can be automated, which formats our price list has, what the price depends on and what to prepare so the estimate is accurate.
What can be automated
- A request → a card in the CRM. A request from the bot or the website instantly creates a card with the right fields — no copying by hand.
- A status → to the client in the bot. A manager changes the status in the CRM, and the client gets a message in Telegram.
- An order → a row in a spreadsheet. If there is no CRM yet, a Google Sheet can play its role at the start — we integrate with it too.
- An event → a notification in Telegram. A new request, a payment, a cancellation — the manager knows straight away, not when they next open the CRM.
- A chain of actions. A request arrives → a card in the CRM → an email to the client → a task for a manager → a row in a spreadsheet. We build such a scenario on n8n or Make, or as a separate script.
Two typical examples
A bot or a website + a CRM. Managers copy requests into the CRM by hand. After the integration a request instantly creates a card with the right fields, statuses from the CRM go back to the client in the bot, and API failures do not lose data. The spec fixes separately how many systems are linked, which fields and statuses we sync and what to do with duplicates.
A bot or a website + a Google Sheet. Every request lands in the sheet in the right columns; if the sheet is unavailable, the data is sent later. If needed, it works the other way too: a status from the sheet goes back to the bot. The logic of the sheet itself — formulas, reports — is not our part unless the spec includes it.
Four formats and their ranges
| Format | Range | Timeline | When it fits |
|---|---|---|---|
| Integration of two systems | 6 000–25 000 ₴ | from 6 days | CRM ↔ bot, website ↔ spreadsheet, with error handling |
| Bot with a CRM or API integration | 5 000–20 000 ₴ | from 3 days | a new bot that writes to the CRM from day one |
| Process automation (n8n, Make, scripts) | 3 000–15 000 ₴ | from 1 day | a chain of steps between services |
| Telegram integration for an existing product | 6 000–25 000 ₴ | from 3 days | you already have a website, an app or a CRM |
The timeline is indicative: the clock starts once the prepayment and the materials are in — and for an integration the materials are the access details and the documentation. Paid plans of the systems are not included: if your CRM offers API access only on a paid plan, you pay for it. You can work out the range for your own setup in the calculator.
What the price depends on
- API quality. With documentation and a test account we estimate the work quickly and accurately. Without them the spread in price and timeline grows.
- The number of systems. Each external integration in a larger project adds +5 000–15 000 ₴: a CRM, 1C, Google, a payment provider, Nova Poshta.
- Data volume and direction. One way or both, how many fields and statuses we sync, what to do with duplicates.
- Error handling. If the CRM or the sheet is temporarily unavailable, data must not get lost: we store it and send it later. That is a separate part of the work, and we put it in the spec.
Which CRM will do: where to start the conversation
The first question is not the name of the system but its API: whether it exists, whether it is documented and on which plan it is available. KeyCRM, Bitrix24 or another CRM — the approach is the same. If there is no CRM yet, start with a Google Sheet: it is the simplest entry point, and moving to a CRM later is a separate stage with its own estimate.
What to prepare for an accurate estimate
- the list of systems and the direction of data: from where, to where, one way or both;
- the API documentation of each system and a test account, if there is one;
- a description of the data: which fields, which statuses, what counts as a duplicate, what to do on an error;
- a person on your side who knows how your systems are set up.
You hand over API keys or a technical user with the right permissions after the start — not in chat. Send a finished integration spec as a file: our team reads it, not the assistant. No spec? Describe the task in the brief, and we write it together.
How the work goes
Brief → a range and a timeline guideline → spec → a 50 % prepayment → development with demos → delivery. The demo of an integration is a live test: you create a request in the bot and see the card in the CRM. Projects from 20 000 ₴ are split into stages paid 40/30/30. After delivery — the source code, a guide and a 7-day warranty on fixes; failures of third-party services are not covered by it. More about the steps — in the article how we work, and about integrations in general — on the Integrations page.
FAQ: common questions about CRM integration
What if we do not have a CRM?
Start with a Google Sheet: at the start it can play the role of a CRM, and we integrate with it the same way. When a CRM appears, moving to it is a separate stage with its own estimate.
Who pays for the CRM plan with API access?
You do. Paid plans of the systems are not part of the integration price — just like subscriptions to automation services such as Make.
Will requests get lost if the CRM is down?
They should not: error handling is part of the work. If a system temporarily does not respond, the data is stored and sent later. Exactly how is fixed in the spec.
How long does an integration take?
Integrating two systems takes from 6 days after the start, an automation from 1 day. API quality affects the timeline most: with documentation and a test account the work goes faster.
The figures in this article come from our price list: they are filled in automatically and match the calculator. It will work out the range for your task in 30 seconds.