Identity, data, file-based, and event-based. Each with its own failure modes — and its own defaults.
Enterprise identity that survives a procurement review.
Warehouse-centric where possible, point-to-point where required.
The protocols your enterprise customers still use, done correctly.
At-least-once delivery, signed payloads, replayable history.
Each integration ships with its own observability, runbook, and customer-facing status.
Written API contracts for every connection — versioned, deprecation policy stated, change-control process named.
Self-service or assisted: customers configure their own SSO, webhook endpoints, SFTP credentials, schemas — with a UI for the support team to assist.
Every integration supports replay of historical events and backfill of historical data. Tested end-to-end before launch.
Daily/hourly reconcile that compares source-of-truth counts against integration delivery counts. Alerts when drift exceeds threshold.
We name the engineering contact at each vendor and maintain it. When something breaks at WorkOS or Stripe, we’re already in their Slack.
Docs your buyers can read and your support team can point to. Code samples in two languages minimum.
From a single critical link to a full integration platform with customer self-service.
Integrations are typically simple to demo and hard to operate. The process is built to surface the operating story before launch.
Written contract per integration: payload, semantics, retry policy, idempotency, security. Reviewed with the partner system’s team.
Code, infra, dashboards, alerts. Customer-facing replay UI. Reconciliation report running in staging.
Live with one partner, watched closely for two weeks. Reconcile drift, latency, error patterns measured against the contract.
Cleanly transferred with runbook + on-call playbook — or kept on by us for ongoing partner additions.
If something isn’t answered here, ask in your intro email — we keep this list short on purpose.
Yes. Three current clients on FHIR R4 with HL7 v2 legacy. We have BAAs in place and have shipped to two health systems and one EHR partner.
Yes, with caveats. ISO 20022 we’ve shipped. SWIFT we’ve integrated through a partner BIC — direct SWIFT membership is its own program we don’t take clients through.
Yes — month 2 onward typically becomes lower-headcount maintenance. Or you can take it over with a 2-week pair-handoff.
Yes — both X12 (US-centric) and EDIFACT (international). We’ve shipped 850/855/856/810 cycles for retail, and 837/835 for healthcare claims.
Send a paragraph about the problem. We’ll come back inside 48 hours with a written take — team shape, cost envelope, riskiest assumptions.