Software maintenance costs after launch: what to budget and why it matters

Software does not wear out like machinery, but the world around it moves constantly. Browsers update, operating systems change, security vulnerabilities are discovered in the libraries every application depends on, and third party APIs deprecate old versions on their own schedule.

A well built application left completely untouched will usually keep working for a while — and then fail suddenly when a dependency, integration, or platform change finally lands. Maintenance is what converts those surprises into routine, scheduled work.

Maintenance is several distinct activities, and a good agreement names them explicitly rather than selling vague support hours.

A useful rule of thumb across the industry is 15 to 25 percent of the original build cost per year for active maintenance and improvement. The exact figure depends on how many integrations the system has and how quickly the business changes.

For typical projects in 2026 that translates to: a business website at $100 to $400 per month, an internal tool or CRM at $300 to $1,200 per month, and a customer facing SaaS platform at $1,000 to $5,000 per month including monitoring, updates, and a steady improvement cadence. Hosting itself is usually the smallest line: most business applications run comfortably on $20 to $200 per month of managed infrastructure.

Neglect has a predictable arc. For the first year nothing visibly breaks. Then an integration fails during a busy week, or a security advisory lands in a framework version three years behind, and the fix that would have been a scheduled afternoon becomes an emergency rebuild under pressure.

Security is the sharpest edge: most successful attacks on small business systems exploit known vulnerabilities that had patches available for months. A modest patching cadence is the cheapest security control that exists.