A $200 Webflow theme and a $15,000 custom build, both figures ex GST, can look almost identical on launch day. Both have a homepage, a product grid and a contact form that submits to an inbox. The difference shows up six months later, in the numbers that actually decide whether the site is working: enquiry rate, average order value and how much it costs to add a new product line without calling in a developer to rebuild half the page.
Templates are not inherently bad. A $200 to $2,000 template can be the right call for a business that needs a functional web presence and doesn't need the site to do heavy commercial lifting. The trouble starts once a business that actually needs the site to convert, scale or hold its own visually against competitors treats a template as good enough simply because it launched on time.
The decision comes down to commercial return more than preference. Custom web design costs more up front, and that extra spend needs to earn its keep somewhere: in conversion rate, in how fast the business can add functionality, or in how the site reads against the two or three competitors chasing the same customers. Our companion guide to custom website design covers the broader case for building custom, including return on investment and where the definition gets blurry. This piece stays on the comparison: what a template gives you, where it starts to cost more than it saves and when the custom premium is worth paying.
What a template actually gives you
A template gives you speed and a fixed cost. You're buying a pre-built structure, sections, page layouts and interactions someone else designed for a generic version of your industry. Design choices, content structure and functionality are all bound by what the template's original author anticipated for a hypothetical average business, rather than by what yours actually needs to say or sell.
On Webflow, that means a marketplace theme bought once, with a fixed set of page templates and a CMS collection structure built around a generic set of content types: blog posts, a handful of service pages, a simple portfolio grid. On Shopify, it means a theme from the Shopify Theme Store or a marketplace like Out of the Sandbox, built on a fixed set of Liquid templates and sections, with product, collection and cart pages following whatever structure the theme's original developer chose.
For a simple business with straightforward requirements, low customer complexity and no real ambition to look different from the next site in the category, that's a reasonable trade. The site loads, it looks professional and it costs a fraction of a custom build, which matters for a business still validating its offer or working within a tight budget in the early stages. Our guide to website design costs in NZ sets out where that budget lands for each route.
Where templates start to cost more than they save
The limitations show up as the business grows, and they rarely show up as something obviously broken. A template built for a generic audience doesn't account for your specific customer journey, so conversion suffers in ways that are hard to diagnose because nothing has technically gone wrong. The page loads. The form submits. The numbers are just worse than they should be, and a small gap in conversion rate is easy to miss without measuring it directly.
Adding a custom feature to a templated site means working against the template's assumptions instead of with them. A Shopify template built around single-variant products turns a wholesale pricing tier or a multi-tier discount structure into an expensive detour: a third-party app bolted on top, plus custom Liquid overrides so the theme's product and cart pages display it correctly. What should be a two-week addition becomes a project in its own right.
The same pattern shows up on Webflow. A theme's CMS collections are built around the content types its author expected: blog posts, team members, a simple case study grid. Adding a different kind of content type, a resource library with filterable categories, a multi-location booking system, means restructuring collections the theme was never designed to hold, then rebuilding every page template that touches them.
Templates also carry the weight of every feature the theme supports, whether your site uses it or not: CSS and JavaScript for a slider you never use, a filtering system built for a catalogue five times the size of yours, animations nobody asked for. That extra weight slows the page down, and page speed is one of the less visible inputs behind why a website stops ranking. Then there's the sameness: if three competitors in your category are running variations of the same popular theme, your site looks like theirs, and in a category where visual differentiation drives trust in the first five seconds, that cost shows up in lower enquiry rates and lower average order values, even when every individual page looks fine.
A conversion gap like that compounds every month it goes unaddressed. We've written more on what that actually costs a business in the opportunity cost of a bad website.
Custom on Webflow versus custom on Shopify
Custom means something slightly different depending on the platform, because the constraints you're building around are different too.
A custom Webflow build starts from a blank canvas rather than a theme file. The CMS collections get structured around your actual content: how your case studies, locations, products or team profiles actually need to be organised, rather than how a theme author guessed a generic business would organise them. Interactions and animation get built to match your brand rather than dropped in from a template's preset library, and adding a new content type later means extending a system built to be extended, rather than fighting a structure that was never meant to hold it.
A custom Shopify build runs into a different set of constraints, because Shopify themes carry more commercial logic than a typical Webflow theme: checkout behaviour, variant and inventory handling, discount rules. A template theme handles straightforward single-variant retail well. It gets harder once the catalogue needs wholesale pricing tiers, bundling, subscription products or a connection to an existing ERP or freight system, because a theme's checkout and cart logic wasn't built with that complexity in mind. We scope and manage integrations like that rather than build the technical connection ourselves, since that sits with the relevant app or platform vendor, but a custom build is what gives the site room to hold the connection properly. Businesses at that end of the complexity spectrum are better served by a custom build on Shopify Plus or a properly scoped ecommerce build, where checkout customisation and app integrations get planned in from the start instead of retrofitted later.
The tradeoff runs in different directions too. On Webflow, the ceiling is mostly structural: CMS fields, layout options, animation. On Shopify, it's mostly commercial: what the checkout and cart can actually handle once the product range gets more complicated. Which ceiling your business is closer to hitting says most of what you need to know about whether custom is worth paying for right now.
What a custom build buys you
A custom build starts from your business rather than from a theme. The information architecture reflects how your actual customers think and buy, instead of a generic best-guess navigation structure borrowed from a theme. The CMS gets configured around the products, services, locations or case studies the business actually has, instead of the generic set a template assumed it would have.
It also scales properly. Adding a new content type, a new integration or a new page template later means extending a system built to be extended, rather than working around one that wasn't. The gain is most visible a year or two after launch, when the business has grown and the site either grows with it or turns into a list of workarounds the team has learned to live with. Extending that system through ongoing support is simpler too, because it was built to be added to in the first place. Our guide to website maintenance costs covers what that looks like month to month.
The visual outcome matters too, particularly for considered-purchase businesses competing on trust as much as price. A design system built for your brand specifically produces a site that doesn't read like the other three in your category. Slight Twist's Webflow and Shopify build won three CSSDA awards in 2025, including a Special Kudos, on the strength of a design system built around their brand rather than adapted from someone else's theme.
The commercial case shows up in the numbers too. Heritage Saunas launched on a custom Webflow build before a single product photo existed, and now converts enquiries at 4.6% against a 2.7% industry benchmark, generating two to three qualified leads a week with no paid advertising behind it. Clean Collective's custom Shopify rebuild lifted conversion rate by 103% and sales by 28%, in a category where the previous site was already live and technically working. Both builds were structured around how their customers actually buy, instead of around a theme's defaults.
When custom pays off
Custom earns its premium in a few recurring situations. The customer journey isn't generic, so a generic structure costs conversions that are hard to claw back without a rebuild. Brand differentiation is a stated part of the business strategy, rather than an afterthought bolted on after launch. Or the site needs functionality, a configurator, a genuine booking system, a CMS structured around a specific catalogue, that no template reasonably stretches to fit.
Add up a template's limitations over twelve months: lost conversions, workaround fees paid to make a theme do something it wasn't built for and a site that looks like the other three in the category. Set that against the premium on a custom build, and the custom build often works out the cheaper option once those costs are counted properly.
A template still makes sense in a narrower set of cases: an early-stage business validating an offer before committing capital to a considered brand, a budget that doesn't support a custom build yet, or a site whose job is simple enough that a template's constraints never come into play. Website costs in NZ and Webflow pricing both set out what that budget looks like at each end of the range, and freelancer versus agency versus in-house is worth reading before deciding who builds either option, alongside our guide to choosing a website agency in NZ.
Most businesses generating meaningful revenue and competing in a market where the site is a real sales tool land on the custom side of that decision once they measure it properly. The businesses still running templates at that revenue stage are paying for it in a conversion rate they've never measured against what a custom site would return.
Common questions
Is a template ever the right choice for an established business?
Yes, in specific circumstances: a new product line being tested before it earns space on the main site, a short-lived campaign page, or a business still validating a new offer. For a business that's already established and running its website as a serious sales channel, a template's sticker price is often smaller than a custom build's, but the workaround costs and lost conversion add up to more within the first year or two.
How much does a custom website cost compared with a template in NZ?
A template build starts in the low thousands and can be live within a couple of weeks. A custom build costs more and takes longer to plan and design properly, because the site is being built around your business rather than adapted from someone else's. Our guide to website design costs in NZ breaks down where both routes land, and Webflow pricing covers platform costs specifically.
Can a template site be upgraded to custom later, or do I have to start again?
Some elements carry across: content, product data, brand assets. The underlying build gets replaced rather than incrementally upgraded, because a template's CMS structure and page templates weren't built to be extended toward custom functionality. It's closer to a rebuild than a renovation, so it's worth deciding early rather than waiting for the template to become a bigger constraint.
Does a custom website take longer to build than a template?
Yes, because more of the work happens before anything gets designed: mapping the customer journey, planning the CMS structure and deciding what the site actually needs to do commercially. A template compresses that phase by inheriting decisions someone else already made. That extra time on a custom build gets spent on decisions that are hard to undo later: information architecture, CMS structure, how the catalogue or content is organised.
Is custom web design worth it for a Shopify store specifically?
It depends on how complex the catalogue and checkout logic actually are. A straightforward single-variant retail catalogue can run well on a good Shopify theme. Once wholesale pricing, subscriptions, bundling or an ERP connection enter the picture, a custom build or a move to Shopify Plus pays for itself in fewer app workarounds at checkout and less time spent fighting the theme's assumptions about how a product is structured.
How do I know if my current template is limiting conversions?
The clearest signal is friction that shows up consistently at the same point without an obvious cause: a specific product category converting worse than the rest, a form with a high abandonment rate, or visitors bouncing on mobile more than desktop. Our piece on why your website isn't converting works through the common causes. When the answer turns out to be structural rather than content-related, the template's constraints are often the actual bottleneck.
If your site is doing less for the business than it should, we build custom Webflow and Shopify websites for established NZ and Australian businesses that need the site to work harder than a template ever could. Get in touch with the Skyrocket team to talk through whether a custom build is the right call for where your business is now.
