WordPress vs. Webflow vs. Custom Code: Run a 12-Question Exit Test
Choose a platform for a service-business lead-generation site by testing editing, integrations, operations, and a real exit path—not by assuming one stack always wins.
WordPress, Webflow, and a custom-coded website can each support a strong service-business site. The useful difference is not which platform sounds more professional. It is which operating model your team can maintain—and what remains usable if the vendor, developer, host, or business requirement changes.
Define the site before comparing platforms
This comparison is for a service-business lead-generation site: service pages, location or audience pages, proof, blog content, analytics, and a contact or booking path. It is not a universal answer for ecommerce, media publishing, membership products, or a complex internal application.
Write the required outcomes first:
- who edits service facts, articles, proof, and team information;
- which forms, booking tools, CRM, analytics, or call systems must connect;
- which pages and languages must be managed;
- which performance, accessibility, privacy, and recovery checks are required;
- what must be transferable if the relationship or platform ends.
Without that scope, a platform demo rewards whichever tool presents the most attractive happy path.
“Ownership” has four separate layers
Do not accept “you own the website” as a complete answer. Verify four layers:
- Content and data: Can you export pages, media, form records, users, and structured collections in usable formats?
- Presentation and code: Can you take the templates, styles, scripts, components, and custom work? What license or contract applies?
- Operations: Does the business control the domain, DNS, analytics, email routing, source repository, hosting account, backups, and deployment credentials?
- Working capability: After export, do forms, search, localization, CMS editing, permissions, and dynamic behavior still operate—or must they be rebuilt?
The fourth layer is where a ZIP file can create false confidence. Files may be portable while the working product is not.
What the platform documents establish
WordPress: portable software with a maintained stack
WordPress is released under GPLv2 or later. That gives the software an open-source foundation, but a business site still includes a database, uploaded media, theme, plugins, custom code, hosting configuration, and third-party services.
The operating burden depends on that assembled stack. WordPress documentation says plugins and themes should be kept current, allows auto-updates to be managed per plugin or theme, and recommends having a rollback-capable backup before enabling them. See the official plugin and theme auto-update guidance.
WordPress is therefore neither automatically portable nor automatically fragile. Audit the actual host, theme license, plugin licenses, customizations, backup restoration, and administrator access. Our WordPress maintenance cost audit covers that operating check in detail.
Webflow: exportable front-end files with documented capability limits
Webflow documents that code export is available on paid Workspace plans, not Site plans. Its code export guidance says an export includes HTML, CSS, JavaScript, and assets.
The same document states that exported code does not include working CMS content/functionality, user accounts, ecommerce functionality, localized content, code components, password protection, form processing, or site search. Some collection data can be exported separately as CSV, but that is not the same as carrying the hosted capability to another provider.
That boundary may be entirely acceptable for a visual marketing site whose team prefers Webflow's editing and hosting workflow. It becomes material when multilingual publishing, dynamic collections, forms, or search are core requirements.
Custom code: control depends on the contract and operating handoff
“Custom” describes how the site is built, not who can operate it. A custom site can still be locked to one developer account, undocumented deployment, proprietary package, or inaccessible repository.
Require the agreement and handoff to name the source-code rights, third-party licenses, repository owner, domain and hosting accounts, build/deploy instructions, environment configuration, data export, backups, monitoring, support, and transition obligations. Test them before final payment or launch.
Custom code is strongest when the required behavior does not fit a hosted builder or plugin stack and the business is prepared to own ongoing engineering. It is weak when the site is standard, the editor experience is poor, or no one owns maintenance after launch.
Run the 12-question evidence test
Ask every vendor to answer with an account screen, sample export, repository, contract clause, or live demonstration—not a yes/no promise.
| Question | Evidence to request | Decision signal |
|---|---|---|
| 1. Who can edit each content type? | Role-based editing demo | Daily work fits the actual team |
| 2. Can fields and templates prevent contradictions? | Service and location content model | Repeated facts have one owner/source |
| 3. How are both languages managed? | Locale workflow, URLs, metadata, export | Parity is maintainable, not copied manually |
| 4. Which integrations are native or custom? | Form-to-CRM/booking demonstration | Failure ownership and retry path are clear |
| 5. Can required business logic be represented? | Prototype using one exception case | No critical workflow depends on a workaround |
| 6. What changes when a third party changes? | Dependency list and owner | Vendor/API/plugin changes have a response path |
| 7. How are updates tested and reversed? | Staging, backup, restore, rollback demonstration | Recovery is proven, not merely purchased |
| 8. How is real-user performance measured? | Field data and page-level test plan | Performance is measured after content/tools load |
| 9. Who owns accessibility and privacy checks? | Named acceptance criteria and reviewer | Responsibility survives launch |
| 10. What exactly can be exported? | Real export plus documented exclusions | Files, data, and capabilities are separated |
| 11. Which accounts does the business control? | Account-owner and recovery inventory | No essential account belongs only to a vendor |
| 12. Can another qualified team operate it? | Clean-environment build/restore handoff | Transition works without the original builder |
Do not total the answers into a fake universal score. A single failed requirement—such as unusable multilingual export or inaccessible domain control—may outweigh ten conveniences.
Test SEO and performance on the actual build
No platform name guarantees search visibility or speed. Test crawlable pages, titles, canonical URLs, redirects, structured data where applicable, image behavior, and the published sitemap on the exact implementation.
For performance, use field data when available and lab tests for diagnosis. Google's Web Vitals guidance defines Core Web Vitals as measurable loading, interactivity, and visual-stability signals and recommends evaluating the 75th percentile separately for mobile and desktop. A clean starter template does not prove the final site will meet those targets after fonts, media, embeds, consent tools, and analytics are added.
Perform an exit drill before choosing
Ask the finalist to produce a small, representative handoff:
- export one service page, one article, one image, one form definition, and one structured collection;
- identify what works outside the platform and what must be replaced;
- restore or build it in an account or clean environment controlled by the business;
- verify URLs, redirects, metadata, analytics ownership, and form delivery;
- document recurring licenses, service dependencies, and the person responsible for each;
- estimate transition work without pretending export equals migration.
This drill exposes the difference between owning artifacts and operating a working lead-generation site.
Frequently asked questions
Is WordPress better for SEO than Webflow or custom code?
Not inherently. All three can expose crawlable content and search metadata; all three can also be implemented poorly. Compare the published pages, content workflow, technical controls, and measured performance.
Does open-source WordPress mean there is no lock-in?
No. The core software license is open, but a specific site may depend on a host, premium theme, proprietary plugin, page builder, custom code, and external services. Portability must be tested on that assembled site.
Does Webflow code export mean the whole site is portable?
No. Webflow documents meaningful exclusions, including hosted CMS behavior, localized content, forms, search, and other functionality. Decide whether those exclusions affect the required site.
Does paying for custom development mean we own everything?
Not automatically. Rights, repositories, accounts, licenses, data access, deployment, and transition support should be explicit in the contract and verified in the handoff.
Which option is cheapest?
There is no platform-wide answer. Compare implementation, platform or hosting fees, plugins or services, updates, support, content operations, changes, incident recovery, and exit work over the same planning period. Our guide to why website prices vary separates those cost layers.
When should a service business choose custom code?
When required integrations, workflow, content model, performance control, or ownership boundary cannot be met responsibly by the hosted or plugin-based options—and the business can support engineering after launch. For operational software beyond the website, use our custom software vs. SaaS bottleneck test.
Choose the operating model you can prove
The best platform is the one that satisfies the required customer journey, fits the editing and maintenance team, and survives a documented transition. Make vendors demonstrate those boundaries before design momentum turns assumptions into expensive dependencies.
Use this checklist to compare any proposal before a rebuild begins. If custom development is the operating model that survives the evidence test, explore NG Technology's website design and development scope.
Request a custom website proposal
