Kevin Johnston · Full-stack designer · Calgary
Keep the useful parts working after launch.
A website or application needs an owner after it goes live. Define the checks, responsibilities, and support arrangement so updates and problems have a clear path.
Discuss your project ↗Prepare for a dependable handover
Document hosting, domain ownership, integrations, and the publishing workflow. Test forms and key customer journeys, configure backups, and agree how access is managed. A handover should make routine operation understandable to the person responsible for it.
Maintain the agreed scope
Support can include dependency updates, content changes, form checks, and monitoring. The right schedule depends on the platform and business risk. Maintenance is separately agreed; it does not imply unlimited changes, round-the-clock support, or a guaranteed response time.
Improve from real feedback
Review customer questions, analytics, search visibility, and operational issues. Prioritise fixes that make the site easier to use before adding features. Bigger changes should have a clear scope, testing plan, and rollback path.
Relevant website work
Explore real websites built through DARKKEVN Labs and Clearwater Digital. Each project has its own scope; these examples are not promises of conversion results.
Dogz Country
Boarding and daycare information, booking details, forms, and rescue support.
Visit website ↗
Village Scholars Preschool
Programs, daily care, meals, and outdoor learning, with a clear path for parent enquiries.
Visit website ↗Before we start
Can you maintain a website built by someone else?
An initial review is needed to understand its platform, access, dependencies, and current condition. Support availability and scope can then be agreed.
Is maintenance included in the website price?
Only when explicitly included in the proposal. Hosting, third-party subscriptions, content changes, and ongoing development should be listed separately so responsibilities are clear.