Working with US clients, from Madrid

Where we work from

We have contracted workspaces in New York, Miami and Los Angeles, and no American company. Polargate is POLARGATE, S.L., a Spanish company registered in Madrid, and that is the entity you contract with, wherever the meeting happens. Those addresses are real places where we can receive post, sit down with you and be named in a contract, but they are not offices with local staff: the studio is two people, Pedro Ciordia, founder and CTO, and Andrés Ciordia, Chief AI Officer, with specialists from our network per project. What is real: a US client with a system in production, hotel software live in the Caribbean, and a working day that overlaps with New York, Miami and Los Angeles.

That is the honest answer. The rest of this page is what it means in practice.

The proof: a US client in production

We build and technically direct the CRM of a legal support services group in the United States. It runs on Odoo 18 Enterprise with a single custom module of ours that depends on nothing beyond Community modules: five new models, each with its permissions file checked and no gaps, plus extensions of the native opportunity, contact, activity and stage models.

The delivery chain is deliberately boring. A private repository, a managed Odoo project, and the client's production running on that same project. The test suite runs on every development and staging build. The promotion to production is always triggered by a person, by hand.

What is measured:

• 15 deliverables completed in five weeks and consolidated into a handover document.
• 99 tests of our own, green, starting from zero tests.
• 313 ms to read the new fields across 400 real production opportunities, checked so that no loop or heavy query slipped in.
• 10 to 15 minutes from merge to the live version in production.
• A reproducible migration rehearsal in a container: 132 rows and 56 relations across 200 records survived the upgrade, and the rollback gave back both the code and access to the data.

That client is NationwideLegal, and they are named here because they agreed to it. Every other client is named only when they say yes. Naming a client is the client's decision, not ours.

How the work gets audited

That system went through an adversarial audit: 41 agents, 2.3 million tokens, 17 findings, with two independent skeptics challenging each finding before it was accepted as real. The first phase of that method is not reading code. It is running the scenarios against a real environment while impersonating the affected user, and writing down the state before and after every write. Validating permissions with an admin account proves nothing, because the admin bypass exempts it.

The Caribbean, on east coast time

Our hotel platform is in production with real guests in two Caribbean hotels, one of them since August 2026. Tenant isolation there is not a claim, it is a test: row level security on every table carrying a hotel id, plus a guard that discovers hotels and tables instead of listing them by hand. Verified in August 2026 across two real hotels with no cross tenant leak, across 81 watched tables, and it runs in continuous integration.

Those hotels sit on UTC-4 all year, so they match New York in summer and run an hour ahead of it in winter. That work already happens in American office hours, and it is already billed from Spain as a service to a company outside the European Union.

Working across the time difference

Madrid is six hours ahead of New York and Miami, and nine hours ahead of Los Angeles.

East coast

The overlap is the second half of our day and the first half of yours. Calls, demos and decisions fit in there without anyone having to get up at five.

West coast

Only the edges of the two days touch, so the work has to survive the night. That means decisions in writing, a weekly reference document that we issue, and releases pushed to production by hand at a moment that suits your day rather than ours.

What we do not promise

No 24/7 desk, no on-call rota, no US phone line and no local account manager: the workspaces in New York, Miami and Los Angeles are places to work and to meet you, not teams sitting there waiting for your call. If you need a response window, we agree it in the contract, where it is an obligation instead of a slogan.

Languages

English, Spanish and Dutch. Work for US clients is delivered in English by default: documents, tickets and code. If your team in Miami works in Spanish, or your operation sits in Latin America, that is the same two people continuing in another language, not a handover to another team.

What we take on

• Building the product. Web, native app and backend on one stack: Vite, React, TypeScript, Tailwind, Supabase with row level security, Vercel, and Capacitor with self hosted over the air updates. The backend always lives on infrastructure owned by you or by us, never on a managed third party backend you would have to migrate off later.
• Technical direction of a system you already run. The US case is exactly that: an ERP and CRM that already existed, with its access model, its migrations and its release discipline rebuilt around how the team actually sells.
• Operation after go live. A client portal, tickets fed by verified inbound email, and an hours bundle settled live from the real time sheets.

How to start

Fill in the brief at /start with what you have today and what needs to happen. The first call goes in your morning. Then scope and priority in writing before anything is added to the list, and a weekly document that we issue, so that nobody has to reconstruct the state of the project from a chat thread.