ENISA Business Plan for Spain Startup Visa 2026: What Each Section Must Contain
ENISA evaluates Spain Startup Visa business plans under Ley 28/2022 against eight explicit criteria, with innovation and scalability weighted most heavily. Most rejections trace back to a weak or missing innovation thesis — not to missing paperwork. This guide walks every section of the business plan that evaluators actually score, with examples of what passes and what doesn't.
ENISA reviews Spain Startup Visa business plans under two laws — Ley 14/2013 (Entrepreneurs Law) and Ley 28/2022 (Startup Act) — and its evaluation runs 10–20 working days. Unlike AIMA in Portugal, which asks whether a business plan is “viable,” ENISA is specifically testing for demonstrable innovation. Two independent evaluators score each plan and their scores are reconciled. Plans that pass the 2026 review cycle have one thing in common: the innovation argument is made early, backed by specific technical and market evidence, and the founder’s credentials connect directly to the product being built. Plans that fail tend to be structurally complete but substantively thin — well-formatted decks with generic claims and unsourced projections.
What ENISA is actually testing under Ley 28/2022
Ley 28/2022 (the Startup Act) tightened the definition of an “innovative startup” beyond what Ley 14/2013 originally required. To qualify, a company must be under five years old (seven years for biotech and hardware), not listed on a regulated market, not created from a corporate restructuring or merger, and must operate a scalable business model based on technological innovation. That final phrase is the operative one. ENISA evaluators interpret it strictly: applying technology to an existing market is not sufficient if the technology itself is not differentiated.
The eight evaluation criteria, derived from the legal framework and confirmed by practitioner experience with 2025–2026 approvals, are:
- Innovation — is the business model or technology genuinely differentiated?
- Scalability — can revenue grow faster than costs?
- Founder capability — do the founders have the technical or domain background to execute?
- Market size — is the addressable market real and well-sourced?
- Competitive moat — what prevents a better-funded competitor from replicating this in 12 months?
- Financial credibility — are the projections grounded in documented unit economics?
- Team structure — is there a credible plan to hire and build the team?
- Spanish economic contribution — does the company create demonstrable value in Spain?
Each criterion is worth attention. Criteria 1 and 2 are weighted most heavily; a weak innovation thesis cannot be offset by strong financials.
Section 1: Innovation thesis

