Table of contents
Custom website development is often quoted as one lump sum starting at six figures, yet fewer than a third of the modules in a typical site need to be written from scratch. Split modules by nature — customise what must be customised, use existing components elsewhere — and the same budget covers twice the scope.
1. You Are Buying Fit, Not Code
The problem with templates is fixed structure. Your business logic gets forced into someone else's frame: parameter tables that do not fit, case studies that cannot be grouped by industry in two levels. Custom work solves structural fit, not aesthetics. If your structure matches a general template, customisation is unnecessary.
Anything tied to a unique process — showing progress by project stage, service points by region, different pricing by customer type — is where templates struggle and where investment pays.
2. Four Module Types, Four Priorities
| Module type | Examples | Customise? | Reason |
|---|---|---|---|
| Display | Home, about, banners | No | Templates suffice |
| Content | News, cases, product library | Partly | Fields and filters need fit |
| Interaction | Enquiry forms, configurators | Yes | Directly affects conversion |
| Data | Analytics, lead routing, CRM | Yes | Touches internal workflow |
Enterprise website budgets should prioritise interaction and data. A beautiful homepage with a three-field form nobody follows up on is wasted spend. Most companies' real pain is what happens after a lead arrives, and templates cannot help there.
3. How Detailed the Requirements Doc Should Be
A document that can start work must include: page inventory and hierarchy, module composition per page, field definitions with required and multilingual flags, roles and permissions, third-party integrations, and acceptance criteria. Skip field definitions and you will revise during development.
Custom website development delays usually come from changing requirements, not technical difficulty. Set a freeze date and a change process in the contract: after the freeze, new requests go through a change order with separate pricing and scheduling.
4. Reading the Quote
| Pricing model | Typical range | Fits | Risk |
|---|---|---|---|
| Per page | 800–3,000 CNY | Simple display sites | Complex pages excluded |
| Per person-day | 1,200–2,500 CNY | Unclear requirements | Total cost floats |
| Module package | 30k–150k CNY | Clear requirements doc | Boundaries must be fixed |
Module packages plus change orders work best. Pure day rates drift with every change; pure page rates turn complex interactions into empty shells.
5. Five Pre-Launch Checks
Layout on three mainstream phones. Form submission producing an email or SMS notification and a visible backend record. Compressed images with first paint under three seconds. Per-page title, description and keywords editable. Analytics and sitemap in place. Fail any of these and the polish gets rebuilt after launch.
6. FAQ
How long does it take? Four to six weeks for a display site with clear requirements; eight to twelve with interactive tools or system integration.
Can we start with a template and upgrade later? Possible, but structural changes approach a rebuild. Use it only for validation.
Should we buy the source code? Yes. Specify source and database delivery so switching vendors later is not blocked.
Related
- See also: six variables behind the quote
- See also: content assets and update cadence
GrowLab focuses on integrated content marketing, offering brand strategy, website development and search marketing (SEO/GEO) as a full-chain service. Contact us for an assessment of your own promotion plan.
Need a professional growth plan?
Add our WeChat for a tailored strategy and annual quote.
Contact Us