Skip to content

Interfaces · one hub instead of fifty wires · Fixed price

Your business runs on fifty tools. Do they talk to each other? We build the hub through which all systems exchange data cleanly.

Shop, CRM, ERP, accounting, shipping, warehouse. Usually each is wired directly to each. With five systems that is ten connections, with ten already forty-five. When a provider changes its interface, an order breaks off somewhere and nobody knows where.

We build a hub instead: every system delivers to one place and receives from one place. It translates between formats, retries when a system is not answering right now and shows where every order is at the moment. You own the code.

Discuss your systems What gets connected

Short conversation, fixed-price quote within five days, two to eight weeks to handover.

What you end up with

  • Every system has one place it delivers to and receives from
  • Nothing is lost when a system is unreachable right now
  • You see where every order, every enquiry and every invoice is stuck
  • When a provider changes its interface, one place is adjusted instead of ten

What we do differently

  • Built to fail safely

    Systems go down. The hub keeps the data, retries and gets in touch instead of quietly losing something.

  • The old languages too

    Modern interfaces are easy. We also talk to old ERP systems, banks and logistics standards.

  • Visible

    Every transaction is traceable. Where is the order, why is it stuck, who received what when.

  • You own the code

    No licence, no fee per transaction. Any developer can take it over.

The problem

When every system talks to every other.

The number of connections grows faster than the number of systems. That is technical debt that slows growth.

  • One change, many breaks

    The CRM gets an update and the sync with the ERP breaks. The shop switches provider and three connections have to be rebuilt.

  • Nobody sees where it is stuck

    An order does not arrive in the warehouse. Was it the shop, the transfer, the ERP? There is no log, only guesses.

  • Old systems get overrun

    Modern tools send hundreds of requests a second. A twenty-year-old ERP cannot take that and buckles.

The solution

One hub instead of fifty wires.

Systems deliver to the hub. It takes care of rules, translation and delivery. The source system does not need to know who receives the data in the end.

That is called decoupling: each side only knows the hub. When one side changes, one connection is adjusted, not all of them.

  1. Delivery with retries

    If the target system is unreachable right now, the order waits in a queue and is delivered later. Nothing is lost.

  2. Protection for old systems

    The hub buffers and spreads requests so even an old ERP keeps up.

  3. Translation

    The shop delivers one format, accounting wants another. The hub translates, sorts and cleans before anything reaches your master data.

  4. Log

    Every transaction has a trail: when it arrived, what became of it, where it was delivered, what went wrong.

What gets connected

We speak every language. The old ones too.

Typical systems and interfaces from finished projects. Any other with an interface works too.

  • ERP

    SAP, Microsoft Dynamics, NetSuite, Oracle. Also through the old XML interfaces many of them still speak.

  • CRM

    Salesforce, HubSpot, Pipedrive and others. Enquiries, contacts, deals in both directions.

  • Shop and payment

    Shopify, Shopware, WooCommerce, Stripe. Orders, payments, refunds.

  • Accounting and bank

    DATEV, bookings, incoming payments. Also through the standards banks require.

  • Logistics

    Carriers, warehouses, suppliers. Also through the exchange formats of the supply chain.

  • Messaging

    Slack, Teams, email. So the right person learns when something is stuck.

How it runs

From the system map to the handover

  1. one or two meetings

    System map

    Which systems exist, who delivers what to whom, where it breaks today. We draw it.

  2. within five days

    Fixed price

    Which connections in which order, what it costs, when it is done.

  3. two to eight weeks

    Build

    Hub, connections, translation, queues, log. With a test environment where your team checks along.

  4. one connection after the other

    Migration

    Old connections are only switched off once the new one is verified. No day without data flow.

  5. includes a manual

    Handover

    Complete code, manual, monitoring. Operation by your team or by us.

Prices

Fixed price per connection.

The price depends on the number of systems and how old their interfaces are. You get it within five days.

What you get

  • Hub and connections

    Build, the agreed connections, translation, queues, log, test, handover.

    by quote

  • Hosting

    Server at Hetzner in Germany, paid directly to the provider. No fee per transaction.

    EUR 10 to 40 per month

  • Further connections later

    Connecting a new system means building one connection, not ten.

    by effort

Afterwards, optional

  • Operation by us

    Updates, security, monitoring, adjustment when a provider changes its interface.

    monthly, cancellable

All prices net. You own the code.

Related

What builds on the hub.

  • Automating processes

    Once the data flows, workflows can run on it: invoices, messages, approvals.

    See automation

  • Reports

    Numbers from all connected systems on one page.

    See reports

  • Conversions back into the ad account

    Enquiries won in the CRM go back to Google and Meta with their value.

    See web tracking

  • Monitoring

    We notice when a connection stops before orders pile up.

    See monitoring

Common questions

Old systems, outages, operation.

Our ERP is twenty years old. Does that work?

Usually yes. Old systems speak old languages, often XML or file exchange. The hub translates and protects the old system from too many requests at once.

What happens when a system goes down?

The data waits in a queue and is delivered as soon as the system is back. You get a message when the queue gets unusually long.

Can we keep working with the existing setup while you build?

Yes. The hub is built next to the existing setup. Connections are migrated one after the other, each only after verification.

Do we need a new licensed tool for this?

No. The hub is built code that belongs to you, on a server you control. For simple workflows we use n8n, which is free for internal use.

Who maintains it later?

Your team, with manual and log, or we do in operation. Both work because the code is open and documented.

Next step

Stop maintaining twenty connections.

Tell us which systems you have and where it breaks today. We draw the system map and make a fixed-price quote.

Fixed price, complete code, servers in Germany.

Discuss your systems See custom software