Skip to content
coderband

How Much Does Software Maintenance Cost in 2026?

Software maintenance runs about 15–25% of build cost a year in 2026: $30,000–$50,000 on a $200,000 product. What it covers, deadlines and ways to buy it.

coderband engineering12 min read

In 2026, plan to spend 15–25% of what your software cost to build, every year, to keep it healthy. By the rules of thumb development firms publish, that is $30,000–$50,000 a year on a $200,000 product, and one vendor’s sample of 24 SaaS products put the median at 21–26%. The total depends on how many things you rely on that someone else can retire (runtimes, app stores, third-party APIs, AI models), how far behind your dependencies already are, and the hourly rate you buy the work at.

Key takeaways

The published rules of thumb

We found no independent survey of maintenance budgets. The figures below all come from companies that sell software development, so read them as what vendors tell buyers to expect.

Source Date Yearly maintenance as a share of build cost Basis
Keyhole Software (vendor) January 2026 15–25%, or $30,000–$50,000 on a $200,000 project Custom software; no source cited for the figure
Netguru (vendor) November 2026 15–20% Mobile apps; cites its own portfolio, no sample size
Topflight (vendor) September 2026 About 25% Mobile apps; its own estimate
Wavect (vendor) July 2026 Medians of 24%, 21% and 26% in years one to three 24 SaaS products it tracked from 2023 to mid-2026

Wavect calls its sample directional, and the spread is wide: the middle half of its products spent between 13% and 40%, depending on the year. For a picture of where aging systems end up, the US Government Accountability Office reported in July 2026 that about 80% of federal IT spending goes to operating and maintaining existing systems, many of them outdated.

What maintenance actually consists of

The international standard for software maintenance, ISO/IEC/IEEE 14764 (third edition, 2022), defines the types. The IEEE Computer Society’s SWEBOK Guide (chapter 7) summarizes them as two kinds of correction and three kinds of enhancement. In plain words:

Type What it covers Examples Main cost driver
Corrective Fixing problems after someone finds them A webhook that fails on retry; a report with wrong totals Test coverage and how many features you run
Preventive Fixing latent faults before they cause a failure Security patches; fixing a race condition before it corrupts data Number of dependencies and the volume of new vulnerabilities
Adaptive Keeping the product usable as its environment changes Runtime upgrades before end of life; app store SDK deadlines; API and model retirements How many platforms and third parties you depend on
Perfective Improving what already exists Faster queries, clearer screens, refactoring, documentation User feedback
Additive Adding new functionality New features Your roadmap; budget it separately

The standard also defines emergency maintenance: an unscheduled, temporary change that keeps a system running until the proper correction is made. SWEBOK notes that surveys over the years put enhancing and adapting at over 80% of maintenance work, so a budget that only covers bug fixes covers the smaller part. The standard leaves out operations work such as backups and system administration. Your budget can’t.

The cost components, with November 2026 facts

Runtime and framework end of life

Every runtime publishes a retirement schedule. After the date, the project ships no more security fixes for that version.

Runtime Latest to reach end of life Next Support policy
Node.js 20, on April 30, 2026 22 on April 30, 2027; 24 on April 30, 2028 About 30 months per LTS line
PHP 8.1, on December 31, 2025 8.2 on December 31, 2026; 8.3 a year later Two years of active support, then two of security fixes
Python 3.10, in October 2026 3.11 in October 2027 Five years per release, security fixes only after about two
.NET 8 and 9, both on November 10, 2026 10 and 11, both on November 14, 2028 Three years for LTS releases, two for STS

Frameworks add their own clocks. React Native, for example, maintains only its latest three minor series, and its schedule shows a new one about every two months.

Dependency and security patching

The CVE Program published 48,244 vulnerability records in 2025 and 72,812 in the first three quarters of 2026. The third quarter alone had 36,962, more than the first two combined. Black Duck’s 2026 audit data (vendor research) found at least one known vulnerability in 87% of 947 commercial codebases, and components four or more years out of date in 92%.

