Website Support Hours Explained
Many business websites need a series of practical improvements rather than a complete rebuild. Perhaps the opening hours have changed, a service page needs clearer wording, the mobile menu is awkward or several product details are out of date. Website support hours are a way to organise and pay for defined work without assuming that every change requires a large project.
This guide explains the decisions a business owner should make before buying a block of professional time: which tasks to include, how to brief the work, what to agree about estimates and approvals, and how to review the outcome. The three scenarios below are illustrative calculations, not claims about specific clients.
Website support hours: who are they suitable for?
They are most useful when you already have a functioning website and can identify a manageable queue of tasks. You might need help changing sections, uploading approved content, improving contact forms, refining product descriptions or testing a mobile layout. The scope can be broad, but each task should have a specific definition of done.
They are less suitable when there is no agreed outcome, the site needs an architectural rebuild, or several external systems must be investigated before anyone can estimate the effort. In those situations, a short discovery and scope discussion may be better than purchasing a large balance immediately.
What can website support hours cover?
Website content: update service descriptions, product details, opening hours, prices supplied by the owner and frequently asked questions.
Design and usability: improve spacing, mobile sections, calls to action, menus, images and readability.
SEO foundations: review titles, descriptions, headings, internal links and pages that need better explanations.
Shop and booking administration: organise product information, service options, forms and tested customer journeys.
Maintenance: identify broken links, outdated content, incomplete sections and recurring update requirements.
Training: explain how the owner can safely make routine edits and maintain structured content.
Wix Solutions publishes a separate website updates and maintenance service for practical changes and a content writing service for customer-facing wording. These give useful examples of work that may be scoped as an individual task or part of a larger support request.
How to buy website support hours without wasting them
1. Prepare a ranked task list
Instead of writing 'improve my website', list the specific pages and problems. Example: 'On the contact page, the confirmation message is too vague; change it to explain when enquiries are reviewed and test delivery.' Mark tasks as urgent, important or optional. A five-minute correction and a new booking workflow should not receive the same estimated effort.
2. Agree what the purchase does and does not include
Ask whether the time pays for investigation, design, copywriting, communication, revision rounds, testing and publishing. Confirm which specialist services or third-party charges are excluded. If new requirements emerge, ask for an updated estimate before committing the remaining balance.
3. Provide usable access and source material
Before work starts, organise the required permissions, approved copy, genuine images, product information and decision maker. Do not send passwords by ordinary email when delegated access is available. Missing source material can create delays and unnecessary clarification time.
4. Ask for a simple time record
A useful log has a date, task, work completed, hours used, remaining balance and blockers. The format can be a short table or agreed written update. It should be understandable without technical knowledge. If a task grows beyond the estimate, the log should make that visible before more work is authorised.
5. Check the result on the live website
A task is not complete just because a design editor says 'saved'. Test the correct published URL, desktop and mobile presentation, links, forms, pricing and any automated confirmation. Ask for a concise handover explaining what changed and what the owner can update independently.
A worked time-block example: 20 hours
A 20-hour package is one of the options displayed in the Wix Solutions time-block collection. The public listing for the 20-hour service package showed £800 when this guide was prepared on 16 October 2026, equivalent to £40 per purchased hour. Prices, availability and detailed purchase conditions should always be checked on the current product page and applicable agreement before ordering.
The following is a hypothetical allocation, not a statement of how every package is delivered. It assumes an agreed starting balance of 20 hours and that each task is approved in advance.
Task A: review and correct five service descriptions — illustrative time: 3.0 hours. Remaining: 17.0 hours.
Task B: improve the main contact page and test enquiry notifications — illustrative time: 2.5 hours. Remaining: 14.5 hours.
Task C: check tablet and phone layouts on three priority pages — illustrative time: 3.5 hours. Remaining: 11.0 hours.
Task D: reorganise four product entries and their accompanying information — illustrative time: 4.0 hours. Remaining: 7.0 hours.
Task E: update page metadata and contextual internal links — illustrative time: 3.0 hours. Remaining: 4.0 hours.
Reserve: keep the final 4.0 hours for authorised follow-up, QA, additional work or handover as agreed.
The calculation shows that a block of time can cover several different small improvements, but it cannot guarantee that a specific number of pages or a complete project will fit. Actual time depends on site complexity, access, client-supplied materials and the agreed service boundaries.
Three website support hours case studies
Case 1: a Hampshire building company
Situation: a small builder has an established site but outdated pictures, unclear service areas and a quote form that is difficult to use on mobile. There is no need to replace the brand or rebuild the whole website.
Possible agreed sequence: verify the current service areas, replace photographs with approved work, clarify the repairs and renovation pages, then submit controlled mobile enquiries. Acceptance check: the customer can identify a relevant service, reach the correct form and receive a suitable acknowledgement. Key lesson: spending the first hours on the enquiry journey can be more valuable than adding decorative animation.
Case 2: an online retailer
Situation: an independent shop is adding new collections and the site contains inconsistent titles, missing size information and old products still visible in seasonal lists.
Possible agreed sequence: select a representative category, agree naming rules, update a small batch, test filters and mobile product pages, then apply the approved pattern. Acceptance check: products display correct details, options and destinations. Key lesson: a carefully defined pilot reduces repeated edits and gives the business owner a maintainable process.
Case 3: a professional training business
Situation: a course provider needs to update programmes, distinguish self-paced from bespoke training and fix confirmation messages. The owner has not yet supplied all materials for a full redesign.
Possible agreed sequence: correct current programme descriptions, add a simple comparison, test contact or enrolment pathways and document which future materials remain missing. Acceptance check: visitors can select an appropriate course route and the business receives the correct enquiry. Key lesson: support hours can solve urgent clarity problems while a larger project remains in planning.
When is a fixed-price website project better?
A clearly defined deliverable such as an agreed new website, a major catalogue rebuild or complex functionality may be easier to manage as a separate project. Compare the total scope, dependencies, approval stages and testing rather than assuming an hourly or fixed-price model is always cheaper. For larger visual and structural changes, review the website redesign service.
Website support hours: a briefing checklist
Current live website address and the relevant page URLs.
Business objective: the customer action the change should improve.
Prioritised list of tasks, with urgent items clearly marked.
Approved texts, photographs, prices and usage permissions.
Required access permissions and the person who approves changes.
Any fixed deadline and dependencies, including products or forms.
Requested acceptance test for each task.
How estimates, progress, remaining balance and additional approvals will be recorded.
Frequently asked questions about website support hours
Can I buy website support hours for one small job?
A small task may be suitable for an individual support request or a smaller time block. Describe the work first, then compare the currently available packages and any minimum booking requirements.
Does a time block guarantee the task will be completed?
Not automatically. A block buys a defined amount of working time. Large, uncertain or changing requests may require more time. Agree estimates, communication and the procedure for authorising further work.
Are meetings, research and revisions included?
That depends on the agreement. Ask for clarity before ordering so neither party assumes that consultations, investigation or additional revisions are free or outside the balance.
Can support hours include SEO and content work?
They may be suitable for agreed on-page changes, content improvements and practical implementation. Search positions or enquiry volumes should not be treated as guaranteed outcomes of buying a number of hours.
What happens if I do not use all my hours?
Check the current package terms and agreement for rules about remaining balances, scheduling, validity and refunds. Do not assume that every provider offers the same arrangement.
A clear next step
If you already have a list of changes, send Wix Solutions the website address and three highest-priority tasks. We can help discuss the scope and which option may fit before you select a time block. For a general enquiry, contact Wix Solutions.
