What the app covers out of the box
Holded by Vexco ships with 14 flows that you turn on or off and edit one by one: companies, individual contacts, products, services, estimates and proformas, sales orders and waybills, deal → document in Holded from the stage you choose in any pipeline, invoices and payments, Holded CRM leads, events and meetings, projects and hours, suppliers, purchase orders and, if you turn it on, Holded documents as HubSpot deals. Each flow has its own direction, conflict rule, conditions, fields with type validation and matching keys, plus “Test with a record”, a dry run that writes nothing.
On top of the flows you get cards on HubSpot records, 21 workflow actions, document rules per deal, company or contact, and safeguards that can't be switched off: the app never edits an issued invoice, never creates a second document for the same deal on a retry, never issues with a date earlier than an invoice already issued in the same series, applies the equivalence surcharge and IRPF withholding only where they belong, keeps only the last 4 digits of the IBAN in HubSpot and never deletes payments it didn't create. See the full feature list and how data is protected on the security page.
When a custom integration wins
Some processes don't fit any ready-made app, and pretending otherwise costs more in workarounds than a build would. Typical cases:
- Custom objects. Your HubSpot account models contracts, sites or assets as custom objects that must map to Holded.
- Multi-entity logic. The app can connect several Holded companies, but rules between them (intercompany sales, consolidated customers) need code written for your structure.
- Special payment flows. Payment gateways, bank logic or approval chains outside Holded and HubSpot.
- More systems. Holded is one of several tools, such as an ecommerce platform, a warehouse system or a sector-specific ERP, that must all speak to HubSpot.
The costs that come after the build
The build is the visible cost. What follows is easier to underestimate:
- Hosting: servers or functions, queues for retries, a database for the links between records.
- API limits: the Holded API allows 100 requests per minute per API key, according to Holded's help centre, plus a monthly quota. A custom build has to queue, throttle and resume on its own.
- API changes: when Holded or HubSpot change an endpoint or a permission, someone has to notice and update the code.
- Monitoring: without an activity log and alerts, a failed sync is found when a salesperson asks why an invoice is missing.
- Knowledge: the logic often lives in one developer's head.
Using both: the app plus custom work
The two options aren't exclusive. The app can run the standard process while a smaller custom piece handles what's unique to you. Custom needs can be quoted from the app's Contact tab, and the Enterprise bundle includes 2 hours a month of custom configuration.
Vexco Solutions, the HubSpot partner agency behind Holded by Vexco, also builds bespoke work: HubSpot integrations with other systems and custom HubSpot development. Our Holded–HubSpot integration case study shows a custom project of this kind.
How to decide
- Do you need HubSpot custom objects to sync with Holded? If yes, custom.
- Do you have logic across several legal entities? If yes, custom, or the app plus custom work.
- Is the process customers → documents → invoices → payments, with or without Holded CRM and projects? If yes, start with the app.
- Is there someone to host, monitor and maintain a build for years? If not, lean towards the app.
To see what the app's setup involves, read how Holded by Vexco works.
Frequently asked questions
Is a custom integration better than an app?
It depends on your process. For the standard flow of customers, documents, invoices and payments, an app saves you building, hosting and maintaining code; for custom objects, multi-entity logic or special payment flows, a custom build fits better.
Does Vexco build custom Holded–HubSpot integrations?
Yes. Vexco Solutions, the HubSpot partner agency behind Holded by Vexco, also builds custom integrations and HubSpot development. If you need something the app doesn't do, request a quote from the app's Contact tab or through Vexco's contact page.
Can the app be adapted to our specific case?
Partly. Each flow can be edited (direction, conditions, fields, matching, conflict rules), and Settings → Rules changes document values per deal, company or contact. Needs beyond that can be quoted from the Contact tab; the Enterprise bundle includes 2 hours a month of custom configuration.
What happens to our data with each option?
With Holded by Vexco, data is processed on Cloudflare in the EU, keys and tokens are encrypted with AES-256-GCM, and the app keeps only the links between records, a summary of the last synced state and the activity log, not a copy of your CRM. With a custom build, those choices are yours to make and document.