One owner per field
Each field has one system that owns it, written down. Updates never bounce between two systems overwriting each other.
CRM integration
Your CRM connected to the systems that hold the real data
Your CRM says one thing, billing says another, and the flows between them stop working without telling anyone. We connect HubSpot, Salesforce or Pipedrive to the systems that hold the real data, as tested code in your repository that your team can read and change.
Typical lengthweeks
From€10,000 · £8,700 · $11,500
Works withHubSpot, Salesforce, Pipedrive
When teams call us
What usually triggers the work
“A zap stopped running three weeks ago and nobody noticed.” “Our deals don't match our invoices.” “We're moving CRM, and nobody knows what the old flows actually do.” CRM integrations tend to grow one flow at a time, built by whoever was free, in Zapier, Make or a script on someone's laptop.
Leaving it costs more than it looks. Sales chase customers who have already paid or left, finance reconciles by hand at month end, forecasts are built on numbers nobody trusts, and the person who understood the flows has moved on. Customers notice first, when they get the wrong email or the wrong invoice.
What we deliver
In your repository, demoed every week
- HubSpot, Salesforce or Pipedrive connected to billing, product and operations systemsTwo-way sync through each system's own API, with one system agreed as the owner of each field. You get a daily report of every record that doesn't match.
- Automations as code, tested and monitored, instead of fragile chains of zapsFlows written as code in your repository, with tests, retries and a log of every run. A failing flow raises an alert instead of going quiet.
- Lead handling with AI drafts and a person approvingAn AI model sorts incoming leads and drafts replies inside the CRM, and nothing is sent until a person approves it. You can see who approved what, and when.
- Documentation so the next person can change itNotes for every flow: what starts it, what it changes and how to switch it off. A new engineer can follow them without calling us.
How it holds up
The questions a reviewer will ask, answered in the build
Safe to run twice
Every event carries a key, so a retry or a replay after an outage never creates a second contact, deal or invoice.
Failures are loud
Every run is logged with what it changed. A failure is retried, then sent to a named person with the record that caused it.
Proof
Where we have done this before
We have no CRM project we can publish. The engineering it needs (keys on every event, replays after an outage, reconciliation, alerts) runs in production in our fintech work, and our data platform depends on the same kind of health checks.
Banking orchestration
One system of record across Sumsub, Fireblocks, a ledger and banking-as-a-service partners, in production for a European payment platform.
Mycarro data platform
About six million car adverts from ten countries, matched into three million cars and priced against the market every day.
Works with
- HubSpot
- Salesforce
- Pipedrive
- n8n
Price
What it costs
CRM integration projects start at €10,000 (£8,700 · $11,500). The first step is a free 30-minute call about your systems and what has to match. After it you get a fixed written quote with milestones, and it changes only if the scope does.
Setting up a CRM itself (pipelines, properties, email templates, training) is not our work: a CRM partner agency does it better and for less. If you are that agency and need engineers behind you, see working with agencies.
Questions
Before you book
Do you set up HubSpot itself?
No. Portal setup, pipelines, email templates and training are better done by a HubSpot partner agency. We build what sits around it: integrations with your own systems, custom code, data sync and AI-assisted lead handling. We are happy to work alongside the agency that set it up.
Can you replace our Zapier flows?
Yes, where it is worth it. We list what each flow does, keep the simple ones that work, and rebuild the ones that carry money or customer data as tested code with retries and alerts. Flows that are fine in Zapier, Make or n8n can stay there.
Do you work under another agency's brand?
Yes. We work white-label for agencies: your client, your brand, our engineers, under an NDA and a non-solicit clause. The terms are on the agencies page.
Who owns the code and the IP?
You do, from the first commit. We work in your repository and your accounts, and the contract assigns the IP to you in the present tense, not at some later date.
Who will actually work on our project?
The engineers named in the proposal, and you meet them before you sign. A key-person clause means nobody is swapped without your written consent.
How do time zones work for a UK or US team?
We work on Lisbon time, which is the same clock as London: Mon–Fri, 08:00–18:00 UK time. That leaves about four working hours a day in common with the US East Coast. You get a demo of working software every week and a short written update every working day.
What contracts do you sign?
A master services agreement with a statement of work for each project, or your own paper if you prefer. A mutual NDA before we see anything, and a GDPR data processing agreement. US clients get a W-8BEN-E from us. Which law governs the contract is answered on Contracts & security.
How do we pay?
The fixed-price first step is paid upfront. Builds are billed by milestone, after you have seen the work running. Monthly care, if you want it, is billed at the start of each month. We invoice in euros, pounds or dollars.
Free 30-minute call
Tell us what has to work, and by when
You talk to an engineer who would work on it, not a salesperson. You leave the call knowing what it would take and what the first step costs, or we tell you that you don't need us.