Maintenance & support
Software rots without attention. A retainer covers dependency and security updates, uptime monitoring with a human on the other end, bug fixes inside an agreed response window, and a monthly block of hours for the improvements that never make it onto a project plan.
What you get
The outcomes we hold ourselves to on this work. If we cannot commit to them for your project, we say so during scoping rather than after the invoice.
- Security patches applied before they become incidents
- A named engineer who already knows your codebase
- Monthly report: uptime, performance, what changed, what is next
- Predictable cost instead of emergency contractor rates
Deliverables
Everything on this list is handed over and documented. Anything outside it is quoted before it is built.
- Uptime and error monitoring with alerting
- Dependency and security patching
- Bug fixes within agreed SLA
- Monthly feature/improvement hours
- Performance and cost review
- Quarterly architecture check-in
Typical timeline
Retainers start with the same discovery and written agreement as a project, then settle into a monthly cycle.
Discovery call
30 minutes, freeWe walk through what you are building, who it is for, and what has to be true for the project to count as a success. You leave with a rough scope, a rough number and an honest read on whether we are the right team.
You receive: Written scope summary within 24 hours
Proposal & fixed scope
2–3 daysA written proposal: milestones, deliverables, timeline, price and explicit exclusions. No hourly surprises — you approve a scope, and changes to it are quoted before any work starts.
You receive: Proposal, contract and milestone schedule
Build in weekly sprints
Bulk of the projectWorking software every week on a staging URL you can click through. A short written update each Friday: what shipped, what is next, anything blocking. You are never guessing where the project stands.
You receive: Staging environment, weekly demo and written update
Handover & support
OngoingDocumentation, a recorded walkthrough and a 30-day warranty on everything we shipped. If you want us to keep operating it, a maintenance retainer picks up from there.
You receive: Docs, walkthrough video, 30-day warranty
Questions we get asked
- Do you maintain apps you did not build?
- Yes, after a short onboarding audit so we understand the risks before we take responsibility for uptime.
- What is the response time?
- Critical production issues: 4 business hours on Standard, 1 hour on Priority. Everything else is triaged into the weekly cycle.
Where this has shipped
Case studies with the numbers we measured, including the ones that did not move.
AK Car Rental
A car rental booking platform — accounts, a vehicle catalogue, and a booking form that captures type, locations and dates in a single pass.
Client projectRead case study
MHB AC Repair & Services
A service business site built around one job: turn a visitor into a booked call-out, on a phone, in under a minute.
Client projectRead case study
Fashion Storefront
A clothing storefront with category browsing, a cart that survives navigation, and a best-sellers carousel on the landing page.
Client projectRead case study
Usually paired with this
Most projects combine two or three of these. We scope them as one engagement rather than separate invoices.
End-to-end web applications
Full product builds — from empty repo to live, monitored deployment.
4–12 weeksFrom $96
Android & iOS applications
Cross-platform mobile apps that ship to both stores from one codebase.
6–16 weeksQuoted per project
RAG systems & knowledge assistants
Retrieval pipelines that answer from your data, with citations.
3–10 weeksFrom $108
Need maintenance & support?
Tell us what you are working with — existing code, a blank repo, or a deadline you are worried about. This one is quoted per project: you get a written scope and a fixed number within 24 hours.
Replies within 4 business hours · No obligation · You keep the scope document