Ready theme or custom website: what you actually pay for

Two studios quote very different sums for what sounds like the same website. Usually they are not quoting the same work. One plans to put your logo on a ready theme. The other plans to design and build the pages around your content. Both can be the right choice, in different situations.

What a ready theme includes

A ready theme is a finished design with prepared page layouts. Your texts, photos and logo go into fixed slots.

  • Fast launch: a simple site can go live in days, not weeks.
  • Lower upfront cost: no design and development from scratch.
  • Design compromises: blocks that almost fit, but not quite.
  • Extra code: a ready theme often carries features you will never use; left untuned, they can slow the site down.
  • Harder to change later: restructuring pages inside a theme is difficult.

What custom development includes

With custom work, the pages are drawn around your real content, and only the features you actually need get built.

  • The design explains your offer, because the pages are built around your texts and photos.
  • Easier to grow: new page types and languages slot in without rebuilding everything.

In my practice, websites with custom layouts, SCSS and ACF have run faster, and their ongoing maintenance has been simpler and cheaper than on sites built on ready themes. Content is edited through ACF fields, without changing the layout.

How the choice shows up in the price

With a theme, most of the budget goes into content setup and adjustments. With custom work, most goes into design and development. A theme site can cost less at launch, but if every small change needs a developer, it can end up costing more over time. Custom work costs more at the start and is often cheaper to grow.

When a ready theme is enough

  • A first simple website: a few pages and a standard structure.
  • A tight deadline or a limited budget.
  • You plan to rebuild the site soon anyway.

When custom work pays off

  • Many different page types or languages.
  • The site has to connect with other systems: booking, a client area, accounting.
  • Brand character matters and the site has to stand out.
  • You know the site will grow with the business.

What to ask a studio before choosing

  • Can I edit texts and pages myself later?
  • Who owns the domain, the hosting account and the code?
  • What happens when I need a new type of page?
  • Who handles updates and backups after launch?

We build WordPress websites with a design made for you, not on a bought theme. Describe your task: after a short conversation you get a quote with a fixed price and timeline. It does not oblige you to anything.

Multilingual websites: how to do it properly

A website in several languages is not a machine translator laid over the design. Estonian, Russian and English visitors search for services differently, and the text in each language has to sound natural and convincing.

How we build multilingual sites

A separate address for each language

Each language version has its own page addresses. Search engines such as Google and Yandex list them separately, so an English-speaking customer lands on the English version straight away, not on a page with a language dropdown.

Structure first

First we design and agree the page structure in the main language, then we adapt it for the others. If some content matters for only one market, we set the navigation so there are no broken links and no empty language switches.

Working with the text

Machine translation is fine for a draft. It does not sell. We help to adapt the text and to say things clearly. Industry terms and details of your business we agree together with you or your translator.

Time and cost

Each extra language takes time for layout, linking the versions, content and SEO settings. The design is not redrawn from scratch, so the price does not double. We price every language version at the start, so the budget is clear before the work begins.

When we talk, say which languages you need and whether the translations are already written. That is enough for an exact quote.

What to prepare before building an online store

A full online store is not just a catalogue with a Buy button. It is a working system: product structure, payment flows, delivery rules and the way orders are handled. The more of this is written down before development starts, the faster and smoother the launch.

1. Catalogue structure

List the products or the categories: names, base prices and variations (size, colour), and the status (in stock or made to order). A spreadsheet in Excel or Google Sheets is enough to start. Good photos can come later. The structure of the catalogue is needed from the start.

2. Payment methods

Decide how customers prefer to pay. We connect popular Estonian and European payment systems (card payments through a bank, Montonio, Stripe), and also cryptocurrency or payment against a bank invoice. You do not have to register with every provider on day one — we choose the right ones together at the start.

3. Logistics and delivery

Parcel lockers (SmartPost, Omniva, DPD), couriers or pickup. Write down the price, where you deliver and the exceptions, such as limits for oversized goods or deliveries to the islands. Clear terms on the site save you from the same questions in support.

4. Legal information

Terms of sale, a privacy policy and how returns of money or goods work. We move the documents you already have, or we point out what an online store in Estonia and the EU has to cover.

5. Day-to-day process

Say who on your team will handle orders, update stock and answer customers. We set up the admin so you can run the store yourself, without calling a developer.

If some of this is still open, that is normal. We go through it on the first consultation and then send a fixed quote.

Website maintenance plans: 1, 2 or 3+ hours

A website is not finished on the day it goes live. WordPress, the plugins and PHP keep receiving updates. Skip them for a year and the site gets slower, and one day a form or a payment simply stops. Someone has to look.

You can do that yourself, call us when something breaks, or take a monthly plan. The work is the same on every plan: updates, backups, small fixes, and a person you can reach quickly. Reply speed does not change with the plan. You can stop any month.

