Integrations
Most software projects don't fail on the shiny parts. They fail on the wiring.
Our job is the wiring — the middleware, the auth flows, the queues, the reconciliation logic that has to be right or nothing else matters.
SAP, Abacus, Bexio, Odoo. Salesforce, HubSpot, Dynamics 365. Shopify, Shopware. Twint, PostFinance, SwissSign. And the twenty-year-old system nobody wants to name in a slide deck.
Getting the CRM, the ERP, the shop and the marketing tool to agree on what a "customer" is — and stay agreed at 03:00 on a Sunday.
Webhooks that survive replays, queues with real retry policies, event buses that don't lose messages during a deploy. The boring reliability nobody demos.
SSO with the corporate Azure tenant, OAuth against a partner API, records that stay consistent across five systems and one hostile CSV import.
When no product fits, a tightly-scoped service that does the one thing needed — deployable, documented, handed over. Not a platform we hope you'll never leave.
You already have a shape of engagement your client bought. One of these four almost always slides in as a subcontract without redrawing your commercial model.
Integration Assessment
001
You need a number in your proposal by Friday. The scope is half-written and the client is a partner of a partner. We give you a one-pager you can put in your quote — architecture, effort band, risks, dependencies — usually inside a week.
- Technical feasibility
- Architecture proposal
- Key risks & assumptions
- Dependencies
- Initial effort estimate
- Recommended delivery approach
Fixed-Scope Integration
002
The scope is real, the number is real, the deadline is real. We deliver against acceptance criteria, hand over the code and the documentation, and stand behind it for a warranty period. Overruns come out of our margin, not yours.
- Agreed scope
- Estimated timeline
- Defined deliverables
- Acceptance criteria
- Documentation & handover
- Warranty period
Integration Rescue
003
Somebody else built it, it worked, and now it doesn't. Orders are stuck, invoices are duplicated, the vendor API changed and nobody read the deprecation notice. We diagnose, stabilise and either hand it back documented or keep it under maintenance — your call.
- Technical assessment
- Root-cause analysis
- Stabilization proposal
- Implementation
- Monitoring
- Ongoing maintenance
Maintenance & Support
004
Any integration we build (and often ones we didn't) can move onto a monthly retainer. Defined response times, one shared ticket queue, a monthly report you can forward straight to your client. Full detail on the Maintenance page.
- Incident resolution
- Dependency updates
- API version changes
- Monitoring
- Small improvements
- SLA-based response
Send us the brief before you write the number. We'll come back with an approach you can quote confidently — or tell you straight it's not our thing.
Discuss a Project