The verdict in three sentences
For a business web application delivered for EUR 60,000 to 150,000 excl. VAT, a reasonable application support and maintenance contract costs 15 to 20% of the build cost per year, or EUR 1,500 to 4,000 per month in 2026. Price matters less than four clauses: resolution times by severity, ownership of the code and accounts, a priced exit plan and penalties that actually bite. A contract without those four points makes you dependent on your vendor from year one.
What application support costs in 2026
Edinburgh's market (fintech, insurance, life sciences, public sector suppliers) keeps rates high: a senior developer bills roughly EUR 550 to 750 (about GBP 470 to 640) per day at a local consultancy, EUR 450 to 650 as a freelancer. Support packages combine a corrective maintenance and security baseline with a volume of enhancement days.
| Support package | Monthly price excl. VAT | Enhancement days included | Critical incident | Typical fit |
|---|---|---|---|---|
| Corrective baseline only | EUR 600 to 1,200 | 0 to 1 day | 8 business hours | Stable app, few changes |
| Essential | EUR 1,500 to 2,200 | 3 days | 4 business hours | SME, 20 to 80 users |
| Standard | EUR 2,300 to 3,200 | 5 days | 2 business hours | Core business tool |
| Enhanced | EUR 3,300 to 4,000 | 8 days | 1 h, 24/7 on-call | Critical app, external clients |
| Time and materials | EUR 550 to 750 per day | On demand | No commitment | Occasional needs |
| Annual rule of thumb | 15 to 20% of build | Per package | Per SLA | Finance budgeting rule |
These prices usually include security updates for dependencies (framework, libraries), monitoring and backups. Hosting is almost always billed separately: budget EUR 80 to 600 per month depending on load.
The clauses that actually protect the company
A standard support contract has about ten articles. Six of them carry most of the financial risk.
| Clause | What to demand | Common trap |
|---|---|---|
| Times by severity | Critical 2 to 4 h, major 1 business day, minor 5 days | "Acknowledgement" time instead of resolution time |
| Code ownership | IP assignment on delivery, Git repository in the client's name | Code stored on the vendor's account |
| Exit plan | Written plan, documentation, 5 to 10 handover days at contract rate | Exit "quoted on request" with no cap |
| Penalties | 2 to 5% of the monthly fee per breach, capped at 20 to 30% | Penalties capped at 5%, no deterrent effect |
| Unused days | Rollover for up to 3 months | Days lost at month end |
| Term and exit | 12 months, 3-month notice, indexed price review | 36-month automatic renewal |
Code ownership deserves special attention: without an express assignment clause, copyright generally stays with the developer or their employer. Also require that cloud accounts, the domain name and the code repository are opened in your company's name, with admin access for your team.
How to size the enhancement volume
The first year after go-live concentrates requests: user feedback, screen adjustments, new exports. In our experience, an application with 40 to 60 screens uses 4 to 6 enhancement days per month in year one, then 2 to 4 days afterwards. Plan a Standard package for the first year and review the volume at month 12. Ask for a monthly dashboard: open tickets, SLA performance, days used, identified technical debt.
Mini case study
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
Claire, finance director of a 140-employee manufacturer in Edinburgh, has just received a production planning application billed EUR 92,000 excl. VAT. The vendor offers a Standard package at EUR 2,900 per month, or EUR 34,800 per year: 37.8% of the build, far too much. Claire renegotiates an Essential package at EUR 1,650 per month with 3 enhancement days, plus time and materials at EUR 600 per day beyond that. With 1 extra day per month on average, the annual cost drops to 19,800 + 7,200 = EUR 27,000, or 29% of the build in year one, then around EUR 19,800 (21.5%) from year two. She adds a 4-hour resolution time for critical incidents, a 4% penalty per breach capped at 25% and an exit plan fixed at 6 days. Savings over 3 years: about EUR 31,000 compared with the initial offer.
FAQ
What annual budget should I plan for web application support?
Budget 15 to 20% of the build cost per year. For an EUR 80,000 application, that means EUR 12,000 to 16,000 per year, excluding hosting.
What is the difference between support and warranty?
The warranty covers defects in the delivered scope free of charge, usually for 3 months after acceptance. Support takes over afterwards and includes security, monitoring and enhancements for a monthly fee of EUR 1,500 to 4,000.
Should the contract specify response time or resolution time?
Always resolution or workaround time. An "acknowledged within 1 hour" commitment guarantees nothing if the fix takes 3 days; aim for 4 hours maximum on critical incidents.
Can we change vendor mid-contract?
Yes, if the exit plan is written: up-to-date documentation, 5 to 10 handover days and full access. With a 3-month notice period, the switch happens without service interruption.
Are unused enhancement days lost?
It depends on the contract. Negotiate a 3-month rollover: on a 5-day package, that avoids losing up to 15 days per quarter, more than EUR 9,000 of work.
Let's scope your project. Send us your application, its build cost and your availability requirements: we will price a support contract with SLA, exit plan and calibrated enhancement volume. Detailed quote within 48 h. WhatsApp +221 77 596 93 33.
Mohamed Bah
Fondateur, Kolonell
Passionate about digital and entrepreneurship in Africa, Mohamed has been helping Sénégalese businesses with their digital transformation since 2020. Founder of Kolonell, he believes every SME deserves a professional and accessible online présence.
