When is it worth replacing a website that still works?

Seattle Talent’s website had a clear job. It introduced the business and gave prospective talent a way to get in touch. But its WordPress installation was repeatedly compromised, and each repair meant returning to a system the business still had to maintain and protect.

I moved the site to Hugo, removing the public WordPress application while preserving the site’s purpose. For another business, the decision could go differently. Staff might depend on publishing tools or features that would be costly to replace.

Start with what people rely on

Write down what visitors use the site for, what staff need to change, and which problems keep taking time to fix. Include the less visible work, such as making sure inquiries arrive, keeping important URLs working, and getting a time-sensitive update published.

Then ask what it would take to repair or simplify the current setup. A recurring problem may come from one component you can remove or replace. If the burden comes from maintaining the platform itself, compare that ongoing work with the cost of moving and supporting the new site. Include the time staff will spend learning how to make the updates they handle today.

Before switching, check that someone can complete the tasks you listed, from sending a test inquiry to publishing a routine update. Those checks tell you whether the replacement can take over the work the business still needs done.

If something like this is happening in your business, tell me what you’ve noticed. We can talk through where to start.