The question comes up in almost every first call with a prospect: "A bespoke website is much more expensive than a WordPress template, isn't it?" The short answer: no, not over three years. The long answer takes a full article, because the reasoning is less intuitive than it seems and many Swiss SMEs budget for their website too short-term.
What follows is a detailed TCO (Total Cost of Ownership) analysis. We compare two real-world paths: on one side, a site built on a ThemeForest or Elementor template, deployed on shared hosting. On the other, a custom-coded site built with a modern stack (Next.js, React, TypeScript). Licence and plugin prices come from the vendors' public price lists (2024). The other amounts are INFUSE estimates, presented as such.
TCO: why the purchase price is not enough
TCO (Total Cost of Ownership) is a concept from corporate finance. It covers all the costs associated with an asset over its useful life: acquisition, operation, maintenance, replacement. A CFO does not buy a machine by looking only at its list price; they factor in training, preventive maintenance, spare parts and end-of-life costs.
Your website is an operational asset and should be costed the same way.
Templates show a very low entry cost (CHF 30 to 80 for the licence), which gives an impression of savings. The real bill builds up elsewhere, in cost lines that most site owners discover too late.
The four categories of hidden costs
Before getting into the figures, here are the four families of expenses that templates systematically generate:
- Recurring licence and plugin costs: the base template is never enough. You need plugins for forms, SEO, security, caching, backups, GDPR cookie consent… Each one has its own annual licence.
- Technical maintenance costs: WordPress and its plugins release updates constantly. Every update can break the site. Maintenance represents a significant amount of monthly work.
- Security and remediation costs: WordPress accounts for 96.2% of the hacked CMSs handled by Sucuri, according to its annual hacked website report. And a hacked site is expensive to put right.
- Forced redesign costs: templates age badly. After 2-3 years, incompatibilities pile up, performance degrades, and a partial or complete redesign becomes inevitable.
Scenario 1: the WordPress/Elementor template
Let's take a concrete, realistic case: a Geneva-based SME buys a ThemeForest template (Avada, Divi or similar) and hires a local webmaster or a small agency to install and configure it.
Year 1: start-up costs
That figure looks reasonable. Now for what comes next.
Years 2 and 3: the maintenance bill
WordPress releases around 3 major versions a year. Every plugin follows its own schedule and publishes its own security fixes. Someone has to track all of it, test, then fix whatever breaks.
The risk of a security incident
Over 3 years, the risk of a WordPress site being hacked is far from negligible. The usual entry points are well known: outdated plugins, themes, and the WordPress installation itself.
Orders of magnitude (INFUSE estimates) for the cost of an incident for an SME:
- Cleaning the site and removing malware: CHF 500 to 2,000
- Restoring from backup (if the backup works): CHF 200 to 500
- Google blacklisting and SEO remediation: potentially weeks of lost traffic
- Reputation and client trust: impossible to quantify
We include a provision of CHF 1,200 over the period in our calculation. It is a calculation assumption, not a measured average.
Performance degradation
This is the least visible cost. Over time, plugins are added, the database fills up with revisions and unoptimised images land on the pages. The site slows down. According to Think with Google (2017), as page load time goes from 1 to 3 seconds, the probability of bounce increases by 32%. A slower site loses prospects.
The partial redesign at the end of the cycle
After roughly 30 months, the verdict is often the same: the template has become too rigid, incompatibilities are piling up, and the client wants to update the design. That leaves three options: a partial redesign (CHF 800 to 2,000), an upgrade to a premium version of the visual builder, or starting over.
We include a partial redesign of CHF 1,500 as year 3 approaches.
Total template TCO over 3 years
And this total excludes opportunity cost: the revenue lost through conversions that never happen because of degraded performance, a mediocre mobile experience or a reputation damaged by a security incident.
Scenario 2: the custom-coded website (Next.js / React)
A bespoke website uses no general-purpose CMS, no third-party plugins and no visual builder. It is written in code to meet the client's business needs exactly, and only those needs.
The initial investment
The upfront investment is higher, that is a fact. For a 6 to 10-page SME showcase site with a contact form, animations and technical SEO optimisation:
We will use the median of CHF 6,260 for the rest of the calculation.
A very different infrastructure
A Next.js site is a compiled JavaScript application that generates static or semi-static pages. There is no database to maintain (unless the project requires one), no plugin to update and no WordPress admin interface to secure. The attack surface is reduced to almost nothing.
The only dependencies are:
- The Next.js framework itself (updated once every 6 to 12 months, handled by the developer)
- Direct npm dependencies (GSAP, Tailwind: stable, few critical vulnerabilities)
- Hosting (Vercel or Infomaniak: no server to administer)
Costs in years 2 and 3
With no plugins, no CMS and no active database, maintenance costs drop sharply.
Performance remains stable over time. A well-built Next.js site does not degrade with use, because there is no build-up of unnecessary data, no plugins being added and no database revisions.
Security: an architecture with no attack surface
Without WordPress, there is no /wp-admin, no xmlrpc.php, no exposable wp-config.php files and no plugin vulnerabilities. The public side of the application is static or near-static. There is no administrator account reachable from the internet to protect.
The risk of a security incident is close to zero for the public part of the site. Security provision: CHF 0.
Total bespoke TCO over 3 years
Head-to-head comparison: the real gap
The bespoke site costs less over 3 years, using cautious assumptions: we have not counted the opportunity cost of degraded performance, nor the internal time the client spends dealing with technical problems.
The break-even point comes at around 30 months. At the end of the first year, the bespoke site has cost about CHF 3,300 more. That gap shrinks by about CHF 1,650 a year thanks to lighter maintenance, then the template's partial redesign, towards the end of the third year, tips the balance.
The factors the tables do not capture
Performance as an ongoing competitive advantage
Google has used Core Web Vitals as a ranking signal since 2021. The "good" thresholds set by Google are:
- LCP < 2.5 s
- INP < 200 ms (INP replaced FID in March 2024)
- CLS < 0.1
A custom-coded site, with no visual builder and no plugins, starts with an advantage in meeting these thresholds. A plugin-heavy site has to fight to get there, then to stay there.
The performance gap shows up in rankings, and then in traffic and prospects.
Adaptability without constraints
With a template, every change has to work around the visual builder's internal logic. An unusual block is only possible if the template allows it. A specific animation depends on a compatible plugin, and a multi-step form needs yet another plugin.
With a bespoke site, a change is a coding decision. If you need a product configurator, a quote calculator or an API integration with your ERP, it can be done, with no workarounds, no third-party plugins and no additional security risk.
Intellectual property and portability
A bespoke website belongs entirely to you. The source code, the assets, the deployment logic: everything is documented and transferable. You are not locked into the ecosystem of a particular theme or builder.
With a template, if the vendor abandons the theme or the visual builder changes its pricing policy, you are in trouble.
The costs missing from the table
Before looking at the exceptions, two categories of cost are still missing from the TCO table, even though they weigh on the business.
Internal time spent managing the site
A WordPress site is supposed to be "manageable without technical skills". That is true in the first few months: the admin interface is accessible and text is easy to edit. But over time, problems accumulate: an update that breaks how a block displays, an image that no longer renders properly on mobile, an error message in the admin console. Every incident takes time: time to notice it, to find the cause, to contact a technician or to look for the solution yourself.
Take an assumption: you or a colleague spend 2 hours a month dealing with website-related problems, and your time is worth CHF 100/h. That adds CHF 2,400 a year (or CHF 7,200 over 3 years) to our TCO calculation without ever appearing on an invoice.
A bespoke Next.js site generates virtually none of this friction. There is no admin interface to monitor, no updates to approve and no plugin errors to diagnose.
The cost of missed opportunities: slow pages = lost clients
The Google/Deloitte study Milliseconds Make Millions (2020) measured the effect of mobile speed across several sectors: on retail sites, a 0.1-second improvement went with 8.4% more conversions.
Conversely, every second of delay has a cost. Take a fictional example: 400 mobile visitors a month and a conversion rate of 1%, so 4 enquiries. If a faster site raised that rate to 2%, you would get 8 enquiries a month without touching your marketing budget. Depending on what a client is worth, the gap over 3 years quickly exceeds the cost of the site, and cost tables do not show it.
When can a template still make sense?
There are cases where a template remains relevant:
- Budget under CHF 2,000: if the budget is very limited and the site is purely informational (one page with an address and phone number), a template can do the job in the short term, provided you know its limits.
- Planned lifespan under 12 months: for an event or a temporary landing page, where TCO has no time to come into play.
- A highly experimental project: to test a business idea without commitment, before investing in something permanent.
In other cases (an SME that wants a professional website that fits its image, converts and lasts), the TCO calculation consistently tips towards bespoke from year 2 onwards.
What INFUSE offers Swiss SMEs
At INFUSE, every site is coded from scratch. No WordPress, no Elementor, no Divi, no page builder. The stack is Next.js 16, React 19, strict TypeScript, Tailwind v4, and GSAP for animations. The code is written for the client and its objectives.
The concrete implications for TCO:
Zero third-party plugins: there is no additional attack surface. Forms, animations, performance optimisations: everything is built into the application code.
Lasting performance: an INFUSE site is built to meet the "good" Core Web Vitals thresholds, and it keeps meeting them over time, because dependencies do not accumulate.
Predictable maintenance: annual maintenance is simple, documented and clearly priced. No surprises from an incompatible plugin update.
Code owned by the client: you receive the complete Git repository. If you want to change provider tomorrow, you can do so without losing your investment.
Before asking whether you can afford a bespoke website, ask whether you want to pay more over 3 years for a weaker result.
If you have a project and would like a TCO analysis tailored to your situation, get in touch. The initial estimate is free and without obligation.
Think in TCO rather than purchase price
The next time you compare the price of a template with that of bespoke development, ask yourself another question: how much will this site cost me in 36 months, all in?
That calculation changes the decision. The template starts cheaper and ends up more expensive. Bespoke starts more expensive and ends up cheaper, with better performance and fewer security risks.
For a Swiss SME that sees its website as a sales tool rather than an expense to keep to a minimum, the calculation clearly favours bespoke.
Frequently asked questions
How much does a WordPress template site cost over 3 years?
In our calculation, CHF 11,071: licences and plugins, hosting, monthly maintenance, a security incident provision of CHF 1,200 and a partial redesign of CHF 1,500.
And a bespoke Next.js site?
CHF 8,380 over 3 years: a median initial investment of CHF 6,260, then around CHF 1,060 a year for hosting, maintenance and minor changes.
When does a template still make sense?
For a budget under CHF 2,000 and a purely informational site, for a planned lifespan of less than 12 months, or to test an idea without commitment.
Sources:
- Sucuri, Hacked Website Annual Report 2023: sucuri.net/resources/reports
- Google Search Central, Core Web Vitals: developers.google.com/search/docs/appearance/core-web-vitals
- Google/Deloitte, Milliseconds Make Millions (2020): study on the impact of load time
- Think with Google, Find out how you stack up to new industry benchmarks for mobile page speed (2017): thinkwithgoogle.com
- ThemeForest pricing 2024: themeforest.net
- Yoast, WP Rocket, Wordfence, Gravity Forms: official 2024 pricing