All services
Integrations & APIs

Make your systems talk to each other.

Most companies don't need new software. They need the software they already pay for to stop living in separate worlds: orders that reach accounting without a spreadsheet, customers that exist in one place, stock numbers that agree. We build those connections properly, so they keep working when the person who usually checks them is on holiday.

Sound familiar?

You're here because one of these is true.

Someone re-types the same data twice a day

Orders from the shop get copied into accounting by hand. It works until that person is away, and it's never quite in sync.

Each system holds a different truth

The CRM says one thing, the shop another, accounting a third. Nobody trusts the numbers, so everyone keeps their own spreadsheet.

The last integration broke and nobody noticed

A vendor changed their API, the sync stopped, and you found out from a customer three weeks later.

What we do

Your shop, CRM, ERP and accounting, finally talking to each other.

An integration is a small piece of software with a big job: move the right data between two systems, every time, without anyone watching. Most of the work is in the parts nobody demos, what happens when a system is down, when a record is malformed, when the same order arrives twice. We build for those cases first, add monitoring so you hear about problems before your customers do, and document it so the next person can pick it up.

A map of your systems and where data actually needs to flow
The integration itself, built as real software in your own repository
Handling for the messy cases: retries, duplicates, outages
Monitoring and alerts when a sync stops
A record of what moved and what failed, that you can search
Plain-English docs plus a handover for your team

The process

How an integration runs.

Light on process, transparent, senior from day one.

  1. 01

    Map

    A few days. We list the systems, the data, and who owns what.

  2. 02

    Connect

    3 – 5 days per pair. Built against your real accounts, not a sandbox.

  3. 03

    Harden

    Retries, duplicate handling, alerts. The parts that matter at 3am.

  4. 04

    Hand over

    Docs, monitoring access, training. Then it's yours.

What you get

What's in. What's out.

Built for

Companies running a shop, CRM and accounting that don't talk · Teams where someone re-types data between systems every day · Businesses whose last integration broke and was never fixed

Not the right fit if

Teams who need the systems themselves replaced (see Migration & Replatforming) · One-off data transfers that will never run again

Every tier includes

  • System mapping and a written data-flow plan
  • The integration built as proper software, in your own repository
  • Authentication and credentials handled properly
  • Retry, duplicate and failure handling
  • Monitoring, logging and alerts when a sync stops
  • A searchable record of every sync, so you can answer "did that go through?"
  • Plain-English docs plus 2 weeks of free support after go-live

Intentionally not included

  • Licence or API costs charged by your own vendors
  • Replacing the systems themselves (see Migration & Replatforming)
  • Building a new shop, CRM or ERP from scratch (see Development)
  • Long-term maintenance beyond Run & monitor (see Monthly Support)
  • Cleaning up years of inconsistent records
  • Systems with no API, no database access and no export

Plain pricing.

Single connection
From CHF 3k
Prices exclude VAT
  • 1 – 2 weeks
  • two systems talking
Recommended
Integration suite
From CHF 12k
Prices exclude VAT
  • 4 – 6 weeks
  • 3 – 5 systems
  • monitoring dashboard
Add-on
Run & monitor
CHF 750 / mo
Prices exclude VAT
  • Optional
  • we watch it and fix vendor API changes

Common questions

Everything else.

What if our system has no API?

Then we look for the next best door: a database view, a scheduled export, a file drop. If there genuinely isn't one, we'll tell you during mapping rather than after the invoice.

What happens when a vendor changes their API?

Things break, usually without warning. That's what the monitoring is for: you hear it from us, not from a customer. Fixing it is what the Run & monitor add-on covers.

Could we just use Zapier or Make?

Sometimes, and we'll say so. When the volume is low and the logic is simple they're the right answer. Once it's business-critical or high-volume, the per-task pricing and the debugging get painful, and real code costs less.

Can you connect an old on-premise system?

Usually, as long as it can reach the internet or we can reach it. We've worked with plenty of systems older than the people using them.

Scope my integration.

No slides, no pitch. Just a quick conversation to see if we're the right fit.

Start a conversation