CRM and SaaS synchronisation
Two-way sync with Pipedrive, Upsales, Zoho and similar — contacts, deals, cases, notes and meetings surfaced where your team actually works.
Services — 02
Integrations, for when two systems have to behave like one
CRM synchronisation, payment rails, third-party APIs and the data-protection obligations that arrive with them. This is most of what makes business software valuable, and the part most often quoted badly.
Typically
From €1,000 for small scoped work
The problem
Integration work is unglamorous and it is where the real money leaks. The happy path takes an afternoon. What takes the other six weeks is rate limits, partial failures, two systems with incompatible ideas about what a contact is, and the question of what happens when one of them is down.
We have built CRM integrations between a telephony platform and both Upsales and Zoho, a transaction layer at IKEA carrying every payment method at global scale, and GDPR-compliant data workflows inside Meta's Workplace platform. Different domains, same discipline: assume the other system will misbehave, and design for it.
What’s included
Everything below, as standard.
Payment and transaction layers
One layer carrying multiple payment methods, with fault isolation between them, built the way we built IKEA's prototype transaction management system.
API design and versioning
REST, RPC or GraphQL, designed so that the next change does not break every consumer. Including public APIs your own customers will build against.
GDPR-compliant data workflows
Data processing that satisfies a regulator and an internal review board. We did this at Meta, where compliance is code that provably runs rather than a policy document.
Legacy system bridges
Synchronisation layers that let an old system and a new one run in agreement while you migrate, instead of demanding a big-bang cutover nobody will approve.
Failure handling that is designed, not discovered
Retries, idempotency, dead-letter queues and conflict rules agreed with your team — because in integration work, 'last write wins' is usually a data-integrity bug.
Sound like the right fit?
You probably need this if
Any of these sound familiar.
01Someone on your team re-types data between two systems daily
02A partner API changed and you found out from a customer
03You need one system's data inside another before a sales call
04Legal has questions about where personal data ends up
Typical stack
TypeScriptNode.jsNestJSRESTRPCGraphQLPostgreSQLMongoDBGitHub Actions
Where we’ve done it
Work of exactly this kind.
Questions
We only need one integration. Is that too small?
No. Small, well-defined integration work starts at €1,000 and it is how a lot of our longer engagements began. If it is genuinely a day's work, we will say so and quote it as a day.
What if the third-party API is badly documented?
That is the normal case. Part of the work is establishing what the API actually does as opposed to what its documentation claims, and building against the former.
Can you take over an integration someone else built?
Yes. We will read it first and tell you honestly whether it is worth keeping — sometimes the right answer is a rewrite of one component rather than the whole thing.
Other services
Let’s build something that lasts.
Tell us about the project. If we’re not the right studio for it, we’ll say so — and usually point you at someone who is.