Spout’s WordPress care starts from K450 a month, confirmed in your written quote. Its broader Mission Control service starts from K3,500 a month, confirmed in your written quote. These cover different scopes. Compare the tasks, responsibilities and exclusions in the written offer before treating two monthly prices as alternatives for the same work.
What are you actually paying someone to maintain?
Start with a list of the things your website does. A service page with a contact form has different dependencies from a shop taking payments and keeping stock records. Note the parts that would stop the business working if they failed: enquiries, checkout, booking, customer accounts or a download promised after payment.
Then list the accounts that support them. The domain, hosting, email, software licences and payment service may have different renewal dates and owners. A monthly care arrangement should make clear which of those costs it includes and which remain separate.
The useful question is whether someone has accepted responsibility for each task. A hosting bill does not, by itself, define who checks a form or repairs a broken shop extension. Ask for that responsibility in writing rather than discovering the gap during an outage.
How do the main care arrangements differ?
Our comparison separates the purpose of the service from its headline price. Exact coverage must still be confirmed against your site and its condition.
| Arrangement | Starting point | Questions to put in the scope |
|---|---|---|
| Hosting | Spout hosting from K150 a month, confirmed in your written quote | What infrastructure, storage and support does this include? |
| WordPress care | From K450 a month, confirmed in your written quote | Which updates, checks and recovery tasks are included? |
| Mission Control | From K3,500 a month, confirmed in your written quote | Which hosting, security, edits, visibility and reporting tasks apply? |
| A repair project | Scope assessed before quotation | What caused the fault and what evidence proves recovery? |
These starting prices are Spout’s approved service figures. They are not a survey of the Zambian market, and the table does not imply that a repair is automatically included in a monthly plan.
Read Mission Control for the broader service and WordPress design and care for that platform. If you are still choosing a build, the website pricing page explains the package conversation separately.
What should a useful monthly report show?
Ask for a short record of completed work and unresolved decisions. It should tell you what changed, which important functions were checked and whether anything needs the owner’s attention. A list of technical version numbers is less helpful if it never says whether customers can still contact or pay you.
Our suggested report has four parts: changes completed, customer journeys checked, renewal or access issues, and decisions required. For a shop, include the outcome of a safe checkout check. For a service business, include evidence that the form reached the right inbox.
Treat this as a proposed reporting structure, rather than a claim that every entry is included in the cheapest care plan. Discuss frequency and scope with the provider. The point is to make the service understandable and the unfinished work visible.
Why do backups and updates need separate questions?
An update changes the running site. A backup is evidence you may be able to recover an earlier state. Ask who makes the backup, where it is kept and who has proved that it restores successfully. A scheduled task labelled successful is not the same demonstration as a working restored site.
WordPress’s update guidance advises backing up before an upgrade. Its security guidance treats maintenance as ongoing work. Sources checked 19 October 2026. Neither document can confirm what your particular care agreement includes.
For your own site, agree how a failed change is handled. Who decides to reverse it? Who tells the business that a form or checkout was affected? Which information would be lost if an earlier backup were restored? Our backup and recovery checklist sets out a safe checking exercise. These answers matter more than a vague promise that everything is secure.
How should edits and emergency work be priced?
Define an edit with examples. Replacing an opening time is different from adding a booking workflow or redesigning a product catalogue. Ask whether the plan includes a set allowance, how requests are prioritised and what happens when the requested change is a new project.
Agree support hours and escalation routes explicitly. Do not infer round-the-clock response, a recovery deadline or compensation from the word managed. If the website supports time-sensitive sales, make that requirement visible before choosing the service.
A neglected site may need an initial review or repair before routine care is sensible. The quote should identify that starting condition and the work required to reach a maintainable state. Otherwise the owner and provider may believe they agreed to different things.
What should you keep when changing providers?
The business should know who controls its domain, website, email and payment accounts. Keep an inventory of account owners and recovery contacts. Ask for a documented handover process and a current backup before ending an existing arrangement.
Do not cancel hosting until the replacement works and the agreed data has been transferred. Check mail separately: a working new website does not prove that every mailbox or message has moved. Record renewal dates so an old contract does not lapse during the transition.
Bring your website address, the functions that matter and your current support arrangement when you request a maintenance review. The useful outcome is a clear scope at a confirmed written price, with an owner for the tasks your business depends on.
Spout Team. Prepared with AI assistance; sources checked on 19 October 2026.