Method
Custom website vs template: what the difference buys
Custom website vs template is a question about what the site has to do. A template is the right answer for a lot of small businesses: a handful of pages, the business's own text and one clear way to get in touch. A custom build pays when the site has to take bookings or payments, run in more than one language, keep data current, load fast on a phone or be read properly by Google.
Sites in the region are offered for a few hundred euros, and that is a real price for a real product: a template with the business's text in it. If customers' questions can be answered on five pages and the next step is a phone call, a template does the job, and a bigger site that nobody finishes writing does less.
| Template | Custom build | |
|---|---|---|
| Right for | A handful of pages, your own text, one clear way to get in touch | Bookings or payments, more than one language, data that stays current |
| Price | ✓ A few hundred euros in the region | From 900 euros with us, web shops from 1,500 |
| Booking | Layout and flow decided before anyone knew who would book | ✓ Built around who books, like Quadomania's handoff to WhatsApp or Viber |
| Content | Five pages that leave a first-timer's questions unanswered | ✓ Shaped to the content, like vertical video and an FAQ for first-time riders |
| Languages | A language added to a finished design means reworking pages | ✓ Planned from the start, which costs less |
| Speed and Google | Same test: check the page source and load it on mobile data | Not automatically better: a React site had to render every route to real HTML |
What the difference buys
Booking comes first. For Quadomania, a quad-tour operator in Žabljak, the visitor is a tourist comparing two operators on a phone. Booking hands off to WhatsApp or Viber with the tour, the date and the number of riders already in the message, and cards, deposits and accounts were left out, because each one is a step where that tourist stops. A template arrives with its layout and flow decided before anyone knew who would be booking. The same middle path for a shop, a catalogue that hands orders to a chat, is in A web shop or selling through Instagram.
Then the shape of the content. Quadomania's rides are filmed on phones, so the video at the top stayed vertical, 720 pixels wide and 1,280 tall, and the nine photos below it share that shape. A first-time rider has questions a five-page template never answers: what gear is provided, whether a licence is needed, what happens when the weather turns on the Durmitor plateau. Writing that FAQ took longer than the booking form did.
Languages cost less planned than added. Quadomania runs in two. A second language added to a finished design means reworking every page whose text changes length.
Data that changes is where a website starts turning into an app. iLokal is a map of places along the coast with live open or closed status, and owners claim and edit their own listing through a merchant portal, because a directory maintained centrally goes stale. Once a site needs accounts, logins and a database, it has become an app, and the next question is custom software vs off the shelf.
Speed, and what Google can read
Custom is not automatically better here. This site is a React app, and a React app sends crawlers an empty page and fills it in with JavaScript. Every route had to be rendered to real HTML at build time, each with its own title, description and canonical address, before Google could read it, as SEO optimization starts with what Google can read explains. However a site is built, open its page source: if the text is not there, search engines may not see it either. Then open it on your own phone, on mobile data rather than office Wi-Fi, and run it through Google's PageSpeed Insights.
WordPress vs a custom website
WordPress sits between the two. A WordPress theme is a template, and bookings, shops and languages are added with plugins, so the same test applies: what the site has to do, whether the page Google fetches contains the text, and who can change it after launch. Ownership matters more than the platform. Whoever builds it, the domain should be registered in your company's name and the code and accounts should be yours at the end, because a site that only the agency can open is a rental. How to choose a web design agency has the full checklist.
- What it has to do. Bookings, a shop, more than one language, or a few pages and a phone number.
- What Google gets. Open the page source: if the text is not there, search engines may not see it either.
- Who can change it. Ask who can edit the site after launch.
- Who owns it. The domain in your company's name, and the code and accounts yours at the end.
What it costs with us
Websites start from 900 euros, and web shops from 1,500, because a shop adds payments, stock, delivery and returns. The price moves with bookings or payments, how much content has to be written, how many languages the site runs in, and data that has to stay current. What a website build costs, and what drives the price goes through those one by one. Scope, price and payment terms are agreed in writing before work starts, and the code and the accounts are handed over at the end. The work is on the web design page.
