Decision helper
Rebuild, or just a refresh?
A full rebuild isn't always the answer — sometimes it's overkill, and a refresh gets you 90% of the win for a fraction of the spend. Here's the honest way to tell which one you actually need.
A refresh is probably enough if…
- The site loads fast and works fine on mobile — it just looks dated
- Your content and structure are mostly right, the styling is the problem
- You're not changing what the site needs to do, only how it looks
- There are no broken flows — forms send, pages link, nothing 404s
- You can edit it without fighting the platform
A rebuild is the honest call if…
- It's slow, clunky on phones, or you're scared to touch it
- You need things it can't do — bookings, lead routing, CRM, real operations
- You're bolting on app after app to patch gaps, each with its own fee
- You don't own it, or exporting would lose half the site
- Every small change needs a developer and a week
The honest version
If the bones are good and you just need it to look current, I'll tell you to refresh — it's cheaper and faster, and I'd rather earn your trust than oversell you a rebuild. But if your site is fighting your business instead of running it, a refresh just puts lipstick on the problem. Velocity X is for the second case: a build that owns the operations layer, not just the looks.
Not sure which column you're in? Send me your site and I'll give you a straight read — refresh or rebuild — with no pressure either way.