Updates without backups is gambling.
Monthly minimum
Core/plugin updates on staging when possible, verified backups, and a known restore path.
Next step
Treat updates as a recoverable change
Use the following worksheet to turn this article into an operating decision. It is a practical plan for a Bangladesh small business, not a claim about a particular client or an industry benchmark. Adapt it to your current workflow and constraints.
Back up files and database, record versions and know the recovery account. Keep a copy outside the same hosting failure domain.
Test changes on a staging copy and run the actual enquiry and checkout paths. Do not assume the homepage looking correct proves everything works.
Update in manageable groups and check errors. If a critical transaction fails, restore the known working version and investigate the failing dependency.
Write this before requesting proposals
Describe the current process, the failing step, the intended users and what a correct outcome looks like. Prepare representative test data so suppliers can demonstrate the same task. Ask separately about recurring costs, third-party dependencies and work excluded from support.
When to change the plan
Resolve missing access, failed acceptance checks or unclear team ownership before paying for the next stage. Use evidence from a small pilot. If scope grows, agree revised time and costs rather than relying on unsupported guarantees.