CRM & field-service integration
ServiceTitan, Bitrix24, HubSpot. Bidirectional sync, identity mapping and a reconciliation layer so two systems can disagree without either one losing data.
Liberon.tech
Liberon.tech is the engineering practice inside Khrestenkov & Co — integration, automation and billing architecture for companies that have outgrown the spreadsheet and cannot afford a bad rebuild.
The problem
It fails at the seams. A CRM that does not talk to the field app, a billing system that does not know a customer left, an automation that works perfectly until the API changes its pagination. None of it appears in an error log. It appears in the revenue.
The newer failure mode is worse: automation built quickly by someone who will not be there when it breaks. Half-finished agents, undocumented webhooks, workflows nobody can read. We build the opposite — small, boring, documented systems a stranger can pick up and run.
What it does
ServiceTitan, Bitrix24, HubSpot. Bidirectional sync, identity mapping and a reconciliation layer so two systems can disagree without either one losing data.
Stripe, recurring revenue, dunning, merchant-of-record decisions, fund flows. The plumbing that determines whether your churn number is real.
State-graph workflows, n8n, LLM agents with guardrails. Low-key and high-control: the system runs itself and you keep the override.
Someone built it fast and left. We read it, document it, and tell you honestly whether it is worth keeping — before anyone spends another month on it.
Under the hood
Every engagement starts with a written architecture and a fixed price. You receive the repository, the documentation and the credentials. There is no dependency on us afterwards, and that is deliberate.
# reconciliation, not replicationdelta = compare(crm.customers, field_app.customers)for row in delta.conflicts: resolve(row, prefer=source_of_truth(row.field))Built with
Next
MemberBay