"Template or custom?" sounds like one decision, but it is really three: which platform runs the site, how it looks, and whether it needs functions the platform does not already provide. Many businesses are best served by a good theme on an established platform. Others need a few targeted custom parts. A smaller number have requirements that justify building most of the site from scratch. The right choice depends on what the site has to do, who will edit it and who will maintain it, more than on how unique it looks.
This guide is for Singapore business owners deciding how to approach a new website or a replacement. For prices, see our website cost guide. This article is about choosing the approach.
Three separate decisions
The platform is the system that runs the site and gives you an admin area: WordPress, WordPress with WooCommerce (an ecommerce plugin for WordPress) or Shopify, for example. It handles things like editing pages, managing products, taking orders and storing customer accounts.
The design is how the site looks and how pages are laid out. A theme or template is a ready-made design for a platform. A custom design is created for your business, then built on the platform or from scratch.
The functionality is what the site does beyond showing content: booking rules, product configurators, member areas, integrations with other systems. Platforms provide a lot of this themselves or through plugins and apps. Where standard features and suitable extensions fall short, the options include targeted custom development, another platform or a different approach to the requirement.
These decisions mix in different ways:
| Approach | Platform | Design | Custom functionality |
|---|---|---|---|
| Theme on a platform | Existing platform | Ready-made theme, adjusted to your brand | None or very little |
| Customised platform | Existing platform | Custom design or heavily adapted theme | Some targeted custom features |
| Custom frontend on a platform backend | Existing platform behind the scenes | Fully custom | Custom frontend features |
| Fully custom build | Built for the project | Fully custom | Built for the project |
Two points follow from this. A customised WordPress or Shopify site is still a WordPress or Shopify site, with that platform's strengths and limits. And a custom design does not automatically mean custom backend development. A unique-looking site can run entirely on standard platform features.
When a theme is enough
An existing theme is often the sensible choice when:
- the site uses common layouts, such as a home page, service pages, a blog, a contact page or a standard product catalogue
- the content is straightforward and your team will mainly update text, images and products
- the features you need are already supported by the platform or by well-maintained plugins and apps
- getting online quickly matters more than a distinctive layout
A theme is not automatically slow or unprofessional. Quality varies a great deal between themes, and a well-chosen one, set up with your own branding, photography and copy, can look polished and perform well. Speed problems on theme-based sites can come from what has been added on top, such as too many plugins or apps and oversized images, as much as from the theme itself. Our guide to web application performance explains how to find the actual cause.
It also helps to separate visual uniqueness from business value. A distinctive layout can strengthen a brand. For many businesses, though, what matters more is whether customers can find what they need, trust the business and complete what they came to do. Clear content, good photos and an easy enquiry or checkout process often matter more than a one-of-a-kind design.
When targeted customisation is worthwhile
Targeted customisation keeps the platform's useful parts (its editor, product management, checkout, user accounts and its own updates) while changing the parts that do not fit. It is worth considering when:
- a key page or interface needs a layout or interaction the theme cannot provide, such as a product builder or an interactive pricing tool
- your business has a specific workflow the platform does not support out of the box
- an existing plugin or app does the job poorly, or adds more than you need
A small example: for a patisserie, we wrote a focused script that populates stock information and available pickup days. That kind of work solves a specific problem without replacing anything.
A larger form of customisation is a custom frontend connected to an existing platform's backend, sometimes called a headless setup. We have built custom frontends on top of WooCommerce backends, where the customer-facing side of the store is custom-built and WooCommerce continues to run the backend. This can suit businesses that want frontend features that are easier to build outside a theme. It also adds work: the frontend has to be built and maintained separately, and some features that come free with a theme may need rebuilding. Our website cost guide covers how this affected one retailer's project.
How customisations are made matters for later maintenance. On WordPress, when modifying an existing theme's code, changes belong in a child theme or a custom plugin, because edits made directly to the theme's files can be lost when it updates. The WordPress developer documentation gives exactly this reason for child themes. On Shopify, for themes covered by Shopify's update process, code edits are carried into a theme update only when they do not conflict with it; otherwise they have to be reapplied by hand, according to Shopify's help centre. A developer who documents their changes makes these updates far easier.
Sometimes a small amount of custom code can replace a plugin or app, as in the Shopify example further down. Each replacement is then code someone has to maintain, so the decision should weigh that against what the app provided.
When a fuller custom build is justified
A largely custom build makes sense when important requirements cannot be met sensibly through an existing platform, even with customisation. For example:
- The core of the site is a business process. Bookings with complex rules, customer portals, multi-step approvals or several user roles with different permissions are application features. Bending a website platform to handle them can cost more and work worse than building them properly. Our guide to custom web application development covers these projects.
- A platform restriction blocks something essential. Platforms limit what can be changed. Shopify, for instance, makes checkout UI extensions in the information, shipping and payment steps of checkout available only on Shopify Plus, although some other checkout customisations are available on lower plans. If a specific checkout change is essential, the options are a plan upgrade, a different platform or a custom build, and each has its own cost.
- The data or integrations do not fit the platform's model. If the site has to work closely with internal systems in ways the platform's structure fights against, a custom build can be simpler overall.
Custom does not automatically mean better. A custom build does not produce better search rankings, easier integrations, greater scalability or lower running costs by default. Those depend on how it is built and maintained. It does mean you take on more: an editing interface has to be built or chosen, every required feature has to be provided, integrated and tested, and your developer becomes responsible for the custom code and its dependencies. Every approach needs someone clearly responsible for maintenance. A WordPress site, for example, still needs its core, theme and plugins kept up to date, and who does that depends on your hosting and support arrangements.
Sometimes the best recommendation is no custom development at all. A tuition company once asked us for custom accounting software. When we looked at what they needed, the real requirements were control over invoice templates and line-item units, so we recommended Xero or a similar accounting package instead.
Practical trade-offs
| Factor | Theme on a platform | Customised platform | Fully custom build |
|---|---|---|---|
| Initial effort | Usually the least | Depends on what is customised | Usually the most |
| Content editing | Platform's familiar editor | Platform editor, plus any custom parts | Depends on the editing interface built or chosen |
| Ongoing updates | Platform, theme and plugin updates | The same, plus checking custom code after updates | Your own code and dependencies |
| Integrations | Plugins and apps for common tools | Plugins plus custom connections | Built as needed, then maintained by you |
| Platform restrictions | Fully applies | Fully applies to the platform parts | More control over your own code; connected platforms and services still impose limits |
| Developer handover | Many developers know the major platforms | Depends on how well customisations are documented | Depends heavily on code quality and documentation |
Pay attention to these two rows: Content editing is easy to overlook during design, but it is what your team lives with every day. Ask to see what can be edited before approving any approach. Developer handover matters because you may change developers one day. A site on a major platform with documented customisations is easier for a new developer to take over than a custom codebase with no documentation, although a well-documented custom build can be handed over cleanly too.
Assess your current site before replacing it
If your current site feels limiting, find out exactly why before paying for a replacement. Common complaints often have narrower causes:
- "The site is slow." Measure it and find the cause first. A client came to us with a Shopify store loaded with apps. We removed the ones that were not doing anything useful and replaced some others with simple custom code, which cut unnecessary work from the storefront. Optimising the existing store was better value for the client than a rebuild.
- "It's hard to edit." The problem may be how the theme or page builder was set up, or how content is structured, more than the platform itself. A better setup or some training can sometimes solve it.
- "It looks dated." A redesign on the same platform may be enough, keeping your content, URLs and integrations in place.
- "It can't do what we need." Check whether a maintained plugin, an app or a targeted custom feature covers the gap before replacing everything.
An assessment shows what you are really working with, and whether the problem is the approach or how it was carried out.
Questions to ask before approving a custom build
Requirements
- Which specific requirements can the existing platform not meet, even with customisation?
- Which parts will be custom, and which will use standard platform features?
Editing and daily use
- How will our team edit pages, products and other content?
- Can we see the editing interface before launch?
Maintenance
- Who applies security updates and fixes, and how are they handled after launch?
- What happens to custom features when the platform or its plugins update?
Ownership and handover
- Will we own the code and have full access to hosting and accounts?
- How will the work be documented so another developer could take over?
Frequently asked questions
Will a custom website rank better on Google?
Not automatically. Search performance depends on content, site structure, technical setup and speed, and all of those can be done well or badly on a theme or a custom build.
Can I start with a theme and customise later?
Yes, and it is a common path. Starting with a well-chosen theme lets you launch, learn what customers actually use and then customise the parts that matter. Choosing a reputable theme and documenting any changes keeps later customisation easier. Whether WordPress or Shopify suits you better is a separate question, which we plan to cover in WordPress vs Shopify for Singapore businesses.
Not Sure How Much Customisation Your Website Needs?
The useful starting point is a list of what the site must do, who will edit it and which systems it has to connect to. From there, we can assess which approach fits.
retroXpect can review your requirements, or your existing site, and recommend whether a theme, targeted customisation or a custom build fits best, then build it on WordPress, WordPress with WooCommerce, Shopify or a custom stack as appropriate. Message us on WhatsApp with what your site needs to do, and we will suggest the approach we would take.
