If a tool already covers the process, we recommend that tool instead of building.
Apps inside your CRM
Screens of our own that open in the deal. At Vita Brevis Fine Art the bookers book a session and take the reservation fee in the deal, and clients check in on the iPad.
Integrations and middleware
Your CRM connected to accounting or ERP. With error handling, so a missed update gets noticed.
Data migration
Moving between CRM environments with mapping and a dry run first. That is what Surge Shift does.
Data quality
Finding duplicates on email or phone and on name. You merge them yourself, after a review.
Forms and intake
Forms that write straight into your CRM, with the right owner and a follow-up task attached.
Reporting and data warehouse
Rebuilding and syncing large datasets. At Diversified Botanics the old account held 40,000+ unstructured leads.
“Sander and Sales Surge built the connection between our website, Pipedrive and MKG, with clear agreements on security and a clear work instruction. Thinks along, works neatly and is easy to reach. Highly recommended! (Translated from Dutch.)”
The audit maps your systems, data flows and current integrations and ends with a roadmap. After that every integration or app gets a fixed price per phase.
Software that has nothing to do with your sales process or your CRM, and standalone websites. If an existing tool already does it well, we say so.
When do you build, and when do you take an existing tool?
Take an existing tool when it covers at least most of your process, and build only the part it cannot do. Our rule is custom where it has to be, ready-made where it can be.
We use a simple test. Does a tool or a standard integration exist that does what you need, without your team working around it every day? Then we recommend it, set it up and connect it. Is the gap one step in your process, such as a booking with payment or an order that has to reach production? Then we build that step and leave the rest standard. Do you have to bend your whole process to a tool? Then a standard tool costs you more in the end than building does.
What we watch out for: custom work has to be maintained. Every app or integration we build gets documentation, monitoring and an owner. If nobody is going to own it, a ready-made tool is the safer choice, even if it fits less well.
Which integrations do you build?
We build integrations between your CRM and the systems that hold the rest of your customer data. This is what that looks like per system type.
System type
Examples
What typically moves
Accounting and ERP
Exact, AFAS, Twinfield, Zoho Books
Customer numbers, orders, invoice status and payment status into the deal
Telephony
CloudTalk, JustCall
Calls, recordings and outcomes as activities on the person and the deal
Controlled access for an AI model to CRM data, per tenant
For every integration we agree per field which system is the source, so one system does not overwrite the other. Moving data between CRMs is a separate build with mapping and a dry run, which is what Surge Shift does. Cleaning duplicates goes through Surge Dedupe, always with a review before anything is merged. An overview of what we connect to Pipedrive is on the page about Pipedrive integrations.
What happens when an integration fails?
When an integration fails, the message waits and is sent again, and someone gets a notification if it keeps failing. Nothing disappears quietly. That is the difference between a quick connection and middleware you can rely on.
Outbox. Every change is first written to an outbox. Only when the other system confirms receipt is it marked as done.
Retries. If the other system is down or slow, the integration tries again later, with growing intervals.
Notification. After a set number of failed attempts a person gets a message with the record and the error.
Audit trail. Every change is logged: what changed, when, by which integration. So you can always trace where a value came from.
A practical example. An invoice is marked as paid in accounting while the CRM is briefly unavailable. The update waits in the outbox, goes through as soon as the CRM is back, and the rep sees the paid status in the deal. Without an outbox that update is simply gone, and you only find out when a client calls about a reminder.
What does an app inside the Pipedrive deal look like?
An app inside the deal is a screen of our own that opens in Pipedrive, so the rep does the work without leaving the CRM. Vita Brevis Fine Art is the clearest example.
At Vita Brevis our own apps run inside the Pipedrive deal. The studio's bookers book a session and take the reservation fee inside the deal, without leaving Pipedrive. On the day itself the client checks in on the iPad, and after check-in the deal moves to the next stage by itself. Orders go through ProSelect, and they too are linked to the same deal. The team works from one place, instead of keeping three systems in step by hand.
Such an app has its own database, login and audit trail. Ten of our eleven products are built the same way. That makes it a real application, not a script that only works as long as nobody touches it. Read the full story in the Vita Brevis Fine Art case.
What does an integration cost?
An integration project starts with an audit of €2,200, which takes 7 to 10 days. In that audit we map your systems, the data flows and the current integrations, and you get findings, a roadmap and quick wins.
After that every integration or app gets a fixed price per phase, set after the blueprint. What determines the price is the number of systems, the number of exceptions in your process and how reliable the integration has to be. A one-way sync of a few fields is a different job from two-way middleware with an outbox.
For comparison: a website whose forms write straight into your CRM starts from €3,750 and takes 2 to 4 weeks. You pay per phase, before that phase starts. Prices exclude VAT.
In short
In short
Sales Surge builds integrations around your CRM: with accounting, ERP, telephony and data warehouses, apps that open inside the Pipedrive deal and middleware with an outbox. Outsourcing a Pipedrive integration starts with a €2,200 audit, after which every phase gets a fixed price. Every change is in an audit trail. Ten of our eleven products are built the same way: with their own database, login and audit trail.
Source: Sales Surge price list, the Vita Brevis Fine Art case and the Sales Surge product line, checked on 16 November 2026.
Frequently asked questions about software and integrations
How long does it take to have an integration built?
The audit up front takes 7 to 10 days. In it we map your systems, data flows and current integrations. How long the build takes after that depends on the number of systems and exceptions, so the lead time per phase is in the quote. We do not name a timeline that is not in it. You do get a delivery per phase, so you do not have to wait until the end.
Can you take over an integration built by another agency?
Yes. We start with an audit, because taking over without knowing what is there goes wrong. In that audit we look at what the integration does, where it runs, who has access and what happens when it fails. After that you know whether we take it over as it is, fix it first or rebuild it. Sometimes rebuilding costs less than repairing it again and again.
When is Make enough, and when do you build your own middleware?
Make is enough when the flow is easy to follow and your team wants to read and adjust the scenarios itself. We are a Make Certified Partner for that. We build our own middleware when a missed update costs money, when volumes are high or when several systems have to agree at the same time. It runs on our own infrastructure, with an outbox, retries and a notification when something keeps failing. Often we use both side by side.
Do you also work with CRMs other than Pipedrive?
Yes. Pipedrive is where we are strongest, but we also implement HubSpot and Zoho, and we migrate between those three. We build integrations around Pipedrive, HubSpot, Zoho and Lumo. Note: our own Surge products such as Reports, Dedupe, Forms and Connect work with Pipedrive. With another CRM we build the integration separately, and you see that in the price per phase.
Who maintains it once it runs?
After the handover there is first a period of hypercare: we fix whatever comes up right after go-live. After that your team can carry on itself, with documentation on what runs where. If you want us to keep monitoring it and update it when a system changes, that works with a retainer or as a fixed part of a growth partnership. You then have one fixed contact at Sales Surge.
Who owns the code and the data once it is done?
Your data is and stays yours, including the data that runs through our integrations and apps. Who owns the code and what you may do with it is agreed per project in the quote. That differs per type of build: an integration that exists only for you is different from one of our own Surge products, which you use under a licence. So you know up front what you hold if you ever stop.
Where does the software you build run?
Our middleware runs on our own infrastructure. Our apps run as applications of their own, with a database, login and audit trail per application. We do not name the suppliers behind it on the website, because that is our problem and not yours. If you have requirements for where data is stored, or you want a data processing agreement, mention it in the intake.
What happens when a system you connect to changes?
Then the integration has to change with it. Suppliers update their systems, and an integration that works today can miss a field a year from now. That is why we monitor what we build and you get a notification when something keeps failing. The update itself is agreed up front: as a separate job when it is needed, or as a fixed part of a growth partnership. It is in the quote, so it does not fall between the cracks.
We build CRM integrations with accounting, ERP and telephony, apps inside the deal and middleware with an outbox. Outsourcing one starts with a €2,200 audit.