Software updates
Identify what needs updating and who approves changes.
Thoughtful websites. Built in Sri Lanka.
077 299 5240Care after launch
Maintenance is easier to manage when responsibilities, access, update frequency, backups, and support expectations are agreed before the site goes live.

Define the care plan
The exact service should be written down so you know what is covered and how requests are handled.
Identify what needs updating and who approves changes.
Confirm what is backed up, how often, and how restoration is handled.
Keep domain, hosting, and administrator access under agreed ownership.
Set the contact route, response expectations, and work included in the plan.
Plan for changes
A new feature or larger content update may require a separate scope.
Document recurring checks and updates included in the maintenance arrangement.
Agree how text, images, products, and business information will be updated.
Estimate new pages, integrations, or workflows separately from routine maintenance.
Before launch
Plan account access and documentation as part of delivery.
Record the domain, hosting, email, analytics, and third-party accounts.
Confirm who controls each account and who can approve changes.
Agree updates, backups, support contact, and response terms.
Revisit the arrangement when the website or business changes.
FAQs
Find an answer below, or ask us about your project.
That depends on the written agreement. Routine upkeep and new development should be described separately.
Ownership should be clear and documented. Make sure the business can access its domain and essential service accounts.
Backups are one part of recovery planning. Confirm what is backed up, how it is stored, and how restoration is tested or supported.
Continue exploring
Explore related services and guides for your project.
A useful website starts with a clear conversation.