What CRM integration services actually cover
I'm Emil Hjorth, and I run em8, a founder-led AI studio in Mora, Sweden. When someone asks me for "a CRM integration", they usually mean one of these:
| Integration | What it does | Where it breaks |
|---|---|---|
| One-way push | A form, signup or order creates or updates a CRM record | Duplicates, because nobody decided how to match an existing contact |
| Two-way sync | Two systems keep the same fields in step, e.g. CRM and billing | Both sides edit the same field and the last write silently wins |
| Writeback | Another tool does work and writes the result back to the CRM record | The result lands in a note nobody reads instead of a field a report uses |
| Event trigger | A stage change, a won deal or a new owner kicks off work elsewhere | The trigger fires twice, or not at all when someone bulk-edits |
| Enrichment | Company and contact data is added from outside sources | It overwrites what a rep typed by hand |
| Reporting feed | CRM data moves to a sheet, warehouse or dashboard on a schedule | Field names change and the report breaks without telling anyone |
Most projects are two or three of these at once. That's why the field map comes before the tool choice.
Integration, CRM automation, or RevOps?
Three words that get mixed up in the same call:
- CRM integration moves data between the CRM and other systems. That's this page.
- CRM automation is the rules that run inside the CRM: lead routing, stage updates, tasks, follow-ups. See CRM automation: 12 pipeline flows.
- RevOps is who owns the revenue system and decides what the pipeline should look like. See RevOps consultant.
You often need all three, but you hire for them differently.
Native connector, iPaaS, or custom build?
| Route | Who builds it | Good for | Weak when |
|---|---|---|---|
| Native connector / marketplace app | You, in an afternoon | Standard objects moving one way between two well-known tools | You need a custom field, a filter, or a rule the vendor didn't think of |
| iPaaS (Zapier, Make) | You or a freelancer | Low-volume pushes, simple triggers, quick wins | Two-way sync, high volume, or logic that needs retries and deduplication |
| Custom build (n8n or the API) | A studio or an engineer | Two-way sync, writeback rules, AI steps, runtime on infrastructure you control | One field moving once a day. That's overkill |
If the native connector does the job, use it. I'll tell you so on the call. If you're already on Zapier or Make, we build there too: see Zapier automation and Make.com automation. For the trade-offs between the three tools, read Make vs Zapier vs n8n. When the integration should run on your own instance, that's n8n automation.
Week 1: how em8 scopes a CRM integration
Week 1 is a diagnosis inside your CRM, not a kickoff deck.
- Access in your name. CRM, the other systems, and the n8n or iPaaS account. If the keys live in our tenant, that's a vendor, not a build.
- Write the field map. For every field that moves: which system is the source of truth, which direction it flows, and what happens on conflict.
- Pull 20 real records. Including the messy ones: duplicates, missing owners, the account with three domains. Write down the exceptions, not the happy path.
- Design the failure path. Retries, deduplication, a log of every call, and an alert to a human when something can't be matched.
- Scope one production path. One or two integrations, the stack, the hours, and what we won't touch. You keep the plan if we stop there.
What CRM integration costs
There's no separate rate card for integrations. A CRM integration is a scoped production path like any other system we ship, so it uses the published bands:
| Engagement | Price | What you get |
|---|---|---|
| Diagnosis | From $2,500 | Week 1 in your CRM: field map, 20 real records, failure path, route decided, kill list |
| First production path | From $8,000 | One integration live: sync or writeback, deduplication, logs, alerts, docs, your keys |
| Retainer | From $4,000 / month | New fields and systems, API changes, breakage, coverage |
Connector and iPaaS subscriptions are billed to you by the vendor, on your account. Across our clients, average payback is 2.8 months. That's the number to test your own case against, not a promise. For the full tables, see the automation agency pricing guide and how much automation costs.
Case 01: Salesforce, SalesLoft and Claude on the client's n8n
An $18M B2B company's reps spent about half their day researching prospects and hand-writing cadences. We built the system that does that prep, on the client's own n8n. A rep ticks one box in Salesforce. The system researches the prospect, writes a personalised cadence, and puts it in SalesLoft.
That's a CRM integration with an AI step in the middle: a trigger in Salesforce, work in n8n with Claude, and a writeback into the cadence tool.
- Build time: 3 weeks, live in production
- Per cadence: about 60 seconds of rep effort
- Quality: 9.7/10, LLM-judged over 20 runs
- Capacity: 175 hours a week of rep time redirected from prep to selling. That figure is a model (7 reps × 10 prospects a day × 30 minutes), not payroll removed.
Speed and quality come from the client's production logs. The full walkthrough is on Case 01.
Red flags when you hire CRM integration services
- No field map. "We'll sync everything" means the last write wins.
- No plan for duplicates or for records that don't match.
- The integration runs on the vendor's account and the vendor's API keys.
- No log and no alert. You find out it broke when the report is wrong.
- A demo in their sandbox, never on 20 of your real records.
- Pricing per "connection" without a scope of fields, volume and failure cases.
When em8 is the wrong fit
- You need a CRM migration or licensing. Moving from one CRM to another, or buying seats, is a job for a certified partner of that CRM. Hire one.
- One field, one direction, once a day. Use the native connector or a single Zapier step. You don't need a studio.
- You only need one n8n workflow built, and someone on your side owns it. Hiring an n8n expert is the cheaper route.
- There's no CRM yet. Pick the CRM first. Integrating a guess is expensive.
- You want a full-time owner in the building. That's a RevOps seat, not an integration project.
em8 is a founder-led studio. I've built or run 7 companies, and em8 has worked with 50+ clients since early 2024. We build mostly on Claude: em8 is Certified in the Claude Partner Network, and I hold the Claude Certified Architect credential.
Frequently asked questions
What are CRM integration services?
CRM integration services connect your CRM to the other systems your team uses, so records, activities and status changes move between them without copy-paste. The work is the field map, the sync direction, the writeback and the error handling, not just installing a connector.
How much does CRM integration cost?
At em8 a CRM integration starts with a diagnosis from $2,500. A first production path starts from $8,000, and an ongoing retainer from $4,000 a month. Connector or iPaaS subscriptions are billed to you by the vendor. Across our clients, average payback is 2.8 months.
How long does a CRM integration take?
Week 1 is the diagnosis inside your CRM. A first production path typically follows within a few weeks. Case 01, a Salesforce and SalesLoft build with Claude on the client's n8n, went live in 3 weeks.
Should we use a native connector, Zapier or Make, or a custom build on n8n?
Use the native connector if it moves the fields you need in the direction you need. Use Zapier or Make for low-volume, one-way pushes. Build on n8n or the API when you need two-way sync, writeback rules, deduplication, or AI steps, and you want the runtime on infrastructure you control.
Do you work with Salesforce and HubSpot?
Yes. Case 01 runs on Salesforce and SalesLoft. We integrate the CRM your reps actually open through its API, usually on n8n on your instance. If you need a certified partner for CRM licensing or a full migration, hire one; that is a different job.
Who owns the integration when you are done?
You do. It runs on your CRM, your n8n or iPaaS account, and API keys in your name. The field map, the workflows and the error path are documented, so you can stop working with us without losing the system.
Book the call
Discovery is 30 minutes, free, and not a pitch. Bring the two systems that don't talk to each other and the report that's always wrong. You'll leave knowing if it's a native connector, an iPaaS job, or a build. Book a discovery call.