Avenryx SystemsPricing
What it costs to keep custom software alive
Software does not finish. Dependencies age, platforms change, and the business asks for things it could not imagine before using the system. Budgeting for that is a planning decision, not a surprise.
Outcomes
- A predictable annual figure
- Clear SLA tiers and response times
- Security patching handled continuously
- Capacity reserved for improvement, not just fixes
Pricing
Where it is used
Essential support
Security patching, uptime and bug fixes — from €1,500 per month.
Support plus evolution
Maintenance with a monthly development allocation — €4,000 to €12,000 per month.
Dedicated ownership
A named team continuously improving the product.
What we deliver
- System size and integration count
- Required response and resolution times
- Compliance and audit obligations
- Rate of business change
- Infrastructure and licence costs
Who this is for
- Companies budgeting the running cost of a system after launch.
- Teams that inherited software from a supplier who has gone quiet.
How delivery runs
- 01
Scoping
One to two weeks on the real workflow, systems and data. Output is a written scope and an indicative band.
- 02
Phased plan
The first usable release is identified explicitly so spend produces something usable early.
- 03
Fixed first phase
Phase one is quoted as a fixed price where scope allows; later phases are re-estimated with real velocity data.
- 04
Change log
Anything added after sign-off is estimated and scheduled in writing, so the budget never moves quietly.
Realistic timeline
Weeks 1–2
Handover, access and a documented current state.
Month 1
Backlog of security and stability items addressed first.
Ongoing
Monthly updates, monitoring review and a prioritised improvement queue.
Build or buy
Buy something existing when
- Managed hosting and monitoring services rather than building operations tooling
Build custom when
- Retained capacity for the changes only someone who knows your system can make
What moves the price
Support hours and response target
Business-hours response is a fraction of the cost of a 24/7 target with guaranteed restore times.
Dependency and security updates
Framework, library and platform updates are unavoidable running cost; deferring them turns into a project later.
Hosting and third-party services
Infrastructure, monitoring and external API charges scale with usage and should be modelled explicitly.
Change volume
Retained development capacity for small improvements is typically the largest part of an annual maintenance line.
Where projects go wrong
Budget set before scope
A number agreed before discovery is a guess. We give a band after a short scoping phase and narrow it once the workflow and integrations are documented.
Data migration priced last
Legacy data is rarely as clean as expected. We survey the actual export during discovery rather than assuming it at the end.
FAQ
Questions buyers ask
What percentage should we budget?+
12 to 20 percent of build cost per year is the usual planning figure for an actively used system.
Can we support it ourselves?+
Yes. You own the code and we provide a documented handover — several clients take it in-house after a year.
You already have the idea. Let's define what comes next.
Available in 12 languages