Operational support
Record and assess problems found in the team's real workflows.
APPS/008Maintenance and ongoing development
Your application in use.
Thoughtful development.
We support your application through fixes, updates and prioritised improvements. We agree what is covered, expected response times and how new features are assessed.
Resolve issues.
Learn from use.
Real use reveals needs that were not visible during development. A support agreement distinguishes operational problems from new capabilities worth adding.
Technical updates
Review the components and services the application needs to continue operating.
Priority improvements
Organise requests and turn the most useful ones into specific releases.
Operational continuity
Agree on backups, recovery, access and checks according to the system's needs.
From daily use
to the next improvement.
Further development starts with what the application needs and the resources available. We distinguish an issue from a new feature and agree on how to handle each.
Starting point
- Use
- Issues
- Requests
Ongoing developmentOutcome
- Corrections
- Updates
- Versions
Defined support.
Evolution through releases.
These are the elements we define in the proposal. The final scope depends on your starting point and business priorities.
/001Application review
We assess its condition and documentation before defining what we can maintain.
/002Support agreement
We agree on channels, service hours, issue priorities and expected response times.
/003Maintenance plan
We agree on the technical reviews, dependencies and operational tasks included.
/004Incremental releases
We define the work and testing needed for each improvement before it is added.
/005Handover and continuity
We hand over the access, documentation and guidance covered by the agreed scope. Follow-up or maintenance is defined separately if commissioned.
From daily use
to the next version.
(4)Review the application
We check the condition, access and documentation before defining support and outstanding tasks.
Agree the coverage
We define channels, hours, incident priorities and included maintenance.
Fix and check
We test the affected features for each change before introducing it into the live application.
Plan improvements
We prioritise the team’s requests and agree the scope and estimate for the next delivery.
Designed for your team.
Sustainable for your business.
Agreed scope
A custom application needs priorities and limits. We document features, user journeys and acceptance criteria before development.
Data and access
We define the profiles, actions and information each person needs, along with the planned backups, recovery and access management.
Operation and ongoing development
We define where the application runs, its recurring costs and who maintains it. Later versions are prioritised according to actual use.
Before we start.
(5)How are new features chosen?
We review the team’s needs, usefulness and required effort. Each improvement has a scope and estimate, separate from fixes included in support.
Can we commission this for an existing application?
Yes, after checking whether we can take it on with the available access, technology and documentation. An initial setup phase may be needed and is assessed separately.
Does everything have to be defined from the beginning?
We need a clear goal and scope for the first version. Further features can be prioritised after testing; changes are assessed before they are added.
Can we connect the tools we already use?
We review the integration interfaces, permissions and terms. If a connection is not feasible, we explain alternatives and their limitations before committing to development.
What happens after delivery?
We agree on hosting, support, maintenance and documentation. The proposal distinguishes operation of the delivered version from extensions and recurring services.
Engineering × Design.
For the next step.