Transparent by design.
One rate ladder, two ways to use it: hourly support and fixed-price projects. The longer you commit, the lower the rate. No hidden fees. All prices are exclusive of VAT — EU reverse charge applies for cross-border B2B transactions.
Rates
Three rates, set by how long you commit. After the assessment, your rate applies to support and fixed-price projects alike — across all your installations.
Systems not built by Imbra start with a separate ad-hoc assessment — from €800 (one day) — before any commitment. Commitments and fixed prices are quoted from it.
- Scheduled as available
- 4-hour minimum
- Also the assessment rate
- Minimum 20 hours / month
- Hours reserved
- Minimum 20 hours / month
- Hours reserved
- 24/7 on-call add-on
Notes
- Reserved capacity is limited; commitments are accepted in order of signing.
- 24/7 on-call is an optional add-on to the Annual tier and is quoted separately.
- Response times, service levels, and expenses are defined in the Master Service Agreement; scheduling, scope, and deployment responsibilities in each Statement of Work.
Engineering Support
Escalation support for industrial software systems — the level your own team or vendor calls when they are stuck: incident investigation, root cause analysis, hotfixes, workaround guidance, documentation, and technical exploration.
Project Engagement
Refactoring, new features, migrations, and integrations. The system assessment (see 1) produces the hour estimate; multiplied by your rate, it is the fixed price — written in the Statement of Work before work starts.
The project consumes its estimated hours, not the hours actually worked: if Imbra's estimate was too low, Imbra absorbs the difference, and the price moves only if the scope does. A project of at least 20 hours per month over three months or more earns the Quarterly rate on its own.
Notes
- A day is 8 hours.
Pricing Examples
Quarterly term, renewed for a year. Two-day assessment of a mid-sized legacy test framework, then support at the minimum volume.
Annual term at 80 hours a month. Four-week assessment of a complex system estate, then support covering every installation under one agreement.
No commitment. One-day assessment, then an 80-hour integration bridging two systems.
Quarterly term. A 400-hour project over four months, run with the client's own team — three-day assessment, then migration off an unsupported runtime.
No commitment. 8-hour engagement on an already-assessed system, on a weekday, subject to availability.
No commitment. 8-hour engagement on an already-assessed system, on a Saturday, subject to availability.
Full terms, including service levels, are defined in the Master Service Agreement.
Not sure which model fits?
Describe your situation and we will recommend the right engagement type.