Two incidents from October show what the work looks like. PHP2Shell and HTTP2Shell were both fixed in the runtime, not in application code: in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, and in Node.js 22.23.4, 24.22.1 and 26.12.1. PHP 8.1 and Node.js 20, both past end of life, got no release. Someone had to know which runtime served production, then upgrade it, restart it and verify it that week. PHP alone has shipped security releases on five dates so far in 2026.

Mobile platform deadlines

Both stores raise their minimum SDK every year. Since April 28, 2026, apps uploaded to App Store Connect must be built with Xcode 26 and the iOS 26 SDK. Since August 31, 2026, new apps and updates on Google Play must target Android 16 (API level 36), and existing apps must target at least API level 35 to stay available to new users on newer Android versions. An app that misses the requirement can’t ship an update, including a security fix.

Third-party API and model deprecations

Providers retire what you build on, with notice measured in months. Anthropic deprecated Claude Sonnet 4.5 on September 30, 2026 and retires it on November 30; its policy is at least 60 days’ notice. OpenAI shut down its Assistants API on August 26, 2026, a year after announcing it, and shuts down gpt-5 and o3 on December 11, 2026, six months after notice. Each migration means testing your prompts and outputs against the replacement before the date.

Hosting and monitoring

For a small product these are the smallest lines: Supabase Pro from $25 a month with daily backups kept for seven days, Vercel Pro at $20, Sentry’s Team plan at $26 billed annually, and Apple’s $99-a-year developer membership. Usage comes on top.

Bug fixes and small improvements

The rest is the work users notice: fixing what they report and making the small changes they ask for. It is the largest share of the budget below, and the part whose size you control most.

What skipping maintenance costs

You’ll see claims that deferred maintenance costs some fixed multiple more later. We couldn’t trace any of them to a study, so they aren’t here. What is documented:

Four ways to buy it

The senior hourly ranges come from our rates guide. The contract mechanics of each model are in fixed price vs. time and materials vs. retainer.

Option What it costs Fits when Check
In-house hire The median US software developer earns $135,980 a year (May 2025). Wages were 70.0% of employer cost in private industry in June 2026, so about $194,000 with benefits You have full-time product work and maintenance is one slice of it Who covers when that person is away or leaves
Freelancer Senior full-stack: $100–$150 an hour in the US, $58–$85 in Eastern Europe, $50–$80 in Latin America (marketplace data, vendor) A small, stable product and an owner who can direct the work Availability in the week a critical patch lands
Agency retainer Senior teams: $100–$250 an hour in the US, $85–$165 in Western Europe, $58–$95 in Central and Eastern Europe, sold as monthly hours. Ours, the Senior Team Retainer, is $6,000 a month for 30 senior hours or $9,500 for 50 The work is steady but changes shape every month Who does the work, and what happens to unused hours
Support plan or SLA Published plans (vendor prices): $999 a month for up to 4 bug-fix hours and critical security patches within 72 hours; $1,700 a month for 20 hours; $1,200 a month for emergency-only cover with 24-hour incident resolution A committed response time matters more than development capacity The included hours are few; one of these plans bills the overflow at $150 an hour

A response-time commitment and development capacity are different products. If you need someone to answer at 3 a.m., buy on-call cover and get the response time in writing. If you need the upgrades done, buy hours. Whichever you choose, the red flags are the same: unnamed people, no written scope, and code that lives outside your accounts.

A worked budget for one product

This example is illustrative. Take a B2B SaaS product that cost $200,000 to build: a Next.js web app on Vercel, a Supabase Postgres database, Stripe billing, one LLM feature and a React Native companion app. The hours are our assumptions for a product of this shape, not measurements. The rate is $150 an hour, inside the US senior range. New features are left out.

