Website maintenance cost — four layers of the bill, two of which nobody quotes

Website maintenance cost has no single-figure answer, and not because "it depends". Because the bill is made of four layers of entirely different predictability. Two can be priced to the cent before you sign. The other two cannot be priced at all — only anticipated by kind.

Companies rarely get this bill wrong on the amount. They get it wrong on which layers they never counted.

The four layers of the bill

Layer 1: infrastructure — known in advance, but only from year two

Hosting, domain and certificate are the only part of the bill that can be stated exactly — with one caveat that overturns most calculations: the price at checkout is the promotional price for the first year.

The scale is larger than the word "promotion" suggests. Prices we read from Polish price lists on 26 August 2026:

home.pl and OVH quote net of VAT; the LH.pl figures are as printed, without a stated basis. Compare net figures.

Credit where due for printing both: OVH writes "Cena odnowienia" (renewal price) against every item, home.pl "Później: 698,99 zł netto za kolejny rok" (later: PLN 698.99 net for the next year), and LH.pl labels a column "/ odnowienie" (renewal). The table also shows where to look hardest: the plan with the lowest first-year price carries the largest step — home.pl's Hosting Start steps seventeenfold — so the offer that looks best on the first invoice is the one with the largest step on the second.

How to match hosting and a domain to your own case is a separate text. Here they are only a line in the bill.

Layer 2: licences — known in advance, but rising at renewal

The second layer behaves the same way, only for software: the theme, the plugins, the visual editor.

The mechanism is identical to hosting — today's price is not the price a year from now. Elementor on the One plan costs €180 a year to buy and €228 to renew — at the NBP (Narodowy Bank Polski) rate of PLN 4.3014 to the euro, PLN 774 now and PLN 981 from year two: same product, same site, 27% more from year two.

A separate line that appears in no implementation quote: paid plugins and extensions. No estimate needed, because the vendor prices it — WooCommerce lists extensions at $29–299 a year each, in dollars worldwide, or PLN 107–1,102. Three of them — not many, once you have payments, shipping and invoicing — come to PLN 321–3,306 a year, plus whatever the exchange rate does.

The practical rule: ask your supplier for the plugin list with a price and renewal date against each. Not one figure "for maintenance". No list means nobody counted it, and you will be the one paying.

Layer 3: work — unknown, because it depends on how much happens

This is where predictability ends. Fixes, updates, small content changes, reacting to what breaks — none of it can be quoted in advance, because nobody knows how much there will be.

The rate can be known — ask for it. In our Polish market study a freelancer charges PLN 50–150 an hour, an interactive agency PLN 120–250 and a software house PLN 200–400, so a single "PLN 200–400" band describes only the top segment. What moves the rate:

• Who does the work. A freelancer is usually cheaper per hour than an agency, and less available when something breaks at night.
• When the hour is bought. Hours bought in advance inside a plan cost less than the same hours bought ad hoc, and work outside a plan costs more — as a rule, everywhere.
• How fast you need it. A guaranteed response time is priced separately, whether it is written into the plan or charged as an emergency surcharge.

With small changes the minimum billing unit matters as much as the rate: half an hour billed as an hour, three times a month, changes the bill more than the rate does.

The alternative is a retainer — a care plan. It converts an unpredictable line into a predictable one and you pay for the conversion, which is fair provided the scope is clear. Technical care has its own text.

Layer 4: limit overruns — invisible until the day they occur

This is the layer no offer mentions, because at signing it does not exist. It appears later, on its own, and always for the same reason: something grew.

The clearest case is any tool priced by list size. Email platforms index the subscription to the number of contacts, and the list grows because growing it is the point — so the same plan, with the same features, costs a multiple of what it did at signing. A measured example from a Polish vendor: GetResponse Starter costs PLN 48.38 net a month at 1,000 contacts, PLN 245.18 at 10,000 and PLN 1,630.98 at 100,000 (annual billing, price list checked 5 October 2026) — over five times at ten times the list, and 33.7 times at a hundred times.

The same mechanism has three other typical forms:

• Hosting limits. A traffic spike or heavy bot crawling exhausts the processor or transfer allowance and the provider proposes a higher plan. The bill rises in a step, not a slope.
• An emergency fix after an update. An automatic update breaks the layout: one to three hours of urgent work at the layer-three rates, usually at the top of them, because it is "now".
• An API call limit. The free tier of a map, currency-conversion or email-sending service runs out, and the next one is priced per call.

The common trait: none of the four appears in the contract, and every one is predictable by kind. You cannot compute the amount; you can compute the risk — and ask before it happens.

Monthly website cost — how to convert without going wrong

Companies budget monthly and this bill arrives annually. An innocent difference, until you compare offers — at which point two figures describing the same thing differ twelvefold.

The conversion rule has one condition: divide the annual lines by twelve only after taking the renewal price rather than the first-year price. A simple business site maintained in-house, from year two, is about PLN 258 a year (LH.pl hosting PLN 199 plus a .pl domain PLN 59) — just under PLN 22 a month. The same site with a paid visual editor is about PLN 1,239 a year, or PLN 103 a month. Against a first year of about PLN 67, that is a fourfold step driven entirely by a promotion expiring.

Packaged care plans start distinctly higher, and any plan worth comparing states how many hours of changes it includes. That does not make them overpriced. It means they contain layer three, the work, which is not in those PLN 22 at all.

