A launch is a beginning. Keep the website useful.
Give your website a clear plan for updates, maintenance, and the occasional unexpected issue. We scope ongoing care around the site you have and the support your business needs.
Discuss your project →Understand what is being maintained.
A simple marketing site and a custom application have different needs. We review the platform, hosting, connected services, and access ownership before proposing support. Existing documentation and the previous developer’s handoff help us understand what can be changed safely.
Separate maintenance from new work.
Routine content edits, software updates, and issue investigation are different from a new page, feature, or integration. A care agreement should make those boundaries clear. We define the included work, how to request changes, and when a separate estimate is needed.
Make ownership and recovery explicit.
Hosting, domains, third-party accounts, and backups need named owners. Depending on the platform, the care scope may include update checks, backup arrangements, and a recovery process. We agree on response expectations and escalation so you know what to do if a problem affects customers.
A care plan should be easy to understand.
Who handles content edits? Who owns the hosting account? How are issues reported? What happens when a change needs development? The scope should answer those practical questions before support starts.
A few useful answers.
Can you maintain a website someone else built?
We can review it first. Platform access, code quality, licensing, and existing support arrangements affect whether we can take it on and what work is needed before ongoing care begins.
Does support include unlimited changes?
The agreement defines the included work. Larger design changes, new features, and new integrations are scoped separately unless explicitly included.
Do you provide 24-hour support?
No round-the-clock coverage is assumed. Response times, support hours, and any urgent-issue process are agreed in the proposal.
What might come next.
Start with the part that should work better.
Tell us what you do, what is getting in the way, and what a useful next step would look like. We’ll help define the scope before the build.