Delaware LLC for SaaS founders: 2026 guide for non-resident founders

Why SaaS founders typically form Delaware LLCs

SaaS founders need a US business entity for Stripe onboarding, US-dollar banking, US client contract signing, and federal tax compliance (EIN, Form 5472, BOI).

Primary platforms in this industry where the US LLC matters most:

• Stripe
• Mercury or Wise Business
• Cloud platforms (AWS, GCP, Azure)

Banking fit for SaaS

Mercury is the standard fit when approved (Atlas-style integration). Wise Business approves more reliably for non-residents. Both work with Stripe for subscription billing.

Delewarellc applies to 4-5 banks per customer regardless of industry; the industry-specific weighting affects which banks the customer is most likely to use operationally rather than which banks we apply to.

Common business structure for SaaS

Single-member Delaware LLC owned by the non-resident founder. Stripe configured with subscription billing (monthly or annual). Customer SaaS contracts signed by the LLC.

Home-country operational entity (if any) provides services to the LLC under an intercompany agreement.

Tax notes specific to SaaS

Form 5472 applies to single-member foreign-owned LLCs. Permanent-establishment analysis under tax treaties matters for SaaS: services rendered from the home country may attribute income to that country.

Engage a CPA familiar with the PE article in your home country's US treaty.

Real scenarios in this industry

From Delewarellc's customer base:

• B2B SaaS founder from India: forms the LLC, signs US customers, bills via Stripe, employs the engineering team through an Indian Pvt Ltd, intercompany pricing follows transfer-pricing rules.
• Solo SaaS founder from Bangladesh: forms the LLC, runs the SaaS solo from Dhaka, bills via Stripe, holds US-dollar revenue in Wise.
• Marketplace-style SaaS from UAE: forms the LLC, takes a percentage of transactions, splits funds to vendors via Stripe Connect.

Pitfalls to avoid

• Permanent establishment: services-from-home-country can create PE attribution. The cross-border analysis is essential before scaling US sales.
• Sales tax on SaaS: some US states impose sales tax on SaaS subscriptions. Wayfair-style economic nexus thresholds apply at the LLC level.
• Customer contract jurisdiction: large US customers may require Delaware governing law and Delaware forum-selection clauses, which the LLC structure supports cleanly.

How Delewarellc handles SaaS

SaaS founders typically use Mercury (when approved) for tight Stripe integration. Wise Business is the most common backup.

The Form 5472 awareness brief specifically addresses the PE-article cross-border consideration for SaaS revenue.

The Delewarellc bundle for SaaS founders includes the standard $297 + state fee deliverables: Certificate of Formation filing, EIN via Form SS-4, registered agent Year 1, Operating Agreement template, applications to 4-5 banks, Form 5472 awareness brief, BOI report awareness, free annual compliance reminders. Multilingual WhatsApp support in 5 languages. Certificate of Formation filing, $110 Delaware state fee, registered agent Year 1, EIN via Form SS-4, Operating Agreement to 6 Del. C. § 18-101 standards, 4-5 bank applications, WhatsApp support in 5 languages, Form 5472 awareness brief.

What you owe after Year 1

• Delaware $300 annual franchise tax (due June 1).
• Registered agent renewal (~$99/year with Delewarellc, or $50/year with HBS if switched).
• CPA fee for Form 5472 + Form 1120 ($200-$500/year for an uncomplicated filing).
• Industry-specific obligations: sales tax registration if economic nexus thresholds are crossed, permits or licenses if your industry is regulated, US insurance coverage if your contracts require it.

How do SaaS founders actually earn and get paid?

A SaaS business earns recurring revenue. Customers subscribe and pay monthly or annually for access to software hosted on cloud platforms like AWS, GCP, or Azure. Unlike a one-time product sale, the money arrives as a stream of small repeating charges, which is why almost every non-resident SaaS founder configures Stripe with subscription billing rather than single invoices. Stripe handles the card vault, the renewal logic, dunning when a card fails, and proration when a customer upgrades mid-cycle. Your Delaware LLC becomes the merchant of record on those charges, the entity that signs the customer contract, and the entity whose name appears on the credit-card statement.

