Ask a founder in Beirut, Cairo, or Amman where their company is registered, and there is a rising chance the answer is a small US state most of their customers could not place on a map. Wyoming. Sometimes Delaware. Almost never the country they are sitting in.

This is not tax theater, and it is not, for most of the people doing it, an attempt to leave anywhere. It is a practical response to a specific and well-understood problem. Building an internet business from much of the MENA region means fighting your own financial infrastructure every single week. The dual-jurisdiction model, a US entity on paper with real operations on the ground, has gone from clever workaround to quiet default. Here is why, how it is actually done, and the cases where it is the wrong move.

The problem it solves

Start with the thing nobody outside the region fully appreciates. For a digital business, the hard part is rarely the product. It is getting paid, holding what you are paid, and paying other people, reliably, in a currency that will still be worth roughly the same next quarter.

Three pressures stack up.

Payment rails. Most global payment processors, the ones your customers expect to see at checkout, either do not support businesses registered in much of the region or support them with restrictions that make ordinary operations awkward. Stripe is the default for software businesses; PayPal Business remains common for e-commerce and international consumer payments. Neither is accessible on ordinary terms without an entity in a jurisdiction they recognize. If your customers are international and you cannot plug into the processor they assume, you are losing sales at the most expensive possible moment: the one where someone has already decided to buy and simply cannot hand you their money.

Banking. A business bank account that can send and receive internationally, hold a stable currency, and not freeze on an unexplained compliance review is not a given. Founders describe spending real, recurring management attention on simply keeping money moving. That is attention a founder in a different jurisdiction never has to spend, and it does not show up on any income statement.

Currency. In several MENA economies, including Lebanon, Sudan, and Yemen, holding revenue in the local currency is itself a risk position. Money earned can lose value between being earned and being deployed. That turns every delay in the financial stack into a small, quiet tax on the business. Even founders in comparatively stable markets, Jordan, Morocco, Tunisia, find that invoicing and holding dollars or euros is simpler than managing the FX conversion on every payment cycle.

None of these is fatal on its own. Together they form a constant drag. The US LLC is, more than anything, a way to stop paying that tax on attention.

What the model actually is

The structure is simpler than it sounds. A founder registers a limited liability company in a US state. That entity becomes the contracting party. It signs with customers, holds the bank account, plugs into the payment processor, and owns the intellectual property. Meanwhile the actual work, the team, the founder, the day-to-day, stays exactly where it was.

The US entity is not a head office. It is a financial and legal interface. The company operates from Beirut or Cairo. It transacts through Wyoming. The two facts coexist, and most of the time they coexist without anyone needing to think about them.

Worth stating plainly, because the model is easy to misread: this is not relocation. The founders doing it are, overwhelmingly, staying. They are hiring locally, living locally, and building where they always were. They have simply moved one layer of the company, the money layer, onto ground that does not shift under it.

Wyoming or Delaware

Two states come up. They are not interchangeable.

Delaware is the default for companies that intend to raise venture capital. Its corporate law is deep and predictable, and US investors are fluent in it. A Delaware C-corp is what an institutional term sheet expects to see. The cost of that fluency is overhead: franchise tax, more involved annual filings, and a structure that is genuinely heavier than a very small company needs.

Wyoming is the default for the founders this article is about. A Wyoming LLC is inexpensive to form and to keep. The annual obligations are light, the privacy protections are stronger, and there is no state income tax. For a bootstrapped software business, a small services firm, or a product company with no near-term plan to raise a US round, Wyoming is almost always the right call.

The rule of thumb is unglamorous but reliable. Raising US venture money soon: Delaware C-corp. Everything else: Wyoming LLC.

The US entity is not a head office. It is a financial interface. The company operates from Beirut and transacts through Wyoming. Both are true at once.

How it is actually done

