01
Health & codebase assessment
Review architecture, dependencies, recurring defects and the information needed to maintain the product.
FMN CAPABILITIES / BUILT AROUND YOUR BUSINESS
Maintenance & modernisation.
Keep your software ready for what comes next.
Ongoing fixes, dependency updates and staged modernisation for existing websites, applications and systems.
Clear scope. Reviewable progress. Documented handover.
FMN / 13SERVICE BLUEPRINT
MAINTAIN
From a need to a working solution.
01
Health & codebase assessment
02
Fixes & preventive updates
03
Staged modernisation
04
Support & continuity
01 / WHY THIS SERVICE
Value starts with a real problem.
Software needs attention after launch: dependencies change, users reveal new needs and small defects accumulate. A maintenance plan turns reactive fixes into prioritised work with clearer responsibilities and safer releases.
Does this sound familiar?
An existing product is slow, hard to change or running on unsupported components.
01
A manageable improvement backlog
02
Fewer unsupported dependencies
03
Clearer ownership of maintenance work
These are goals to review together; success measures depend on the agreed scope and your starting point.
02 / INSIDE THE SCOPE
What do we actually work on?
Connected capabilities, shaped to your project. The proposal defines which parts are included and what each one delivers.
02
Fixes & preventive updates
Prioritise bugs and dependency upgrades with targeted tests to reduce avoidable regressions.
03
Staged modernisation
Refactor or replace high-friction parts in stages, keeping migration and rollback requirements visible.
04
Support & continuity
Agree on request channels, responsibilities, response arrangements and a visible improvement backlog.
03 / FROM DISCOVERY TO HANDOVER
Clear steps. Tangible outputs.
- 01
Understand & define
We review your current situation, users and constraints, then agree on scope, responsibilities and acceptance criteria.
- 02
Design the solution
We make the proposed journey or technical approach reviewable before implementation, with clear decisions and dependencies.
- 03
Implement & review
We assess the codebase, agree on support scope and prioritise changes with regression checks and rollback plans.
- 04
Validate & hand over
We review the agreed outputs with your team, record remaining actions and hand over the documentation needed for the next step.
THE PRACTICAL HANDOVER
What do you walk away with?
Reviewable, usable outputs checked against the scope we agree together.
- Technical health review and prioritised backlog
- Bug fixes, dependency updates and targeted refactoring
- Maintenance plan and agreed response channels
04 / WHERE IT FITS
A solution that fits your context.
Who is it for?
Businesses improving an existing product without replacing everything at once.
Illustrative project possibilities, rather than claims of completed client work.
Can you maintain an existing codebase?
We begin with an assessment of access, documentation, code health and deployment. This determines feasibility, onboarding work and a realistic support scope.
Do you offer fixed response times?
Response arrangements depend on the support agreement and operating hours. We specify them explicitly rather than treating every maintenance engagement as continuous emergency coverage.
How is website or application maintenance priced?
Codebase health, supported technologies, the change backlog and response arrangements determine the work. We assess the product first and distinguish routine maintenance from new features and major migrations.
How are scope, timing and cost agreed?
We review your goals, existing systems and required outputs first. The proposal defines deliverables, responsibilities, dependencies and commercial terms. Optional features and ongoing support are agreed explicitly.
Capabilities that work together.
All capabilitiesYOUR NEXT STEP
Let’s make your next idea work.
Tell us where you want to go. We’ll start with your challenge and shape the way forward together.