In my years directing Startup Burgenland and advising Austrian founders, I’ve watched dozens of startups work through the FFG and AWS funding process. Some sailed through. Others burned months on applications that never had a chance. The difference wasn’t the quality of their ideas—it was understanding how these agencies actually work, what they’re really looking for, and how to position your application.
Austria’s public funding ecosystem is genuinely generous by international standards. The FFG (Forschungsförderungsgesellschaft) and AWS (Austria Wirtschaftsservice) together distribute hundreds of millions of euros annually to businesses. If you’re building a company in Austria and not exploring these programs, you’re leaving money on the table.
But “generous” doesn’t mean “easy.” The application process rewards preparation, precision, and a clear understanding of what each agency prioritizes.
FFG: Research and Innovation Focus
The FFG funds research, development, and innovation. If your startup involves developing new technology, processes, or knowledge, FFG is likely your primary funding target.
What FFG funds:
- Basic and applied research (Basisprogramm)
- Experimental development
- Innovation projects with novel technological components
- Collaborative research between businesses and academic institutions
- Feasibility studies for research-intensive projects
What FFG doesn’t fund:
- Pure marketing or market entry without research components
- Established technologies applied to new markets (unless there’s genuine innovation)
- Business model innovation without technological novelty
- Projects where the “research” is really just product development with no uncertainty
This distinction trips up many founders. They have a great product idea and assume FFG will fund the development. But FFG’s mandate is research and innovation—they need to see genuine technical uncertainty, novel approaches, and knowledge creation. If your project is applying known technology to a new market, FFG probably isn’t the right fit. AWS might be.
Funding amounts: Range from small feasibility studies (€10,000-€50,000) to major research projects (€500,000+). The Basisprogramm, which most startups access first, typically funds projects in the €100,000-€500,000 range.
Funding type: Mix of grants (Zuschüsse) and loans (Darlehen), depending on the program. Early-stage programs tend to have higher grant components. The exact mix depends on your company’s size, location, and the project’s risk profile.
I covered the basics in my introduction to FFG grants, but here I want to go deeper into what actually makes applications succeed.
AWS: Business Growth and Market Focus
AWS focuses on business development, growth, and market entry. If your startup needs funding for scaling, market expansion, or operational development, AWS is your target.
What AWS funds:
- Business establishment and early-stage growth (aws Gründungsfonds, aws Preseed)
- Market expansion and internationalization
- Working capital for growth phases
- Guarantee programs for bank financing
- Investment support (aws Business Angel Fund, aws Venture Capital Initiative)
Key AWS programs for startups:
- aws Preseed: Up to €200,000 for pre-revenue deep-tech and IP-based startups
- aws Seedfinancing: Up to €800,000 for innovative startups in growth phase
- aws Gründungsfonds: Equity-like funding for early-stage companies
- aws Garantie: Government-backed guarantees for bank loans
- aws erp-Kredit: Subsidized loans for investment projects
The critical difference from FFG: AWS evaluates business potential, not research merit. They want to see viable business models, market opportunity, and a team capable of execution. You need a credible path to revenue, not a novel research approach.
Many Austrian founders apply to the wrong agency because they don’t understand this distinction. A deep-tech startup with genuine research challenges should start with FFG. A marketplace or service business with a proven model looking to scale should start with AWS. Some startups qualify for both—and should apply to both, with different project scopes for each.
The Application Process: What Actually Matters
Having reviewed dozens of applications and helped prepare many successful ones, here’s what actually drives decisions:
For FFG:
Innovation narrative. FFG reviewers need to understand what’s genuinely new about your approach. Not “we’re the first to do X in Austria” (that’s a market claim, not an innovation claim), but “current approaches to X have limitations A, B, and C. Our approach addresses these through novel method Y, which hasn’t been attempted because of challenge Z.” Be specific about the state of the art and how you advance it.
Methodology rigor. Describe your research approach in detail. What are the research questions? What methods will you use? What are the work packages and milestones? FFG reviewers are typically domain experts—they’ll catch vague or unrealistic methodologies.
Team qualification. The team’s ability to execute the proposed research. Academic credentials, industry experience, previous research output. If your team lacks specific expertise, show how you’ll acquire it (partnerships, hiring plans, academic collaborations).
Budget realism. Inflated budgets are an instant red flag. FFG reviewers know what things cost. If your budget includes €80,000 for “market research” in a technical research project, they’ll question your priorities.
For AWS:
Business model clarity. AWS wants to see a clear path from funding to revenue. How does the money translate into business outcomes? What metrics will improve? When does the business become self-sustaining?
Market evidence. Not just market size (everyone quotes TAM/SAM/SOM numbers), but evidence of demand. Customer letters of intent, pilot project results, waiting lists, competitive analysis showing unmet needs. Real evidence, not projections.
Financial projections. Realistic, defensible projections with clear assumptions. AWS has seen thousands of hockey-stick projections—yours needs to stand out by being honest about the path and the risks. I discussed financial planning approaches in my piece about AI-assisted financial projections, and the same principles apply here: be precise, be honest, model multiple scenarios.
Founding team. AWS evaluates the team’s ability to build a business, not just a product. Commercial experience, industry connections, track record of execution. Technical founders without business experience should show how they’ve addressed this gap (co-founder, advisor, mentor).
Timing and Strategic Considerations
Application timing matters. Both agencies have review cycles, and submitting at the right time can significantly affect processing speed. FFG’s continuous submission programs (like the Basisprogramm) process applications year-round, but review capacity is limited and there can be significant delays. Thematic calls (like those for specific research priorities) have fixed deadlines—miss them and you wait for the next cycle.
Regional bonuses. Projects in underserved regions (outside Vienna and its immediate surroundings) often receive higher funding rates. Operating from Graz, Linz, or other regional cities can mean 5-15% higher grant components. This isn’t widely publicized but it’s significant. When I discuss the advantages of building outside Vienna, funding rates are one of the tangible benefits.
Co-funding requirements. Most programs require you to cover a portion of project costs yourself. FFG projects typically require 30-60% own contribution. AWS programs vary but most expect some own contribution. Plan your cash flow accordingly—grant money isn’t immediate, and you need to survive until it arrives.
Reporting obligations. Both agencies require progress reports and financial documentation. Underestimating the administrative burden of ongoing reporting is a common mistake. Budget 5-10% of the project lead’s time for grant administration.
Combinability. You can often combine FFG and AWS funding with other sources—regional funding (from your Bundesland), EU programs, private investment. The combination can significantly increase total available funding, but the administrative complexity also increases. A good funding advisor helps here.
Common Mistakes from Startup Burgenland Experience
From working with 40+ startups at Startup Burgenland, here are the mistakes I saw most often:
Applying before you’re ready. Agencies track applications. A rejected application is on file. Applying with a half-baked proposal to “see what happens” damages your credibility for future applications. Apply when you have a strong case, not when you’re desperate for money.
Ignoring the funding advisor. Both FFG and AWS offer free pre-application consultations. USE THEM. Advisors will tell you whether your project fits the program, suggest improvements to your positioning, and flag issues before you submit. Skipping this step is like refusing free coaching before a competition.
Writing for yourself instead of the reviewer. Your application is read by reviewers who process dozens of applications. Be clear, structured, and explicit. Don’t assume they know your industry jargon. Don’t bury the key innovation in paragraph 12. Front-load the most important information.
Underestimating the timeline. From initial concept to funding in your account: FFG Basisprogramm typically takes 6-9 months. AWS programs vary from 3-6 months. If you need money now, public funding isn’t the answer. Plan 6-12 months ahead.
Forgetting de minimis. Small grants often fall under de minimis regulations, which cap total public aid at €300,000 over three years. If you’ve received other public support, this ceiling can limit your new funding options. Track your de minimis usage carefully.
The Practical Action Plan
If you’re an Austrian founder exploring public funding:
Week 1: Research which programs fit your stage and type of business. Start with the FFG and AWS websites, but also check your Bundesland’s regional funding agency and the WKO’s funding database.
Week 2: Contact the relevant agency’s advisory service. Describe your project in two paragraphs and ask which programs you should consider. They’re helpful—it’s their job.
Week 3-4: Prepare a preliminary application outline based on the advisor’s guidance. Get feedback before investing in a full application.
Month 2-3: Write the full application with the feedback incorporated. Have someone outside your team review it for clarity—if they can’t understand your innovation and business case in 10 minutes, neither will the reviewer.
Month 3+: Submit and prepare for the wait. Use the waiting period productively—the best applications are from founders who kept building regardless of the funding outcome.
The Austrian funding ecosystem is one of the genuine structural advantages of building a business here. The support is real, the amounts are meaningful, and the programs are well-designed. But they reward preparation, not desperation. Invest the time to apply well, and the returns can be substantial.
Takeaways
- FFG funds research and innovation (technical novelty, methodology rigor); AWS funds business growth and market entry (business model clarity, market evidence)—apply to the right agency for your project type.
- Use free pre-application consultations at both agencies; advisors will improve your positioning and flag issues before you submit.
- Plan 6-12 months from concept to funds in your account; public funding is for planned growth, not emergency capital.
- Regional location outside Vienna often means higher grant rates (5-15% more); Austrian founders outside the capital have a funding advantage many overlook.
- Track de minimis usage across all public grants and be ruthlessly realistic in your budget and projections—inflated numbers and unrealistic timelines are instant red flags for reviewers.
