Pre-built or custom-built: choose the right necessary threshold
Most websites do not need to be built separately. The rest cannot avoid being built separately. The issue is knowing which group you belong to.
A ready-made platform (website builder or existing CMS like Webflow, WordPress, Shopify) is sufficient for most basic promotional and sales websites. The condition is that the tasks the site needs to perform still fit within common templates. You should only build custom if the site needs to do something that templates cannot handle: specific conversion flows, internal system integration, very strict speed thresholds, or very large content scales. Don't build custom just because it sounds more sophisticated. If your actual needs still fit within the template, the costs and time spent on a custom build will not be justified.
- introduction website, campaign landing page, basic sales
- need to launch quickly at low cost, team not technically skilled
- specific conversion flows or deeply integrated systems
- strict speed or scale of tens of thousands of pages
This is a question Sinh Vũ hears frequently, and the answer is mostly: a ready-made solution is sufficient. Not because custom builds are inferior, but because most small and medium-sized business websites do not actually have needs that exceed the template. The issue is that you need to know how to ask the right questions to determine which group you belong to.
The first question to ask.
Before asking "which platform should I use," ask: what does this site need to do that common templates cannot handle? If you do not have a clear answer to that question, it is likely that the site still fits within the template, and a ready-made platform is a reasonable choice.
A ready-made platform (website builder or CMS, such as Webflow, WordPress, Shopify) is suitable when you need to launch quickly and keep initial costs low. It also allows non-technical users to edit content later. This is a reasonable default choice for most small and medium-sized businesses.
When a pre-made is sufficient
You can confidently use the pre-built platform in the following cases:
- A company introduction website presents services and product catalogs in a conventional structure.
- A campaign landing page for a specific advertising campaign.
- Basic sales according to common shopping flows, without complex product configurations.
- A blog or content page that the editorial team needs to post without technical support each time.
In these cases, a ready-made platform is not a second choice; it is the right choice. The budget saved can be invested in content, images, and optimizing conversion flows (the process of customers moving from viewing to purchasing or contacting). This approach produces much more tangible results than building a complex technical system.
When you need to build separately
Custom building (meaning the technical team writes code from scratch without relying on intermediary platforms) is only worth investing in when at least one of the following conditions is met:
- A flow for specific product configurations or transitions that no existing platform supports.
- Deep integration with internal systems: ERP (enterprise resource planning), CRM (customer relationship management), or real-time data.
- The threshold for page load speed and user experience is very strict, which the pre-built platforms cannot meet due to their architecture.
- The scale of content is very large, for example, tens of thousands of pages requiring complex display logic.
Custom builds offer complete control and allow for clean HTML (the language of web structure) to be written exactly as desired. This benefits technical SEO (optimizing for search engines). In return, you need a capable technical team. The budget will also be higher both during development and maintenance after delivery, and the implementation time will be longer.
Create a custom solution: Complete control, maximum flexibility, tailored to specific needs. In return, it requires ongoing technical expertise and incurs higher costs in both the development and operational phases.
Common errors
Sinh Vũ sees two recurring mistakes at two opposite ends:
- Create a custom solution too early: The needs still fit within a template, but a custom solution is chosen because it sounds more sophisticated or because the consultant did not ask in detail. The result is wasted money and time without creating a real advantage.
- Forcing a pre-built platform to work beyond its capabilities: attempting to achieve specific features by patching together multiple plugins. The system becomes fragile, slow, and difficult to maintain in the long run.
- Skip the risk of vendor lock-in: choosing a closed platform without considering whether data and designs can be transferred if you want to switch.
Sinh Vũ's viewpoint
Sinh Vũ clearly separates three levels for clients to choose according to their actual capacity:
- DIY with available templates: Suitable when the budget is very tight and you can manage operations yourself. Accept limitations on interface customization.
- Hire to work on a pre-existing foundation: A central choice for most businesses. Money is invested in design, content, and optimizing conversion flows, rather than in foundational technology.
- Custom design and assembly: For when the website is the main closing channel and the page needs to perform tasks that templates cannot achieve. This is a long-term investment, not a low initial cost.
The foundation is a means, not an end. The right question is what the site needs to accomplish, not what the site is built with.
Practical experience, Sinh Vũ Studio
You do not need to know technical details to make the right decision. You just need to describe what the site needs to do, clearly and specifically. From there, the choice of platform will become apparent.
For brand websites, SCMS is Sinh Vũ's solution for the middle ground: not building custom from scratch, but using brand-specific blocks that are locked in place, so they won't deviate even after multiple edits. If you need a shopping cart and online payment, or want to drag and drop to rearrange the layout every month, a platform specifically designed for that will be more suitable.
Decision checklist
Topic: When a ready-made platform is sufficient and when a custom build is necessary. Sinh Vũ guide, sinhvu.com
Tick each item that applies or that you can already answer, then print or save as PDF to take with you.
If you have marked most of the signs above, this is the time to discuss in more detail. Sinh Vũ can help you review and propose a direction.
References
WeWeb: Best No-Code Website Builder Platforms 2026; Amply: Best No-Code Website Builders 2026. The analysis section and consulting perspective are based on Sinh Vũ Studio's practical experience.
Frequently asked questions
Is Webflow or WordPress a custom build?
No. Webflow and WordPress are both ready-made platforms, meaning you are using an existing system and customizing it. A custom build means the technical team writes code from scratch, without relying on any intermediary platform. Most small and medium-sized businesses do not need to go that far.
How much more expensive is custom building compared to pre-built?
Sinh Vũ does not provide market comparison figures because they vary greatly depending on the team and features. What you need to know is that custom builds are more expensive, both during the development phase and in the maintenance phase after delivery, because every change requires technical intervention. A ready-made solution allows non-technical users to edit content themselves, which is a practical operational advantage.
If starting with a pre-built design and later wanting to switch to a custom build, is that allowed?
Yes, but it usually has to be rebuilt from scratch rather than converted directly. That is why Sinh Vũ advises you to clearly define what the site needs to do from the beginning, to choose the right threshold and avoid paying twice.
This article is for reference. The scope, pricing, and specific commitments of Sinh Vũ are detailed in the proposal and signed contract.