Ship Shift

AI consulting for US companies

Ship Shift is a Barcelona-based AI engineering team for US companies: agents, document automation and integrations in production — GDPR-grade contracts, indicative East Coast overlap, no US office claim.

Updated: 17/11/2026

Consultoría de IA aplicada

Why companies in the United States work with us

US companies hire us as a European AI engineering team: GDPR-grade privacy habits, production delivery, and afternoon Barcelona / morning East Coast overlap for live sessions — without pretending we are a Delaware-headquartered consultancy.

Finance, legal, media and software teams share document and workflow debt. We automate the boring path and keep humans on exceptions.

We are an AI consulting firm with engineering based in Barcelona — not a local office network. The offer is production systems (agents, document AI, process automation) under European privacy standards, delivered remotely with async rituals. We never claim a team or clients based in the United States unless published with permission.

Ship Shift builds software that writes into the tools your staff already use. That is the opposite of a slide-deck pilot. See our global English hub at ship-shift.com/en for the shared service catalogue; this page is the the United States market frame.

Buyers in the United States usually arrive with one of three pains: documents that never become structured data, customer channels that re-type the same answers, or AI pilots stuck in a sandbox with no ERP write-back. We scope the thinnest slice that moves a KPI, then expand. That discipline matters more than a long list of model names.

We also decline work that requires inventing a local office story for procurement theatre. If your RFP demands a registered address in the United States, we will say clearly that our legal seat is in Spain and that delivery is remote-first. Honesty keeps Search and sales aligned.

AI adoption and the the United States economy

We describe demand drivers — enterprise software, professional services, and multi-state operations — without inventing Census Bureau percentages. When we cite a figure it will include an official URL. Until then, sector narrative only.

City pages for the US will appear only with unique sources (oleada discipline). This hub stands alone first.

Whatever the sector mix in the United States, the engineering pattern repeats: capture unstructured input, validate critical fields, write to the system of record, and leave exceptions in a human queue. Marketing copy about «AI transformation» without those steps is noise. We document owners, metrics and go/no-go gates so the pilot can be killed or scaled on evidence.

What we build

Six frequent entry points. Full catalogue: AI services (shared English pages — we do not duplicate every service under each market prefix).

Also available: internal document assistants, predictive data work, custom software, ERP/CRM integrations, training, and generative-AI rollout programmes for the organization.

Regulation and data protection in the United States

There is no single federal general AI law. State laws are evolving. Example: Colorado SB26-189 was signed on 14 May 2026, revising the prior AI statute, delaying obligations to 1 January 2027, and focusing on disclosure/transparency for automated decision technologies. Treat this as an illustration, not a 50-state map.

Contracts can still adopt GDPR-grade processing terms for EU personal data. Your US counsel owns statutory interpretation.

Not legal advice. Verify with counsel and official publications before relying on any summary.

How we work across time zones

Indicative clocks only — OverlapHours does not publish a fixed coverage commitment.

Default stack: video calls, Slack or Teams, weekly written status, and human queues where risk requires them. Methodology: five phases with go/no-go when the English page is available, otherwise the Spanish methodology page. We do not promise on-site travel calendars here.

Async does not mean invisible. Weekly written status lists what shipped, what blocked, and what decision is needed from your side. That rhythm suits the United States stakeholders who cannot spend every afternoon on a call with Barcelona. When live overlap exists, we use it for workshops and demos — not for status theatre.

Case studies

Published patterns — without claiming the client sits in the United States:

Use these cases as proof of engineering style, not as proof of a local client roster in the United States. If a future case is cleared for geographic naming, we will update the page with permission — never with invented geography.

Cities we publish in the United States

No US city pages in this wave — by design, to avoid doorway spam. Ask if you need a scoped remote engagement from a specific metro.

How we choose US engagements

US buyers often compare onshore studios with overseas vendors. Our position is European engineering with GDPR-grade processing habits and production delivery — not a cheaper slide deck. We do not claim «always cheaper» or publish USD rate cards here.

State AI laws differ; Colorado SB26-189 is one cited example with dates and a bill URL. We will not pretend to map all fifty states on this page. Counsel owns interpretation; we own technical controls and documentation.

No US city doorways in this wave. If a metro needs a page later, it must carry local sources and pass similarity checks. Until then, /en-us/ is the market entry.

East Coast mornings / Barcelona afternoons support workshops; async covers the rest. OverlapHours does not equal an SLA. White-label partners welcome via the dedicated service page.

American English spelling (organization, optimization, consulting) is intentional. Healthcare buyers: we do not claim HIPAA certification on this page — scope compliance explicitly if needed.

Never IP-redirect US visitors away from other market hubs; Google crawls from the US and must still see Spain, UK, Ireland and LATAM versions.

Agencies and software firms in the US can white-label our engineering when they need production AI without hiring a full ML team. The end customer sees their brand; we stay the build partner. That model also avoids pretending we run a US payroll.

For multi-state operators, we keep configuration and policy packs explicit so the same agent does not silently mix jurisdictions. Your counsel still owns legal mapping; we own the technical seams.

Typical US entry projects: internal knowledge assistants with directory permissions, document extraction into CRM/ERP fields, and customer-support drafts that cite approved policies. We measure deflection and error rates, not vanity demo scores. If HIPAA, GLBA or other sector rules apply, they must be named in the statement of work before build starts.

Oleada discipline: New York, Miami or Austin pages appear only with local sources and similarity checks. This hub must index and earn impressions first.

American buyers should expect explicit statements of work listing systems in scope, data classes, and acceptance tests. We refuse vague «AI transformation» retainers without a production target. That filter keeps both sides honest.

Final note for the USA: /en-us/ joins the reciprocal market hreflang set with x-default /en/. No city URLs in this wave. Footer market selector is voluntary — never an IP redirect. Updated 17/11/2026. Security baseline: least privilege, no secrets in prompts, human approval before irreversible writes. Ask for a sample acceptance-test list before kickoff. Prefer a thin production pilot over a wide deck.

Extra USA note: multi-state operators should expect explicit policy packs so the same agent does not silently mix jurisdictions. We document technical seams; counsel still owns legal mapping. That split keeps Search claims and sales decks aligned with what engineering can actually ship.

Contact details (NAP)

SHIPSHIFT, S.L. (Ship Shift brand)
C/ Fra. Arquitecte Josep de la Concepció, 6
43800 Valls (Tarragona), Spain
Tel. +34 632 50 61 35 · info@ship-shift.com

Service area: the United States. One legal seat in Spain; we do not publish a LocalBusiness for other cities.

Frequently asked questions

Do you have a US office?

No. European AI engineering from Barcelona for US companies. No LocalBusiness outside our Spanish legal seat.

American or British English?

American English on en-us (organization, optimization, consulting).

What about state AI laws?

US rules are state-driven and evolving. Example: Colorado SB26-189 (signed 14 May 2026) with obligations from 1 Jan 2027. Not legal advice.

East Coast overlap?

OverlapHours shows indicative Barcelona/US clocks. We do not commit to a fixed coverage window on this page.

Pricing in USD?

We do not publish billing currency or rates here.

HIPAA / healthcare?

We do not claim HIPAA certification on this page. Healthcare projects need an explicit compliance scope.

Can agencies white-label your engineering?

Yes — see our white-label AI engineering service.

How to start?

Contact /en/contact?origen=en-us with the workflow to automate.