Customer & partner portals
Self-service for customers, partners and suppliers instead of email threads and PDF forms — connected to your ERP, CRM or core system.
Service 03
System integrations and APIs that keep your data consistent — and tell you when they don’t
Most integration pain is invisible until month-end: orders that did not sync, customers duplicated in two systems, a partner feed that silently stopped. We design integrations as products — with contracts, monitoring, retries and an audit trail.
Problem
Why integrations are where mid-sized companies bleed
A typical 200-person company runs an ERP, a CRM, a shop or portal, a payroll system, a ticketing tool and three to ten SaaS products. Each pair is connected by a script, a plug-in, a nightly export or a person. Nobody owns the whole picture; every change to one system risks the others.
The cost shows up as reconciliation work, wrong data in customer-facing channels and projects that stall because “the interface is not ready”. With the right architecture — an integration layer with clear contracts — each system can change without breaking the rest.
When to bring us in
- You are introducing a new ERP, CRM or shop and need it connected to everything else.
- Manual re-typing or Excel exports move data between systems today.
- A partner, marketplace or regulator requires an API or data feed from you.
- Existing point-to-point integrations break regularly and nobody knows why.
- You need an SAP or Microsoft Dynamics system to talk to a custom application.
Approach
How we build it
Integrations are engineering, not configuration. We treat them with the same rigour as any production system.
Integration map and contracts
Discovery produces an inventory of systems, data owners, flows, volumes and failure modes — and a target design: which system is master for which data, synchronous vs event-driven, and how errors surface.
Build the backbone
Depending on scale: direct REST/SOAP integration, a lightweight integration service, or a message broker (e.g. RabbitMQ, Kafka, cloud-native queues). Idempotency, retries and dead-letter handling are in from day one.
Observability
Every flow has metrics, logs and alerts. A dashboard shows what synced, what failed, and why — readable by your operations team, not just engineers.
Public or partner APIs
Where you expose data to partners, we design the API contract (OpenAPI), authentication, rate limits, versioning and documentation — so partners can integrate without calling you.
Deliverables
What you get
- Integration architecture document with system-of-record decisions and data-flow diagrams.
- Integration services or middleware configuration, with automated tests against recorded interface data.
- Error handling with retries, alerts and a replay mechanism; monitoring dashboards.
- Partner/customer APIs with OpenAPI specification, authentication and documentation.
- Infrastructure as code, CI/CD, runbooks; all in your accounts and repositories.
Indicative range
- Investment
- CHF 25,000 – 100,000
- Duration
- 1 – 3 months per integration programme
Indicative, for planning. Individual integrations can be smaller; an integration layer for a new ERP is usually larger. The discovery sprint produces a fixed price. How pricing works →
Typical technology
Java/Kotlin or Node.js services; REST, SOAP, OData, EDI, SFTP as the interfaces demand; message brokers where volume or decoupling requires; PostgreSQL for state; OpenAPI; OpenTelemetry-based monitoring. The founder’s background includes SAP (2019–2022) and Deutsche Börse (2014–2018), environments where interface reliability was not optional.
A representative engagement
Illustrative scenario — not a client case study
Before
A distributor receives orders from a web shop, two marketplaces and EDI from key accounts. Four scripts written by former employees push them into the ERP; failed orders are noticed when customers call.
After
One integration service receives orders from all channels, validates and normalises them, writes them to the ERP with idempotent retries, and alerts operations on failures with a one-click replay. Stock and prices flow back to the channels every few minutes.
We publish real case studies only with written client permission. Until then, this section shows the shape of the work, not a result we claim.
Led by a software engineer (since 2008) with roles at
- Deutsche BörseGerman stock exchange, 2014–2018
- SAPSenior Software Engineer, 2019–2022
- UnbluSenior Software Engineer, 2022–2024
- InfosysSoftware Engineer, 2008–2012
Founder’s employers — not Monolith clients.
FAQ
Common questions
Do you integrate with SAP?
Yes — via OData/REST APIs, IDocs/RFC where necessary, and SAP BTP where the customer uses it. We do not do ABAP development inside SAP; we build the systems around it and the integration layer.
Should we buy an iPaaS (Boomi, MuleSoft, Make, n8n) instead?
Sometimes. For many simple SaaS-to-SaaS flows, an iPaaS is faster and we will recommend one. Custom integration services win when flows carry business logic, need transactional guarantees, high volume, or when per-task pricing becomes expensive. The assessment gives you a recommendation with reasoning.
Who operates the integrations after you leave?
Your team, with our runbooks and dashboards — or us, under a support retainer with defined response times. Either way, you own the code and accounts.
Can you fix our existing, undocumented integrations?
Usually. We start with a short diagnostic (fixed fee): document what exists, add monitoring so failures become visible, then decide what to stabilise and what to replace.
Other services01 02 04
Related services
Internal tools & workflow automation
Replace the spreadsheet, Access database or email loop that your operations secretly depend on with a tool built for the job.
Legacy modernisation
Move off the application nobody dares to touch — incrementally, with the business running, instead of a big-bang rewrite that never ships.
Which systems need to talk to each other?
List them, tell us what data flows and what breaks today. You receive a written assessment within two business days.