Build vs Maintain a Website: Why the Upfront Price Is Not the Real Cost

When someone asks “how much to build a website?”, the answer going around is usually a single number: Rp5m, Rp15m, Rp50m. That number feels like a big decision, and it is. But one thing is rarely realised: the build price is not the total cost of owning a website. It is only the entry cost. The rest is the cost of maintaining it, and what that work involves is set out in our article on website maintenance services.

A website is the only business asset that starts ageing the moment it is bought. WordPress and plugin versions fall behind, new security gaps are found every month, browsers change standards, and content that was once relevant goes stale. Without care, the value of that asset falls every day, even though no bill arrives to remind you.

This article discusses the difference between building and maintaining a website honestly, with numbers you can use to do your own calculation.

What is not included in the build price

When you receive a website build quote, look at what is genuinely covered. What is most often not included:

• Hosting. Paid annually, from a few hundred thousand up to several million rupiah depending on needs.
• Domain. Paid annually, small in value but fatal if you forget to renew.
• SSL certificate. Sometimes included, sometimes extra. Some providers bill it every year.
• Updates and repairs after handover. Generally outside the builder’s responsibility unless specially agreed.
• Backup and monitoring. Rarely included, though this is what determines whether the website can recover when something goes wrong. Why an untested backup is as good as a lie is discussed in the importance of website backups.
• Content. Article writing, photo shoots, and product updates continue, not once.
• Advanced speed optimisation. Often appears as new work once traffic starts rising.
• Malware cleanup. This cost only appears once the website has been attacked, and it can approach the original build price.

This list does not mean website builders behave unfairly. It explains something more fundamental: the build work ends at one point, while the care work never really ends.

The most honest analogy

Imagine two choices when buying a vehicle. Option one: buy the vehicle and never change the oil, never check the brakes, and only go to the workshop when the engine dies on the road. Option two: buy the vehicle with scheduled periodic servicing.

Both owners pay the same purchase price. What differs is two things: the total cost over several years, and the peace of mind while driving.

A website works the same way. Monthly care feels like an extra expense because it is routine and quiet. Emergency repair feels like an extraordinary event even though it is actually more expensive, both in money and in time and customer trust.

A three-year calculation: two scenarios

Let us use sensible numbers for a small company website. This is a simplification, not a quote, but the proportions illustrate the point.

Scenario A, build then leave it

• Website build: Rp12m
• Hosting and domain for three years: Rp4.5m
• Fixing the layout after a broken update: Rp1.5m
• Malware cleanup and data recovery: Rp2.5m
• Speed repair after two years: Rp2m
• Three-year total: about Rp22.5m

Scenario B, build then maintain it

• Website build: Rp12m
• Hosting and domain for three years: Rp4.5m
• Monthly care at Rp600k for three years: Rp21.6m
• Three-year total: about Rp38m

On paper, scenario A looks about Rp15m cheaper. But notice what has happened in scenario A by year three: the website is most likely slow, the design has aged as best it can, and the content has never grown. Scenario B gets routine updates, tested backups, problem handling at no extra cost, and content that grows every month.

This comparison explains one important thing: the difference is not between thrifty and wasteful, but between two kinds of spending. Scenario A pays to repair damage. Scenario B pays to prevent it, and receives much more work within it.

Why “rebuild it later” is not maintenance

There is a popular belief: if a website has aged, leave it and rebuild completely every few years. At first glance it makes sense. In reality there are several hidden costs in a rebuild.

Temporary loss of traffic. A new website takes time to be recognised again by search engines. If the URL structure and redirects are not done correctly, the positions built over years can vanish and be hard to recover.

Costs that repeat. A rebuild requires reinstalling forms, payment integrations, tracking, and all the content. You already paid for that work once, and now pay for it again at today’s rates.

Downtime risk. A rebuild that misses its schedule means the old website has been abandoned while the new one is not ready.

