<integrations_/>

NEVER ENTER ANYTHING TWICE AGAIN.

An integration between your webshop, your accounts and your stock. Enter it once, correct everywhere. Even when the package on the other side is old or has no decent documentation.

  • The common Dutch accounting packages, and the international ones
  • Payment providers, carriers and marketplaces
  • Your own ERP, or a package nobody maintains any more
  • With logging, so you can see what went across and when
€ 1,850 GUIDE PRICE excl. VAT // final amount after one conversation
<who_for_/>

WHEN YOU END UP WITH US.

Four situations we hear almost weekly.

01

RETYPING ORDERS INTO THE ACCOUNTS_

Entering every order twice. At fifty orders a week that is a day of work a month, plus the typing errors.

02

YOUR STOCK IS NEVER RIGHT_

What the webshop says and what is on the shelf are two different things. That costs you sales and goodwill both.

03

THE PACKAGE HAS NO DECENT API_

No documentation, an odd format, or only an export by e-mail. That is exactly the work other people back away from.

04

SOMEBODY ELSE'S LINK FAILS SILENTLY_

It works most of the time, and nobody notices on the day it does not. Until the bookkeeper calls.

<scope_/>

WHAT IS IN THE FIXED PRICE.

From first analysis to three months of aftercare.

  • Analysis of both systems and their fields
  • A field mapping you can read back
  • Building the integration
  • Error handling and recovery after a failure
  • Logging and alerts when something goes wrong
  • A test environment with real data
  • One-off migration of existing data
  • Documentation of what runs when
  • Launch outside office hours
  • Three months of warranty

AND FURTHER

  • Full source code under your control
  • One contact person with a direct number
  • No charge per message passed across
  • Maintenance optional, never compulsory
<approach_/>

HOW WE GO ABOUT IT.

An integration is only as good as the agreements behind it. That is where it starts.

  1. 01

    WORKING IT OUT

    Which data has to go where, how often, and what should happen when it goes wrong. That last one is the real work.

    1 conversation, costs you nothing
  2. 02

    BUILDING & TESTING

    On a test environment with your own data first, so you can see what happens before it touches your administration.

    around 2–4 weeks
  3. 03

    LIVE & WATCHED

    Live outside office hours, with alerts if anything jams. Then three months of warranty.

    around 4–6 weeks in total
<pricing_/>

WHAT IT COSTS.

The guide price is a starting point. Below is what moves the amount.

GUIDE PRICE INTEGRATION

€ 1,850
excl. VAT // complete project, fixed price
  • Final amount after one free conversation
  • Payment in two instalments: 50% / 50%
  • Lead time around 4–6 weeks
Ask for your price

MAKES IT MORE EXPENSIVE

A package with no documentation or no test environment. Data that has to travel both ways. Plenty of exceptions to the rules. A supplier who is slow to answer questions.

MAKES IT CHEAPER

A modern API with documentation. One direction instead of two. Once a night instead of real time. Clear agreements about what should happen with an error.

Curious how we arrive at that amount? We work three projects out in full for you. See what it costs

<proof_/>

A PROJECT FROM PRACTICE.

What went wrong, what we built, and what it delivered.

1
plug-in for every customer
0
bespoke work per site
4
gaps in the standard closed

The brief was: at least as good as what already exists. It is that, and better on four points.

— Product manager, recruitment software vendor
Read the full case
PLUG-IN VACANCIES ON EVERY CUSTOMER SITE
<answers_/>

QUESTIONS ABOUT INTEGRATIONS.

Not your question? Just call — we will not talk you into anything.

Usually, yes. We have integrated with packages that could only export by e-mail, with CSV on an FTP server, and with a database we were allowed to read directly. It takes more time than a modern API, so it goes in the quote — but it is nearly always possible.

We get an alert and you get an e-mail, and the messages that could not go across stay in the queue until it works again. An integration that stops quietly is worse than no integration, so that is the first thing we set up.

We choose that together. Orders to the accounts can go immediately; stock once a quarter of an hour is usually enough. Real time everywhere is more expensive and rarely needed — so we ask first what it really comes down to.

No. You pay once for the build and after that only for hosting and maintenance if you take it. The number of orders or products makes no difference to the price.

<next_step/>

WHAT WILL YOUR INTEGRATION COST_

Half an hour on the phone is enough for an honest estimate. You will hear what it costs and how long it takes — including if the answer is that you are better off doing something else.