Freelancer vs agency for website maintenance: which is safer?

Your website has to keep working next year and the year after. Someone must update it, fix it when it breaks and make the changes your team asks for. The choice is usually a freelancer you may already know or a dedicated web development partner with a team behind it.

The short answer on freelancer vs agency for website maintenance is this: the safer option is the one where a single absence cannot stop your site and where you own the accounts and the code. A freelancer can meet that bar on a small, stable site. A partner meets it more easily when the site earns revenue or changes every week.

This guide gives you four risks to check, a table that matches your site to an arrangement, a way to compare cost per outcome with your own numbers and a contract checklist. Many freelancers are excellent, and the goal is to show where the risk sits so you can decide with open eyes.

Freelancer vs agency: the short answer#

Safety is a question of how much of your site's health depends on one person, one inbox and one set of passwords. Freelancers and agencies can both fail that test, and both can pass it. What changes is how much effort it takes to pass.

Safety comes down to four risks#

Four risks decide the outcome. Bus factor is how many people can fix your site. Coverage hours are when someone answers. Access and ownership is who holds the keys. Documentation is how quickly a stranger could take over. The next section turns each one into a question you can ask today.

When a freelancer is a sound choice#

A freelancer fits when the site presents the company, changes a few times a year and costs you little if it waits a day or two for a fix. A ten-page company site on WordPress or Webflow that gets a new case study each quarter is a typical example. You talk directly to the person doing the work, overhead is low and they learn your site deeply.

Add a written handover and accounts in your name, and most of the remaining risk is covered.

When a dedicated partner is the safer choice#

A partner fits when a stopped site costs you sales or bookings within hours. It also fits when changes arrive weekly, or when the site touches payments, customer data or integrations with your CRM or ERP. The reason is not that agencies write better code. A team gives you cover for holidays, illness and busy weeks, with a shared queue and documented work.

Four risks to check before you sign#

Each risk below comes with one question. Put it to any candidate, freelancer or agency, and write down the answer before you decide.

Bus factor: what if one person is unavailable#

Bus factor is the number of people who can be lost before the work stops. With one freelancer it is one. An illness, a holiday, a new full-time job or a closed business, and your site has nobody. Ask who covers during absences and whether that person has ever seen your site.

Agencies have a higher bus factor on paper. Ask for names: a team of five where only one person knows your site gives you the same exposure with a larger invoice.

Coverage hours and response time#

Coverage hours are the hours someone is on duty. Response time is how long a human takes to reply. A freelancer in another time zone can be perfectly fine for a Tuesday change and out of reach during your busiest weekend. Ask for the response target in writing, and for what counts as an incident.

The diagram below follows the same Friday failure handled by one person and by a team with a shared queue.

Friday failure

1. 01Site breaks FridayCheckout or forms stop working

• ASingle personDown until Monday
  1. Message sentNo reply comes
  2. Person unavailableSite waits for the weekend
• BTeam with shared queueBack within hours
  1. Alert and triageSomeone on duty picks it up
  2. Fix and reportSite restored, summary sent

A Friday site failure splits into two paths: a single person who is unavailable so the site waits, and a team that alerts, triages, fixes and reports

Access and ownership of accounts and code#

Ownership means your company, not your supplier, is the account holder for the domain, hosting, platform workspace, code repository, analytics and backups. When access sits in someone's personal account, leaving them costs weeks. Ask for admin roles under your own email, with the supplier added as a user.

The same applies to code. Custom themes, plugins and Next.js applications should live in a repository your company owns. The questions to ask a web development agency work just as well for a freelancer.

Documentation that lets anyone take over#

Documentation is a short written record of how the site is built, hosted, deployed and backed up, plus a log of what changed and why. It does not need to be long. One page of architecture, a list of plugins, apps and integrations with their purpose, and a change log are enough for a competent developer to start within a day.

Ask to see a sample from another project with the client details removed. A supplier who keeps notes already will have one ready.

Decision table by criticality and change volume#

Match your site to one row and one column. The table shows the arrangement that usually carries the least risk, and you can read the rating guides first.

How to rate your site's criticality#

Choose the row that describes what happens when the site is offline for a working day:

• Brochure: it presents the company, and a day offline costs little.
• Lead engine: forms and calls come from it, so hours offline lose enquiries.
• Revenue-critical: a store, bookings or subscriptions, where an hour offline loses sales.
• Regulated: it handles health, financial or personal data and carries compliance duties.

How to rate your change volume#

Count the requests you sent to your developer over the last three months. Rare means a few edits a year. Monthly means new content or small features. Weekly means campaigns, product launches, tests or integrations that keep your developer busy every week.

Reading the table#

Hybrid means a freelancer and an agency sharing the work, described in the hybrid models section below. For regulated sites the partner column is a starting point: check the obligations that apply to you with your legal adviser, then ask each candidate how they meet them.

If you sit between two rows, pick the higher one. The cost of one extra level of cover is usually smaller than the cost of one bad Friday.

Cost of freelancer vs agency maintenance#

Compare cost per outcome, not rate per hour. An outcome is a site that stays up, stays patched and ships the changes you asked for. The invoice is only one part of it.

What the hourly rate leaves out#

Hourly billing charges for work done. It does not charge for being available. Incident hours arrive as unplanned invoices, and quiet weeks cost nothing, which also means a busy freelancer may have no free time at the moment you need it.

There is a second cost that never appears on an invoice: every hour the site waits for help. The hidden cost of every web platform covers hosting, maintenance and technical debt in more depth.

