Your WordPress site broke last month. Someone fixed it, you paid, and it has been fine since. Now the same person, or a different company, suggests a monthly plan. You wonder whether that is genuinely useful or just a way to turn one bill into twelve. After all, the site worked for two years before this with nobody looking after it.
Care plan vs one-time fix is a fair question, and the honest answer depends on your site rather than on anyone’s sales pitch. This post gives you a way to work it out: what each option actually buys, which sites suit which, and the questions that tell you whether a plan on offer is worth paying for.
Care plan vs one-time fix: what you are really comparing
The two options solve different problems, which is why comparing their prices directly can mislead.
- A one-time fix is paid after something has gone wrong. You get a specific problem solved: a white screen, a broken form, an error after an update. When the job is done, nobody is responsible for the site until the next time you call.
- A care plan is paid in advance, every month, for routine work that aims to stop problems happening and to catch them early when they do: updates applied and tested, backups taken and kept off the server, uptime and security watched, small fixes handled as part of the plan.
A wordpress monthly maintenance service is that routine work done for you on a schedule. So the real comparison is not “monthly fee against one repair bill”. It is “steady routine cost” against “occasional repair bills, plus the cost of the site being broken while you notice, find someone and wait for the repair”.
Monthly plan or pay per fix: a side-by-side view
| One-time fix | Care plan | |
|---|---|---|
| When you pay | Only when something breaks | Every month, broken or not |
| Who notices problems | You, or a customer | Usually whoever runs the plan, through monitoring |
| Updates | Your job, or left undone | Done as part of the plan |
| Backups | Whatever your host provides, if anything | Taken on a schedule and stored elsewhere |
| Knowledge of your site | Starts from zero each time, unless you reuse the same person | Builds up month by month |
| Budget | Unpredictable | Predictable |
| Commitment | None | Depends on the provider’s terms |
Sites where a one-time fix is usually enough
Pay-as-you-go is a sensible choice when most of these are true:
- The site is small, mostly informational, and changes rarely.
- It takes no payments and holds little customer data.
- Nobody is spending money on ads that send traffic to it.
- A day or two of it being broken would be an annoyance rather than a loss.
- You, or someone on staff, will reliably apply updates and check that backups exist.
That last point is the one people underestimate. Choosing one-time fixes is really choosing to do the routine work yourself. If nobody does it, the site drifts: plugins fall behind, the PHP version ages, and the next fix is bigger. Our post on what happens when a website stops being maintained describes how that drift tends to play out.
Sites where a care plan usually pays for itself
A monthly plan starts to make sense when any of these apply:
- The site earns money directly. A shop, a booking site or anything taking payments. An hour of broken checkout costs real orders.
- You run ads. If you pay per click, every click sent to a broken page is money spent for nothing.
- The site has many plugins. More plugins means more updates, more chances of two of them clashing, and more value in someone testing changes before they go live.
- Enquiries arrive through forms. A contact form that silently stops sending can lose leads for weeks before anyone notices.
- You have just had a serious fix. A site that needed rescuing often needed it because nothing routine was being done. Putting a plan in place afterwards stops a repeat.
How often each routine task should be done is a separate question, covered in our guide to how often a website should be maintained.
A simple way to decide: three questions
1. What does a broken day cost you?
Think of lost orders, lost enquiries, wasted ad spend and the time you spend dealing with it. You do not need an exact figure. You only need to know whether it is clearly more or clearly less than a month of maintenance.
2. Who will do the routine work if nobody is paid to?
Name a person. If the honest answer is “probably nobody”, a one-time fix is a plan to wait for the next breakage.
3. How many times has something broken in the last year?
Look back at invoices and messages. If you have paid for several fixes, add them up and compare them with a year of a plan. If you have paid for none, that is a point in favour of pay-as-you-go, as long as the routine work is genuinely being done.
Prices, and what to compare
Prices for both vary widely between providers, and the cheapest monthly plan is not automatically the best value if it covers very little. For reference, our own prices are ₹1,499/month onwards for a standalone retainer on a basic site, and ₹1,499 per incident onwards for a bug fix, with WooCommerce and larger sites priced separately. Whatever figures you are quoted, compare what is included, not only the number.
Questions to ask about any care plan
- Are updates tested before or after they go live, and on what?
- Where are backups stored, and how long are they kept?
- When was a backup last actually restored, to prove it works?
- Which fixes are included, and what counts as extra work?
- What will I receive each month to show what was done?
- Can I cancel, and on what notice?
- If I leave, do I keep my backups and logins?
Get the answers in writing. Our post on what belongs in a website maintenance contract explains how to turn them into terms both sides can hold to.
Questions to ask about any one-time fix
- Will you take a backup before you start?
- Will you tell me what caused the problem, not only that it is fixed?
- Is the price fixed before you begin, or charged by time?
- What happens if the same problem returns soon after?
- Will you tell me what else you noticed that may cause trouble later?
The answer to the last question is often the most useful part of a one-time job. A good repair comes with a short list of risks spotted along the way. That list is also the best evidence for deciding whether you need ongoing care.
Costs that do not appear on either invoice
Each option has a cost that is easy to miss when you only look at the bills.
With one-time fixes
- Your own time. Noticing the problem, finding someone free to look at it, sharing logins, explaining the history of the site, checking the result.
- The broken period. The hours or days between something failing and someone fixing it, often longer than you expect because the failure was not noticed at first.
- Bigger repairs later. Updates skipped for a year tend to arrive together, and fixing their combined effect is usually more work than applying them one month at a time.
With a care plan
- Paying for quiet months. Some months nothing visible happens. That is the plan working, but it can feel like paying for nothing.
- Checking the provider. You still need to read the monthly report now and then, and ask a question when something in it looks odd. A plan nobody reviews can quietly shrink to very little.
Mixing the two
You do not have to pick one for ever. Common, sensible patterns are:
- Fix first, plan second. A site that is broken today needs the repair before anything else. Get it working through a pay-per-incident bug fix, then decide about ongoing care once it is stable.
- Plan for the busy season. Some businesses keep a plan during the months when the site matters most and drop to one-time help in quiet months, if the provider’s terms allow it.
- Do it yourself, with a backstop. Handle updates and backups in-house, and keep the number of someone you trust for the jobs that go beyond your comfort.
Whichever you choose, write down who is responsible for updates, backups and monitoring. Plenty of website emergencies start in the gap where everyone assumed someone else was doing it.
The short version
If the site makes money, runs ads or depends on forms, a care plan is usually the steadier choice. If it is small, quiet and someone genuinely does the routine work, paying per fix is reasonable. When you are unsure, the one-time fix you need today often tells you the answer, through what it finds. Either way, the comparison is always against who would otherwise do the routine work.
If you want to see the plans and one-off prices side by side before deciding, our pricing page lists what each one includes.
