Written scope and responsibilities
We document deliverables, responsibilities, dependencies, review points and exclusions before production begins, so every participant works from the same agreed scope.
Maintenance & Support
Website Maintenance and Support After Launch
We manage agreed updates, fixes, monitoring and routine checks after a website goes live.
NovaCraft reviews requests, prioritises impact, tests supported changes and documents releases so ongoing website maintenance remains controlled and visible.
- Routine Updates
- Technical Support
- Continuous Improvement
- Routine updates
- Bug fixes
- Performance checks
- Dependency updates
- Content support
- Monitoring
- Small enhancements
- Improvement planning
What support can include
Website Maintenance and Support Scope
Support scope is agreed around the platform, team and level of ongoing change.
Agreed content, component and configuration updates without reopening the whole project.
Investigation and resolution of reproducible issues within the supported codebase.
Planned updates where frameworks, packages or platforms need routine maintenance.
Periodic checks for obvious regressions in loading, assets and front-end behaviour.
Review alerts and reported issues so the right work is prioritised rather than every request becoming urgent.
Small enhancements informed by real usage, feedback and changing business priorities.
Tools we use
Tools used for support, testing and controlled website updates
Support tools are selected around the existing stack so updates can be reviewed, tested and documented before release.
Code and Deployment
Used where the supported website already runs on these tools, allowing changes to be reviewed and deployed with version history.
- GitHub
- Vercel
- Next.js
Performance and Search Checks
Used to identify regressions, technical search issues and performance changes that may need maintenance work.
- Lighthouse
- PageSpeed Insights
- Google Search Console
Planning and Handover
Used to record requests, approvals, recurring tasks, design references and changes that need a clear client handover.
- Notion
- Figma
- Google Sheets
Code and Deployment ยท Used where the supported website already runs on these tools, allowing changes to be reviewed and deployed with version history.
Who it helps
When Ongoing Website Support Helps
Growing Businesses
Teams whose website changes regularly but does not justify a full internal development team.
Startup Products
Products that need structured iteration after an initial launch.
Marketing Teams
Teams running campaigns and content that require dependable website support.
Existing NovaCraft Clients
A natural continuation when the launch needs ongoing care and improvement.
What you receive
What the Support Process Includes
A maintenance plan may include:
- Agreed support scope
- Request and priority process
- Routine maintenance window
- Issue tracking
- Update notes
- Performance observations
- Monthly or periodic review
- Recommendations for larger improvements
Client project management
How we manage maintenance & support projects
The delivery method stays visible to both teams. Scope, responsibilities, feedback, approvals and handover are documented from the start.
Step 01 Step 02 One shared project workspace
Files, notes, decisions, links and current priorities stay in one shared workspace, giving both teams a consistent source of project information.
Step 03 Weekly status and next actions
Each week we record completed work, current tasks, blockers, decisions required and the next review point, keeping progress visible without constant meetings.
Step 04 Structured feedback and approvals
Feedback is consolidated by the client decision owner, reviewed against the agreed objective, then recorded before the next production stage begins.
Step 05 Documented scope changes
Requests outside the approved scope are documented with their impact on timing, effort and dependencies before either team commits to the change.
Step 06 QA, handover and next steps
Before handover, we review agreed acceptance criteria, test required journeys, document remaining actions and confirm ownership for launch or ongoing support.
Working instructions
What we agree with the client at kickoff
- Nominate one client decision owner for consolidated approvals.
- Share required access, brand assets and source material before the relevant stage begins.
- Return consolidated feedback against the agreed review date whenever possible.
- Use the shared workspace for decisions so important context is not split across channels.
- Raise blockers and changing priorities early so timeline or scope impact can be reviewed before work continues.
Frequently asked questions
Maintenance & Support questions we are asked most
Coverage is agreed before the plan begins and can include routine updates, supported technical fixes, monitoring and small improvements.
Sometimes. We first review the existing stack, access, code quality and known issues before confirming support.
Usually not. Larger features or redesigns are scoped separately so maintenance capacity remains predictable.
Not by default. Any availability or response commitment is agreed explicitly in the support plan rather than implied on the website.
Stay supported
Need Ongoing Website Maintenance Support?
Tell us what platform you are running, what support you need and whether NovaCraft built the original project.
We usually reply within one business day.