Skip to content
Zorix Systems — software that powers your business

Markets · United States

US organisations, UK engineering, deliberate overlap

US clients come to us for the same reason UK clients do: a configured platform has hit its ceiling and the operation now runs on exports, workarounds and spreadsheets. What differs is the regulatory frame, the vendor landscape and the clock.

We are honest about the clock. We have no US office. We staff US engagements so that a named architect and delivery lead are reachable through the Eastern and Central working morning, and we plan the cadence around that window rather than claiming follow-the-sun coverage.

Contracting

How US engagements are structured

Entity

Software Systems Limited, company number 14466340, United Kingdom

Governing law

English law by default; alternative governing law considered on request

Overlap

Four to five hours with Eastern time, three to four with Central

Data residency

US regions of AWS or Azure, or your own tenancy

Healthcare

Business Associate Agreement signed where our role requires one

Intellectual property

Assigns to the client on payment, including source code

Vendor landscape

The US systems we integrate with

Healthcare work in the US means FHIR R4 and HL7 v2 against Epic and Cerner endpoints, SMART on FHIR authorisation, and eligibility and claims transactions in X12 formats. Financial and commercial work means Stripe, Plaid, Salesforce and NetSuite far more often than their UK equivalents. Property and field operations work means different address, tax and jurisdiction models than a UK-built system assumes.

We treat the integration surface as the primary cost driver in any estimate, which is why we map it explicitly during discovery instead of quoting from a feature list.

How we approach integration

Working with us

What a US engagement looks like

A fixed-fee discovery sprint runs first, delivered largely over video with a written architecture document, integration map, phased estimate and risk register at the end. Build then proceeds in two-week iterations with fortnightly demos scheduled in your morning, a staging environment available from sprint one, and written sprint notes so nothing depends on having attended a call.

Engagement models

Questions

Frequently asked

Do you have a US office?

No, and we will not pretend otherwise. US clients contract with our UK entity and are served by UK and Germany-based technical leadership with engineering capacity across our delivery network. If a US contracting entity is a hard procurement requirement, tell us early and we will say plainly whether we can meet it.

How much working-day overlap do we get?

Eastern time shares roughly four to five hours of the UK working day, and Central roughly three to four. We schedule stand-ups, demos and steering meetings inside that window, and we do not promise Pacific-time coverage we would have to staff artificially to deliver.

Can you work under HIPAA?

We build systems for covered entities and business associates and will sign a Business Associate Agreement where our role requires one. Technically that means US-region hosting, encryption at rest and in transit, minimum-necessary access controls, audit logging of PHI access, and documented breach notification behaviour. We are engineers, not your compliance counsel, and we work to the interpretation your privacy officer sets.

Where would our data be hosted?

US regions of AWS or Azure, or your own tenancy. Where any engineering access from outside the US is required, it is contractually controlled and logged, and the access model is agreed during discovery rather than assumed.

Tell us what your systems are doing wrong.

Send the problem, not a brief. We will tell you whether it is a project we should be involved in.

Talk to us