06 · Software Development
Maintenance & Technical Support
Structured technical care for software that already supports your operations.
What this service is
Turn reactive fixes into a visible, prioritised technical care programme.
Maintenance and technical support provide a controlled way to care for software that already supports the client's operation. The service begins with a suitability and health review so responsibilities, access, risks and the current backlog are understood before response expectations are agreed. It is not presented as unlimited emergency cover or an informal promise to repair any system without context.
Suitable arrangements can include defect investigation, dependency reviews, small approved improvements, release preparation and technical recommendations. Work is recorded through a visible queue with priorities, evidence and release notes, helping the client distinguish urgent incidents from planned maintenance and larger development requirements.
Typical situations
When this service is usually considered.
The examples below help frame suitability. The actual requirement, risks and intended outcome are confirmed during the initial review.
- 01
Issues are reported through messages and repeatedly investigated without a shared technical record.
- 02
Updates are postponed because the impact on the application is not understood.
- 03
The original supplier is unavailable and ownership of the technical backlog is unclear.
- 04
Small operational improvements accumulate but do not justify a new project each time.
- 05
The system works but logs, documentation and release practice make diagnosis unnecessarily slow.
Scope of work
What the engagement may include.
Every item is selected and bounded in the written proposal. Inclusion here describes capability, not an automatic promise that all activities fit the starting price.
Initial technical health review
Review of architecture, environments, dependencies, access, known issues and the information available for safe maintenance.
Support boundary and priority model
Written definition of included systems, contact route, working hours, severity, client responsibilities and matters requiring separate scope.
Issue investigation
Evidence-based diagnosis of accepted defects or operational problems, with findings and recommended action recorded.
Approved fixes and minor changes
Implementation and testing of work accepted into the maintenance queue within the agreed commercial arrangement.
Dependency and compatibility review
Planned attention to relevant libraries, platform changes and supplier notices rather than reactive updating without impact assessment.
Release notes and recommendations
A record of changes, verification, known limitations and items that should become a separate improvement project.
Expected outputs
Useful artefacts, decisions and working results.
The output is designed to support operation, delivery or a clearly defined next decision—not to create presentation volume without practical value.
Initial technical health review
A baseline view of the system, access, operating risks, documentation condition and immediate maintenance priorities.
Maintenance priorities and support boundaries
A written maintenance boundary covering communication, priorities, responsibilities and exclusions.
Agreed fixes, updates or small improvements
Accepted fixes, updates or small improvements delivered through the agreed queue and release route.
Release notes and ongoing recommendations
Clear release records, unresolved items and recommendations for risk reduction or larger change.
Application
Common use cases.
These examples show how the service can be applied. They are illustrative and do not represent claims of completed client engagements.
Post-launch application care
Manage defects and measured improvement after a new application enters everyday use.
Inherited business software
Establish enough technical context to support a system whose original developer is no longer available.
Planned dependency maintenance
Review and apply necessary platform or library updates through controlled testing and release.
Small operational enhancement queue
Group minor approved changes into sensible releases without treating each request as an unstructured interruption.
Service-specific approach
How NORYVIA approaches Maintenance.
The method is adapted to the service rather than repeating one generic project formula across every requirement.
Establish context before response promises
Access, architecture, risk and documentation are reviewed before service levels or support boundaries are proposed.
Prioritise by operational impact
Severity reflects the effect on users and service continuity, not only how urgently a request is worded.
Record diagnosis and change
Issues, evidence, decisions, verification and release information remain visible for future investigation.
Separate maintenance from new product work
Material features, redesigns and migrations receive their own scope so the maintenance queue remains predictable.
Engagement sequence
Six stages with visible decisions.
Activities can overlap where appropriate, but each stage has a clear purpose and produces evidence for the next one.
Suitability review
Confirm the system can be accessed and supported responsibly within available knowledge and authority.
Baseline
Review health, dependencies, environments, documentation, issue history and immediate risks.
Support agreement
Define included systems, communication, priority, working hours, commercial model and exclusions.
Queue and investigate
Record accepted work, gather evidence, reproduce where possible and propose the appropriate action.
Change and verify
Implement approved fixes or updates, complete relevant checks and release through the agreed route.
Review
Report completed work, recurring causes, backlog position and recommendations for the next period.
Relevant capabilities
The disciplines brought into the work.
The precise technical or advisory depth depends on the accepted scope, available evidence and client environment.
Investigation
- Issue reproduction and evidence
- Log and error-context review
- Dependency and configuration checks
- Data and integration diagnosis
- Root-cause and workaround notes
Maintenance
- Approved defect correction
- Small functional improvements
- Dependency updates
- Configuration and compatibility work
- Release preparation
Control
- Visible maintenance backlog
- Severity and priority rules
- Testing and release notes
- Known-risk tracking
- Periodic recommendations
Client contribution
Information and access needed from the client.
Good delivery depends on timely, authorised access to relevant people and evidence. Missing inputs are surfaced as assumptions or constraints rather than quietly filled with guesses.
- 01
Authorised access to code, environments, logs and supplier accounts where relevant.
- 02
Existing documentation, release history and known issue records.
- 03
A nominated contact who can confirm impact, priority and acceptance.
- 04
Representative steps, screenshots and timestamps for reported issues.
- 05
Advance notice of planned business, supplier or platform changes where possible.
Scope, price and timing
A defined starting point—not a blank cheque.
The displayed price is an indicative starting guide for a bounded initial engagement. Before work begins, a written proposal confirms the selected activities, deliverables, assumptions, client responsibilities, exclusions, timetable, payment schedule and any third-party costs.
Indicative engagement shapes
Initial health and suitability reviewTypically 1–2 weeks
Defined maintenance packageAgreed monthly or staged period
Major remediationQuoted as a separate project
Factors that may change scope, price or duration
- 01
System complexity, documentation, test coverage and ease of safe access.
- 02
Required response expectations, support periods and priority levels.
- 03
Number of environments, integrations and external suppliers involved.
- 04
Volume and mixture of investigation, maintenance and small-change work.
- 05
Release, reporting and client coordination requirements.
Scope boundaries
What is not automatically included.
Boundaries protect both parties from assumptions. A separate requirement can still be assessed and included where it is suitable and confirmed in writing.
Automatic 24/7 response
Continuous cover and guaranteed response or resolution times are not included unless a separate agreement expressly provides them.
Unknown or unlawful access
Work may be declined where ownership, authority, security or licensing cannot be established responsibly.
Major feature programmes
Substantial new capability, redesign, migration or modernisation is scoped separately from routine maintenance.
Service FAQ
Questions about Maintenance.
Project-specific answers depend on the current environment, intended outcome and evidence available during review.
Potentially, following a suitability review of access, architecture, documentation, licensing and risk. The review may identify prerequisite stabilisation work.
Only where a separate written arrangement defines the hours, response expectations, contact route and commercial terms. The standard website information does not promise emergency cover.
They can be included when they remain within the agreed maintenance boundary. Material changes are described and quoted separately before work begins.
Priority considers service impact, affected users, workaround availability, data or security risk and the information available for diagnosis.
Related capabilities
Other ways to move the requirement forward.
01Software Development
Custom Business Software
Purpose-built software shaped around the way your organisation actually works.
Explore service · from £2,500
02Software Development
Web Applications & Portals
Secure, usable web experiences for customers, teams and partners.
Explore service · from £2,200
03Software Development
Workflow Automation
Reduce repetitive work without losing visibility or control.
Explore service · from £1,800
Start with clarity
Start a conversation about Maintenance.
Use the structured questionnaire to explain the current situation. NORYVIA will review suitability and respond with questions or a proposed next step.