Writing an E-2 Visa Business Plan for a Technology Startup

Consular officers and USCIS adjudicators apply the same five-factor test to every E-2 case, but tech startups reliably create friction on two of them: the substantiality of the investment and the marginality question. A software company can launch with a laptop and a cloud subscription. That is a real business, but the capital deployed looks thin relative to what an officer expects from a filing that claims a substantial investment.

The second pressure point is non-marginality. 9 FAM 402.9-4(C) requires the enterprise to have present or future capacity to generate income significantly beyond a minimal living for the investor and family, or to make a significant economic contribution. A SaaS product still pre-revenue, or a consulting business that currently has one client, has to show that trajectory convincingly. The plan carries more weight than the current bank balance.

Understanding these pressure points is the first step. The plan should address each one directly rather than hoping the officer reads between the lines.

Substantiality is a proportionality test, not a dollar-amount test. Under 9 FAM 402.9-4(B)(3), the amount invested is weighed against the total cost of establishing the enterprise. A software startup with a realistic total cost of $80,000 to reach a working product and first paying customers can clear the substantiality bar with a lower absolute number than a restaurant requiring $400,000 in build-out.

The key is documenting the total cost of the business carefully. For a tech startup, that means identifying every category of spend: development costs (in-house labor, freelancers, or an offshore team), cloud infrastructure, software licenses, legal and formation fees, marketing spend, and working capital to cover payroll and operations while the business builds revenue. When those categories are quantified and the invested capital covers a high percentage of the total, the proportionality math works in the applicant's favor.

Cash spent on development before filing counts as invested capital, as long as it is traceable and irrevocably committed to the enterprise. Code repositories, contractor invoices, platform subscriptions, and formation costs all document a real investment. The mistake many tech applicants make is treating pre-formation spending as irrelevant to the E-2 calculation when it is exactly the evidence that anchors the investment claim.

The E-2 standard under 9 FAM 402.9-4(B)(1) requires a real, active commercial or entrepreneurial undertaking. For a technology company, that means the business is actually doing something: building a product, signing contracts, serving clients, or deploying code. A holding company, an IP shell, or a company that exists only on paper fails this test regardless of the capital invested.

Document operational activity with concrete records. Source code repositories with commit history show development activity. A signed SaaS contract or a statement of work shows commercial engagement. A support ticket system or a customer onboarding flow shows an operating business. For pre-revenue startups, letters of intent from prospective customers or signed pilot agreements are stronger than projected revenue with no supporting evidence.

The develop and direct requirement under 9 FAM 402.9-4(B)(5) means the investor must have day-to-day operational control. In a tech startup, the founding engineer who is also the CEO has a credible develop-and-direct narrative. A passive investor who funds a team but makes no operational decisions does not. The organizational chart and the description of the investor's role should make the control structure unambiguous.

Tech startup projections get challenged when they are disconnected from any observable data. Officers see projections that jump from zero to $2 million in year two with no explanation of how the business acquires customers, at what price, or with what conversion funnel. The projection itself is not the problem; unsupported assumptions are.

Build the revenue model from first principles. For a SaaS business: state the monthly subscription price, estimate the addressable customer pool in the target market, project a realistic monthly acquisition rate based on the planned marketing spend, and apply a standard churn assumption. For a services business: state the rate, the number of clients the investor can realistically serve, and how clients will be acquired. Each assumption should be a sentence in the plan so the officer can follow the logic.

The five-year projection must show a path to non-marginality. Under 9 FAM 402.9-4(C), a plan that plateaus at $60,000 net income in year five raises a marginal enterprise concern. A plan that shows $200,000 in year-three net income with two to three U.S. employees by year four is telling a different story. The non-marginality showing does not require certainty, only credibility.

• Year-one revenue: conservative assumption based on signed contracts or realistic acquisition rate
• Year-three and year-five net income: must exceed a minimal living for the investor's household
• Payroll schedule: name the roles being hired, approximate salary, and timing of each hire
• Break-even analysis: the month in which recurring revenue covers operating costs
• Assumptions page: one or two sentences explaining each major revenue and cost assumption

The at-risk requirement under 8 CFR 214.2(e)(12) means the invested capital must be subject to partial or total loss if the enterprise fails. For a technology company, the primary risk is that the product never generates revenue and the invested development capital is written off. That is a real financial risk, and the plan should acknowledge it plainly.

Where tech startups can create problems is when the "investment" is structured in a way that hedges the risk entirely. IP licensed back to the investor on favorable terms, a loan from the company to the investor, or funds held in a personal account that the investor controls and has not genuinely committed to the business all weaken the at-risk showing. The capital needs to be in the business, working. Bank statements or a capitalization table showing the investment in the company's account, paired with evidence of how it has been spent, is the standard documentation.

The most frequent mistake is describing the product in technical language that makes sense to a developer but tells an officer nothing about the commercial reality. Officers are not engineers. They need to understand what the product does, who pays for it, how much they pay, and why they would choose this product over alternatives. A two-paragraph plain-English description of the business model is more useful than a detailed architecture diagram.

The second common mistake is omitting the competitive analysis. Technology markets move fast and officers know it. A plan that claims no competitors, or that names competitors dismissively without a real differentiation argument, loses credibility. A straightforward two-paragraph analysis that names actual competitors and explains the specific position the startup occupies is more persuasive than silence or bravado.

Third: underdocumenting the investor's qualifications. The plan should include a resume or professional profile showing the investor has relevant experience, whether that is technical background, industry experience, or prior entrepreneurship. An investor who has never worked in technology before launching a SaaS business needs to explain what fills that gap, such as a technical co-founder or a development contractor.

Consular officers reviewing a tech startup E-2 case often focus the interview on three areas: the nature of the product and business model, the source and amount of the investment, and the applicant's role in running the company. Having crisp, one-sentence answers to each ready in advance reduces the risk of a confused interview record.

Bring evidence of operational activity to the interview where the post allows it: a printed screenshot of the product, a customer contract, or a bank statement showing the invested capital. These materials let the officer confirm the business is real without relying entirely on the written plan.