Launch is a milestone.
Not the end of the story.
Websites and software need care as platforms, dependencies and business needs change. We help define the right support arrangement, rather than leaving responsibilities unspoken.
Discuss ongoing support
Maintenance
Dependency and platform updates, compatibility checks and routine technical care appropriate to the stack.
Backup planning
Agree what is backed up, how often, where copies are kept and how restoration is tested. Static files and business data need different plans.
Technical support
A defined route for reporting issues, with agreed availability and priorities. No implied round-the-clock cover.
Continual improvements
Scope new features, content changes and performance improvements separately, with a clear reason for each change.
Start with a review.
For an existing system, we first need to understand the code, hosting, access and current condition. An initial review helps identify what can be supported and any changes needed before taking on maintenance.
Support costs depend on the platform, complexity, expected work and agreed response arrangements. Hosting and third-party charges should be explicit.
Can you support something you did not build?
Potentially. An initial technical review is needed before we can agree a support scope or responsibility for an existing system.
Does maintenance include new features?
Routine maintenance and feature development are different activities. We agree what is included and quote additional work separately.
Something in mind?
Let’s make it work.
A new website, a better system, or an idea you’d like to explore.
Tell us where you want to go.