Does Sinh Vũ take on small projects?

Sinh Vũ serves individuals, SMBs, and enterprises. Each tier has a suitable scope and approach. Small project clients often start with a 30-minute Coffee chat (free) or a Workshop/Audit to get the right direction before investing.

Self-brief, or do you need Sinh Vũ to assist with the brief?

Both are fine. Door 01 Detailed form for you if the scope is clear. Door 02 Chat with Sinh Vũ (5 minutes, AI asks the right questions) for you if the scope is unclear and needs consultation first.

How long from brief to the first deliverable?

Sinh Vũ responds within 24 hours. Detailed proposals within 48–72 hours. The first deliverable depends on the scope, typically 2–6 weeks from contract signing and deposit receipt.

What industries does Sinh Vũ work in?

300+ projects across 16 major sectors: F&B, Cosmetics, Fashion, Real Estate, Technology and SaaS, Manufacturing, Education, Healthcare, Finance, Travel, Agriculture, B2B professional services, and other sectors.

Is there a contract and confidentiality?

Yes. Every project signs a standard service contract from Sinh Vũ Studio, including clear confidentiality (NDA) and intellectual property terms. Briefs are stored separately, accessible only to the responsible team.

How much more expensive is building separately compared to using a template?

Sinh Vũ does not provide market comparison numbers because they vary significantly depending on the team and features. What you need to know is that building something custom is more expensive both during the creation phase and the maintenance phase after delivery, as every change requires technical intervention. Pre-built solutions allow non-technical users to edit content themselves, which is a practical operational advantage.

Pre-built platform or custom build: choosing the right one for your website

Quick summary

Pre-built foundations (website builders or existing CMS like Webflow, WordPress, Shopify) are sufficient for most basic promotional and sales websites, as long as the tasks remain within common templates. Custom builds should only be considered when the site needs to perform a task that templates cannot handle: specific conversion flows, internal system integrations, very strict speed thresholds, or very large content scales. Do not build custom just because it sounds more sophisticated, as the costs and time invested will not be proportional if the actual needs fit within a template.

Quick comparison

You should choose this direction when

introduction website, campaign landing page, basic sales
need to launch quickly at low cost, team not technically skilled

Not needed when.

specific conversion flows or deeply integrated systems
strict speed or scale of tens of thousands of pages

This is a question that Sinh Vũ frequently hears, and the answer is mostly: pre-built is sufficient. It’s not that custom builds are inferior, but because most small and medium-sized business websites do not actually need to go beyond 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 "what platform should we use?", ask: what does this page need to accomplish that common templates cannot? If you do not have a clear answer to that question, it is likely that the page will still fit within a template, and a pre-built platform is a reasonable choice.

Pre-built foundations (website builders or CMS, meaning content management systems, available like Webflow, WordPress, Shopify) are suitable when you need to launch quickly, keep initial costs low, and allow non-technical users to edit content later. This is the 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 pre-built platform is not a second choice; it is the right choice. The budget saved can be allocated to content, imagery, and optimizing the conversion flow (the process customers go through from viewing to purchasing or contacting), which yields 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 building provides complete control and allows for clean HTML (the structure language of websites) according to your preferences, which benefits technical SEO (optimization for search engines). In return, you need a capable technical team, a higher budget for both building and maintaining after handover, and a longer implementation time.

Create in advance: Quick launch, low initial costs, and non-technical users can make adjustments. Limited in deep customization, difficult to scale for very high traffic, and there is a risk of vendor lock-in (i.e., difficulty switching if you want to change platforms later).

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:

Using 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 understand the technical details to make the right decision. You just need to clearly and specifically describe what the page needs to do. From there, the choice of platform will become apparent.

The tool brings back.

Decision checklist

Topic: When a ready-made platform is sufficient and when a custom build is necessary. Sinh Vũ guide, sinhvu.com

0 more than 6 items

Select each item you find appropriate, then print or save as PDF to take with you.

Sign indicating that you should take action

introduction website, campaign landing page, basic sales
need to launch quickly at low cost, team not technically skilled

Questions to answer before deciding

What does your page need to achieve that an existing platform hasn’t done?
Is Webflow or WordPress a custom build?
How much more expensive is custom building compared to pre-built?
If starting with a pre-built design and later wanting to switch to a custom build, is that allowed?

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 pre-built platforms, meaning you are using an existing system and customizing it. 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 to that extent.

How much more expensive is custom building compared to pre-built?

Sinh Vũ does not provide a market comparison number because it varies greatly depending on the team and features. What you need to know is that building something custom incurs higher costs both during the creation phase and after delivery, as every change requires technical intervention. Pre-built solutions allow 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 often requires starting over instead of directly converting. That’s why Sinh Vũ advises you to clearly define what the page needs to do from the beginning, to choose the right threshold and avoid paying twice.