Start with the work, then choose the platform
List the tasks people must complete: edit a service page, compare an offering, submit a request, find that request and respond. Add the rules that genuinely matter, such as which team can see a record or what must be confirmed before work continues.
Separate a current requirement from a possible future product. A team that needs clear pages and a working form does not automatically need a bespoke application. A team with a distinctive multi-step process may need more than a visual redesign. Write an acceptance example for the difficult step before choosing a stack.
Compare four approaches rather than two extremes
| Approach | A useful fit | What to check |
|---|---|---|
| Website builder | Service pages, content editing and standard enquiries. | Form storage, notifications, exports, language support and the plan limits you actually need. |
| Builder plus existing tools | A familiar website with an added CRM, scheduling or request workflow. | Where the source record lives, integration failures, duplicate records and ongoing ownership. |
| Custom website | Specific content structure, interactions or integration needs that justify code. | Who can edit it, deployment and updates, accessibility, and the boundary with backend services. |
| Custom business system | Defined records, roles, states and actions that standard tools cannot handle well. | Permission checks, recovery, migration, maintenance and acceptance by actual users. |
A builder can be enough
If the work is mostly publishing service information and receiving standard requests, try the platform’s own capabilities before commissioning a replacement. Wix documents that form submissions are stored in a submissions table and can be managed or exported. That is one concrete example of a builder providing more than a contact button.
Test the exact plan and configuration with your own acceptance example. Check what happens if a notification fails, how the team retrieves a record and how you can export it. A feature listed on a platform page is not proof that your configured site is working.
Official reference: Wix: Viewing and managing form submissions
An integration may solve the missing step
A working website can remain in place while a form is connected to an existing tool or a small backend. This middle path can avoid rebuilding content and workflows that already serve the team. It still needs a clear owner for the connection, a way to detect failure and a decision about which system holds the authoritative record.
Webflow’s Code Embed supports HTML, CSS and browser JavaScript, but does not run server-side languages. Its documentation also describes third-party embeds. This is a boundary of that feature, not a claim that Webflow can never connect to business systems: server-side work can live in an external service.
Official reference: Webflow: Custom code embed
Custom work earns its place when the rules need it
Consider custom development when the important task cannot be supported clearly by configuration or a maintainable integration. Examples include tightly controlled record access, a specific approval sequence or state changes that must stay consistent across tools. These are generic requirements, not claims about any client’s internal system.
Ask for a small working slice that includes its difficult exception. A happy-path screen is not enough if the important risk is a missing record, repeated action or a staff member seeing information outside their role. Agree who will operate, update and recover the system after handover.
Use these questions before approving a rebuild
Content ownership
Who edits service information and translations? Demonstrate the edit rather than judging only the finished design.
Records and handovers
Where does a submitted request go, who can retrieve it and which tool owns its status?
Change and failure
What happens when a connection is unavailable, a person retries or the business rule changes?
Ongoing responsibility
Compare platform subscriptions, integrations, maintenance, updates and support effort. Get the actual scope before comparing prices.
Leaving the setup
Check content and record exports, domains, access and a practical handover. A custom codebase also needs documentation and a maintainer.
Keep the search requirements separate from the platform label
Neither a builder nor custom code supplies a ranking guarantee. Check the output: readable service content, useful internal links, correct page URLs and a usable mobile experience. Google’s starter guidance is about helping people and search engines understand content, and explicitly offers no automatic route to first position.
Choose a platform that your team can maintain while meeting those requirements. If the existing site can do that, focus the work on the missing task. If it cannot, document the limit and test a replacement against the same acceptance example.
Official reference: Google Search: SEO Starter Guide
Illustrative example: improve one enquiry path first
A service team has clear pages on a builder, but staff manually copy requests into another tool. Begin by mapping the few fields the next person needs and testing a supported integration. Keep the website if it can still explain the offer and receive requests reliably.
If an essential rule cannot be represented or recovered safely, evaluate a small custom component. Expand into a larger system only when the working example and actual use justify it. This is a decision method, not a promise that custom development will be cheaper or improve sales.
Sources & next steps
- Wix: Viewing and managing form submissions
- Webflow: Custom code embed
- Google Search: SEO Starter Guide
Continue reading
- Website Traffic but No Enquiries? Check the Path to Contact
- Inquiry-ready websites for service businesses