The operating system behind a real US launch.

Remote execution breaks in predictable ways.

Three things break at the same time when US work becomes real:

• Context sits abroad. US customers, providers, and employees need fast answers, but the knowledge lives at headquarters, hours away.
• Authority is unclear. The local team hesitates because nobody knows which decisions can be made in the US and which must return to the founder.
• Dependencies stay hidden. Entity, banking, employment, and compliance work overlap, and nobody owns the order.

The result is the US Expansion Wall: demand keeps growing while execution waits.

Sending a trusted manager from headquarters does not solve it. Loyalty is not local fluency, and the transplant becomes one more person waiting for home to wake up.

Three layers: decisions, rhythm, infrastructure.

Decision rights. A written contract of authority with two sides. You own strategy and product: pricing, brand, roadmap, and global direction stay yours and are not mine to change. I own execution and sequencing: how and when things happen in the US, the local calendar, the setup order, and the compliance requirements. Within that division, the rules state which decisions I make locally, which need your approval before money, people, or customer promises move, and which questions go to licensed professionals. Exceptions, delays, and risk flags have a defined escalation path. The rules bind both sides: my thresholds are written, and so are your response times, so nothing waits in an inbox across an ocean.

Weekly operating rhythm. One recurring review of everything in motion: owners, blockers, deadlines, next actions, escalations. You see the whole launch on one page, every week, instead of chasing updates across time zones.

Operating infrastructure. The five areas of practical setup a US operation runs on: entity, banking, and finance; employment and contractors; service delivery and customer commitments; security and compliance; and provider coordination across all of them. The system keeps these areas sequenced and connected, so work in one area does not silently block another.

Two tracks, one pace.

A US launch runs on two dependent tracks at the same time: the commercial track (adapting sales, contracts, and service to how US buyers actually operate) and the infrastructure track (the entity, banking, payroll, insurance, and compliance that make the company real). Only sales, and you hit a compliance wall; only administration, and you burn cash without revenue.

My continuous job is keeping the two at the same pace, with the infrastructure built exactly one step ahead of the business. Not too late, and not too early. That is what the tagline means: build the infrastructure before you scale, and do not build far beyond what the business can use.

The work becomes visible through ordinary, disciplined tools.

No proprietary software and no black box. The system runs on working documents any executive will recognize, kept accurate week after week:

• Decision rights map: who decides what, in writing
• Weekly scorecard: active work, owners, blockers, deadlines
• Dependency tracker: open items across all five infrastructure areas and every provider
• Risk register: what could go wrong, its likely impact, its owner, and the mitigation
• Customer promise map: what you have committed to US customers, and the capacity behind each commitment
• Security and compliance knowledge base: the answers that customer and vendor reviews keep asking for
• Provider map: which lawyer, accountant, or specialist owns which question, and the escalation path
• Migration readiness plan: what can move to the US now, and what must wait

The value is not the documents. It is that they are current, owned, and reviewed every week, which is what turns scattered expansion work into an operation.

Delegation with written limits.

The system is not "trust me." The authority I hold is written and bounded: spending limits, founder approval points, a second review for high-risk decisions, and clear escalation rules. At any time you know exactly what I can decide, what I will bring to you, and what goes to the professionals.

Where this leads: you do not stay dependent on me.

The Stateside Operator is the initial execution owner, not the permanent center of your US office. The foundation I build is designed for handover: as the operation stabilizes, your own veterans and your local hires, what the method calls the Landing Team, take over the running of it, carrying your company's culture into the US office and carrying US market reality back to headquarters. I build the infrastructure; your people scale it. A launch that ends with the company dependent on one outside person has failed one of its own readiness checks, and the system is built to prevent exactly that.

The system is installed on a 135-day schedule.

When we engage, the system runs through the 135-Day US Launch Sequence: assess the wall, build the operating infrastructure, then migrate only what is stable enough to hold local responsibility.

See the full 135-day path

I built this by doing the job.

Every element on this page comes from work I actually did at ALM Works, from first US employee to COO to a successful sale. The method is not licensed from anyone and not adapted from a book. When you engage me, the system and its author come together.

The full story

Read the complete method: The Foreign Founder's Guide to a US Launch (free PDF, no email required)