The cash path runs Stripe to a US business bank account, then onward to wherever the founder lives. For a solo founder in Dhaka or a B2B team in India, the practical sequence looks like this:

• Customer subscribes and Stripe charges the card on a recurring schedule.
• Stripe settles the payout in US dollars to the LLC's Mercury or Wise Business account.
• The founder draws funds to a home-country account when needed, holding a US-dollar buffer for cloud bills and software costs.
• Annual plans front-load cash, which smooths the runway that pure monthly billing tends to make lumpy.

Because the revenue is contractual and predictable, a Delaware LLC fits the model cleanly. The entity can sign enterprise agreements, accept ACH from larger US accounts, and carry the subscription relationship without the founder needing a US address or US residency.

Which bank and payment processor fit a SaaS LLC?

For SaaS, the pairing that comes up most often is Stripe for billing and Mercury for banking, with Wise Business as the reliable backup. Mercury is the standard fit when approved because its onboarding flow was built around exactly this profile of a software company billing through Stripe, and the two integrate tightly. The catch is that Mercury reviews non-resident applications carefully and does reject some. When that happens, Wise Business approves more reliably for founders outside the US, and it links to Stripe with a manual account connection rather than a one-click flow. Both options hold US dollars, both work with Stripe subscription payouts, and both let you keep a dollar buffer for the cloud invoices that dominate SaaS cost structures.

The realistic banking shortlist for a non-resident SaaS founder looks like this:

• Mercury: the first choice when the application is approved, for the tight Stripe pairing.
• Wise Business: the most common backup, with stronger approval odds for non-residents and clean multi-currency holding.
• Relay: useful when a founder wants multiple sub-accounts to separate cloud spend, payroll-style draws, and tax reserves.
• Lili: a lighter option for a true solo operator who wants simple bookkeeping.
• Payoneer: less common for subscription SaaS, but it appears when a founder also takes marketplace or platform payouts.

Whichever you pick, the account must stay in good standing, because Stripe payouts stop flowing the moment the linked bank account is frozen or closed.

Is SaaS income effectively connected to a US trade or business?

This is the question that decides whether a non-resident SaaS founder owes US income tax, and it rarely has a simple answer. The short version is that selling subscriptions to US customers does not automatically make the income effectively connected income, often shortened to ECI. What matters far more is where the work happens and whether the founder has a US presence that rises to the level of a trade or business. A founder writing code and running the product from Dhaka or Bangalore, with no US office, no US employees, and no dependent agent in the US, is in a very different position from one who relocates engineers to a US workspace.

Tax treaties add a second layer through the permanent-establishment analysis. Under the relevant article of a home-country US treaty, services rendered from the home country can attribute the income to that country rather than the US. SaaS sits awkwardly here because the "service" is software running on US-based cloud servers while the human work happens abroad. Because the cross-border treatment turns on facts specific to each treaty and each operating setup, the right move is to engage a CPA familiar with the permanent-establishment article in your home country's US treaty before you scale US sales. Getting this analysis on paper early protects the structure when revenue grows and the stakes rise.

What sales-tax and economic-nexus exposure does SaaS carry?

SaaS founders often assume software is exempt from sales tax. That assumption is wrong in a growing number of states. Some US states treat SaaS subscriptions as taxable, and the obligation can attach to your Delaware LLC even though you sit abroad and even though Delaware itself has no sales tax. The trigger is economic nexus under the Wayfair-style rules: once your sales into a particular state cross that state's dollar or transaction threshold, the LLC may be required to register, collect tax from customers in that state, and remit it. This applies at the LLC level, so the entity becomes the taxpayer regardless of where the founder lives.

