Custom web design

When custom is worth it — and when it is not

Template builders are good tools, provided your content happens to fit the shape they assume. Custom work earns its cost in a few specific situations: your products carry a lot of specification that needs structuring; your service needs explaining rather than listing; your brand has a defined visual language that a template's default corners and shadows would quietly destroy; or you have been locked into a platform before and do not want your assets on someone else's server again.

If you need a five-page brochure site and the content is not settled yet, a template is genuinely better value and we will tell you so. Custom pays off when there is complexity to carry — with no complexity, that value goes unused.

How we work

1. Establish what the site must achieve

Every project starts there. Getting an overseas buyer to actually send the enquiry. Making a thirty-year-old firm legible to younger clients. Turning a personal style into something people remember. Without that answer there is no standard to judge the design against, and revisions become endless matters of taste.

2. Information architecture before visuals

We sort the content into three lists: what every visitor must see, what they need to be able to find, and what can simply go. Most rebuilds lose about a third of their pages at this step — not because that content was bad, but because it was diluting the message that matters.

3. Design by subtraction

We treat whitespace as a method, not a style. Strip the pop-ups, carousels and decorative motion, and let typographic rhythm, proportion and eye-path do the communicating. That is why our work looks quiet — every decision went into making the content easier to read.

4. Build on a static architecture

We use static site generation rather than WordPress. Pages are produced at deploy time, so no visitor waits on a database round trip; no plugin ecosystem means no plugin vulnerabilities; and the content sits in the HTML, so crawlers and generative search read every word without waiting on JavaScript.

5. Handover and long-term care

You receive the source code, a private database and your own admin area. If you would rather not run a server, annual licensing and management covers upkeep, certificates and routine content changes.

What "no template" actually changes

• Speed — builders ship framework code you never use. Custom ships only what this site needs.
• Ownership — stop paying a subscription platform and the site goes away. With the code in your hands, that cannot happen.
• SEO structure — heading hierarchy, structured data and URL rules follow the search strategy, not the template's limits.
• Maintainability — when requirements change you edit your own code instead of working around a theme.

Two plans

Blank Pro — from NT$ 80,000. For well-defined projects that need to ship quickly: professional service firms, industrial brands and personal brands.

Blank ProX — from NT$ 180,000. For multi-brand or multi-location businesses, sites with large structured catalogues, or teams needing strict permissions and audit logs.

Both include full source code and a private database, and both can add annual licensing and management. The comparison is on the home page — you should not have to ask twice to learn roughly what it costs.

Common questions

What is included?

Discovery, information architecture, visual design, front-end build, responsive work across breakpoints, baseline SEO setup and deployment. Domain and hosting fees, photography, copywriting and translation are quoted separately and itemised up front — never added afterwards.

How long does it take?

Four to eight weeks for a typical Blank Pro project, depending on page count and how fast content arrives. In practice the usual delay is not design or code — it is waiting on copy and images, so we hand you that list at kick-off.

Can we edit it ourselves?

Yes. You get your own admin area; changing text and swapping images is about as hard as editing a spreadsheet. Structural changes can go through the annual management plan.

Do we own the code?

Yes. Source code and database are handed over at completion — back it up, move it, or give it to another team. That is the fundamental difference from a subscription platform.