Website Maintenance Plans: How to Price Them and Build Recurring Revenue

Abstract website window with a circular refresh arrow, a check mark and rising bars, in navy with orange accents.

Most freelance web designers run on a feast-and-famine cycle. A project lands, you work flat out for six weeks, the invoice clears, and then you are back to prospecting with an empty calendar. The way out is not a bigger pipeline alone. It is a base of small, predictable monthly payments from clients you have already won.

A website maintenance plan is the simplest version of that base. Done well, it gives clients something they genuinely need and gives you income that does not reset to zero every month. Done badly, it becomes unlimited free support at a price that never covered your time. This guide shows how to scope, tier, price and sell a plan, with the contract wording and tracking that keep it profitable.

Why recurring revenue changes how your business feels

A $3,000 project and a $100 monthly plan look nothing alike on one invoice. Over time they behave very differently. Project income is lumpy and depends on you finding the next client. Plan income arrives whether or not you sold anything this month, so it covers your fixed costs and lets you say no to a bad project.

There is also a client-side logic. A small business owner who paid for a website has no idea whether it is being backed up, whether the contact form still works, or whether the plugin that got flagged last week was patched. They do not want to learn. A plan lets them hand the worry to someone they already trust. That is a service people will pay for monthly, and it is much easier to sell to an existing client than any new project is to sell to a stranger.

This also changes your acquisition maths. If you are working through our guide to where web design clients actually come from, you will notice that referrals and repeat work are the cheapest sources. A maintenance relationship keeps you in front of a client every month, which is when referrals and upgrade projects happen.

What a maintenance plan should (and should not) include

Before you set a price, decide what the plan is. Across the agency and care-plan pages we reviewed, the core of a plan is consistent: backups, updates, uptime monitoring, security checks and some form of reporting. Sources such as Redefine Web and FatLab describe the same baseline, and they are explicit that it covers recurring operational work, not new development.

The core, in plain language for clients

The core of a plan

Notice what is missing: new pages, redesign work, ongoing SEO campaigns, unlimited edits. Those are different services with different pricing. The most common reason maintenance plans fail is that the boundary between a plan task and a project is never written down.

The small bucket of changes

Most clients also want to change a phone number, swap a photo or update opening hours. Rather than promising unlimited edits, include a small bucket: for example, up to an agreed number of minutes or a set number of small requests per month. State what counts as small, and state that unused time does not roll over. Some providers add a discounted hourly rate for anything beyond the bucket, which turns an awkward conversation into a menu.

Decide on hosting up front

Hosting is often a separate line item from maintenance. If you resell hosting, you take on uptime responsibility and the support that goes with it. If you do not, you still need to specify who owns the hosting account and who pays. Write it into the plan description so a client never assumes a $75 plan includes a server they have not paid for.

How to structure tiers

Three tiers is the usual pattern because it gives clients a middle option and gives you an anchor. Resist the urge to build five. Each extra tier is another thing to explain, track and support.

What changes between tiers

BasicGrowth
Backups, updates and uptime monitoring✓✓
Monthly report✓✓
Included small changes each month✗✓
Faster response commitment✗✓
Quarterly performance and search check✗✓
Priority scheduling for larger fixes✗✓

In practice, a clean structure looks like this:

Basic covers the protection layer only: backups, updates, monitoring and a report. It is for clients who rarely change their site and mostly want peace of mind.

Standard adds the bucket of small changes and a quicker response commitment. This is the tier most small local businesses should land on, and it is the one to make your default recommendation.

Growth adds a periodic review, a quarterly check of speed, search visibility and conversion paths, and a short list of recommended improvements. It is for businesses that depend on the site for leads and want a partner, not just a caretaker. If you already run audits as part of your sales process, as covered in website audits that win web design clients, this review is the same skill applied to a client you already have.

How to price a plan

Published benchmarks give you a sanity check, not an answer. Vendor guides we looked at put basic maintenance-only plans somewhere around $25 to $150 a month, plans with some support and hosting at roughly $100 to $300, and ecommerce or larger sites well above that. One FatLab pricing guide breaks the market into budget, professional, business and enterprise bands. The spread is huge because scope is huge. A $30 plan and a $300 plan may differ more in what they promise than in how much work they involve.

Start from your time, not the market

Work out what a month of care actually costs you. Track the real time for a typical client over a few months: monitoring review, updates, backup check, report, and the small requests that arrive. Then price from that.

Price for the risk you are accepting

A plan is not just time. You are on the hook when an update breaks a checkout or the site goes down on a Saturday. Part of the price is insurance for that risk. This is why plans for simple brochure sites should cost less than plans for booking systems or ecommerce, even when the monthly hours look similar.

Annual billing and discounts

Offering an annual option at a modest discount improves cash flow and retention. Keep the monthly option as the default so the decision stays easy. Whatever you choose, never discount by adding unlimited scope. Discount by changing the billing period, not the promise.

