[01/06] > Service //04 · Data and systems

Enter it once.
See it everywhere.

The accounting package, the mailbox, the warehouse and the enquiry form, connected so nobody retypes a record from one screen into another. Scoped against your systems and quoted as a fixed price before work starts.

On request

Quoted per system

45 min

Free scoping call

Fixed

Price before work starts

Alerts

On every failed transfer

[02/06] > Included

Connections that fail loudly,
not silently.

The hard part of an integration is not the happy path. It is what happens at 3 am when the other end returns an error, and whether anyone finds out.

//01Rules you agree

Two-way sync

Records created or changed on one side appear on the other, with conflicts resolved by rules you agree rather than by whoever wrote last.

//02Your schedule

Scheduled transfers

Imports, exports and reconciliation on the schedule your business runs on, whether that is every five minutes or once a night.

//03With cleanup

Migration

Spreadsheets, exports from another tool, or a database from an older system, moved across with the cleanup that historical data usually needs.

//04Alert, not silence

Failure handling

Retries with backoff, a dead-letter record for what could not be delivered, and an alert to a human. Nothing disappears quietly.

//05Scoped and rotatable

Credentials kept properly

API keys scoped to the minimum needed, stored outside the repository, rotatable without a redeploy, and held in accounts opened in your name.

//06Handed over

A written map

A document showing what flows where, on what schedule, and who to call when it stops. Handed over with the code.

[03/06] > Fit

Honest fit.
Before you pay.

Build an integration if

  • //01The same record is typed into two systems by two people.
  • //02Your accountant asks for an export somebody prepares by hand every month.
  • //03Stock, prices or contacts disagree between systems and nobody knows which is right.
  • //04A transfer already exists and fails silently.
  • //05You are moving off an old system and the data has to come with you.

Look elsewhere if

  • //01A ready-made connector already covers it. We will tell you if one does.
  • //02The systems have no API and no export at all.
  • //03You need the system itself built first → Operations System
  • //04Nobody can say which system should win a conflict.
  • //05The data is not yours to move.
[04/06] > Compare

Where Integrations sits.

CapabilityBusiness Site€700Client Portal€1,000Operations System€1,500IntegrationsOn request
Custom-coded front endOptional
Deployment, domain and SSLOptional
Enquiry and contact forms
Client logins and permission rolesOptional
Document storage and downloadsOptionalOptional
Internal records and workflowsOptionalOptional
Management reportingOptionalOptional
Connections to other systemsOptionalOptional
Data migration from existing toolsOptionalOptional
Fixed price published up front€700€1,000€1,500Quoted per system
Included Optional, quoted separately — Not included
[05/06] > Process

Brief to handover.
The same four steps.

  1. //01 Day 1

    A conversation about what the system has to do, who uses it and what it has to talk to. You leave with a written specification: screens, roles, data model, integrations, and the exact list of what is not included.

    Scope call

    RequirementsWritten specFixed quote
  2. //02 Days 2–3

    We agree what data lives where, who may see it, and how anything existing gets migrated. Credentials and third-party accounts are opened in your name before a line is written.

    Data and access

    Data modelRolesAccounts
  3. //03 Days 4–12

    The build happens on a staging URL you can open at any time. Progress is visible daily rather than revealed in a single handover at the end.

    Engineering

    Staging URLDaily commitsReview rounds
  4. //04 Days 13–15

    We deploy to your hosting, point your domain, hand over the repository and every credential, and walk your team through the parts they will operate themselves.

    Handover

    DNS and SSLRepo transferTeam walkthrough
[06/06] > Questions

About this package.

On requestexcl. VAT

Request a quote
//01 Which systems do you connect?

Anything that exposes an API or can export a scheduled file: accounting packages, CRMs, warehouses, mailboxes, payment providers, marketplaces. Tell us what you use at the scope call and we confirm before quoting. We do not promise an integration we have not verified is possible.

//02 Why is there no price on this page?

The three packages have published prices because their scope is fixed. An integration's scope comes from your systems, and no two combinations are alike. So the price is quoted rather than guessed, and you still get a fixed figure in writing before anything starts.

//03 What happens when the other side changes its API?

Third-party APIs change and connections break; that is normal. Under a monthly plan the fix is part of the change hours. Without one, it is quoted as a small project when it happens.

//04 Who holds the API keys?

You do. Third-party accounts are opened in your company's name and the keys live in your infrastructure, scoped to the minimum permissions the integration needs. We can rotate them without a redeploy, and you can revoke our access at any time.

Integrations

Describe your systems.

List what you run today and where the retyping happens. You get a written specification and a fixed quote back.

Reply within two working days. No sales call unless you ask for one.