A record of systems and accounts
Record the platform, hosting, domain, components needing renewal and account owners. Identify required permissions and system limitations before support begins.
Website maintenance
Website maintenance services
Keep your website ready for everyday business in Vietnam, including the pages and contact journeys used by local and international customers.
AT A GLANCE
Agree the updates, backups, checks and support your website needs.
- Start with
- Your website, platform, essential functions and known issues to review.
- Deliverable
- An agreed maintenance schedule, change records, checks and open issue reports.
- Agree first
- Response expectations, backup retention and external costs are agreed before support.
What this starting fee covers
- One small website, subject to a compatibility review.
- Weekly backups; monthly checks, updates and a report.
- Up to one hour of small fixes or content updates per month.
Separate costs / conditions: Hosting, backup storage, major incidents, attack recovery and new features are separate; 24/7 cover is not included.
Compare service prices →Cost depends on the amount and complexity of the work. A smaller scope may reduce the total; we confirm this after reviewing your requirements. Work fees exclude any applicable taxes; domains, hosting, paid tools/APIs and advertising are separate. The final quote confirms scope, total, taxes and timing before work begins.
Taking over
Review the website before support begins
Record systems, access and existing defects before recurring support begins.
A checklist of essential functions
Agree the pages, forms, contact links and editing tasks to check. Record how each is tested and what a successful result looks like, so checks can be repeated after changes.
Existing issues
We separate unresolved defects from recurring maintenance and identify any initial repairs or missing documentation that need a separate scope before ongoing work begins.
Recurring work
Recurring technical maintenance
Pair updates and backups with functional checks and recovery planning.
Updates in agreed maintenance windows
Review versions and compatibility, then prepare a backup before the change. After an approved update, repeat the agreed checks and keep a way to restore the previous version if problems arise.
Backups with a recovery plan
Record what is backed up, the frequency, storage location, retention and recovery permissions. Agree when recovery is tested and record the result; a backup file alone does not confirm successful recovery.
Incidents and additional work
Record when an incident was reported, its impact, affected functions and owner. Investigate and address covered issues; identify work needing another provider or additional development for approval.
Responsibilities
Clear scope and responsibilities
Clarify support schedules, reporting and approval for additional work.
Frequency and response expectations
The plan states check schedules, support channels, working hours and priority levels. Agree a response expectation for each level; resolution still depends on the cause, available access and other providers.
A report for each agreed period
Receive dates and versions of updates, check results, backup status, open issues and decisions needed from you. Incomplete work includes the reason and the next action.
Costs and support boundaries
The proposal separates recurring maintenance, initial repairs and additional work. It identifies who pays for hosting, domains, licences and tools. Regular publishing, SEO, in-depth speed optimisation and new features have their own scope.
HOW WE WORK
Clarity at every step.
Review the current website
Share the website address, available system information and current concerns. We confirm the access needed and any obstacles to taking over support.
Agree the maintenance plan
Agree supported systems, the work schedule, response expectations, reports and approval for additional requests.
Carry out and check changes
Complete approved work, check the relevant functions and record outcomes. If an issue needs a larger change, discuss its impact before expanding the work.
Report and adjust
Review completed work at agreed intervals and adjust the plan when the website, its dependencies or your operational needs change.
ILLUSTRATIVE SCENARIO
After an update, check the form too.
An example of defining requirements and checking the output. This is an illustrative scenario, not a deployed project or a measured client result.
- Scenario
- A technical change may affect the contact form. The check needs to cover its layout, delivery and the feedback shown to the visitor.
- Test boundaries
- Use a test environment, sample data and a separate recipient. Confirm the backup, change scope and recovery plan before updating.
- Expected output
- A short record of the version changed, checks completed, open defects and the decision to keep the update or recover the previous version.
- Acceptance checks
- Missing required fields produce a clear message; valid enquiries reach the test recipient; delivery errors preserve the entered details without showing success.
FAQ
Before we begin.
A few useful answers to help define the right scope.
Can you maintain a website built by someone else?
We can assess it first. Acceptance depends on access, documentation, platform and condition. Existing defects or unsupported components may require separate remedial work.
Does maintenance include publishing content and SEO?
The starting scope includes up to one hour of small fixes or content updates per month. Ongoing publishing, product administration and SEO need separately agreed goals, deliverables and pricing.
Will an incident be fixed immediately?
Response expectations are agreed in advance. Resolution depends on the cause, impact, available access and any hosting or other provider involved.
How is the maintenance cost determined?
The published starting price covers the stated base maintenance scope. The final quote reflects the website’s platform, functions, maintenance frequency and support needs. Initial repairs, hosting, domain renewal and external service charges are identified separately.
How often is the website checked and backed up?
The starting scope includes weekly backups, plus monthly checks, updates and a report. Relevant functions are checked again after each update. If website data changes frequently, we propose a more suitable backup schedule; the quote records frequency, retention, recovery checks and cost.
LET’S DEFINE THE REQUIREMENTS
Discuss website maintenance.
Share your website and describe the issue or maintenance you need. We clarify the scope and required access before taking on the work.