Observe
Monitor the signals that reveal where attention is needed.
Support and Care
Ongoing maintenance, support and measured improvement for websites that need to remain reliable.
Quiet continuity
Dependencies age, small errors accumulate, content drifts and integrations evolve. Continuous care keeps friction from becoming a larger problem.
Monitor the signals that reveal where attention is needed.
Resolve small issues before they affect customers or editors.
Use recurring insight to refine what already exists.
Review the result and return the system to a known state.
Support plans
A light safety net for stable websites that need routine technical attention.
Planned review window
Ongoing care for active business websites with regular content and improvement needs.
Priority working window
Closer technical support for websites that play an important operational role.
Reserved support capacity
The care system
Four responsibilities create a readable service instead of an undefined bucket of hours.
Uptime, forms, browser behaviour and visible errors are reviewed in context.
Dependencies, platform changes and technical hygiene are handled deliberately.
Content changes and contained adjustments move through one clear request flow.
Small evidence-led improvements compound without turning into a redesign.
Small changes and continuous maintenance belong in the appropriate plan. New functionality, complex integrations, new page systems and redesigns become separate projects.
The working rhythm
A visible loop makes it clear what is being reviewed, what is underway and what should happen next.
Confirm the website stack, current condition, access and immediate risks.
Match priorities and request types to the agreed support level.
Review signals, apply planned maintenance and document material changes.
Handle suitable requests within capacity and flag work that needs separate scope.
Look back at recurring friction and identify the next useful improvement.
The Kanso Standard
Maintenance is guided by accessibility, performance, technical clarity, maintainability and honest ownership boundaries.
Read the Kanso StandardReplace an image or adjust existing copy.
Refine a contained component within the current system.
Create a new page, workflow or editorial pattern.
Rebuild architecture, migrate platform or add a complex integration.
The distinction is based on structural impact, not only the time a task takes.
Frequently asked questions
Support and Care
Call or email Kanso to discuss the website, its current setup and the support it needs.