Pick for year two
The build is a short part of a website’s life. The harder question is who handles a new service, an outdated page, a broken integration, or a staff change next year. Put a real name beside that work before choosing a platform.
Each option can be right. Little Fight builds custom sites, so that bias should be clear. A business that publishes constantly or needs an existing platform feature may have a better fit elsewhere.
Compare the ongoing job
| Option | Good fit when | Owner needs to plan for |
|---|---|---|
| WordPress | You publish substantial content or need a mature publishing system. | Core, theme, plugin, hosting, backup, and access responsibilities. |
| Webflow | Design control and a hosted editor suit the people maintaining it. | Platform account ownership, editor training, and the practical cost of moving later. |
| Custom | The site has a clear customer job and changes are planned rather than constant. | A documented relationship for updates, integrations, and handoff. |
Every choice needs care. A custom site can still need software updates and repairs. Ask what this particular site uses and who maintains it.
Ask these questions before you sign
- How often will we honestly edit the site? Count normal changes over a year, not the changes you hope to make.
- Who owns the accounts? The business should control the domain, billing, recovery routes, and access record.
- Which integrations carry customer information or money? Booking, payments, forms, email, and analytics need named owners and test plans.
- Who checks the upkeep? Name who installs updates and checks whether they succeeded. Ask who keeps backups and proves they can restore them. Put the support and recovery plan in writing.
- What can we take with us? Ask what exports cleanly and what must be rebuilt.
Platform guidance changes
Read the current official documentation for the version and plan you are considering. WordPress, Webflow, and hosting providers change features and terms. A builder should explain the decision in business language before relying on a technical feature list.
When to keep the site you have
WordPress is not a reason to rebuild by itself. If it works and someone maintains it, keep it.
Open your site on a phone and check three things. Can you tell what the business does? Can you find a way to call? Can you finish the booking or inquiry path? Start with the specific step that fails. Unclear words or a buried button may need a cleanup.
What if we do change platforms?
Keep existing page addresses where practical. List any addresses that need to move and their replacements. Have your builder set up redirects and test them. Check forms and booking links from a phone before launch.
Make the tradeoff visible
WordPress recommends keeping plugins and themes current. These are the add-ons and designs your site uses. Administrators can enable their automatic updates. Check the actual settings and who watches for failures. WordPress: plugin and theme auto-updates — checked Oct. 20, 2026.
WordPress also recommends backing up before an update. Ask how the site would be restored if something breaks. WordPress: updating WordPress — checked Oct. 20, 2026.
Webflow documents what can be exported as site code; connected CMS, ecommerce, and hosting behavior need their own review. A custom site should come with equally clear information about the delivered files and later changes.
Read the Wix comparison for the platform-versus-custom question, and the ownership guide before moving any domain or account. A website scope should make the long-term responsibility clear before work starts.
Talk to Little Fight.
Send a website link, an error message, or a few lines about the work. The first 30 minutes are free, and we’ll explain what we can help with.
David answers 9am–9pm Eastern. After hours, leave a message.