Price the plan and the original build together, because a low build price with no plan means you carry the long-term support for free.

The mistakes that make plans unprofitable

The first is the worst. A plan with vague edit language slowly turns into a part-time job paid at a fraction of your rate. Define small in minutes or request counts, and offer a clear path to buy more.

The second is scope drift. Clients will ask for a new page and call it maintenance. Have one sentence ready: "That is a small project; here is the quote." Having that sentence in your contract makes it routine instead of confrontational.

The third is silence. If a client pays $100 a month and hears nothing, they will eventually cancel because they cannot see value. A short monthly report that lists what was backed up, what was updated and what you recommend is the cheapest retention tool you have.

How to sell it to clients you already have

The best time to introduce a plan is before the project ends, not after. Put it in the proposal as an option with the launch price, so it reads as part of how the site stays healthy rather than an afterthought. Our guide to selling a website to a small business owner covers the objection patterns, and the same ones show up here: "I can just do it myself," "I will call you if something breaks," "that seems like a lot for nothing."

Introducing the plan

  1. Mention it in the proposal: List the plan as an optional line next to the build price, with a one-sentence description of what it protects.
  2. Show what happens without it: Describe, factually, what unmaintained sites run into: outdated components, expired certificates, forms that quietly stop working.
  3. Recommend one tier: Do not present a menu cold. Say which tier fits their business and why.
  4. Offer a trial start date: Start billing on launch day, with the first report due a month later.
  5. Confirm it in the contract: Attach the plan terms to the agreement so scope and cancellation are on paper.

For clients who declined a plan at launch, a small-scale audit is a natural way back in. Run a health check on their site and send the findings. Tools like Leaddly's health and SEO scans produce an audit you can reference, so the conversation starts from something concrete rather than "are you sure you do not want a plan?"

Running the plans without drowning in admin

Plans are only profitable if the admin is light. Three habits matter most.

Use a standard schedule. Batch client updates on a fixed day each month. Doing the same tasks in the same order across clients is far faster than reacting individually.

Track the time. Log what each client's plan actually takes. After three months you will know which clients are profitable, which are not, and where your tiers need adjusting. Leaddly includes time tracking and invoicing, so recurring plan work and extra-hours billing can sit alongside the original project in the same client record.

Keep the paperwork consistent. Plan terms should come from a template you reuse, not a document you rewrite for each client. Leaddly's contracts and templates exist for exactly that reason, and its client CRM keeps renewal dates, notes and plan tiers attached to each client.

A plan client, month by month

  1. Launch day: Site goes live; plan begins; baseline backup taken and logged.
  2. End of month one: First report sent, with updates applied and any recommendations.
  3. Month three: Review time spent against the plan; adjust the bucket or the tier if needed.
  4. Month six: Send the audit-style check-in and propose any improvement project.
  5. Month twelve: Renew terms, review pricing and offer annual billing.

Growing from plans to a steady base

A few plans do not replace project income, but they change what project income has to do. If monthly plans cover your core costs, a slow month is an inconvenience, not a crisis. Each new site you launch then adds a little more to that base.

Plans also feed your pipeline. Clients on a plan trust you, see your work monthly and refer you more often. They are also the easiest source of upgrade projects. And a cleaner pipeline makes outbound more optional: if you use lead scanning to find local businesses with weak sites, you can use it to fill gaps rather than to survive. For the broader system, see how to find local web design clients.

A simple launch plan

If you have no plans today, do not start by designing a perfect offer. Start with the clients you already have.

Write a one-page description of two tiers. Pick your five most recent clients. Send each a short message offering the plan with a specific start date. Track the replies. Even two signups will teach you more about scope, pricing and admin than another month of planning.

After a quarter, you will know how long plan work really takes, what clients actually ask for, and where to raise the price. Then add the third tier and make the plan a standard line in every proposal you write.

Frequently Asked Questions

How much should I charge for a website maintenance plan?

There is no single right number. Published benchmarks from vendors range from roughly $25 to a few hundred dollars a month for small sites, with ecommerce higher, but those prices reflect very different scopes. Track the real time a typical client takes, add a margin for the months when something breaks, and price from that.

What should a maintenance plan include?

Verified backups, tested updates with a rollback path, uptime and SSL monitoring, basic security checks and a short monthly report. Many plans also include a small bucket of content changes. New pages, redesigns and ongoing SEO are separate services.

Should I include unlimited edits?

No. Unlimited edits tend to turn into unpaid work. Define small changes by minutes or request count, say that unused time does not roll over, and offer a clear rate for anything beyond the bucket.

Do I need to provide hosting?

Not necessarily. Hosting is often sold separately. If you do not provide it, state who owns the account and who pays. If you do, be clear about the uptime and support you are taking on.

When should I offer a plan to a client?

Ideally in the original proposal, as an optional line item, and again at launch. For past clients without a plan, a short check-in with specific observations about their site is a natural way to reopen the conversation.

More from Leaddly