Maintenance and support after delivery
A system must remain secure, stable, and understandable after go-live. We define maintenance as a clear scope of responsibility, not open-ended availability.
When this approach makes sense
- An application or website is in production and needs regular operational monitoring.
- Security updates and dependencies require ongoing maintenance.
- Users report issues that need structured, timely handling.
- The business is growing and the system needs new functionality or adjustments.
- There is no internal team for technical maintenance.
- The previous contractor is no longer available or maintenance was not agreed.
What the service includes
- System monitoring and availability checks
- Regular backups and verification of recovery
- Incident handling and problem diagnosis
- Dependency and security patch updates
- Bug fixes and technical issue resolution
- Minor improvements within agreed scope
- Roadmap for new functionality
- Response-time model according to agreement
- Clearly defined exclusions from scope
- Regular reporting on system status
- Documentation of changes and decisions
- Coordination with hosting and infrastructure
Typical applications
- Maintenance of a business application after initial delivery
- Website support — updates, security, performance
- Monitoring and fixes after integration rollout
- Development of new functionality in agreed cycles
- Taking over maintenance from a previous contractor
- Seasonal or project-based extension of an existing system
Development process
The process is deliberately simple and transparent: clear scope, short phases, and a version you can use. That reduces risk and keeps the work aligned with how your organisation actually operates.
Gathering requirements
We work with you to define what the system must solve. The aim is a first usable version — a minimum that can be relied on in daily work — not everything at once.
User stories, use cases, and sketches
Requirements are broken into small parts: who does what, why, and with what result. Where useful, we use flow sketches or simple wireframes to align expectations quickly.
Estimates and cost
Each unit of work gets a realistic estimate. Together they give a clear view of duration and cost. Requirements can change — with a transparent impact on timeline and price.
Priority backlog
Before development starts, agreed items go into a priority list: features, integrations, fixes, and everything needed for a viable delivery.
Defining phases
Work is split into short phases (usually one to two weeks). Each phase has an agreed scope and a goal: a part of the system that can be reviewed and verified.
Iterating and reviews
At the end of each phase we review progress, correct assumptions, and choose the next set of items. You stay in control of direction while the system is built.
Go-live
When a version is ready, we roll out in a controlled way: data preparation, checks in real conditions, and support for first use. Quality improves through phases — not only at the end.
Quality and security
- Regular backups with recovery verification
- Availability and performance monitoring
- Planned application of security patches
- Change log and documentation of interventions
- Data protection during maintenance work
- Testing before applying changes in production
What we need from you
- A contact person for reporting issues and approving changes
- Access to the system, repository, and infrastructure
- Existing documentation if available
- Definition of priorities and business-critical functionality
- Information on users and expected support scope
- Decisions on budget for new functionality outside basic maintenance