Custom website: how much it costs and when it pays off.
"Custom" is the most sold and least explained word in the industry. What a custom website is, what it really costs, when it beats a standard solution and when it is money wasted.
A custom website is designed and coded for the specific case, with no pre-made template dictating what is possible. It costs more than a standard solution because it is built from zero: projects that require bespoke code (web apps, platforms, integrations) start from €5,000, while a standard brochure site starts at €1,500 and a subscription at €49/month. It pays off when the site needs specific functionality, integrations with company systems or its own business logic; it does not pay off when the goal is presenting services and receiving enquiries, because then paying for custom is paying for complexity that brings nothing.
| Need | The right answer |
|---|---|
| Present services and receive enquiries | Standard site: €1,500+ or subscription €49+/month |
| Sell online with a normal catalogue | Standard shop: €3,000+ or Commerce €199/month |
| Own functionality (internal bookings, client portal) | Custom: €5,000+ (web app) |
| Integration with company systems (CRM, invoicing) | Custom or automation |
| One-off campaign with a single goal | Landing page: €800+ |
Swipe the table sideways →
The rule: custom is paid for when the business logic does not fit a standard solution, not for status. The price bases per project type are in the pricing guide.
What a custom website is
A custom website is designed and programmed from zero for the concrete problem: the design does not come out of a template, and the functionality is written for the case. It is the opposite of two standard solutions that are also legitimate: sites built on platforms (WordPress, Wix, Shopify) and subscription sites with fixed plans.
Custom web development covers both sites and web apps, which are applications running in the browser: client portals, internal booking systems, platforms with member areas and their own rules. The difference is not beauty; it is logic. Whenever the question is "what if my business worked like this?", the answer is code written for it.
How much a custom website costs
Projects that require bespoke code start from €5,000 on this site, and the value rises with the complexity of the logic, not with the number of pages. What pushes it up: integrations with existing systems (CRM, invoicing, ERP), authentication and member areas with different roles, proprietary calculations or business rules, and multiple languages or markets. What should not push it up: simple content pages, which in any project are baseline work.
For comparison, the standard alternatives: brochure from €1,500, shop from €3,000, subscription from €49/month. And there is a middle ground many people ignore: a well-built standard site with one or two custom features costs a fraction of a fully custom build and solves most "special" cases.
In custom projects, the quote must detail phases and deliverables with even more rigour than usual, because scope is the variable that controls cost; the website quotes guide shows what the document must contain.
When it pays off (and when it does not)
Custom pays off when there is proprietary logic:
- Internal processes the site must execute: bookings with company rules, fleet management, real-time stock control.
- Integrations: the site talks to the existing CRM, invoicing or reservation system, without copy-pasting between systems.
- Member areas with rules: customers, staff and managers see different things, with permissions.
- Competitive advantage through functionality: the way the site works is part of what the customer pays for.
It does not pay off when the goal is presence and contact. A well-made standard brochure site presents services, receives forms and appears on Google just as well as a custom one, for less than half the value. Paying for custom code "to have something different" is buying complexity: complexity costs at build time, pays again in maintenance and charges you in evolution speed.
How long a custom project takes
Longer than a standard site, and the reason is designing the logic, not writing the code: a web app typically takes 8 to 16 weeks, against 2 to 3 for a landing and 4 to 6 for a brochure site. What most influences the timeline is definition: custom projects that arrive at the developer with clear business rules move faster than small projects with requirements changing every week. The detail per phase is in the timeline guide.
How to decide between standard and custom
Three questions settle the decision:
- Is there any functionality no standard solution can do? If the answer is "I do not know", the answer is no (for now). List the three business processes the site would have to execute; if they fit in a form and a simple database, it is standard.
- When does the extra cost pay itself back? If the custom feature saves hours of work every week or unlocks revenue, the math closes; if it is "prettier" or "more ours", it does not.
- Who maintains it? Custom code is an ongoing responsibility: updates, fixes and evolution. If the company does not want that responsibility, a subscription with maintenance included or a simple standard site is the honest choice.
Whoever hires custom development applies the usual criterion: proof of work in the same technology, scope in writing, code ownership defined in the contract. The choosing a provider article applies here in full.
Describe the logic, get the right bill.
Describe what the site must do and receive a quote with phases, deliverables and published prices. I reply in under 24 business hours.
Request a quote, no commitment