Five things that push a website quote up

Clients sometimes come to a call expecting €700 and leave with a quote for €2,200. The gap is rarely a surprise to us — by the time we've talked through what the site needs to do, the reasons are obvious. The problem is that most of those reasons were set before the call, by decisions the business had already made.

Here are five of them.

You need the site to connect to something else

A website that just shows information is one thing. A website that talks to a booking system, a delivery platform, a payment processor, a CRM, or a stock feed is a different build entirely.

Every integration adds scope: the connection itself, error handling for when the other system has a bad day, and testing that covers more than a desktop browser in good conditions. One integration is usually manageable. Three becomes the majority of the project.

If your brief includes the word "sync" or "automatically" — as in, orders automatically go to the kitchen, or availability automatically updates — that's integration work, and it costs proportionally.

You don't have your content ready

This one surprises people. Content isn't just copy — it includes real photos, menu items with descriptions and prices, team bios, opening hours that are actually correct, and any document the site needs to display.

When content arrives late or incomplete, the project extends. When we have to write or source content ourselves, that's a separate line of work. When photos are stock images swapped in as placeholders, that's a site that will need to be rebuilt the moment someone sends us real ones.

Content is not a finishing detail. It shapes the design. Waiting on it after the build starts is the single most common reason a ten-day project runs to three weeks — and a three-week project costs more than a ten-day one in attention and coordination, even if the price was fixed.

You need more than one language

A multilingual site is not a translated site with a flag in the corner. It needs a content structure that holds two or three versions of every page, a switching mechanism that doesn't break navigation, and testing in each language — including right-to-left scripts if that's in scope.

For each additional language beyond the first, add roughly 30–40% to the content-layer work. If the translation itself needs to be produced, that's a further cost depending on volume.

If your market is genuinely multilingual, it's worth doing properly. The cost is real and the shortcut version tends to be embarrassing.

The design starts from scratch

We do custom design on every project — we don't drop a logo onto a theme. But there's a meaningful difference between building from our own foundation and building from a blank brief with no existing brand assets.

If you have a logo, a typeface, a colour palette and a sense of what you like and don't like, the design period is two days and produces something solid. If the brief is "make it look good, you decide", that's a different kind of engagement — more rounds, more direction-finding, more decisions that have to be made before anything else can move.

The design period is where expensive mistakes get caught. Extending it is sometimes the right call. It's not free.

You need someone to manage it after launch

This doesn't push the build quote up, but it pushes the total cost of the project up, and that confusion is worth clearing up early.

If the site needs ongoing updates — new menu items, new team members, new offers, seasonal changes — someone has to make those changes. If that's us, that's a care plan. If that's you, the build needs to include an admin panel you can actually use. An admin panel takes time to build and test, and it's scope that doesn't show up in the page count.

A five-page site with a full content management panel for a non-technical owner is not the same build as a five-page site we maintain ourselves. Same page count, different price.

What to do with this

None of these are things we invented to justify higher quotes. They're features the business asked for, or conditions it created. The number follows the scope — when the scope grows, so does the number.

The most useful thing you can do before a call is write down what the site needs to do, not what it needs to look like. Features and functions land as a brief. "Modern and clean" doesn't.

If you want to know where your project sits, the intro call is thirty minutes and free — we'll tell you the range honestly and say if you're asking for more than the entry price covers.