The practical takeaway: ask how much of the monthly figure is infrastructure and licences, and how much is work. The first two can be checked against price lists in five minutes. The third is what you are actually paying for.

There is also an accounting move that removes the nuisance entirely: divide the annual amount by twelve and set it aside. Renewals then arrive as a transfer rather than a surprise — and with lines that renew at five times the purchase price, that is the difference between planning and firefighting.

The billing model itself — build paid once or monthly — reshapes the whole bill, and has its own text with the crossover calculated.

Build plus upkeep — the bill you have to set side by side

The commonest budgeting mistake is not under-estimating any line individually. It is that they are counted at two different moments and never set side by side: the build when the contract is signed, upkeep when the first invoice arrives a year later.

How to prepare that budget and compare offers is covered separately. The comparison is done over three years, because only then do the proportions show. For a business site at the market median from our report, maintained in-house, the build is by far the larger part and three years of upkeep only a few per cent of it. With a care plan the proportion shifts: three years of care can equal the build.

This is the right place for one question worth asking before choosing a supplier, and asked by very few: can this site be maintained without you after we stop working together? If the answer is "only we can handle it", layer three stops being negotiable for the life of the site.

A shop: the entry price is not the cost of upkeep

With a shop the bill changes shape, because subscription platforms replace layers one and two with a single fee — and add a line a business site does not have at all: transaction fees.

On the manufacturers' price lists in August 2026, Shopify's Basic plan costs PLN 109 a month, while Shoper Standard (a Polish platform) costs PLN 299 net a month. That looks like the whole cost, and it is how such platforms are usually compared. Until you add the payments.

Shopify charges an additional 2% whenever payments go through anyone other than its own gateway. That fee scales with turnover, not with the plan. Take our study scenario: 200 orders a month at a PLN 200 basket, so PLN 480,000 of turnover a year. Without fees Shopify Basic comes to PLN 5,032 a year against PLN 6,973 for Shoper — but with payment fees it is PLN 21,323 against PLN 13,664, and the order reverses. The cheapest subscription stops being the cheapest platform at roughly PLN 97,000 of annual turnover, below PLN 8,000 a month.

We are not reproducing a full comparison against a self-hosted shop, because the honest version depends on your payment mix. What transfers is the shape: on a subscription platform the recurring bill is a fixed fee plus a percentage of sales; on a self-hosted stack it is hosting plus extension licences, with no percentage at all — and with a shop, exceeding a limit is not an exception but the plan.

What it comes to, year one and year two

Two profiles, line by line. Every figure comes from a price list we name — these are not bands "from the market".

Every amount comes from a price list we name: Polish hosts and OVH read on 26 August 2026, Elementor and WooCommerce converted at the NBP rates of table 165/A/NBP/2026 (PLN 4.3014 to the euro, PLN 3.6852 to the dollar).

Two things to take from that table. First: a simple business site maintained in-house really costs a few hundred złoty a year — not thousands, as packaged offers imply. Second: the hosting and domain lines quadruple between year one and year two, and the step comes entirely from a promotion expiring.

Price your own case in the maintenance cost calculator, and the build itself in the website cost calculator.

Four questions for your supplier, one per layer

The whole bill comes down to four questions that fit one conversation, asked before signing rather than after the first invoice.

1. What is the renewal price, not the first year? For hosting and the domain. If the answer is the starting-offer figure, ask to be shown it on the provider's page — it is usually printed right next to it, under the word "renewal".

2. What is the list of paid plugins and licences, with a price and renewal date against each? Not one figure "for maintenance" — a list. No list means nobody counted it.

3. How is work outside the plan billed, and what is the minimum unit? An hourly rate without the second answer says nothing: three small items a month billed as full hours doubles the bill with no extra work.

4. What happens when we exceed a limit? Traffic, contacts, API calls. The point is not the amount but whether an answer exists at all — because if it does not, nobody has thought that scenario through.

Answers to those four turn an unpredictable bill into a predictable one about two-thirds of the way. The rest stays risk, and that is an honest boundary — it cannot be removed, only named.

What happens when you stop paying

The layers differ not only in predictability but in what happens when payment lapses — usually asked only once it is too late.

A plugin or editor licence. The site keeps working. What expires is the right to updates and support, so fixes stop arriving, security ones included. Nothing shows for months; then a hole appears that cannot be patched.

Hosting. The site stops opening, usually after a grace period, and data is kept a while before deletion. Both windows differ by provider and are written in the terms — worth knowing before they are needed.

The domain. The most serious of the three: once it expires and the redemption period ends, the address returns to the pool and anyone can register it. Recovering it from a new owner is not a fee but a negotiation — or the absence of one.

The rule that organises this: register the domain to the company, and make sure renewal notices go to an address somebody reads. The commonest cause of losing a domain is not financial — it is a renewal email sent to the mailbox of somebody who no longer works there.

What can safely wait, and what cannot

Not every line carries the same cost of delay, and budgets are cut by amount rather than by risk.

Can wait: a premium theme, if the current one works. A larger tier of an email tool, while the list is small. An extended-validation certificate — free ones cover the encryption. Extra domain variants bought "just in case".

Cannot wait: domain and hosting renewals, because the consequence is irreversible. Security updates, because the cost of neglect grows in a step on the day of the breach, not in a line. Backups — the only line that repays itself in full the first time it is used.

The order of cutting, if the budget were genuinely tight: convenience first, then features, security last — and never below the level at which the site stops being yours.