A subsidy advisor writes the application. Nobody builds the project.
We do both. Stratalytic designs the AI or data project, files the WBSO and MIT applications for it, and then actually builds the thing. The application describes work that genuinely happens, which is exactly where most rejections come from.
What the first call gets you
30 minutes, free, with the architect who builds it.
- Which schemes your project actually qualifies for, and which it does not
- A rough figure: what stays on your own books after the subsidy
- Whether the plan is technically defensible as R&D, judged honestly
- The deadline you are working against, per scheme
36-50%
WBSO on development costs
35%
MIT on the broader project
€1.8bn
WBSO budget for 2026
€0
For the funding check
You talk directly to a solution architect.
No sales team and no subsidy salesperson. In 30 minutes we go through the plan and you hear whether there is funding in it, how much roughly, and whether the project is worth doing without it. That last answer is free too.
Measured at these companies
Sound familiar?
The advisor delivered an application, not a project
A fee for the paperwork, and afterwards you still have to find a builder. If that builder scopes the work differently than the application describes, you have a problem at the audit and not before.
Nobody can tell you whether this counts as R&D
The line between 'development' and 'just implementing an existing tool' decides the whole application. It is a technical judgement, and a subsidy consultant without engineers cannot make it.
The scheme is understood, the project is not
WBSO reimburses development hours, MIT covers the wider project costs. Which of your work falls into which pot is the question that determines how much you actually get back.
Curious what this looks like on your data?
Book a free 30-minute call with the solution architect who also builds the work. You walk through your processes together and get an honest answer on where the numbers are for you, and where they are not.
Free intro call
30 minutes, no obligation, directly with the builder.
How it works, without risk on your side
1. Funding check, 30 minutes
We go through the plan and say plainly which schemes fit, which do not, and roughly what stays on your own books. If nothing fits, you hear that in the same call.
2. Application and technical file
We write the application from the actual build plan: which parts are genuinely development, which hours belong to them, and why that qualifies. That file is what carries you through an RVO audit.
3. Build, with the hours recorded properly
The project gets built and the S&O hours are recorded as the scheme requires. No reconstruction afterwards from memory, which is where most companies lose their claim.
Why not a subsidy consultancy or a no-cure-no-pay agency?
| Subsidy consultancy | No cure no pay | Stratalytic | |
|---|---|---|---|
| What you get | An application | An application, on commission | Application plus the working project |
| Technical judgement | By generalists | Optimised for approval odds | By the engineer who builds it |
| Risk at the audit | Yours | Yours | The file matches the actual work |
| What it costs you | Fee, regardless of outcome | A share of the grant | Included in the project |
Before you book
Does our AI project qualify for WBSO?
WBSO reimburses development work that is technically new for your organisation: model development, data engineering, architecture, technical research. Wiring up an existing SaaS tool does not qualify. The honest test is whether your team faces a technical problem with an uncertain outcome. We judge that in the first call, on your actual plan.
How much do we get back?
WBSO gives 36% on the first €391,020 of R&D labour costs, 50% if your company is under five years old, and 16% above that. MIT adds 35% on the broader project costs. Combined, that regularly clears 50% of total project cost, but the exact figure depends on how many hours are genuinely R&D.
Can you apply and build at the same time?
Yes, and that is the point. A separate advisor writes an application based on what you tell them; we write it from the build plan we are going to execute. That means the hours, the deliverables and the technical narrative already line up when RVO comes to check.
What if the application is rejected?
Then the project is scoped on its own business case, which is how we advise you to judge it anyway. Subsidy should shorten the payback period, not be the reason to start. If a project only makes sense with a grant, we say so.
What are the deadlines?
WBSO runs in application rounds through the year and must be filed before the work starts, which is the mistake we see most often. MIT R&D has a fixed opening per province with a hard closing date and is usually oversubscribed. In the call we tell you which window you are realistically aiming for.