For a subscription business that can sign customers in any state through a self-serve checkout, the exposure spreads quietly as you grow. A few practical points keep it manageable:

• States set their own thresholds, and several explicitly tax SaaS while others do not, so the map is uneven.
• Crossing a threshold creates a forward-looking collection duty, not just a one-time filing.
• Stripe Tax and similar tooling can compute and collect the right rate at checkout once you know where you have nexus.
• B2B sales to exempt resellers or tax-exempt entities may not count the same way as B2C sales.

The point is not to register everywhere from day one. It is to monitor where your subscriber base concentrates so that the LLC registers in a state before it materially exceeds that state's nexus threshold.

What is the Form 5472 obligation for a foreign-owned SaaS LLC?

Every single-member Delaware LLC owned by a non-resident is treated as a disregarded entity that must file Form 5472 together with a pro forma Form 1120 each year. This applies to a SaaS LLC even if it never owes a dollar of US income tax. The form reports "reportable transactions" between the LLC and its foreign owner, and for SaaS founders those transactions show up constantly: capital you put in to cover cloud bills, distributions you draw from Stripe revenue, and any intercompany charges if a home-country company provides engineering to the LLC. The filing is informational rather than a tax bill, but the penalty for missing it is severe, set at $25,000.

SaaS founders trip on this more than most because the business can look deceptively simple. A solo founder billing through Stripe from a single laptop still has the full Form 5472 obligation, and the very fact that money moved between the founder and the LLC is what creates the reportable transaction. Keep a clean record of every transfer in and out, match it to your Stripe payouts and bank statements, and file on the annual schedule. If you run a home-country operating entity that builds the product under an intercompany agreement, those intercompany flows also belong on the form and need transfer-pricing support. Treat the filing as a fixed yearly cost of running the structure, not an optional extra.

Why do non-resident SaaS founders choose a Delaware LLC?

The Delaware LLC has become the default wrapper for non-resident SaaS for reasons that map directly to how software companies sell. US customers, and especially larger US buyers, trust a US legal entity as a counterparty far more than an unfamiliar foreign company. When a B2B customer's procurement team reviews a contract, a Delaware LLC reads as a known quantity. The structure also supports the governing-law and forum-selection clauses that enterprise customers ask for. Large US customers may require Delaware governing law and a Delaware forum, and an LLC formed there satisfies that request without friction.

Beyond credibility, the operational fit is strong:

• Stripe and Mercury both onboard Delaware LLCs through well-worn paths built for software businesses.
• A single-member LLC keeps ownership and bookkeeping simple for a solo founder or a small team.
• The entity can sign customer contracts, hold US-dollar revenue, and accept ACH and card payments under one name.
• A home-country operating company can sit alongside it under an intercompany agreement when the engineering team lives abroad.

For a founder whose product runs on US cloud infrastructure and bills US customers, a Delaware LLC aligns the legal entity with where the revenue and the trust already sit.

How does the permanent-establishment trap catch SaaS teams?

The single sharpest risk for a scaling SaaS company is permanent establishment, the trap that catches founders who build the product in one country while billing customers through a US LLC. Under most US tax treaties, the income attributable to where the services are performed can be taxed in that country. For SaaS, the human work, writing code, running support, closing sales, frequently happens in the founder's home country, which means the home country may have a strong claim on the profit even though the LLC is American and the servers are American. If you ignore this and treat the LLC as if it operates in a vacuum, you risk a surprise home-country assessment once revenue grows.

The exposure gets worse, not better, as the company succeeds. A B2B SaaS founder from India who employs an engineering team through an Indian private limited company has to price the intercompany services between the Indian entity and the US LLC according to transfer-pricing rules, or the arrangement looks artificial to both tax authorities. The cross-border analysis is not a formality to skip until later. It is essential before you scale US sales, because the structure you document early is the structure that defends your profit allocation when revenue reaches a level that draws attention. Engage a CPA who understands the permanent-establishment article in your specific treaty rather than relying on a generic US-only adviser.

