A long integration catalogue is a confession. Most of what other vendors connect to, we already include.
Banks, carriers, tax authorities and identity providers are genuinely outside your company. Those we connect to properly.
The connections a Dutch company cannot operate without.
So that the record of a conversation lives with the customer, not in somebody's inbox.
The outside parties that physically move things or take orders.
Because access should be governed centrally, not per application.
Dutch and European obligations, handled in the system rather than around it.
Where a documented interface matters more than a logo grid.
Most integration catalogues are long because the product is narrow. Every connector on a competitor's marketplace is a gap in their own suite. The applications you would normally connect are already inside your Site, sharing a database, so the list of things left to integrate is short by design.
Every record in every application is reachable over a documented REST interface with the same permission rules as the interface. Anything you can do in a screen you can do in a call, which means you are never blocked waiting for us to build a connector.
There is no per-connector fee, no premium tier that unlocks the useful ones, and no third-party automation subscription needed to make two of our own applications talk to each other.
A typical fifty-person company runs a CRM connected to an accounting package, connected to a webshop, connected to a helpdesk, connected to an HR tool, with an automation platform in the middle and a data warehouse at the end so somebody can produce a report.
That is six subscriptions, five synchronisations and at least one person who knows which system to believe when two of them disagree. Each connection has its own failure mode, its own retry behaviour and its own quiet way of creating duplicates.
After moving, the count is normally two: your bank and your carrier. Everything else became a table in the same database.
Yes, in one of two ways. Give them a scoped login to your Site so they work in the live ledger, or export in the format their software expects. Most Dutch accountants prefer the first once they see it, because it removes the export-and-question cycle entirely.
Usually, over the API. Be honest with yourself about why, though. Keeping one system means keeping one synchronisation, and synchronisation is the thing you are buying a suite to escape.
Generous limits per Site that no ordinary integration reaches. Sustained high-volume use counts as API usage and appears on your bill, at rates published on the pricing page.
Either. The API is documented and your developer can use it. If you would rather not, we scope and quote the work fixed price during onboarding.
Ask. If it is something several customers need it usually gets built and made standard. If it is specific to you, it is a quoted piece of work that stays yours.
