Start with requirements, then choose a platform
WordPress, Webflow, Framer and custom development can each be appropriate for a website. The right choice depends on publishing needs, design, integrations and ongoing ownership. Use this guide to make an initial shortlist, then test a representative page and the main visitor journey.
WordPress
Consider WordPress when its publishing model, extension ecosystem or choice of hosting arrangements matches your requirements. Decide whether you want a hosted WordPress.com service or software from WordPress.org with a separate host.
Check the actual theme, extensions, plan and hosting service you intend to use. Agree who handles compatibility, updates, backups and restores. The flexibility of an ecosystem comes with decisions that need ongoing ownership.
Start with WordPress.com vs WordPress.org or the WordPress website guide.
Webflow
Include Webflow in the shortlist for a custom marketing website where visual control, reusable CMS content and a defined editing workflow matter. Test your real collection model, responsive layouts and integrations rather than relying on a demo.
Confirm the current plan, publishing limits, seats, localization and any additional services required by the project. Plan a handoff that lets the business maintain normal content updates.
Read the Webflow and Framer comparison for a practical evaluation session.
Framer
Include Framer when your marketing website can benefit from its visual design and publishing workflow. Check your CMS structure, editing needs, responsive behavior and integrations in a representative build.
Verify current plan features rather than treating platform capabilities as permanent. Review how the team will operate the website after the original designer hands it over.
The Webflow and Framer comparison uses the same evaluation questions for both platforms.
Custom development
Evaluate custom development when your requirements involve application behavior, specific data flows, permissions or integrations that justify engineering control. A marketing website and an application can also use different parts of a combined architecture.
Document the operational work alongside the build: deployment, monitoring, dependencies, backups, security updates and incident ownership. More control should answer a real requirement rather than becoming an automatic preference.
Run the same small experiment in each shortlisted option
- Build a representative page using real copy and images.
- Publish one example of every important reusable content type.
- Complete the primary enquiry, account or purchase flow.
- Test validation, failure and success states.
- Check phone, tablet, desktop, keyboard and reduced-motion behavior.
- Ask the intended editor to make a normal update.
- Record plan costs, remaining compromises and operational ownership.
Make the decision reviewable
Write a short decision record: requirements, options considered, demonstrated tradeoffs, current costs and owner. Keep links to the official documentation used to verify important constraints.
Use the website brief template to record scope. Try the platform finder if you need help creating your first shortlist.
Official references
The Blitz Studio team
We design brands, build websites and engineer digital products.
Talk about your next project