The WordPress rebuild you do not need
Most businesses asking for a new site actually want one new capability. A plugin inside the site they own is cheaper, faster and keeps their SEO intact.
A client with a working WordPress site asks for a rebuild. Nine times out of ten, what they want is one thing the site cannot do — take orders, show live availability, sync with their POS. A rebuild puts that behind three months and a new design argument. The faster route is to add features to an existing WordPress site instead.
Why keeping the site wins
Existing URLs keep their rankings. The team already knows the editor. And the budget goes into the capability instead of re-approving a homepage.
Where plugins go wrong
Theme hacks and direct database writes. Build against the real APIs, add your own admin screens, and the site survives core updates without a support call.
What good looks like
For Direct Dine I built a plugin that turns any WordPress site into a full ordering system: a live order board inside wp-admin, menu import, card payments on the client's own gateway. Nobody learns a second dashboard.
When the code itself is the problem
Sometimes the site does the right things but runs badly: slow, fragile, bloated with plugins. Then you need new code, not a new look. I cover that case in WordPress rebuild without redesign.
I take on a small number of projects at a time. Tell me what you are building and I will tell you honestly whether I am the right person for it.
Get in touch →
1 comment