AI engineering for US engineering teams
Last verified: July 2026· regulatory detail
What actually constrains US teams
There is no comprehensive federal AI statute. What exists instead is a patchwork: state laws (Colorado’s AI Act and California’s transparency and privacy rules are the ones most often cited), sector regulators applying existing authority, and the FTC treating deceptive AI claims as it treats any other deceptive claim.
For most engineering teams, though, the thing that actually changes the roadmap is not a statute — it is the enterprise security questionnaire. Your customers ask where their data goes, whether it trains a model, whether you can evidence what the system did, and whether a human is in the loop. Those answers are engineering artefacts, and teams that lack them lose deals long before a regulator ever appears.
If you sell into the EU, the AI Act reaches you regardless of being a US company — see our EU page for the amended timeline. That is increasingly the forcing function for US teams: the deadline arrives via a European customer, not a US regulator.
Where your data can sit
- US regions on the major clouds where data must stay onshore, including GovCloud-style isolation where that is the requirement.
- Zero-retention and no-training configurations are available from most major providers, but they are per-account and per-route settings — we verify rather than assume.
- Self-hosted inference for teams whose customers will not accept a third-party processor at all.
- Prompt egress and retention are the questions security reviews actually ask. We make the answer demonstrable instead of aspirational.
What US teams come to us for
Spend that scales faster than revenue
The dominant US engagement is cost. Usage-based AI spend compounds quietly, and the first serious look almost always finds 30–60% — routing, caching, and batching behind evals so nothing regresses.
Passing the security review
Enterprise buyers now ask AI-specific questions: data flow, retention, training, evidence, human oversight. The work is redaction at the boundary, traces, and a defensible architecture — the same infrastructure that keeps quality honest.
The EU deadline arriving via a customer
US teams increasingly inherit AI Act obligations through a European customer. Article 50 transparency lands 2 August 2026 and reaches you if your output is used in the EU.
How working together works
- Contracting
- With Neul Labs Limited (Scotland), invoiced in USD. W-8BEN-E on file; your AP team has seen this shape before.
- Overlap
- A solid afternoon overlap with US East Coast and a morning block with the West Coast, agreed at kickoff so reviews are not a 24-hour round trip.
- Security review
- We work under your NDA, MSA and access rules, and prefer read-only access for audits.
- On-site
- Remote by default; travel where a workshop or kickoff genuinely earns it.
Frequently asked questions
Is there a federal AI law we need to comply with?
No comprehensive federal AI statute exists. You are dealing with a state patchwork — Colorado and California are the ones most commonly cited — plus sector regulators using existing authority, and the FTC on deceptive claims. In day-to-day practice, the constraint that actually moves roadmaps is the enterprise security review, not a statute.
Does the EU AI Act apply to a US company?
It can. The Act applies based on the EU market and on where system output is used, not on where you are incorporated. If you place an AI system on the EU market or your output is used there, you can be in scope. For many US teams the AI Act arrives as a customer requirement rather than a regulatory letter.
How does the timezone actually work?
We are UK-based, so East Coast teams get a solid afternoon overlap and West Coast teams a morning block. We agree the window at kickoff and keep reviews inside it, so feedback is same-day rather than a 24-hour round trip. Async-by-default artefacts — written findings, PRs, runbooks — do the rest.
Can we contract and pay in USD?
Yes. You contract with Neul Labs Limited, a company registered in Scotland, invoiced in USD with a W-8BEN-E on file. It is a shape most US AP and procurement teams have processed before.
Regulatory detail on this page was verified in July 2026 and is a summary for engineers, not legal advice. Rules change — confirm your specific obligations with counsel before relying on them.