SOFTWARE & APP MAINTENANCE

Keep Your Software, Apps & SaaS Products Working After Launch

Ongoing technical support for web apps, mobile apps, SaaS products and internal software — including bug fixes, dependency updates, API changes, deployment issues, performance work and practical product improvements.

Maintenance is defined around the system and level of responsibility. Small fixes and ongoing improvements can fit maintenance, while major new modules, large redesigns or architectural rebuilds are scoped separately.

Systems We Can Review

Web applications
Mobile apps
SaaS products
Customer portals
Admin systems
Internal business software
APIs & backends
AI-enabled software
Automation-backed applications

What Software & App Maintenance Can Include

The exact mix depends on the product and technology stack. These are common maintenance responsibilities after a software product is already in use.

Bug Fixes

Investigate and resolve defects, broken workflows, regressions and unexpected application behavior.

Dependency Updates

Update frameworks, libraries, packages or SDKs where needed and assess compatibility risk.

API & Integration Changes

Adapt software when payment, email, AI, CRM or other third-party APIs change.

Backend Maintenance

Support APIs, queues, background jobs, authentication, storage and server-side application logic.

Database Maintenance

Review data issues, migrations, indexes, storage growth and database-related application problems.

Performance Work

Investigate slow pages, heavy queries, expensive API calls or inefficient application behavior.

Deployment Support

Resolve build, environment, configuration, release and deployment problems.

Small Feature Improvements

Add reasonable enhancements or workflow improvements within the agreed maintenance scope.

Monitoring & Error Review

Use appropriate uptime, logs or error monitoring to detect and diagnose recurring problems.

Mobile Apps Need Platform Maintenance Too

iOS and Android ecosystems change over time. SDKs, permissions, store requirements, device versions and third-party libraries can eventually require updates even when the app itself has not changed much.

iOS / Android compatibility
SDK / dependency updates
Build configuration
Push notification issues
Store submission updates
Backend/API compatibility
Crash and error investigation

App Store Updates May Be Part of Maintenance

Where included in scope, SiteLumo can help prepare updated builds and normal App Store / Google Play submission changes.

Developer accounts remain under the client’s ownership, and store approval remains controlled by Apple or Google.

SaaS Products Keep Moving

A live SaaS product may need ongoing work across authentication, billing, user accounts, email, background jobs, analytics, integrations and infrastructure.

Maintenance can keep the core product stable while smaller improvements are added in a controlled way.

Common SaaS Maintenance Areas

Login / account issues
Subscription or payment changes
Email / notification problems
Third-party API changes
Admin-tool fixes
Background job failures
Usage / performance issues
Small workflow improvements

Software Built by SiteLumo?

Maintenance can continue after delivery so fixes, dependency updates, small improvements and provider changes have a clear technical owner.

The ongoing support arrangement can stay focused or expand as the product becomes more important to the business.

Software Built Somewhere Else?

We can often take over an existing product after review. We first need to understand the codebase, repository access, deployment process, infrastructure, dependencies, documentation and known problems.

A fragile or undocumented system may need a stabilisation project before normal maintenance becomes realistic.

Maintenance vs. New Development

Software maintenance should support a live product without pretending every future idea belongs inside the same support scope.

Normally Maintenance

Bug fixes
Dependency updates
Small UI changes
API compatibility updates
Minor workflow changes
Performance fixes
Deployment support
Routine store updates

Usually Separate Scope

Major new module
Complete redesign
New mobile platform
Large architecture rewrite
Major database migration
New multi-tenant model
Complex new billing system
Large product expansion

Maintainable Software Needs Operational Basics

The application itself is only part of maintenance. Access, repositories, environments, logs, backups and third-party accounts matter too.

Repository Access

Source code should live in a repository the maintenance process can access and understand.

Environment Access

Hosting, cloud, server or deployment access needs to be available for the parts SiteLumo is responsible for.

Logs & Errors

Useful logs and error reporting make diagnosis much faster than guessing from screenshots alone.

Backups

Databases, files and infrastructure should have recovery expectations appropriate to the product.

Third-Party Accounts

Payment, email, AI, storage and other provider accounts should have clear ownership and access.

Release Process

Changes should have a predictable path from development to testing and production.

What Determines the Software Maintenance Quote?

Pricing depends on the codebase, technology, current condition, expected workload and how much production responsibility SiteLumo is taking on.

Codebase Condition

Clean, current code is easier to support than an undocumented or heavily outdated system.

Technology Stack

Frameworks, mobile platforms, infrastructure and deployment setup affect maintenance effort.

System Criticality

A small internal tool and revenue-critical SaaS product require different levels of responsibility.

Third-Party Dependencies

Payments, AI, email, storage, maps and APIs can create ongoing maintenance work.

Change Volume

Occasional fixes and continuous product iteration are different maintenance workloads.

Response Expectations

Routine support and urgent production-response requirements need different service levels.

Existing Products Need a Technical Review First

Before accepting ongoing responsibility for software built elsewhere, we may need repository access, deployment details, infrastructure information and known-issue context so the support scope reflects the real condition of the product.

A Written-First Software Maintenance Workflow

Bug reports, screenshots, logs, reproduction steps, release notes, test links, progress updates and approvals can all be handled asynchronously in writing. Meetings are optional.

Share the Product

Send the app/software details, repository or technical information available, and the support problems you want solved.

Review the Current State

We assess the codebase, dependencies, environments, integrations, deployment and known issues relevant to support.

Define Responsibility

We confirm what maintenance includes, what stays outside scope and what access or accounts are required.

Maintain & Improve

Fixes, updates and agreed small improvements are handled through the written support workflow.

Adjust as the Product Grows

As usage, features and technical complexity change, the maintenance scope can be revised realistically.

Software & App Maintenance Questions

Do you maintain software you did not build?

Often yes, after review. We need enough access and technical context to understand the current codebase, deployment, dependencies and known problems before accepting ongoing responsibility.

Can you maintain both web apps and mobile apps?

Yes. SiteLumo can support web applications, SaaS products, internal software and mobile apps depending on the technology and current condition.

Does maintenance include new features?

Small improvements can be included depending on scope. Large new modules, redesigns or architectural changes are normally separate projects.

Can you fix production bugs without a monthly maintenance plan?

Yes. A specific issue can be handled through Fixes & Troubleshooting when ongoing maintenance is not needed.

Can you handle App Store / Google Play updates?

Yes, where included in scope. Developer accounts normally remain owned by the client, and store approval remains controlled by Apple or Google.

Can you update old dependencies or frameworks?

Potentially. Small dependency updates can be maintenance; major framework upgrades may become a separate migration project if they require substantial rewriting.

Can you maintain APIs and backend systems?

Yes, where the backend and infrastructure are part of the supported scope and the required access is available.

What if the software has no documentation?

We can still review it, but missing documentation and unclear deployment processes increase takeover risk and may require a stabilisation or discovery phase first.

Do we need meetings?

No. SiteLumo uses a written-first process. Logs, screenshots, reproduction steps and technical notes are usually more useful than meetings.

What should I send for a quote?

Share what the product does, the technology stack if known, repository/hosting details available, current problems, how often changes are expected and what level of ongoing support you want.

Need Ongoing Support for Software or an App?

Tell us what the product does, what technology or platform it uses, what is currently going wrong and how much ongoing support you expect. We’ll reply in writing with the next questions needed to define the maintenance scope.