Cost to Update a Website: Small Changes, Real Numbers

The invoice says $100. The job was a new phone number in the footer and updated opening hours for the holidays. First time round, that feels like a rip-off. Once you understand how small jobs get billed, you’ll commission the next batch differently and pay barely more for four changes than you paid for one.

How long common website updates take

Below are rough time ranges for frequent changes on a site with a content management system. They’re estimates, not measurements. A well-built site the developer already knows puts you at the low end. An unfamiliar site built with a page builder, no staging copy and software two years out of date puts you near the top.

1. Swap a text or image15–30 min · $25–50
2. Paste in a new privacy or legal page0.5–1 h · $50–100
3. Add a field to the contact form0.5–1.5 h · $50–150
4. Run updates and test0.5–2 h · $50–200
5. New page from an existing template1–3 h · $100–300
6. Fix the mobile layout of a section1–3 h · $100–300

Own estimate for CMS-based sites, testing included. Not survey data. Cost at a $100/h example rate.

The $100 rate is an example, roughly the US break-even figure from our article on the freelance developer hourly rate. For comparison, freelance software developers in Germany ask a median of €90 an hour, according to a September 2026 freelancermap analysis. Your developer’s rate may be higher or lower. The time ranges stay similar.

Billing increments and minimum charges

On a three-day project nobody cares whether time is counted in minutes or quarter hours. On a phone number change, it decides the price.

Two rules are common. The billing increment sets the unit time is counted in, often 15 minutes, so seven minutes of work shows up as fifteen. The minimum charge sets what one job costs at the very least, sometimes half an hour, sometimes a full hour. Both are legitimate. The developer has to get into your site for every job, however small.

Ask about both. Before the first job, ideally. With those two numbers you can work out when batching starts to pay.

Worked example: four changes, one at a time or batched

Say you’ve collected four small requests over a month: new phone number, updated opening hours, a photo on the team page and an extra field on the contact form. The developer charges $100 an hour in 15-minute increments with a one-hour minimum per job. Those terms are an example.

Separately: phone number (1 h minimum)

$100

Separately: opening hours (1 h minimum)

$100

Separately: team photo (1 h minimum)

$100

Separately: form field (1.25 h)

$125

Total as four separate jobs

$425

Batched: one job, everything together (2 h)

$200

Saved by batching

$225

Assumed terms: $100/h, 15-minute increments, 1-hour minimum per job. Time needed is estimated.

The saving doesn’t come from faster typing. It comes from paying once for the overhead before (logging in, getting oriented, clearing caches) and once for the overhead after (testing, reporting back). Obviously a wrong price on your shop shouldn’t wait a month. Everything else can.

Why the same change costs more on one site than another

One new form field can take twenty minutes on one site and two hours on the next. The difference rarely lies in the change itself. It lies in the surroundings:

• Known or unfamiliar site. If the developer built it, they know where everything lives. If not, finding things costs money.
• Page builder or clean theme. Some page builders scatter settings across many elements, which turns a global change into busywork.
• Staging copy or not. With a test copy the developer can experiment safely. Without one they work slowly and carefully on the live site, or set up a copy first.
• Current or outdated software. If WordPress and its plugins need updating first so nothing breaks, a small change becomes half a day.
• Backup or no backup. Careful developers back up before touching anything. If there’s no recent backup, they’ll make one, and it goes on the invoice.

That last point you can handle yourself. Our guide on how to back up a website walks through it.

What you can (and should) change yourself

The cheapest developer is the one you didn’t need, because you made the change in five minutes in your own admin area without waiting for anybody’s reply.

On a site with a content management system, text, images, opening hours and new blog posts are content. That’s what the system was built for. Ask for a walkthrough once. Thirty minutes over a screen share costs $50 at our example rate and will probably pay for itself many times over in the first year. Ask the developer to set you up with an Editor account rather than Administrator. You can then edit content but can’t accidentally delete a plugin.

Keep your hands off anything beyond content: editing theme files, updating plugins on the live site, pasting code into the footer. It might work. If it doesn’t, the site goes blank and the repair costs more than the change would have. Without a recent backup, doubly so.

Here’s a simple rule of thumb. If you click “Save” in the admin and immediately see the result, do it yourself. If you need to open a file or install something, don’t.

Pay per job, prepaid hours or a retainer?

For a few changes a year, paying per job is fine. You send an email, get an estimate, approve it. Admin stays light on both sides.

For regular changes, a prepaid block of hours is often more convenient. You buy, say, five hours upfront, the developer deducts from it and sends you a summary. Some offer a discount on blocks because they gain planning security. Ask.

Monthly maintenance retainers usually combine a block of hours with fixed services such as updates, backup checks and a promised response time. They make sense when the site is business-critical, a shop for instance, and you don’t want to run updates yourself. Read carefully what’s included. “Maintenance” can mean anything from clicking “Update all” to testing the site after every update. Our comparison of fixed price vs hourly shows which model suits which kind of work.

How to request a change so it stays cheap

Good change requests avoid follow-up questions, and with 15-minute increments every question costs real money. Three things are enough:

1. The exact URL of the page.
2. A screenshot with the spot marked.
3. The new text or image as a finished file, not “something suitable”.

For fixing faults, use a proper bug report. For bigger requests, a short developer brief with acceptance criteria pays off.

If change requests keep piling up and every second one is a workaround for something your site can’t really do, take that as a signal. You are no longer maintaining a site, you are stretching it past what it was built for. That’s the moment to talk to a team that builds web applications about what would actually fit your business.

Until then: start a running list of change requests the moment they occur to you, and send it to your developer once a month, with screenshots and finished text.

Questions people ask

Why does changing one line of text cost a full hour?

Because of minimum charges and the work around the change. Logging in, finding the right spot, clearing the cache, checking on a phone and confirming by email all take time, even when typing takes a minute. Some developers bill at least one hour per job for that reason.

Can I make small changes myself?

On sites with a content management system such as WordPress, usually yes. Text, images and new posts are content, and a short walkthrough is enough. Stay away from theme files, plugin updates on the live site and anything involving code unless you have a backup.

Is a monthly maintenance retainer worth it?

If you need regular changes and don't want to handle updates yourself, often yes. A retainer with a fixed block of hours cuts admin on both sides. For two changes a year, paying per job is simpler.

Why is my page builder site more expensive to change?

Some page builders spread design settings across many individual elements. Changing a colour or font site-wide can mean touching dozens of places one by one. On a cleanly built theme, one central setting does the job.