"How much does it cost to make a website?" is one of the most common questions I receive, and also one of the most poorly formulated. It's like asking how much a vehicle costs without saying whether you want a bicycle or a truck. The price range is so wide that the isolated answer doesn't help anyone.
The problem is not the lack of information on the market. The question hides confusion about what is being purchased. A "website" can be a single presentation page or a complete system with login, payment and integration. Same name, completely different costs.
This article is for anyone who needs to make this decision, a manager, an entrepreneur, a secretary evaluating a public portal, and wants to understand what really determines the price, so as not to buy unnecessary expensive things or cheap things that will cost dearly later.
What are you buying anyway
Before talking about values, it is necessary to separate categories. They have costs of different orders of magnitude.
Simple institutional website. Some pages, company information, contact form. It can be built with ready-made tools and cost little. It's the equivalent of a digital business card.
Content website or blog. Need a system to publish and manage articles frequently. More complex than the institutional one, but still within consolidated solutions.
Virtual store. Catalog, cart, payment, stock control, transaction security. Here the cost rises, because money and sensitive data are processed.
System or web application. User login, restricted areas, business rules, integrations. This is no longer "a website", it's software. And software has a software cost.
Most budget frustrations come from people who asked for a price for one category and had another in mind.
The thesis: price follows complexity, not the number of screens
The instinct of those who hire is to measure size by number of pages. It's a misleading rule. One page with a form that processes payment and validates data is more complex, and more expensive, than twenty static pages of text.
What drives the cost is the complexity of the logic behind it, not what appears on the screen. Features that involve user data, money, integrations with other systems or specific business rules are where the effort is concentrated.
Therefore, the best way to control the cost of a website is not to cut pages. It’s about being clear about which features you really need now and which ones can wait.
The costs that no one includes in the initial budget
The construction price is only part of the bill. A recurring mistake, especially in public projects and in companies without digital experience, is treating the website as a one-time purchase, when it is more like a vehicle that needs ongoing maintenance.
- Hosting. The website needs to live somewhere. It is a recurring cost, monthly or annually.
- Domain. The address (yoursite.com.br) has registration and renewal costs.
- Maintenance and updates. Software ages. Security flaws are discovered, technologies need to be updated. An abandoned website becomes a risk.
- Content. Text, image, video. Often overlooked in the budget, and often the bottleneck that delays launch.
- Security. Especially in stores and systems that store people's data, adequate protection and compliance with LGPD are not optional. They are the cost of operating responsibly.
Ignoring these items does not make them disappear. It just turns them into unpleasant surprises later.
Why does the same website have three different quotes
Those who ask for a quote in three places tend to receive very different amounts and become confused. It's not necessarily a sign that someone is overcharging. Reflects different choices.
A ready-made website assembly tool delivers quickly and cheaply, with limits. A freelance developer offers more flexibility at an intermediate cost. An agency or software company delivers a tailored project, with process, guarantee and support, and charges for it.
The right question is not "who is cheaper", but "what does each option deliver and which one meets what I need". Paying a lot for a custom-made system when a ready-made tool would do the trick is a waste. But saving on a limited tool when the business requires a robust system is a saving that pays interest later.
The most expensive mistake: hiring for price, not fit
The most common trap is choosing at the bottom of the budget. The cheap thing that doesn't work becomes rework, and rework is the cruelest invisible cost, you pay twice for the same thing.
I've seen this happen in city hall projects that hired the cheapest option for a service portal, discovered that it didn't support the necessary integrations and had to start over. The money saved on hiring was more than lost on reworking, not to mention time and credibility.
An honest reflection: the real cost of a website is not measured in the budget, but in its lifetime. A well-made website that serves for years is cheaper than a poorly made one rebuilt every eighteen months.
The factor that changes the entire account: who owns the code
There is a question that almost no one asks when hiring and that defines the long-term cost: in the end, whose website is it? Who has access to the code, domain, hosting and accounts involved?
When the answer is "the supplier", you are held hostage. Any future adjustment depends on him, any price increase you are forced to accept, and changing partners means starting almost from scratch. This is a hidden cost that does not appear in the budget, but weighs on you for years.
The recommendation is simple and applies to companies and public bodies: guarantee, by contract, ownership of the code and access to all accounts. In the public sector this is even more critical, because the continuity of service to citizens cannot depend on the goodwill of a single supplier. Independence has value, and acquiring it from the beginning costs much less than regaining it later.
How to decide clearly
Before asking for any quote, answer three questions. What is this website for? What features are essential now? Who will take care of it after it's ready?
With these answers, the conversation with suppliers changes direction. You stop buying "a website" and start buying a solution to a defined problem. And then the price stops being a mystery and becomes an informed decision.
Creating a website is not an expense, it is an investment in a digital asset. Like any investment, the return depends less on how much you pay and more on how well the choice fits what you need.
If you are at that decision point and want to structure what you really need before hiring, there are other articles on the blog about software costs, choosing suppliers and digital products. If it is a relevant decision for your organization, it is worth discussing it before signing.
Also read
- How much does web development cost (and what really sets the price)
- Website or app? The guide for beginners to decide without burning money
- How much does it cost to hire a software house (and what defines the real price)
- Tailored digital solution: the checklist before hiring
- What Are React Server Components and Why Logic Is Moving Back to the Server
- How to choose a web development company without regretting