Table of contents
Two quotes for a premium custom website can differ several times over, and the gap is rarely page count. It is the completeness of what is handed over. One project delivers a set of pages that look right; the other delivers a system that can keep extending. Three years later only the second can add a new section without a redesign.
1. Where the Money Goes
Planning and information architecture: turning the business into sections and customer questions into pages.
Visual system: not a homepage mockup, but a reusable set of rules.
Front-end engineering: components, responsive behaviour, performance and compatibility.
Back end and content model: field design, permissions, APIs.
The last three drive cost. A project with visual work but no system needs everything redrawn at the first redesign.
2. Four Deliverables
| Deliverable | Content | Test | Later value |
|---|---|---|---|
| Design system | Colour, type scale, spacing, grid rules | A new page can be built from the rules | Redesign without rethinking |
| Component library | Buttons, cards, forms, navigation | Components documented with states | Faster development |
| Multilingual architecture | Language packs, routing, sync method | A new language needs no structural change | Smooth market expansion |
| Performance budget | First-screen asset limits, image rules | Explicit numbers and a test method | Traffic growth without slowdown |
The essence of premium custom work is converting a one-off design into reusable rules. These four items are the rules.
3. Acceptance Must Be Measured
Visual: compare screen by screen against the approved design, with a stated tolerance.
Performance: specify metrics and test conditions, including an upper bound for mobile first-screen load on an agreed connection.
Compatibility: list the browsers and devices in scope and confirm each with a screenshot.
Content: confirm section structure, fields and sample content, and whether the client can publish a new article unaided.
Release the final payment after all four. Verbal approval has no standing later.
4. Two Items Usually Forgotten
Multilingual: many projects build it as "duplicate the site and translate", producing two structures maintained separately. Build the model once and distribute across languages.
Accessibility: image alt text, form labels, keyboard operability, contrast. None affect the visual impression, all affect crawling and usability — and it is exactly what nobody specifies at acceptance.
This is the dividing line between a premium custom build and a theme: a theme meets today, a custom system has to meet the year after next.
5. How to Negotiate These Four
Ask the vendor to respond to the deliverable list item by item rather than presenting mockups and a page count.
Attach this table to the contract as an annex, with each item written as a verifiable condition. A team willing to sign that annex usually delivers it too.
6. FAQ
How long does it take? Eight to twelve weeks for a typical corporate site; sixteen or more with multilingual support and system integration. Sign-off and content preparation consume more than expected.
Can it be built in two phases? Yes. Phase one covers structure and the design system; phase two rolls out pages and content. The rules must be fixed in phase one.
With a limited budget, which deliverable comes first? The design system and component library, because they set the cost of every page that follows. Multilingual can wait for the market entry.
Related
- See also: deciding whether a redesign means rebuilding
- See also: a website acceptance checklist
GrowLab focuses on integrated content marketing, covering brand strategy, website development and search marketing (SEO/GEO). 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