Home / Services / Software Maintenance
Keep your software useful as requirements change.
Support an existing product through issue resolution, dependency updates and planned improvements, with a process that makes priorities and responsibilities clear.
★★★★★5.0· 57 client reviews
Overview
Software Maintenance, explained
Software needs regular care after launch: security updates, dependency upgrades, bug fixes, performance tuning and small improvements requested by users. Without it, products slowly become fragile and expensive to change.
We take over maintenance of applications built by us or by other teams. We start with a technical review, stabilise the most important issues and then agree a predictable support routine with priorities, response targets and a backlog of improvements.
Before you build
Decisions worth settling first
Settling these points early keeps scope realistic and makes the estimate meaningful.
01
Current state
Review code, infrastructure, documentation and known issues.
02
Access
Collect repositories, cloud accounts and third-party service access.
03
Priorities
Agree which issues and improvements matter most.
04
Response needs
Define severity levels and expected response times.
05
Release process
Confirm how fixes are tested and deployed.
06
Reporting
Choose how work and system health are reported.
Services
What our software maintenance services include
Bug fixing
Investigation and resolution of reported issues.
Security updates
Dependency upgrades and patching of vulnerabilities.
Performance improvements
Profiling and optimisation of slow pages, queries and APIs.
Platform upgrades
Framework, OS and app store requirement updates.
Feature enhancements
Small improvements prioritised with your team.
Monitoring
Uptime, error and performance monitoring with alerts.
How it is built
The layers behind a dependable result
Every layer has an owner, tests and documentation, so the system can be supported after launch.
01
Assess
Technical review and risk list.
02
Stabilise
Fix critical issues and set up monitoring.
03
Maintain
Regular updates, fixes and support.
04
Improve
Planned enhancements and modernisation.
Use cases
Where it helps
Inherited applications
Products whose original team is no longer available.
Mobile apps
Keeping up with iOS and Android changes.
Business systems
Reliable operation of internal tools.
SaaS products
Ongoing fixes and small features.
Websites and portals
Security updates and content support.
Legacy platforms
Gradual modernisation while running.
From our portfolio
Aircraft Marketplace
A marketplace for listing aircraft for sale, from light sport aircraft to heavy jets.
.NETASP.NETAzureJavaScriptXamarin
Why PoliteTech
Why teams choose PoliteTech
Scope before commitment
Priorities, assumptions and acceptance criteria are agreed in writing before a delivery plan is fixed.
Engineers who build
Recommendations come from the people who design, code and support the software, so they reflect real implementation effort.
Visible progress
A shared backlog, regular demos and recorded decisions keep you informed without chasing updates.
Practical AI
Evaluation sets, review steps, cost limits and monitoring are part of every AI feature we ship.
Flexible engagement
Start with a scoped project, a dedicated team or support, and change the model as your roadmap evolves.
Clear ownership
Repositories and accounts can live in your organisation, with IP and confidentiality terms agreed in the contract.
Industries
Where this work fits
Retail and Ecommerce
Build web and mobile journeys around product discovery, ordering and customer service.
Financial Software
Support reporting, document processing and internal operations through defined application workflows.
Logistics Software
Connect planning, task assignment and operational updates in one workflow.
Education and Elearning
Create platforms for content, activities and progress tracking.
Fitness and Wellness Apps
Support tracking, coaching content and user engagement around a clear product goal.
Manufacturing Software
Replace fragmented tracking with workflows for quotations, work status and supporting documents.
Real Estate Applications
Create listing, enquiry and internal coordination tools around your business process.
Business Operations
Build task, approval and reporting tools around the way your team works.
Process
A practical path from requirements to release.
Each stage ends with something you can review: a scope, a prototype, a working increment or a release.
01
Understand
Discuss your users, business needs, existing systems and delivery constraints.
02
Define
Agree scope, technical approach, responsibilities and a delivery plan.
03
Design and build
Develop in manageable increments with visible progress and review points.
04
Test and release
Validate agreed workflows, resolve release blockers and prepare deployment.
05
Support and improve
Document the handover, review production feedback and plan the next priorities.
Technology
Tools and platforms we work with
ReactAngularVueNode.js.NETJavaPHPPythonRuby on RailsReact NativeFlutterSwiftKotlinAWSAzureGoogle CloudSentryDatadogJira
Cost
What shapes the cost of your project?
There is no useful price without scope. These are the factors we review when preparing an estimate, and the estimate lists every assumption so you can see what would change it.
01
Platforms
Web, iOS, Android or all three, and whether apps are native or cross-platform.
02
Features and roles
The number of user journeys, roles and business rules in the first release.
03
Integrations
Payments, maps, CRMs, ERPs and third-party APIs each add scope.
04
Design depth
From using a component library to a fully custom design system.
05
Data migration
Moving and validating data from existing systems.
06
Non-functional needs
Performance, security, availability and compliance requirements.
Engagement models
Choose the engagement that fits your next step.
Dedicated Team
For a changing roadmap or ongoing development. Agree roles and working process, then manage priorities through a shared backlog.
Best for team extension and long-term product work.
Scoped Project
For a defined product or milestone. Align on requirements, deliverables and acceptance criteria, with changes reviewed before they affect the plan.
Best for MVPs, integrations and focused releases.
Maintenance and Improvement
For software that already exists. Start with a technical review, then agree support routines and planned improvements.
Best for live applications and modernisation.
FAQ
Questions about software maintenance
Can you maintain software built by another company?
Yes. We begin with a technical review and knowledge transfer.
What does a technical health check include?
Code quality, dependencies, security, infrastructure, documentation and a prioritised list of risks.
How are support requests handled?
Through your ticketing tool or ours, with agreed severity levels and response targets.
Do you offer emergency support?
Coverage is agreed in the support plan based on your needs.
Can maintenance include new features?
Yes, small enhancements can be scheduled within the plan.
How is maintenance priced?
Usually as a monthly plan sized to expected effort, with additional work estimated separately.
Can you maintain software you did not build?
Yes, subject to reviewing the codebase, licenses, documentation and available access.
Can you guarantee no downtime?
Availability targets and deployment constraints must be agreed for the specific system. We do not promise a universal zero-downtime outcome.
How are pricing and timelines determined?
We review requirements, technical complexity, team needs and delivery constraints before proposing an engagement. Estimates list assumptions and what may change the plan.
Can we discuss a project under an NDA?
Yes. Let us know before sharing confidential materials so we can agree confidentiality terms first.
Discuss your software maintenance needs
Share your goals, current situation and the help you need. We will review your message and suggest a practical next step.