What integrations we build
An integration connects your site to the services you already use so data flows automatically. Most commonly we set up:
- CRM. Kommo, HubSpot, and others - form submissions go directly into the pipeline.
- Payments. On-site payment processing, status handling, receipts.
- Forms. Lead forms, multi-step forms, delivery to CRM, email, and messengers.
- Analytics. Web analytics, goals and events, multi-touch attribution.
- Chats and messengers. Live chat widgets, Telegram and WhatsApp widgets.
- Webhooks and API. Custom data exchange with any service that has an API.
An enquiry must arrive even when a service is down
The most galling failure is a form that works while the enquiry never lands: the CRM had an outage, a token expired, the recipient address changed. The visitor sees "thank you", the salesperson sees nothing, and you find out a week later.
So we do not send an enquiry to a single service and call the job done. The enquiry is stored on the site's side or duplicated to a second channel, a failed delivery is retried rather than lost, and errors are visible instead of being swallowed. That is a few extra hours of work, repaid by the first enquiry that is not lost.
What to send along with the enquiry
An enquiry with just a phone number is half the value. It is worth sending the source and campaign parameters with it, the page the person came from, and the form answers as separate fields rather than one line in a note.
Then the CRM shows not merely "a lead arrived" but where from and with what request - and you can measure cost per customer rather than cost per lead. To connect this with deals and reporting, that is integration work on the CRM side.
How we work
We start by clarifying which services need to be connected and what the data flow should look like - which fields, at what point, going where. Then we connect the service, configure field mapping and error handling, and test against real scenarios. The quote is fixed after a brief: connecting a standard service is scoped quickly, a custom API integration is treated as a separate task.
Any CRM, not just the popular ones
We work directly with Kommo and HubSpot, and connect other CRMs through their APIs or webhooks. If your service has an open API, we can almost certainly integrate it. If you are selecting and implementing a CRM from scratch, see our CRM implementation service - we can set up the system and then connect it to your site.
Related services
Does the integration require development work on the site - new forms, pages, or logic? That is custom development. Need a full CRM implementation rather than just connecting it to the site? See CRM implementation.
FAQ
What integrations do you build?
We connect CRMs (Kommo, HubSpot, and others), payment processors, lead forms with delivery to any target system, web and multi-touch analytics, live chats, messengers, email campaigns, as well as webhook and API integrations with any external service. If a service has an API or webhooks, we can almost certainly integrate it.
How much does an integration cost?
It depends on complexity: connecting a standard third-party service is a few hours of work, while a custom API integration with data transformation is a separate scoped task. We fix a quote after a brief, once we know which services are involved and what data flow is needed.
How long does an integration take?
Connecting a standard service (analytics, chat, simple form to CRM) typically takes one to two days. A custom API integration with field mapping and error handling takes from a few days to a week. Exact timeline is given after a brief.
Can you connect my CRM, or only specific ones?
Practically any CRM. We work directly with popular CRMs like Kommo and HubSpot, and connect others through their APIs or webhooks. If your CRM has an open API, we can integrate it. Tell us which services you use and we will confirm what is possible.