Separate guest Wi-Fi from office network
Separate guest Wi-Fi from office network traffic so visitors never sit one hop from finance, payments, or file shares.
·
3 min read
Website care plan vs rebuild is the choice London SMBs face when the site still loads but every change feels fragile. A care plan keeps a workable site safe and tidy; a rebuild is for when structure, stack, or conversion has hit a ceiling. You want an honest call, not a sales script that always lands on “start again.”
A website care plan is ongoing maintenance: security and CMS updates, backups you can restore, hosting hygiene, small content edits, and fixes when a form or plugin breaks. It assumes the information architecture still matches how you sell, the theme or build is maintainable, and conversion is “good enough to improve in place.”
It fits firms whose site is a few years old but still clear, whose plugins or framework are still supported, and who mainly need someone accountable for updates and the odd page change. I’ve kept plenty of London trade and professional sites on care when the only real gaps were outdated plugins, a slow homepage image, and nobody owning SSL renewals.
The honest limit: care cannot rescue a site whose templates fight every edit, whose navigation confuses buyers, or whose stack is abandoned. Pouring monthly hours into an unmaintainable build is how you pay forever for a site that still does not convert.
A website rebuild replaces the public site (and often the CMS or static setup underneath) so structure, content model, performance, and design match how the business sells now. You migrate what still earns its keep, cut the rest, and hand back accounts and a stack someone can actually change.
It fits when IA is broken, mobile conversion is stuck, the theme is a tangle of child overrides, SEO has plateaued because URLs and templates cannot express the offer, or compliance and accessibility need a clean base. Eight Mile’s web design work is this path when a care plan would only polish a dead end.
The honest limit: rebuild costs more up front and needs content decisions from you. Rebuilding because a competitor launched a prettier homepage, while your real problem is unclear offers and slow lead follow-up, wastes money. Fear of “looking old” is not a brief.
Many SMBs need a short audit before either path. If plugins, hosting, and content edits are the bottleneck, start care and measure enquiries for a quarter. If every “small change” needs a developer excavation, or buyers cannot find the offer in three clicks, budget a rebuild and park unlimited care hours that only paper over the mess.
After a rebuild you still want a care plan. New sites age the same way: updates, backups, and someone who notices when the contact form fails on a Friday. Care after rebuild is cheap insurance. Care instead of rebuild, when the stack is already dead, is expensive denial.
If you are weighing website care plan vs rebuild, choose care when the site’s structure still matches the business and you mainly need security, updates, and light edits. Choose rebuild when IA, stack, or conversion has capped what polish can do. Need both in sequence: rebuild once, then care so the new site does not rot.
Care protects a working asset. Rebuild replaces one that no longer earns its keep. Decide from how hard changes are and whether buyers can still find you, not from a redesign mood.
If you want a short look at your live site and a plain recommendation — stay on care, rebuild, or a staged path — contact Eight Mile and send the URL plus what you wish the site did that it will not do today.
Separate guest Wi-Fi from office network traffic so visitors never sit one hop from finance, payments, or file shares.
·
3 min read
A backup restore test proves copies work on a clock you can live with. Untested backups are hope with a green tick.
·
3 min read
Moving off the server under the desk: stage a move to managed hosting or cloud you own — without a big-bang rewrite.
·
3 min read
When UniFi is enough, and when you want Meraki/Cisco: cost, ownership, multi-site, and support for London offices.
·
3 min read
Multi-site office network design for London SMEs: site-to-site links, consistent segmentation, accounts you keep.
·
3 min read
Security audit vs penetration test: when to review config first, when a buyer needs a pentest, and usual order for SaaS.
·
3 min read
Secrets in git repository history outlive a deleted file. Rotate first, then stop the next temporary commit.
·
3 min read
Office network for a growing London team: when the ISP router fails, what a proper office network includes, and why survey first.
·
3 min read