This is where most plans fail. ENISA’s standard, as stated in Ley 28/2022, is “innovative use of technology or scalable business model.” Simply applying existing technology to an underserved niche is not enough. Evaluators will ask: is the underlying technology novel, or is the differentiation purely commercial?
What scores 10/10: A precise technical description of what the product does that no competitor currently does, with specific reference to the technology stack, an explanation of why the approach is non-obvious, and at least one supporting signal — a patent application, published research, a proprietary dataset, or a working prototype with documented technical architecture. The innovation thesis must appear in the executive summary and be elaborated in a dedicated section. Plans that bury it in an appendix score lower.
What scores 5/10: “We use AI to optimise restaurant bookings.” The AI claim is generic, no technical depth is provided, and multiple competitors offer the same framing. ENISA evaluators recognise this pattern immediately.
What gets rejected: A mobile app for any commodity vertical without technical differentiation. “We are building an app for [niche]” is not, by itself, an innovation thesis. ENISA evaluators have seen this framing in hundreds of applications and now apply heightened scrutiny to any app-plus-niche positioning that lacks a specific technical claim.
Section 2: Scalability narrative
Ley 28/2022 explicitly requires a scalable business model. ENISA will look for a concrete ratio of revenue growth to cost growth. A 5/10 score implies roughly proportional growth (doubling revenue requires doubling cost). A 10/10 score demonstrates positive leverage: doubling revenue on a 30–40% cost increase is the benchmark for what evaluators consider credible scalability in 2026.
The business types that consistently fail on scalability are covered in depth in what ENISA rejects in 2026: the 4 business categories that always fail. In short: HoReCa businesses (each new location adds proportional cost), franchises (no central scalability driver), and traditional professional service firms (each new euro of revenue requires new labour). For borderline models — e-commerce, B2B services, marketplaces — the plan must explicitly describe the mechanism by which revenue growth decouples from cost. If your model is “more clients = more consultants,” you need to demonstrate the product, process, or technology that breaks that linearity.
Section 3: Founder background and technical depth
ENISA reads founder CVs against the product being built. For a software product, at least one founder should have traceable technical credentials: specific programming languages, prior shipped products, open-source contributions, or a published technical record. For fintech or biotech, domain expertise is expected alongside technical capability.
Common gap in 2026 applications: Teams where the listed CTO or technical co-founder has no verifiable technical background. ENISA has declined applications where the technical founder’s CV shows only management roles with no software development or engineering history.
What to include: Specific technical projects with names and outcomes (repositories, deployed products, published APIs), domain expertise directly relevant to the problem, and prior entrepreneurship — even failed ventures add credibility. For teams without a strong in-house technical co-founder, the plan must explain how that capability is addressed: named advisors, signed contractor agreements, or a funded hiring plan with a technical role in the first 90 days.
Section 4: Market analysis
ENISA expects TAM/SAM/SOM structure and evaluators are sceptical of inflated top-down claims. A plan stating “the global food delivery market is $500 billion; we are targeting 0.001%” will score low. What passes is bottom-up sourcing: “our target segment is X, based on [specific published source], and our initial geography contains Y potential customers at an average contract value of €Z.” The TAM figure should be traceable to a named third-party source — an industry report, government statistics, or published research.
Common mistake: Citing an enormous global market with no explanation of penetration mechanics. ENISA evaluators verify whether stated figures are plausible and internally consistent with the rest of the plan.
For comparison: the structure of a rigorous business plan market section for ENISA is similar in discipline to what AIMA requires for the Portugal D2 business plan, though the regulatory lens is different — AIMA asks “is this viable?” while ENISA asks “is this innovative?”
Section 5: Competitive moat
ENISA does not expect a monopoly position; it expects a differentiated one. The moat section should answer: why won’t a well-capitalised competitor replicate this within 12 months?
Acceptable moats: proprietary technology, proprietary data or training sets, network effects, regulatory advantage (a licence or certification that takes time to obtain), and switching costs. Unacceptable moats: first-mover advantage stated without further evidence (ENISA evaluators know first-mover is often temporary), cost leadership (price competition is not innovation), and market familiarity (“we know this market well”).
The competitive moat section should name at least two direct competitors and explain specifically why the proposed solution is harder to replicate. Generic statements — “no one else does what we do” — score low unless they are backed by technical or structural evidence.
Section 6: Financial projections
Three-year projections are standard. ENISA evaluators cross-check unit economics: if a plan claims 10,000 users in Year 1 at €200K total revenue, the implied ARPU is €20 per year — does that match the stated pricing? Inconsistencies between pricing slides, the financial model, and prose descriptions are a red flag.
What scores well: Conservative Year 1 assumptions, growth-stage Years 2–3, with all assumptions documented. “We assume a 3% free-to-paid conversion rate, based on industry benchmarks from [source]” is more credible than any unlabelled growth curve.
What raises flags: Hockey-stick projections with unstated assumptions; negative EBITDA in Year 3 with no explained path to profitability; missing CAC/LTV analysis for subscription or recurring-revenue models; revenue model in the prose that does not reconcile with the financial table.
The arithmetic must be internally consistent. ENISA has flagged applications where the revenue model described in the text does not match the figures in the attached spreadsheet.
Ready to submit your ENISA business plan? Relovisa prepares and audits ENISA-ready business plans for Spain Startup Visa applicants, drawing on approval patterns from 2025–2026 submissions. See what we offer.
Section 7: Team and hiring plan
ENISA needs to see a credible execution path. For a product that requires five developers to ship an MVP, a plan with two non-technical founders and no hiring timeline will not pass. Solo-founder applications receive particular scrutiny: a solo applicant must explain in detail how the work will be done — named advisors, signed contractor agreements, or a funded near-term hire — with enough specificity that the “ghost team” concern is addressed.
What to include: Current team roles with specific skills mapped to the product’s technical requirements; planned Year 1 hires with titles, functions, and approximate timing; whether any hires will be Spain-based (this also strengthens Section 8).
Section 8: Spanish economic contribution
This section is consistently underweighted, and it matters. Ley 28/2022 frames the Spain Startup Visa as an instrument of economic policy: ENISA’s mandate is to approve applications that generate value in Spain. Evaluators assess:
- Employment: Plans to hire Spanish residents, even 1–2 in Year 1, are a strong positive signal.
- Revenue and clients: Revenue from Spanish clients, or a credible plan to develop the Spanish market as part of the initial go-to-market.
- Ecosystem participation: Named accelerators, co-working memberships, or community affiliations in Spain.
- Tax and social contributions: Plans to register for Spanish corporate tax, pay into Spanish social security (or coordinate with Portuguese social security under applicable bilateral arrangements), and comply with AEAT reporting.
A plan that places the entire team outside Spain with no Spanish clients, no Spanish hires, and no Spanish ecosystem activity will struggle in Section 8 — even when Sections 1 through 7 are strong. This is not a bureaucratic formality; it reflects the purpose of the law.
What 10/10 looks like vs 5/10
10/10 plan:
- Innovation thesis is specific, technical, and prominent — in the executive summary and in its own section
- Scalability narrative uses real unit economics with documented assumptions and demonstrates revenue/cost decoupling
- Founder CVs connect directly to the technology: “I built X at company Y using Z stack; here is the repository”
- Market figures are sourced from named publications; TAM/SAM/SOM is bottom-up
- Financial model is internally consistent with all assumptions stated
- Year 1 hiring plan includes at least one Spain-based role
- Spanish contribution section is substantive — not a single paragraph
5/10 plan:
- Innovation section says “we use AI/ML” without technical specifics
- Scalability section says “our model scales” without demonstrating the mechanism
- Founder credentials are management-only with no traceable technical depth
- Market section uses a top-down TAM from a generic industry report without bottom-up validation
- Financials are positive but assumptions are unstated
- Hiring plan is vague or absent

