Skip to content
creative group · Global Book a conversation

A Business Website Cost Is Not a Number Pulled from a Hat


Blank white price tags on a red background
Photo: Eva Bronzini / Pexels

A website’s price is not one thing. It is the sum of decisions about what the site needs to do and explain, who prepares the material, what has to work behind the scenes, and who will help when the first problem appears after launch. That is why the question “How much does a website cost?” deserves more than a figure pulled out of thin air.

Many agency websites do not list a single number, only a “Request a quote” button. A quote can be justified: building a business website is not the same product for everyone. But when there is no explanation of how the price is set, a person must agree to a sales step before finding out whether it is even within their budget.

The first decision is scope. A site with a few clear pages and one that must guide people through multiple services, locations, audiences, and decisions are not the same job, even if both end up with a beautiful opening screen. Pages are not just menu items. Each needs structure, a message, review, and a relationship to the others. That is why it helps to establish what the site needs to say and to whom, not just how many sections need to be drawn. My article on a business website explores that work: a good site is not a collection of blocks but a path a visitor can follow toward a decision.

Then comes the difference between a template and custom work. A ready-made template is not a scam; sometimes it is a sensible way to get a neat, simple site quickly. The problem starts when the same word, “development,” hides two entirely different jobs. With a template, an existing structure is adapted to the company’s content. With custom work, the first questions are what the structure should be, how the user moves through it, how the offer will differ from others, and how the design will support that particular story. One is not morally better than the other. But they do not cost the same, and they should not look like the same offer.

Features change the picture, too. A contact form is not the same as a system that receives inquiries, assigns them to people, and connects them to an existing CRM, a customer relationship management system. A catalog is not the same as a store with payments, inventory, shipping, and invoices. Multiple languages, bookings, user accounts, connections to external services, and special administrative roles are not decorations added at the end. Each raises new questions: what happens when data does not arrive, who checks it, where is it stored, how is something changed? The price rises because the system carries more responsibility, not because the word “integration” sounded serious.

Then there is content, often the quietest part of a proposal. Photos, copy, service descriptions, references, translations, and decisions about who approves what all come before launch, but rarely fit into one short line item. If content is not ready, someone has to collect it, edit it, or wait for it. If each new version raises another question about the basic message, revisions do not end because no point has been set for making a decision. It is not fair to hide that under “minor changes.” It is even less fair to promise unlimited revisions as though time had no price.

After launch, there are costs that are not particularly exciting but are real: a domain, hosting, tool licenses when needed, security updates, backups, and help when a form stops sending messages or someone wants a new page. These do not all have to be in the same monthly line item. They do, however, have to be named. A site without a maintenance agreement is like handing over the keys to a space without saying who fixes the lock when it first jams.

Publicly available price ranges for Serbia do not solve this problem. Agencies publish their own price lists and estimates, but without a shared methodology, so the same project name can cover things that cannot be compared. Foreign guides offer even more numbers, just for a different market, a different cost structure, and often a different scope of work. A number can act as an anchor: the first price we see easily becomes the measure for everything that follows. If it is not explained, that kind of anchor is bait, not a guide.

It can be done differently. Basecamp shows its price right on the page, with no form to fill out and no sales call to book. A small difference on the screen, and a big difference in the conversation that has yet to begin.

That does not mean every price listed as “on request” hides bad intent. A precise figure before discussing scope can force a company to inflate it just in case, or promise something the customer will later have to pay extra for. A legitimate estimate requires discovering the work involved. But between a price list fixed in advance and a blank page there is honest ground: explain what affects the price, ask the questions that will determine it, and clearly state what is included and what falls outside the proposal.

When you look at a proposal for a business website, don’t look only for the lowest number. Look for the trail of decisions. Is it clear what will be built, what will be adapted, who prepares the content, how many rounds of revisions are expected, and what remains after launch? Examples of the best business websites show that clarity on the screen is no accident; the same kind of clarity should exist before a contract is signed. And when price is trying to influence a decision, it is also worth understanding conversion psychology: removing uncertainty is not the same as pushing a person toward a button.

An honest price does not promise to be low. It leaves enough light to see what you are paying for.