How to outsource web development: a guide for agencies

What is web development outsourcing?

Web development outsourcing means paying someone outside your agency to build a website, or part of one, that you then sell to your client. The client relationship, the brief and the price stay with you; they do the build.

For an agency it comes in three forms, and they behave very differently: a freelancer (one person), an outsourcing company (a development shop that sells its team’s time to anyone who needs it) and a white label partner (a studio that builds only for agencies, under the agency’s name). There’s a fourth option that isn’t outsourcing at all, which is hiring a developer. We’ve included it, because a fair comparison has to.

What you send out varies too. Usually the agency keeps strategy, the client relationship and often the design, and outsources the build: turning approved designs into a working site on WordPress, Shopify, Webflow or a custom stack. Some agencies send design and build together. If the design is leaving your agency as well, read how to outsource web design alongside this one.

Freelancer, outsourcing company, white label partner or a hire: which fits?

It depends on how regular your web work is and how much managing you want to take on. Each of the four wins somewhere and loses somewhere.

What are the benefits of outsourcing web development?

Why outsource web development at all? Mostly because web work comes in waves and salaries don’t. Each benefit comes with a condition.

• You pay only when there’s work, which helps only if the supplier can start when you need them. So ask about their lead time early.
• You can say yes to a Shopify store or a Webflow build without anyone in-house knowing the platform. You still need to know enough to scope it properly with your client.
• With a fixed price per project, you know your cost before you quote, so you can set your client’s price and your margin on day one. With hourly billing, you can’t.
• Your strategists, designers and account leads stay on the work your agency is known for. Someone still has to own the brief and the review.

What you give up is day-to-day control, and the knowledge that builds up when a developer sits in your team. You can win some of it back by keeping the work in your own accounts and asking for documentation at handover.

When should you not outsource web development?

Four cases where we’d say outsourcing is the wrong call, or at least not the right one yet.

• You can’t describe what you want yet. Without designs, a page list or any decisions, the brief is unclear, and an unclear brief gets you an unclear site and a bill for the changes. Scope it first.
• Nobody at your agency can review the result. Someone has to check the build against the design and the brief before your client sees it.
• Your client contract forbids subcontracting, or names the staff who’ll do the work. Read it before you brief anyone. If it’s silent, add a right-to-subcontract clause to your next contract: there’s one in the white label agreement template.
• You’re choosing on the lowest price alone. Rework and missed dates will cost more than you saved, and your name is on the result.

How to outsource web development, step by step

Eight steps, in this order. The first two happen before you speak to anyone.

1. Decide what to outsource.

   List what leaves your agency and what stays: design, build, content entry, testing, launch, care after launch. Keep the client relationship and the final sign-off. And start with one contained project; your largest account can wait until you trust the supplier.

2. Write the brief.

   Platform, page list and unique templates, the designs, features and integrations, who supplies copy and images, the browsers and devices to test on, and the deadline. If you’re sending designs, run them through the Figma handoff checklist first: missing states and mobile frames are where quotes go wrong.

3. Shortlist and vet two or three candidates.

   Ask each one for work on your platform, who will do the build, how they test and how they handle changes. Get the contract before the sales call, too. The vetting checklist below has the full list.

4. Agree the contract.

   Scope, price, the delivery date and what happens if it’s missed. Acceptance and defects. Who owns the work. Confidentiality, non-solicitation of your clients, and no passing the work on without your consent. The white label agreement template is a starting draft you can use with any supplier; have your lawyer review it.

5. Run a paid pilot.

   Give a new supplier one small, real job with a fixed scope and date (a landing page, one template, an audit), and pay for it. You’ll learn how they communicate, whether the date holds and what their build is like.

6. Set up accounts and communication.

   Create the accounts yourself and invite the supplier in: staging (a private preview link), the CMS, the code repository, your project board. Agree one channel, one contact on each side, the hours you overlap and a written update every week. Access you created yourself is access you can switch off.

7. Review, test and sign off.

   Review on staging against the design and the brief, on real phones. Send one consolidated list. Keep defects (it doesn’t match what was agreed) apart from changes (you want something new): defects should be fixed free, and changes priced before any work starts. Then approve in writing.

8. Launch and hand over.

   Before the final payment, check that the site, the code and the design files sit in accounts you or your client own, that you hold admin access and the documentation, and that the rights in the work have passed to you. Then remove the supplier’s access, or keep it for a care plan.

How much does it cost to outsource web development?

We’d look at the pricing model before the rate. There are three, and each one puts the risk of an overrun somewhere different.

We haven’t listed market rates. They swing with country, seniority and platform, and we haven’t found figures we’d trust. Send two or three candidates the same brief, ask each for a written quote, and compare those.

When you compare them, check what sits outside each price: hosting, domains, licences for plugins, themes and fonts, copywriting, stock images, content entry, and how many rounds of revisions you get.

What are the risks of outsourcing web development, and how do you control each?

Seven things go wrong often enough to plan for, and we’ve been on the buying side of most of them. When the work at our old agency outgrew the team, we tried several white label partners. With every one of them the agreed date drifted, and the bugs they shipped ended up on our desk. For each risk there’s something you can do about it, and a clause to put in the contract.

There’s a clause for each of these in the white label agreement template. It’s a starting draft, so have a lawyer look at it before you rely on it.

How do you vet a web development outsourcing company?

The same eight checks work for a freelancer, an outsourcing company or a white label partner. Ask for evidence, not adjectives.

• Work on your platform, built by the people who would work on your project.
• Who does the work: their own staff, or freelancers they pass it to.
• The contract, sent before you commit. Read non-solicitation, ownership and lateness first.
• A fixed quote against your brief, with what’s excluded written down.
• How they test: which screen sizes and browsers, and whether someone other than the builder checks.
• How changes are handled: quoted in writing first, and never started without your approval.
• Who you talk to, in which hours, and who covers when that person is away.
• Whether they also work for businesses directly, and what stops them working with your client.

The longer version, with the answers to look for, is the partner vetting checklist.