Opportunities lost in the years before. During the three years before the rebuild, your website was slow, hard to find, and did not produce as much as it should have.

A rebuild is legitimate work. But treating it as a replacement for maintenance is like treating a house renovation as a replacement for fixing a leaking roof. They are different needs, and each has its own right time.

What you are actually buying with a care subscription

If monthly care feels like an intangible cost, here is a more concrete list. What you buy includes:

1. Components that are always current, so old security gaps are closed before someone else finds them.
2. Tested data copies, so any damage can be recovered quickly, not in days.
3. Fast response when something breaks, based on an agreed written time, not the seller’s spare time.
4. Content that grows, so the website strengthens its search position month after month.
5. A readable report, so you know what work was done and what deserves attention.

All of that contributes to one outcome: your website remains a working marketing channel, not just a rarely visited digital business card.

When care is enough, and when a rebuild is needed

Care is almost always the first option. But there are conditions where a rebuild or major restructuring is genuinely more sensible:

• A platform that no longer supports your needs, for example an online store growing fast while the system can no longer handle the number of products and transactions.
• A structure that blocks growth, where every new page requires excessive work, or the design cannot hold new types of content.
• Structural speed and security problems, caused by old code that is hard to tidy up without rebuilding.
• A website that no longer reflects your business scale, to the point of damaging credibility.

Outside those conditions, fixing what exists is almost always more economical: cheaper, faster, and without the risk of losing search positions.

What often happens in the field is not one of the two conditions above, but a combination. The right time to decide is not when the website is already broken, but when you are calming down after a small problem has been handled.

How to decide with a cool head

Before making a big decision, answer these five questions:

1. How much do you lose per day if this website cannot be accessed?
2. How many leads or orders come from the website each month?
3. Is there a technical problem blocking growth, and if so, is it structural or fixable?
4. What is the total cost of a rebuild, including content writing, reinstalling integrations, and the risk of falling search positions?
5. After the rebuild, will someone maintain it, or are we back to where we were three years ago?

The answer to the last question usually decides it. A rebuild without a care plan is the most expensive way to experience the same problem again.

Signs your website is ageing without you noticing

Invisible damage does not mean it is not happening. Some signs that are usually missed:

• Load time gets slower every year. A page that once opened in two seconds now takes five, especially on mobile networks.
• The plugin count grows and never shrinks. Every addition feels practical, but they pile up into a maintenance burden.
• Warnings in the admin panel are no longer read. There are pending update messages and certificate warnings, and both have been ignored for a long time.
• Nobody knows whether the backup really exists. If this question cannot be answered within a minute, the likely answer is “no”.
• Pages that look broken on phones. Display standards change; what was once tidy now feels off.
• Content last updated more than a year ago. To visitors and search engines alike, this signals the website is no longer cared for.

Finding two or three of these signs does not mean your website is broken. But it means work has piled up, and delayed work is almost always more expensive when it is finally done.

How to explain this to a boss or business partner

If you need to convince someone else that a care budget makes sense, use these three sentences:

First, “a website is the one asset whose value falls if it is not maintained, and rises if it is.” Second, “monthly care costs less than a single recovery after an incident.” Third, “what we are buying is not technical work, but the certainty that the website stays reachable and keeps producing.”

Avoid technical terms like plugins, Core Web Vitals, or hardening without explaining them. What decision-makers need to understand is simple: what risk is being avoided, and what it costs compared with the loss if that risk happens.

If a number is needed, use the estimated loss per day when the website cannot be accessed. That number usually settles the debate immediately.

A conclusion you can use today

If you are deciding a website budget, separate the two kinds of cost from the start: the build cost and the care cost. Put both into the annual budget. A consistently maintained website is almost always cheaper than expected, and an abandoned website is almost always more expensive than expected.

If your website has never been maintained regularly, start by finding out its condition. Our free website health audit checks security, speed, backup, and technical SEO, then gives recommendations you can take in part. There is no need to take a plan, and no pressure.