What a monthly plan bundles#

A monthly plan charges for availability and routine work together: updates, backups, monitoring and a response commitment. Updates matter because weaknesses in common software are well documented. The WordPress security documentation and the OWASP Top 10 list the typical ones.

Monitoring after each change belongs in the bundle too. For example, checking Core Web Vitals, Google's measures of loading speed, visual stability and responsiveness, on web.dev shows whether an update slowed your pages.

For a brochure site that rarely changes, option A is often the cheaper and perfectly adequate choice. The worked example below shows why.

A worked example with your own numbers#

Use these two formulas with your own quotes:

• Hourly: (planned hours + incident hours) × rate + hours of downtime × cost of one hour offline.
• Monthly plan: monthly fee × 12 + extra hours × rate + hours of downtime × cost of one hour offline.

The figures below are invented, round numbers for illustration only. They are not market rates and not werun.dev prices. Assume a rate of 50 per hour, 48 planned hours a year, two incidents a year with 20 hours of repair work in total, and a monthly plan of 400 that covers incident work. The freelancer takes 24 hours on average to start on each incident. The plan team takes 3.

The same two arrangements swap places depending on what an hour offline costs you. That is why the answer is about your site rather than the type of supplier. Put your own cost per hour of downtime in the formula, ask both suppliers for a quote, and the answer appears. For the build side of the budget, see the custom WordPress website cost breakdown.

Contract checklist: access, repos, handover, SLA#

Whichever you choose, put the terms in writing. SLA means service level agreement: the response and fix targets your supplier commits to. A freelancer can sign these terms as easily as an agency, and a good one will welcome them.

Access and ownership terms#

The contract should say that the domain, hosting, platform workspace, analytics and repository belong to your company. The supplier holds user roles, not owner roles. Backups are stored where you can reach them, and a restore is tested at least twice a year, so you know they work before you need them.

Handover and documentation terms#

Require handover notes after each significant change, and a short architecture page kept up to date. Set a notice period long enough to hire a replacement, and an exit clause that includes a handover session. These terms cost the supplier little while they work with you and save weeks if they stop.

Response and reporting terms#

Ask for a response target by severity: site down, feature broken and small request each deserve their own time. Name the coverage hours and the backup contact. Add a monthly report of updates applied, incidents, uptime and requests closed, so you see the health of the site without asking.

Use the list below to check your current agreement line by line.

• Domain, hosting and platform accounts are registered to your company
• The code lives in a repository your company owns
• Backups are stored outside the supplier's accounts and restores are tested
• Handover notes are delivered after each significant change
• Response targets are written by severity, with named coverage hours
• A backup contact is named for absences
• The notice period includes a handover session
• A monthly report shows updates, incidents and closed requests

Hybrid models that spread the risk#

You are not forced to pick one side. Three combinations lower the risk when the budget is tight or the team is small.

Freelancer with an agency as backup#

Keep your freelancer for day-to-day work and agree on a backup agency that has the documentation and can step in during incidents or absences. You pay a small standby fee or an hourly rate only when it is used. This suits lead engines with rare or monthly changes.

Partner for upkeep, freelancer for projects#

Let a partner handle updates, backups and monitoring on a monthly plan, and hire a specialist freelancer for one-off builds such as a redesign or a custom plugin. The partner keeps the site healthy while the freelancer builds. Make sure both work in the same repository and share one change log.

In-house editor with a partner behind#

Your marketing person edits content every day, and a partner covers the technical layer: updates, integrations, performance and incidents. This works well on Webflow and Shopify, where editors can do a lot without a developer. Requests that need code go to the partner through a single channel.

What the werun.dev Care plan and Retainer include#

werun.dev acts as a dedicated partner on WordPress, Webflow, Shopify and custom Next.js applications. Two monthly engagements cover the time after launch, and you can see how they fit together on the engagements page. The exact scope is written into your agreement.

Care plan: keeping the site healthy#

The Care plan is monthly maintenance: updates, backups, monitoring and fixes when something breaks. You send requests through the client panel, where you also see projects and invoices. We reply in under 2 hours on business days, and for WordPress the post on who fixes broken updates goes into the detail.

Retainer: keeping the site improving#

The Retainer is for ongoing improvements: new pages, features, integrations and tests. With Client Feedback you click any element on the site and ask for a change, so you never have to describe it in an email. werun.Experiments then lets real visitors pick the winner of an A/B test.

How both answer the four risks#

Here is how the two plans address each risk from earlier:

• Bus factor: a team works from a shared queue and shared notes, with 200+ sites looked after over 12+ years.
• Coverage and response: a reply in under 2 hours on business days.
• Access and ownership: we work to the terms in the checklist above, and you can ask us to confirm them in writing.
• Documentation: a written monthly report and a client panel with every request on record.

If a freelancer fits your site better, we will tell you. A small, stable site rarely needs a team, and a plain handover is worth more than a plan you do not use.

Where to start this week#

Run the four-risk audit on your current arrangement. It takes about an hour.

1. List who can fix your site today and who covers their absence.
2. Check whose name is on the domain, hosting, platform and repository.
3. Find the last handover note or change log, and ask for one if it does not exist.
4. Write down what one hour offline costs you, and rate your site in the decision table.

If the answers show a gap, tell us your goal and we will build the way there. Start with the engagements to see the monthly options, or contact us and describe your site. You will hear back within 2 hours on a business day.

Frequently asked questions#