The mechanics are more routine than founders expect. In rough order:

  1. Form the entity. A registered agent in the chosen state files the formation documents. Formation services have made this a commodity. Stripe Atlas is the most recognized option, though its default setup points toward a Delaware C-corp with bundled banking; founders who want a Wyoming LLC specifically should confirm that path before paying. Firstbase is faster for solo founders and cheaper. Doola targets non-resident founders explicitly, with onboarding that accounts for the MENA context. Clerky produces the highest-quality legal documents and is preferred by YC-track founders, but it is slower and more expensive than the others.
  2. Appoint a registered agent. US states require a local address to receive legal mail. Northwest Registered Agent is the quality default, at roughly $125 per year. Harvard Business Services is cheaper but lower-touch. The formation services above typically bundle a registered agent for year one, then charge annually after that.
  3. Get an EIN. The Employer Identification Number is the company’s US tax identifier. Non-US founders without a Social Security number file IRS Form SS-4 and submit by fax or mail to the IRS international desk. At current backlogs, that takes four to six weeks. Some formation services handle the EIN application as part of their package, which saves the friction of dealing with IRS correspondence in a foreign timezone. Start this step first, in parallel with everything else, because it is the long pole.
  4. Open banking. Mercury is where most non-resident-owned LLCs land in 2026. It was built with exactly this customer in mind, accepts EIN-only applicants, and integrates cleanly with Stripe and other processors. Brex has tightened its non-resident requirements and is harder to open from MENA than it used to be. Relay is a quieter alternative that still accepts non-resident applicants. Wise Business handles multi-currency operations well once the LLC is funded, but it is not a substitute for a primary US business bank account.
  5. Connect payments. With a US entity, an EIN, and a Mercury account in place, Stripe becomes available on ordinary terms. For founders selling software subscriptions or SaaS, that is almost always the destination. Founders who want to avoid managing US sales-tax compliance across fifty states should consider Paddle or Lemon Squeezy, both of which operate as merchant of record, meaning they collect and remit tax on your behalf. Paddle is more established and better suited to larger SaaS businesses; Lemon Squeezy is simpler and targets digital downloads and smaller subscription products.

The recurring cost of the whole structure is real but small. State fees, registered agent, and annual compliance together run in the low hundreds of dollars per year before accounting fees. Measured against the weekly friction it removes, that is not a close call.

The patterns we see

The model is not one thing. It shows up in several recognizable shapes.

There is the solo product founder. One person, a software product, customers worldwide. They need the US entity purely to access Stripe, and they never think about the structure again after month one.

There is the small services firm that bills international clients and simply could not get paid cleanly on local infrastructure. One example we keep encountering is a Wyoming-registered agency operating out of Beirut, with its whole team in Lebanon, using the US entity solely so that international clients can pay it the way they pay any other vendor. Nothing about the company is American except the line on the invoice. That is the model working exactly as intended: boring, legal, and quietly load-bearing.

There is the regional startup that fully intends to raise later and registers in Delaware early, so it does not have to redo the structure under deal pressure with a closing date looming. Clerky is popular here because investors doing diligence want clean documents.

There is the distributed team. A founder in the Gulf, engineers in Cairo, a designer in Amman. No single local jurisdiction fits everyone, and a neutral US entity becomes the least-bad common ground.

Different founders, same underlying move. Put the money layer somewhere stable, and leave everything else at home.

When it does not work

The model is genuinely useful, which is exactly why it gets oversold.

If your customers and revenue are entirely local, you may be adding a US tax and compliance surface for benefits you will never use. A company that sells only within its own country, in its own currency, to customers who pay through local rails, often should just be a local company. The US entity solves cross-border problems. Without a cross-border problem, it is pure overhead.

If you cannot keep up with the compliance, the structure turns against you. A US LLC has annual obligations: state filings, US tax filings even when no US tax is owed, and bookkeeping that an accountant who understands non-resident-owned LLCs needs to handle. Founders who form the entity and then ignore it create a slow, compounding problem that surfaces at the worst time, usually when the company next needs to look clean for a bank or a buyer.

If you are doing it to disappear, reconsider. The structure is legal, ordinary, and increasingly common, but it is not opacity. It works because it is transparent and well-documented. Treat it as a clean interface, declare what should be declared in every jurisdiction that has a claim, and it stays an asset. Treat it as a hiding place and it becomes a liability with your name on it.

The honest summary

Tax is the part outsiders assume is central, and for most founders running this model it is close to the least interesting part. A non-resident-owned US LLC is generally a pass-through entity. The founder’s real tax obligations are mostly determined by where the founder actually lives and works, not by the state printed on the formation certificate. Anyone who sells you the structure primarily as a tax cut is selling you a misunderstanding, and possibly a future problem.

The honest case for a Wyoming or Delaware LLC is narrower and stronger than the tax pitch. It is an infrastructure decision. It gives a MENA founder access to the same financial plumbing a founder in London or Toronto takes for granted: Stripe, Mercury, stable banking, a currency that holds its value, without asking anyone to leave home, change citizenship, or pretend to be something they are not. Founders in Iraq, Palestine, or Syria, where local financial infrastructure is under even more structural pressure, are running the same model for the same reasons, with the same Mercury account and the same IRS fax queue.

For a founder spending real attention every week just keeping money moving, that is not a loophole. It is the difference between fighting your infrastructure and forgetting it exists. Most weeks, forgetting it exists is the entire goal.