Home/Services/Maintenance & support

// Maintenance & support

Maintenance and support for the custom software your business runs on

“Our developer is moving on, and someone needs to keep this running.” We provide custom software maintenance and support for the systems operations teams, plants and contractor networks depend on, including ones someone else built. That means security updates, backups, fixes, small improvements and, if you want it, hosting. You talk directly to the engineers doing the work.

Example (hypothetical): a monthly maintenance pass
✓ database backup restored to a test copy✓ security patches applied to framework and libraries! SQL Server 2016 is past Microsoft’s extended support! certificate renewal is manual: automate it✓ domain set to auto-renew→ “add a column to the weekly report” → maintenance→ “add a purchase approval workflow” → new work, scoped first

// What’s included

What’s included in software maintenance and support, and what’s a new project

Maintenance is the planned work that keeps a system healthy. Support is what happens when someone hits a problem: a supervisor can’t log in, an import didn’t run, a total looks wrong. Custom software needs both, because the world around it keeps changing even when the code doesn’t: browsers update, outside services change their APIs, and the database and frameworks underneath reach end of support.

Software maintenance and support services cover four kinds of work:

Type of work
What it means
Example (hypothetical)
Corrective
Fixing something that’s broken or wrong.
A daily report double-counts orders entered after midnight.
Adaptive
Keeping the software working as things around it change: a new browser version, an outside service’s new API, a database version losing support.
A shipping carrier retires the API version your order screen uses.
Preventive
Fixing small problems before they turn into outages.
A search that slows down every month as the table grows gets an index before it starts timing out.
Small improvements (sometimes called perfective maintenance)
The modest changes your team asks for as they use the system.
A new filter on a list, an extra column on an export, clearer wording on a form.

Where new work starts. A new workflow, a new set of screens, a connection to another system or a new group of users (say, opening an internal tool to your vendors) is a project, not maintenance. We scope those separately, like anything else in our services. When a request sits near the line, we tell you which side it’s on before we start.

For the routine tasks, by month, quarter and year, see our web application maintenance checklist.

// Keeping it running

Web application hosting, backups, security and updates

This is the unglamorous work that decides whether the system is up at 6 a.m. when the first shift logs in.

Hosting

We can host your application, so the engineers who change the code also run the environment it lives on. When something breaks, nobody has to settle whether it’s the code or the hosting before the right person looks.

Backups and restore tests

Backups of the database and uploaded files only matter if they restore. A test restore to a separate copy proves the backup works and shows how long a real recovery takes.

Security and dependency updates

Frameworks, libraries, the server operating system and the database all get security fixes, and each eventually loses support. For example, Microsoft’s extended support for SQL Server 2016 ended in July 2026. We plan upgrades like that before they turn urgent.

Monitoring and error alerts

Uptime checks and error logging send failures to an engineer instead of leaving them with whoever hit them. You want to learn about a stopped import from the logs, not from a supervisor at shift change.

Domains and certificates

An expired domain or security certificate can take a working system offline overnight. Certificate lifetimes are shrinking: a CA/Browser Forum ballot cuts the maximum lifetime of public TLS certificates from 398 days to 47 days in steps between March 2026 and March 2029. Renewals need to be automated and watched.

// Inherited systems

Supporting and maintaining software we didn’t build

The developer who built your system took another job, or the agency that launched it moved on. The system still runs, and people depend on it every day.

Taking over maintenance of existing software starts with a review of the code, accounts and hosting: how the system fits together, how a release reaches production, what it depends on and where the risks are. We both know what we’re taking on before we agree to keep it running.

The handover matters as much as the code. While your outgoing developer is still reachable, ask for everything on our software handover checklist, which builds the request for you. If the developer has gone quiet and work stalled mid-build, that’s a software project rescue, which starts differently. If an employee built the tool and people now rely on it, see prototype to production.

  • ✓The code repository, with its full history
  • ✓Written steps to build and release it, or a note that none exist
  • ✓Hosting, database and file storage access
  • ✓Domain, DNS and certificate renewal dates
  • ✓Outside services and their API keys: payments, email, maps
  • ✓The latest backup, and whether anyone has restored it
  • ✓Documentation: what exists, what’s out of date, what’s missing

// Support requests

How support requests reach an engineer

When something breaks or someone needs a change, you contact the engineers who maintain your system directly, with no account manager relaying messages. They already know the code, the hosting and what was fixed last time, so you don’t start from scratch.

We don’t publish response-time promises. Tell us how many people are affected and whether work has stopped, so the engineer can weigh it against everything else on your list. Application support for custom software goes faster when a request includes:

  • ✓What you were trying to do, and what happened instead
  • ✓Who’s affected: one user, one site or everyone
  • ✓When it started, and anything that changed around then
  • ✓A screenshot or the exact error message
  • ✓Whether people are blocked or can work around it
Example (hypothetical): one support request
→ “The weekly export has been empty since Monday.”✓ read by an engineer who maintains the system✓ cause: an outside service changed its date format✓ fix released; this week’s export re-run and checked→ change noted in the system’s log
“

They take the time to truly understand the use case and business need and suggest solutions tailored to our specific needs. Solutions often exceed expectations as to final design and functionality. They are always quick to respond to issues that require urgency and frequently offer help outside the scope of current projects.

Scot Carson

Chief Experience Officer, Amusement Advantage

// Getting started

How ongoing software support starts

Four steps from the first conversation to routine maintenance. Your first call is with an engineer.

Step 1

Review and handover

We review the code, accounts, hosting and documentation, and help you collect what the previous developer should hand over. You come away knowing what you have, including the risks nobody mentioned.

Step 2

Stabilize

Urgent items come first: overdue security updates, backups nobody has restored, a certificate or domain close to expiring, errors people have learned to work around. If nobody has written down how to release the system, we do.

Step 3

Agree what’s covered

We agree on what maintenance includes for your system (updates, backups, monitoring, small changes) and what counts as new work.

Step 4

Ongoing maintenance

Routine updates, backups and checks, fixes when something breaks, and the small improvements your team asks for, from the same crew each time.

// Credentials

The basics, before you ask.

Since 2018

Building and supporting software

Orlando, FL

100% U.S.-based team, clients nationwide

SAP Ariba

Registered supplier

NDAs welcome

Happy to sign before you share details

DesignRush Top Web Design Companies badge

Top Web Design Companies

DesignRush

// FAQ

Custom software maintenance and support FAQ

What’s the difference between software maintenance and support?

Maintenance is planned work that keeps a system healthy: security updates, backups, monitoring, renewals and small fixes. Support is responding when someone hits a problem or needs help. Custom software needs both, and we provide both.

Will you maintain software someone else built?

Yes, after we’ve reviewed the code, accounts and hosting so we know what we’re taking on. If the project stalled before it was finished, start with software project rescue instead.

What do we need from our previous developer?

The code repository with its full history, hosting and domain access, database access and recent backups, logins for outside services such as payments or email, and whatever documentation exists. Our free software handover checklist generates the request for you.

What’s covered versus a new feature?

Maintenance keeps the software running, secure and current: fixes, updates, backups and small adjustments. New workflows, screens or integrations are new work, and we’ll always say which is which before starting.

How quickly do you respond?

We don’t publish response-time promises. You reach the engineers who know your system directly, without an account-manager relay.

Do you host it too?

We can. The same crew builds, hosts and maintains it, so changes and fixes come from people who know the code.

// Bring us in

Tell us about the software your business runs on.

A new build, a system that’s hard to use, a stuck project or a prototype that needs to go live. An engineer, not a salesperson, will get back to you.

202-88-MAGIC · or email info@effortlesspresence.com