Keep Your Software Healthy After Launch
We look after live web and mobile products: fixing faults, applying updates and making the small improvements that keep a product useful.
- Response terms agreed in writing
- Monthly report of work done
- Month-to-month, with no exit fee
What Maintenance And Support Covers
Software needs care after launch. Dependencies need security updates, app stores change their rules, and users find faults that testing missed. Left alone, a working product slowly becomes a risky one.
We take on products we built and products built by others. For an inherited product we start with a review, so you know its condition before we agree what support will cover.
What Is Included
Bug Fixes
Faults investigated, fixed and released, with the cause written down.
Security Updates
Frameworks and libraries kept up to date.
Monitoring
Uptime and error monitoring, with alerts to the people who can act.
Backups
Backups checked by restoring them, not only by taking them.
Small Improvements
Minor features and adjustments, prioritised with you each month.
App Store Updates
Mobile apps kept compatible with new operating system versions.
Who This Is For
Business Owners
Your software is live and the people who built it have moved on.
Development Teams
Your engineers are busy with new features and support work keeps interrupting them.
Companies With Older Systems
A system still runs the business and few people are able to change it safely.
How Support Runs
- 1Step 1
Review
We review the code, hosting and access, and report its condition.
- 2Step 2
Agree Terms
What is covered, response times and how to reach us, in writing.
- 3Step 3
Take Over
Access, monitoring and documentation put in place.
- 4Step 4
Support
Faults handled as they arise and improvements planned monthly.
- 5Step 5
Report
A monthly summary of work done and anything that needs a decision.
The full process, from first call to support after launch, is on the How We Build page.
What You Receive
Condition Report
The state of the product at the start, with risks listed.
Point Of Contact
A named person who knows your product.
Monthly Report
Work done, time used and recommendations.
Ownership
All changes stay in your repository and belong to you.
Technologies We Work With
We choose the stack to suit the product and your team. These are the ones we use most.
Ways To Work With Us
Pick the model that suits how clear the scope is. We quote in writing before you commit.
- Clear scope
Fixed Scope
Agreed features, timeline and price. Suits a well-defined first version.
Compare the models - Evolving scope
Time And Material
Work is planned sprint by sprint, so priorities can change as you learn.
Compare the models - Ongoing product
Dedicated Team
A team that works only on your product, month to month.
See dedicated teams
Tell Us What You Want To Build
Helpful to include
- What the product should do
- Who will use it
- Anything already built
- Your target date
What happens next
- We read your brief and reply within two working days
- A scoping call to agree goals and must-haves
- A written proposal: scope, timeline and cost
Maintenance And Support Questions
Yes. We begin with a review of the code, hosting and documentation, and tell you what condition it is in before we agree the terms of support.
Response times are agreed in writing at the start and depend on severity. A fault that stops the business is handled ahead of a cosmetic one.
Support runs month to month, with the notice period stated in the agreement and no exit fee.
If the review shows the product needs larger work, such as modernising an ageing system, we explain the options and quote for that separately.
You do. All work is committed to your repository and belongs to you.
Have Something To Build?
Tell us the idea and the timeline. We will reply with questions, then a written proposal.