What makes recent successful applications work (anonymised)
Case A — Legal-tech SaaS: Two-founder team (lawyer + developer), €50K ARR from UK clients at time of filing. Innovation thesis: proprietary LLM fine-tuned on a curated Spanish legal corpus, validated against 2,000+ case outcomes. Year 1 plan: hire two developers in Barcelona. Spanish contribution: data processing infrastructure in Madrid for GDPR compliance. ENISA approved in 14 working days.
Case B — B2B translation API: Solo technical founder, 8 years in NLP at a German software company. Market analysis sourced from a Gartner report and internal analysis of 200 potential enterprise clients. Scalability documented via marginal cost per API call declining with volume. Spanish contribution: Spanish-language fine-tuning dataset collaboration with two Madrid universities. ENISA approved in 18 working days.
Case C — Discovery platform (resubmission): Initially positioned as “a marketplace connecting consumers with manufacturers.” First submission declined — ENISA’s note cited “insufficient innovation; marketplace model is not differentiated.” After reframing to foreground the proprietary supplier-ranking algorithm and the structured product data layer (which no existing marketplace had published), the second submission was approved. The underlying business had not changed; the innovation framing had.
Case C is worth noting because it illustrates a recoverable position. Most ENISA rejection categories — HoReCa, franchises, real estate dressed as PropTech — are structurally unfixable. But innovation-framing failures, where a genuinely differentiated product is described generically, are correctable. The distinction between fixable and unfixable ENISA rejections is one of the most practically useful things to understand before filing; the four ENISA rejection categories cover each case in detail.
For founders weighing Spain Startup against Portugal D2 — which has a significantly lower innovation bar but a longer citizenship path and different tax regime — Portugal D2 vs Spain Startup: which entrepreneur route fits your profile addresses that decision by business type.
Relovisa structures and audits ENISA business plans as part of the Spain Startup Visa engagement. We have supported approvals in both the first-submission and resubmission cases, and we review plans against the current 2026 ENISA evaluation patterns before submission. Start the process here.
Sources
- Ley 14/2013, de 27 de septiembre, de apoyo a los emprendedores y su internacionalización — BOE-A-2013-10074 — verified June 2026
- Ley 28/2022, de 21 de diciembre, de fomento del ecosistema de las empresas emergentes (Startup Act) — BOE-A-2022-21739 — verified June 2026
- ENISA — Empresa Nacional de Innovación — evaluation criteria and process overview at enisa.es — verified June 2026
- Secretaría de Estado de Migraciones — Spain Startup Visa (Ley de emprendedores) residence permit documentation — extranjeros.inclusion.gob.es — verified June 2026
- UGE-CE (Unidad de Grandes Empresas y Colectivos Estratégicos) — processing timelines and 2026 fraud-detection guidance — verified June 2026
- Beckham Law (artículo 93 LIRPF) — 24% flat tax up to €600K, 6-year duration, application deadline 6 months from Spanish Social Security registration — verified June 2026