Off-the-shelf connector or custom API? How to choose
Short answer
An off-the-shelf connector is enough when your case is close to what the connector was built for: standard fields, a one-way flow, reasonable data quality. A custom API build is needed when you have custom objects, custom processes or require two-way sync with conflict handling. The difference in price is large, but the real cost lies in choosing wrong.
When an off-the-shelf connector is actually enough
This is the part consultants are reluctant to say out loud, because we earn more from building: a great many companies do not need a custom-built integration.
If you want customers and invoices from the ERP into HubSpot, if you run on standard fields, if the flow goes in one direction and if you do not carry ten years of duplicates, then a ready-made connection does the job. Paying six figures for a custom build then is not ambitious, it is waste.
When the connector runs out
The connector runs out when reality gets specific. Four typical breaking points:
Custom objects and fields. You have built your own properties in HubSpot that mirror how you actually sell. The connector does not know about them.
Two-way sync. As soon as both systems can write, someone has to decide who wins in a conflict. That is not a technical question, it is a business decision, and an off-the-shelf connector cannot make it for you.
Volume. Automations and lightweight connections that work fine on a hundred rows start dropping records when it becomes a hundred thousand.
Error handling. What happens when the ERP is down for three hours? A good middleware queues and retries. An off-the-shelf connector often just drops the record and says nothing.
The middle ground: automation in Make
Between connector and custom there is iPaaS. A flow in Make that moves data in one direction costs a few thousand SEK and is often the right first step. A new order in Shopify creates a deal in HubSpot. That is good enough for a long time, and it is a cheap way to discover what you actually need before you build for real.
The real decision criterion
The question is not "off-the-shelf or custom". The question is how well your data model matches the model the connector assumes. The bigger the gap, the more you end up building anyway, only then you do it on top of someone else's assumptions.
A vendor who answers "we have a ready-made connection" to everything has not asked themselves that question. One who starts by asking to look at your data has.
More on this in our guide to HubSpot integrations, what they cost and why they fail.
