The short answer
- The right web delivery model follows scope, dependency, risk, and ownership—not supplier size or job title.
- A freelancer can be the strongest choice for bounded work that matches one person’s proven capability and capacity.
- An agency can reduce client coordination when strategy, content, design, engineering, migration, and assurance must move together.
- An internal owner remains necessary because no external supplier can make every proposition, evidence, priority, and governance decision.
- A hybrid model can combine client knowledge, external integration, and specialist scrutiny when no single delivery category covers the work.
Start with the operating problem, not the supplier label
A web design agency and a freelancer are commercial labels, not guarantees of competence, quality, availability, or fit. A freelancer may lead complex programmes through a trusted network, while an agency may allocate only a small delivery team. Compare the named people, responsibilities, evidence, capacity, decision process, and contract—not assumptions attached to the category.
A freelancer is often appropriate when the release has a clear boundary, one primary craft, few integrations, an available client decision-maker, and tolerable continuity risk. An agency becomes more useful when research, positioning, content, information architecture, interface design, engineering, accessibility, analytics, migration, and launch assurance are interdependent. In-house capability is stronger when the website changes continuously and must remain close to product, sales, operations, or regulated knowledge.
A hybrid is a legitimate option. A business might retain proposition, evidence, product ownership, and publishing internally; use an agency to integrate discovery, design, and build; and appoint an independent accessibility, security, or search specialist for consequential assurance. The correct boundary is the smallest team that can cover the real work without hiding coordination or operational risk.
- Name the website’s commercial and user job before naming a supplier type
- Separate one-off release work from ongoing publishing, optimisation, support, and governance
- List required disciplines, then identify who integrates decisions across them
- Treat internal decision time and subject knowledge as part of the delivery model
- Use the companion UK website cost guide to test scope assumptions after choosing the model
Compare agency, freelancer, in-house and hybrid delivery
Use the matrix as a discussion prompt rather than a score that automatically selects a winner. Each row describes a typical structural tendency; actual suppliers can operate differently, and evidence about the proposed team should override category assumptions.
Ask every option to respond to the same brief and risk register. A cheaper or larger option is not more suitable unless it covers the required outcomes, client dependencies, acceptance evidence, ownership, and live operation on comparable terms.
| Decision factor | Freelancer | Agency | In-house or hybrid |
|---|---|---|---|
| Bounded specialist task | Strong when one person’s demonstrated craft matches the whole task | Can work, but coordination overhead may be unnecessary | Use internal delivery when capability and capacity already exist |
| Multi-disciplinary release | Requires explicit partners, interfaces, and one integration owner | Often suited when several disciplines must be managed as one release | Hybrid can retain product ownership while external specialists deliver defined workstreams |
| Decision and coordination load | Client commonly coordinates adjacent content, technology, and approval work | Agency can integrate work, but the named lead and escalation path still matter | Internal owner coordinates knowledge, priority, approval, and supplier boundaries |
| Continuity and capacity | Key-person availability and contingency need explicit treatment | Team cover may reduce key-person dependency, but staff allocation can change | Employment continuity is not automatic; document knowledge, repositories, and handovers in every model |
| Assurance and regulated risk | Commission independent review when one specialist cannot credibly assure every area | Ask which checks are internal, independent, automated, manual, included, or excluded | Hybrid assurance can separate delivery from consequential accessibility, privacy, security, or legal review |
| Ownership and exit | Contract for rights, source files, accounts, documentation, and support after completion | Confirm subcontractors, licences, repositories, hosting, handover, and exit assistance | Keep organisation-controlled accounts and avoid dependency on one employee or external supplier |
| Continuous website operation | Retainer or repeat commissioning can work when demand is predictable | Managed service can combine support and planned change with defined service levels | In-house or hybrid can suit continuous daily publishing and product learning |
Contract for the work, risk and exit you actually need
Commissioned work does not automatically become the commissioner’s copyright. UK Intellectual Property Office guidance says the creator is normally the first owner unless rights are agreed otherwise in writing. The agreement should address background intellectual property, new work, licences, assignments, fonts, imagery, code dependencies, source files, adaptation, portfolio use, territories, duration, and third-party restrictions. This guide is procurement information, not legal advice.[1]
A freelancer’s employment status for tax is determined by the real engagement, not the label in a contract. HMRC’s Check Employment Status for Tax tool gives HMRC’s view from the information supplied. Businesses should assess each arrangement accurately and obtain professional advice where the position matters; the tool does not choose the best creative operating model.[2]
Where a supplier processes personal data on the client’s behalf, the controller–processor relationship and required terms need to be identified. The ICO’s detailed contract guidance is currently marked for review following the Data (Use and Access) Act, so verify the latest position before signing. NCSC supplier-assurance questions can support proportionate security due diligence, while WCAG 2.2 supplies testable accessibility criteria rather than proof that one supplier category is accessible by default.[3][4][5]
- Name the actual team, subcontractors, specialist reviewers, allocation, and substitution rules
- Define deliverables, responsibilities, dependencies, decision windows, acceptance evidence, and change control
- Keep domains, analytics, hosting, repositories, platform accounts, and recovery routes under appropriate client control
- Plan URL mapping, redirects, canonicals, analytics, and monitoring when a redesign changes structure or domain[6]
- Specify warranty, support, incident response, documentation, data return or deletion, and supplier exit
Illustrative worked example: a content-led B2B website replacement
This example is illustrative and hypothetical; it is not a Blancc client result, supplier recommendation, price, schedule, or performance forecast. A UK B2B company needs to replace an ageing marketing site. The release includes proposition work, fifteen structured service and insight pages, a reusable design system, CMS migration, CRM-connected forms, accessibility testing, redirects, analytics continuity, and staff publishing training.
One experienced designer-developer could create the interface and build, but the client would still need to lead positioning, produce and approve content, define CRM behaviour, manage migration, and commission specialist assurance. A full-service agency could integrate more of that work, but only if the proposal names credible content, engineering, accessibility, migration, and delivery responsibility. Hiring an internal team solely for the release would create a continuing employment commitment before the future workload is understood.
The hypothetical business selects a hybrid structure: an internal product owner controls decisions and accounts; an external integrated team runs discovery, information architecture, design, engineering, and migration; client subject experts supply evidence; and an independent specialist reviews priority accessibility journeys before acceptance. After launch, publishing stays internal while the external team provides bounded support. This arrangement is not universally better—the example shows how work boundaries can decide the model.
- Release characteristic: several dependent disciplines and a consequential migration
- Internal responsibility: proposition truth, evidence, approvals, accounts, and operational ownership
- External responsibility: integrated discovery, design, build, migration, and documented handover
- Independent responsibility: risk-based assurance with findings and remediation evidence
- Limitation: different capability, risk, workload, or client capacity could justify a freelancer or in-house team
Common web supplier selection failure modes
The most common failure is comparing portfolios and headline fees without comparing the release boundary. Attractive screenshots do not reveal content responsibility, decision quality, accessibility, code maintainability, migration discipline, or what happens when a live form fails. A proposal is comparable only after inclusions, exclusions, client effort, external costs, assurance, and operation are normalised.
Another failure is outsourcing ownership with delivery. The business still owns the accuracy of its proposition, claims, personal-data purposes, customer experience, and operational response. External teams can facilitate and challenge those decisions, but cannot manufacture missing evidence or accept accountability on behalf of the organisation.
- Choosing by day rate without comparing total work, coordination, and operating cost
- Assuming an agency supplies every discipline or a freelancer supplies only one discipline
- Allowing a supplier to own the only domain, repository, hosting, analytics, or recovery account
- Leaving content, redirects, accessibility, privacy, security, analytics, training, or support outside every scope
- Treating certifications, automated scans, or a portfolio as sufficient acceptance evidence
- Beginning visual design before the audience, offer, evidence, journeys, content, and constraints are usable
- Migrating URLs without a complete old-to-new URL map, permanent redirects, canonical checks, and post-launch monitoring
Practical selection checklist, method and limitations
This guide uses an operating-model method: define the release and live service, map disciplines and dependencies, assess client capacity, compare coordination and continuity risk, specify assurance, contract ownership and exit, and score like-for-like proposals. The method synthesises current primary guidance and editorial analysis; it is not first-party research, legal or tax advice, an endorsement of a supplier type, or a guarantee of quality, cost, delivery time, rankings, enquiries, or revenue.
The public guidance has different scopes. HMRC and ICO materials address specific legal or regulatory questions; WCAG defines accessibility criteria; NCSC offers security assurance prompts; and Google’s site-move documentation explains search migration practices. None ranks agencies against freelancers. Supplier competence, chemistry, capacity, market conditions, technology, organisational maturity, and the accuracy of the brief can change the appropriate answer.[2][3][4][5][6]
- Write one common brief covering outcomes, audiences, content, systems, migration, assurance, operation, and exclusions
- Map every discipline and dependency to one named responsible owner and one acceptance decision
- Ask for the proposed people, relevant evidence, capacity, subcontractors, contingencies, and escalation route
- Normalise fees, client effort, VAT treatment, licences, external reviews, support, and first-year operating costs
- Review employment-status, intellectual-property, privacy, accessibility, security, and contractual questions with appropriate specialists
- Verify client-controlled accounts, documentation, data return or deletion, handover, warranty, support, and exit before signing
- Choose the model whose evidence and boundaries best fit the work; retain a hybrid option when no single category covers it responsibly
Sources and further guidance
Blancc uses primary guidance where factual or regulatory context matters. Recommendations remain general and should be assessed against the specific business, audience, product, and risk.
Read Blancc’s editorial standards and corrections policy for source selection, illustrative labels, update dates, software assistance and corrections.
- UK Intellectual Property Office: Ownership of copyright works
- HM Revenue & Customs: Check employment status for tax
- Information Commissioner's Office: Contracts and liabilities between controllers and processors
- National Cyber Security Centre: Supplier assurance questions
- W3C Recommendation: Web Content Accessibility Guidelines 2.2
- Google Search Central: Site moves and migrations