What changes is the size of the site. A typical company site or an online store takes about an hour of care a month. A large site needs two. A very large one needs three.

1 hour

This is the usual amount for a normal site or a store.

2 hours

For a large site.

3+ hours

For a very large site.

What a plan does not include

Design changes, new pages with their own layout, and new functions are separate work. Texts, images and ordinary pages you edit yourself, without our help. Hosting and the domain stay in your name and are billed by the provider.

If you are not sure how many hours fit, write to us. After a short look at the site we will say.

What to prepare before ordering a website

Most delays on a website are not caused by development. They come from questions nobody answered at the start, and then everyone waits. A rough list is enough. Nobody expects a finished brief.

Here is what is useful to have before the first conversation, even as notes. If something is missing, we can fill it in on the call. The list is there so the call is about your company, not about hunting for the domain password.

1. What the site should do

Write one or two sentences: “The site should bring requests for X from Y.” Everything else — structure, design, texts — follows from this.

2. Who it is for

Describe your typical client: who they are, what they worry about, what they want to know before contacting you. If you have several groups, list them.

3. A rough list of pages

Services, prices, about, contacts, maybe cases or a blog. It does not need to be final — we will refine it together — but a draft saves a lot of time.

4. Texts and images

  • What you already have: old site, brochures, presentations, photos.
  • What is missing and who will prepare it.
  • Logo and brand colours, if they exist.

5. Examples you like

Two or three sites you like and one you do not, with a note on why. This says more about taste than any description.

6. Access details

Domain registrar, current hosting, email and the old site admin, if there is one. Finding these at the end often delays the launch.

7. Budget and deadline

Even an approximate range helps to suggest a solution that fits, instead of an ideal one that does not.

If something on the list is missing, that is fine. We can go through it together in the first conversation.

WordPress or a website builder: what to choose for a business

Wix, Squarespace and similar builders let you put a site together in an evening. WordPress needs a developer at the start and gives you more room later. Both are sensible. They suit different situations, and the expensive mistake is picking one because a neighbour did.

The useful question is not which name sounds more modern. It is what you will be doing with the site in a year: changing a phone number, or adding languages, a catalogue and pages that do not look like the template.

When a builder is enough

  • You need a simple business card site with a few pages.
  • You want to build and update it entirely yourself.
  • You are fine with the design limits of the templates.

The trade-off: you pay a monthly fee as long as the site exists, and moving the site to another platform later usually means rebuilding it.

When WordPress is the better choice

  • The site has many pages, several languages or a blog that grows.
  • You need your own design, not a template, or functions a builder does not offer.
  • You want to own the site: the code and the data stay with you, and any developer can continue the work.
  • You plan to sell online — WooCommerce adds a full store to the same site.

What about editing?

A common worry is that WordPress is hard to edit. A well-built site has clear fields for texts, images and pages, so day-to-day changes take minutes. We set it up so that you do not need us for routine updates.

A simple rule

If the site is a small addition to your business and you have time to do it yourself, start with a builder. If the site brings clients, has to grow and should look like your company rather than a template, choose WordPress.

How much does a website cost and what the price depends on

People ask what a website costs as if there were one number. There is not — just as there is no single price for a house. A fair price is still not a guess. It is made of a few things you can point at and compare.

If two studios quote very different sums for what sounds like the same site, they are usually not quoting the same work. One may be fitting your logo onto a ready theme. The other may be designing the pages around your texts. Both can be honest. They are just different jobs.

What the price is made of

  • How many kinds of pages there are. Ten service pages that share one layout cost less than five pages that each need their own.
  • The design. A ready theme with your logo is cheaper. A design made for your content usually explains the offer more clearly, because the pages are drawn around what you actually say.
  • What the site has to do. A contact form is straightforward. Booking, a client area, a calculator or a link to accounting software adds real work.
  • Languages. Each language needs its own texts, its own addresses and a proper check. It does not double the design, but it does add time.
  • Texts and photos. If they are ready, the build moves. If they still have to be written or edited, that is a separate piece of the job, and it should be in the quote.

Where our prices start

Apps, software and SEO are priced after we know the task. After the first conversation we send one figure for the agreed scope, so the price does not grow quietly while the work is underway.

How to compare two offers

When the numbers are far apart, ask both studios the same four questions:

  • Is the design made for my texts, or is it a ready theme?
  • After launch, can I change texts, photos and pages myself?
  • Who owns the domain, the hosting account and the code?
  • What happens after the launch: updates, backups, small changes?

The answers usually explain the gap better than the total on the last line. A lower price that leaves you paying a builder every month, or calling a developer to change every sentence, is not always the cheaper site a year later.