Skip to content
NovaCraft AgencyContact Us
Maintenance & Support

Website Maintenance and Support After Launch

We manage agreed updates, fixes and 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
Beyond launch

Keep Post-Launch Work Controlled

Maintenance is not a promise that nothing will ever break. It is a clear process for reviewing, prioritising and resolving the work that appears after launch.

We define what is covered, how requests are handled and when larger changes should become a separate project.

What support can include

Website Maintenance and Support Scope

Support scope is agreed around the platform, team and level of ongoing change.

  • Routine Website Updates

    Agreed content, component and configuration updates without reopening the whole project.

  • Technical Fixes

    Investigation and resolution of reproducible issues within the supported codebase.

  • Dependency and Platform Updates

    Planned updates where frameworks, packages or platforms need routine maintenance.

  • Performance Review

    Periodic checks for obvious regressions in loading, assets and front-end behaviour.

  • Monitoring and Issue Triage

    Review alerts and reported issues so the right work is prioritised rather than every request becoming urgent.

  • Continuous Improvement

    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

    • GitHub
    • Vercel
    • Next.js

    Used where the supported website already runs on these tools, allowing changes to be reviewed and deployed with version history.

  • Performance and Search Checks

    • Lighthouse
    • PageSpeed Insights
    • Google Search Console

    Used to identify regressions, technical search issues and performance changes that may need maintenance work.

  • Planning and Handover

    • Notion
    • Figma
    • Google Sheets

    Used to record requests, approvals, recurring tasks, design references and changes that need a clear client handover.

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.

  • 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.

  • 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.

  • 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.

  • 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.

  • 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.

  • 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.

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.