What rejections and high-risk hurdles do SaaS founders face?

Most SaaS businesses are low-risk in payment-processor terms, but not all, and the rejections that do happen usually come from the processor or bank rather than the state of Delaware. Mercury reviews non-resident applications and turns some down, which is why Wise Business exists as the standard fallback. Stripe, meanwhile, scrutinizes the underlying business model. SaaS that sits near a restricted category can hit friction even when the formation paperwork is perfect.

Watch for these specific snags:

• SaaS adjacent to high-risk verticals, such as gambling tools, certain crypto services, or adult content, draws extra processor review or outright rejection.
• Marketplace-style SaaS that splits funds to vendors needs Stripe Connect, which adds its own onboarding and identity checks for each payee.
• High chargeback rates from a consumer-facing free-trial funnel can trigger Stripe holds, which then choke the payout flow into your bank.
• A vague or generic business description on the bank application invites questions, so describe the actual product and customer plainly.

None of these are reasons to avoid the Delaware LLC. They are reasons to present the business clearly, keep chargebacks low, and line up Wise Business in advance so a Mercury rejection does not stall your launch.

What does the recommended SaaS setup look like end to end?

The structure that fits the most non-resident SaaS founders is a single-member Delaware LLC owned by the founder, with Stripe configured for subscription billing and a US bank account holding the dollar revenue. Customer SaaS contracts are signed by the LLC. If an operating company exists in the home country, for example to employ the engineering team, it provides services to the LLC under an intercompany agreement priced according to transfer-pricing rules. This is the same shape across the common cases: a B2B founder from India running an Indian private limited alongside the LLC, a solo founder from Bangladesh running everything from Dhaka and holding revenue in Wise, or a marketplace SaaS from the UAE taking a transaction percentage through Stripe Connect.

The formation and compliance mechanics are fixed and worth knowing up front:

• Delaware Certificate of Formation costs $110 to file.
• The EIN comes free from the IRS via Form SS-4, typically in about 8 to 10 business days for a non-resident.
• The Delaware franchise tax for an LLC is a flat $300 due each June 1.
• Form 5472 with a pro forma 1120 is filed annually, with a $25,000 penalty for missing it.
• US-formed LLCs are exempt from the FinCEN beneficial-ownership (BOI) report under the Interim Final Rule of March 26 2025, so there is no 90-day filing requirement and no daily penalty for domestic entities.

Delewarellc forms the LLC, obtains the EIN, and provides the registered agent for a one-time price of $297, then hands you a structure built to sign customers, bill through Stripe, and bank in dollars from day one.

How should a SaaS founder sequence the first 90 days?

Sequencing matters because Stripe and the bank both depend on the EIN, and the EIN depends on the LLC existing. The clean order is to form the Delaware LLC first, then apply for the EIN, then open the bank account, then connect Stripe. Rushing to apply for Stripe or Mercury before the EIN lands only produces a rejection and a wasted attempt. Because the EIN for a non-resident usually takes about 8 to 10 business days, plan the launch calendar around that window rather than assuming same-week access to payments.

A realistic first-quarter checklist for a non-resident SaaS founder runs roughly like this:

• File the Certificate of Formation and appoint a registered agent.
• Apply for the EIN by Form SS-4 and wait for the assignment.
• Open Mercury, or Wise Business if Mercury declines, using the EIN and formation documents.
• Connect Stripe, set up subscription plans, and turn on Stripe Tax once you understand your nexus map.
• Sign your first customer contracts under the LLC name and start tracking transfers for Form 5472.
• Book a session with a CPA who knows your treaty's permanent-establishment article before US revenue scales.

Handled in this order, a founder can move from no entity to a live subscription business banking in US dollars inside a single quarter, with the tax and reporting groundwork already in place rather than bolted on after the fact.