Software Maintenance and Support: What Businesses Get Wrong

Most businesses treat software as a purchase. You pay, it's delivered, it's done. Then eighteen months later the site is running an outdated version with known security holes, backups stopped working months ago, and the developer who built it has moved on.

This is the most predictable and most preventable technology failure in Indian small business — and it comes from a single wrong assumption: that finished software stays finished.

Why Software Needs Ongoing Maintenance

Software doesn't wear out, but the world around it changes:

Security vulnerabilities get discovered in the frameworks, libraries, and plugins your software uses. When they're found, patches are released — and unpatched systems become known targets. Most compromised small business websites weren't specifically targeted; they were running something with a known, published, unfixed weakness.

Underlying platforms change. Server software, PHP versions, browsers, and mobile operating systems all update. Software that worked perfectly can break when the ground beneath it moves.

Third-party services change. Payment gateways update their interfaces, messaging APIs change requirements, cloud services deprecate features. Each one can break an integration without warning.

Businesses change. New services, revised pricing, updated compliance requirements — the software has to keep up.

What Maintenance Should Actually Include

"AMC" means very different things from different providers, so define it rather than assume it. A meaningful maintenance arrangement covers:

Security updates to frameworks, plugins, and libraries — applied promptly, not annually.

Backups that are verified. Not "backups are configured" — someone actually confirming they run and that a restore works.

Uptime monitoring so problems are noticed by your provider rather than reported by a customer.

Bug fixes for defects in the delivered work.

Small content and configuration changes — a phone number, a price, a new team member.

Platform compatibility as servers and browsers update.

A defined response time for urgent issues, in writing.

Notice what's not automatically included: new features. Adding functionality is development work, not maintenance, and pretending otherwise is how both sides end up frustrated. Agree the boundary explicitly.

The Backup Question That Exposes Everything

Almost every business believes it has backups. Considerably fewer have working ones.

Ask this today: "Can you restore a file from backup right now, while I watch?"

If nobody can demonstrate it within an hour, you don't have backups — you have an assumption. And a backup stored on the same server as the original is not a backup; it's a copy that disappears with everything else.

Confirm four things: how often backups run, where they're stored (somewhere separate), how far back they go, and who verifies they're succeeding.

What Maintenance Should Cost

A common industry benchmark for annual software maintenance is a percentage of the original development cost — often cited in the range of 15-20% per year, varying with complexity and how much content support you need.

That figure surprises businesses, but compare it against the alternatives: an emergency rebuild after a security compromise, revenue lost while a site is down during peak season, or data lost because backups silently failed. Maintenance is insurance with a productivity benefit attached.

Some providers charge per task instead of a retainer, which is cheaper if you rarely need changes and painful when you need something urgently and there's no agreement in place.

The Questions to Ask Before Signing an AMC

What exactly is included, and what is billed separately? Get the boundary between maintenance and new development in writing.

What is the response time for an urgent issue? "We'll look at it" is not a commitment. Ask for hours.

How many hours of changes are included monthly? Unlimited support is not a real offering; a defined allocation is.

Who holds the credentials? They should be yours, shared with the provider — not held by them alone.

What happens if we end the contract? Handover terms for code, documentation, and access should be agreed at the start, not negotiated during a disagreement.

Do you maintain software you didn't build? Worth knowing, because businesses frequently need this and many providers decline.

If Your Original Developer Has Disappeared

A common situation, and it's recoverable. Before approaching anyone, gather what you can: hosting login details, domain registrar account, any source code you have, and a list of third-party services in use.

Then be prepared for an assessment phase. Any competent provider taking over unfamiliar software needs time to understand it before quoting ongoing support — and one who quotes without looking is guessing.

The urgent item regardless: confirm your domain is registered in your business's name with renewal notices going to an email you control. Expired domains are among the most avoidable disasters in small business, and they usually happen because the renewal notice went to someone who left.

The Simplest Framing

You don't own software the way you own furniture. You own it the way you own a vehicle — it works well when serviced and becomes expensive and unreliable when neglected.

Budget for the servicing at the same time you budget for the purchase, and the surprises stop happening.

Need support for software someone else built, or a maintenance arrangement for a new project? Get in touch — we're happy to start with an assessment of what you currently have.