Line Assumption Hours a year Cost at $150 an hour
Routine dependency and security updates 3 hours a month 36 $5,400
Urgent out-of-band patches 2 incidents × 6 hours 12 $1,800
Runtime and framework major upgrade One a year 30 $4,500
Store SDK deadlines and React Native upgrades Both stores, yearly 30 $4,500
API and model migrations 2 migrations × 8 hours 16 $2,400
Bug fixes 6 hours a month 72 $10,800
Small improvements 8 hours a month 96 $14,400
Monitoring review, backup restore test, access review 2 hours a month 24 $3,600
Engineering subtotal 316 $47,400
Services Supabase $300 + Vercel $240 + Sentry $312 + Apple $99 $951
Total $48,351

That is 24% of the build cost: the top of the vendor range, and level with Wavect’s first-year median. Change only the rate and the same 316 hours cost $32,551 with services at $100 an hour (16%), or $79,951 at $250 (40%). The work averages 26 hours a month, about eight working weeks a year for one engineer, but it doesn’t arrive evenly. The upgrade, the store deadlines and the urgent patches land when their owners decide.

What a maintenance plan should include

  1. A named owner for patching, and a written rule for how fast critical fixes ship.
  2. An inventory: runtimes and versions in production, base images, dependencies, and every third-party API and model you call.
  3. A deadline calendar: end-of-life dates, store SDK requirements and provider retirements for the next 12 months.
  4. Automated dependency update pull requests, reviewed on a schedule, with tests on the paths that make money.
  5. Error tracking, uptime checks and cost alerts that a person reads.
  6. Backups with a tested restore.
  7. An access review: who can reach production, the repository, DNS, the stores and billing, with every account in your company’s name.
  8. A monthly hours budget for bug fixes and small improvements.
  9. A regular written update: what shipped, hours used, what comes due next.
  10. A runbook, so a second person can deploy, roll back and rotate a secret.
  11. Exit terms: the code in your repository, notice to cancel, and what gets handed over.

How AI-built apps change the picture

Apps built with Lovable, Bolt, Replit, Cursor or v0 change the budget in three ways.

There’s a catch-up cost first. Steady maintenance assumes tests, error tracking, backups and a deploy pipeline. Stabilizing an AI-built app means adding them, and published prices for that run from $7,500 to $40,000 (vendor numbers, in our guide to fixing a vibe-coded app). In Veracode’s 2025 tests, AI-generated code introduced a security flaw in 45% of tasks, and leaked API keys are a common finding. Our AI-App Rescue Audit ($1,490 fixed, 72 hours) ends with a fixed quote for that work.

The code costs more to change. GitClear’s analysis of 211 million changed lines found that refactoring fell from 25% of changes in 2021 to under 10% in 2024 while copy-pasted code rose. Maintenance pays that back later.

Review stays a person’s job. An AI tool can draft an upgrade or a patch, but someone still has to decide what ships and verify it. On our own work, a senior engineer reviews all code before delivery, as our terms set out.

Putting a monthly number on it

The worked example comes to 26 hours a month. Our Senior Team Retainer comes in two sizes: Retainer 30 is $6,000 a month for 30 senior hours, and Retainer 50 is $9,500 for 50. Retainer 30 adds up to 360 hours a year, against the example’s 316.

Senior engineers work in your repository on patching, runtime upgrades, fixes, reviews, infrastructure and features. We plan with you every week, send a weekly written update of what shipped and the hours used, and hold a monthly roadmap call where you can move between plans. Unused hours roll into the next month, up to 20% of the plan, and a heavier month can add hours at the same effective rate with your written approval. The first week includes a codebase review and the first shipped improvement. If that week isn’t worth it, cancel and the first month is refunded in full. After that, cancel anytime, effective at the end of the paid month.

We work US Eastern business hours, and on-call cover can be quoted separately. To talk through your own stack and its deadlines first, book a call: 30 minutes on your product, team and priorities.