Web development studio, agency, or freelancer?

Choose a freelancer for a clearly bounded website when one capable person can cover the work and you are comfortable owning more of the coordination. Choose a larger agency when the project needs several specialists, formal stakeholder management or substantial capacity at the same time. Choose a small web development studio when you want direct access to the people making the site, but need the build to combine scope, design and technical decisions.

None of those labels guarantees quality. “Agency”, “studio” and even “web developer” are not protected job titles. A two-person studio can call itself a full-service agency. A freelancer can coordinate a trusted group of specialists. A large agency may assign a compact senior team. The useful comparison is therefore not prestige or team size. It is how the work moves from your brief to a working website.

Model	Strongest fit	What you need to verify
Freelancer	A focused assignment one person can deliver	Availability, skill coverage and handover
Webdesign specialist	Visual direction, UX or a supplied design brief	Who handles development, content and launch
Full-service digital agency	Brand, content, marketing and web work running together	Which services are truly in scope and who executes
Web development studio	A focused custom site or web product with direct maker access	Capacity, specialist partners and support after launch
In-house team	Continuous product work with enough demand for permanent roles	Hiring time, management and the expertise still missing

First, separate the labels from the work

Clients often begin with “we need a web agency” when they actually need one of several different things:

• a clearer story and better website structure;
• a visual redesign;
• front-end and back-end development;
• a standard company website configured in an existing CMS;
• a custom booking flow, platform or integration;
• ongoing content, SEO or paid campaign management.

Those are not interchangeable jobs. A beautiful design file is not a deployed website. A technically strong build does not automatically explain the offer. “SEO included” may mean anything from editable metadata to a full research and content programme.

Before comparing suppliers, write one sentence that describes the result:

We need a website that helps this audience understand this offer and take this action, with these content, integration and maintenance requirements.

That sentence is more useful than deciding in advance that you need a freelancer or agency. It reveals which responsibilities must exist, whether one person can realistically hold them and what your own team still needs to supply.

What hiring a freelancer really means

A freelancer gives you a direct relationship with one independent professional. That can make decisions quick and communication unusually clear. When the scope matches the person’s strengths, it is an efficient model.

A freelancer is often the right choice when:

• the assignment is narrow and can be completed sequentially;
• you already have the strategy, copy or design;
• one specialist skill is missing from your internal team;
• you can make decisions and manage dependencies yourself;
• the launch does not require several disciplines working in parallel.

The main constraint is not professionalism. It is finite coverage. One person has one calendar and a particular range of skills. A developer may need you to provide design. A designer may build with a standard platform rather than custom code. Someone who can do both may still rely on another specialist for copy, accessibility review or complex back-end work.

Ask what happens outside their core expertise. A good answer can be “that part belongs with someone else.” A clear boundary is safer than one person promising strategy, brand, copy, design, development, SEO, hosting and permanent support at equal depth.

Continuity also deserves a practical conversation. You do not need a dramatic worst-case scenario. You need access, documentation and a handover that lets another capable professional understand the work.

What a webdesign bureau or specialist optimises

A webdesign partner usually begins with how the website communicates visually and how someone moves through it. That can include research, information architecture, user experience, interface design and a design system. Some webdesign bureaus also develop every site they design. Others hand the approved design to an internal or external development team.

This model fits when visual repositioning is the largest part of the problem, especially when:

• the current identity does not translate to digital;
• several page types need a coherent design system;
• user research or prototyping must happen before development;
• your own developers can implement the result;
• stakeholders need to approve the visual direction before a build starts.

The handoff is the point to inspect. Who decides whether a component is practical, responsive and accessible? Who covers interaction states that are not visible in a static design? Who checks the implemented pages against the intended system?

At The Brand Refresh, design happens in the build instead of moving through a separate design department. We can also implement a design a client already has, or introduce a designer when a project genuinely needs a separate design phase. That is one operating model, not a universal rule. A formal design lane is useful when many stakeholders need to align before engineering begins.

What a full-service digital agency is built to do

A digital agency becomes valuable when the website is one part of a broader programme. It may combine brand strategy, campaign concepts, copy, SEO, paid media, analytics, development and ongoing account management.

Choose that breadth when the coordination itself is valuable. For example, a rebrand, content production and multi-channel launch all have to happen together, or several departments need one accountable partner and a formal review process.

The trade-off is that you are buying an organisation as well as deliverables. Account management, workshops, internal reviews and specialist handoffs can reduce risk on a large programme. They can also be unnecessary overhead for a focused website.

Clarify which version you are hiring:

1. Is the work completed by permanent specialists, external partners or a mixed team?
2. Will you speak to the designer and developer, or mainly to an account manager?
3. Does “full service” describe real capability or a list of services the agency can resell?
4. Which work ends at launch, and which work becomes a retainer?

There is nothing inherently wrong with layers. The question is whether your project needs them.

What makes a web development studio different

“Studio” usually signals a deliberately smaller, specialist practice, but the name alone proves nothing. The useful version sits between a solo freelancer and a broad agency: direct contact with the people making technical and design decisions, enough range to take responsibility for the whole website, and a scope kept narrow enough to move quickly.

A web development studio is a strong fit when:

• the website needs custom structure or functionality;
• design and development choices need to happen together;
• you want to brief the person who will make the work;
• the project benefits from a lean decision process;
• you need a complete launch, but not a full outsourced marketing department.

The studio model has real limits. A small team cannot pretend to have infinite parallel capacity. It should be honest about which specialists are internal, which are brought in when needed and which work it does not offer.

That is where The Brand Refresh sits. We are a small Amsterdam studio focused on sharp custom websites and web products. We scope tightly, design while we build and keep contact close to the work. A focused custom website starts at €500 excl. VAT. A Strapi CMS, webshop or more involved web product costs more because the system and testing are larger. Paid ads are available when they fit the client and the site is ready, but we are not a full-service marketing agency disguised as a web team.

Web design and web development are different responsibilities

Web design shapes the hierarchy, interface, visual system and experience. Web development turns those decisions into a responsive, accessible and maintainable website, including the front end, content model, integrations and deployment where required.

On a small project, one person can perform both responsibilities. On a complex product, design, front-end development, back-end development, content, accessibility and quality assurance may each need focused attention.

The dangerous assumption is that one automatically includes the other. Ask suppliers to mark each responsibility in the proposal:

Responsibility	Questions to ask
Positioning and structure	Who turns our business context into a page hierarchy?
Copy and assets	Who writes, edits and supplies final content?
Visual design	Is it bespoke, adapted or supplied by us?
Development	What is custom-built and what depends on a platform?
CMS and editing	What can our team safely change after launch?
Accessibility	Who checks keyboard use, semantics and contrast?
Search foundations	Who handles crawlability, metadata, redirects and structured data?
Launch and support	Who owns deployment, fixes and future updates?

W3C treats accessibility as work that needs planning, responsibility and monitoring throughout a project, not a plugin applied at the end. Performance and search readiness work the same way. Core Web Vitals depend on the finished implementation, while Google’s SEO Starter Guide makes clear that useful structure and content matter alongside technical discoverability.

“Included” is not a sufficient answer. Ask what will actually be done and how you will verify it.

Compare responsibility, not just price

Quotes become hard to compare when every supplier defines “a website” differently. One price may include discovery, copy editing, custom development, analytics setup and launch support. Another may cover only page assembly from supplied material.

Compare the boundary of responsibility:

• Who turns the brief into a usable scope?
• Who chases missing content and decisions?
• How many page types and states are included?
• Which integrations are working at launch?
• Who tests mobile, forms, browsers and accessibility?
• Who handles redirects and preserves important URLs?
• What support exists after deployment?
• What counts as a change or extra work?

A low-overhead model can offer strong value because less budget is spent on internal coordination. It can also shift that coordination to you. A larger proposal can remove work from your team, or simply add process. Read the scope until you can tell which.

Price should follow the job. It should not be used as a shortcut for judging quality.

Eight questions to ask before you sign

1. Who will actually do the work?

Ask to meet or identify the people responsible for structure, design and development. A strong sales conversation does not tell you who will make the key decisions after kickoff.

2. What do you need from us?

Content, imagery, approvals and system access often determine the schedule. The answer should make your own workload visible.

3. What is not included?

Exclusions reveal more than a long feature list. Ask specifically about copy, content entry, CMS, search migration, analytics, cookie consent, hosting and support.

4. Which parts are custom?

Custom can describe the visual styling, a theme configuration, the code or the complete content system. Make the term concrete.

5. What can we change after launch?

Editing should match the recurring work. A team publishing weekly needs a different CMS from a founder changing a phone number twice a year.

6. Who controls the accounts and assets?

Your organisation should know where its domain, DNS, hosting, analytics, repository, design files and CMS accounts live. ICANN’s registrant guidance is a useful reminder that domain registration carries explicit rights and responsibilities. Record access before launch, not during an emergency.

7. What happens when something breaks?

Ask for the practical route: who receives the message, what support is included and how urgent work is handled. Do not assume that “maintenance available” means a guaranteed response time.

8. How do we leave?

A professional relationship should survive a clean exit. Confirm access, export options, source files, documentation and any ongoing licences in writing.

When each model is the wrong fit

Do not hire a freelancer if the project depends on several specialists working at once and you cannot coordinate them. Do not hire a design-led partner without establishing who owns implementation. Do not hire a full-service agency for one focused build if you will resent every layer of its process. Do not hire a small studio when your procurement, compliance or delivery requirements need a large dedicated team.

And do not build an in-house team for a one-off redesign. In-house becomes logical when the website or product needs enough continuous work to justify permanent ownership, not because outsourcing feels less controlled.

The strongest supplier is not the one that claims to cover every possibility. It is the one that can explain where its model fits, where it stops and how the work remains usable after handover.

The decision in one sentence

Choose the smallest operating model that can take real responsibility for the result without making you coordinate the gaps.

For a bounded specialist task, that may be a freelancer. For a broad brand and marketing programme, it may be a full-service agency. For continuous product development, build in-house. For a sharp custom website with direct contact and a lean process, a web development studio can be the right middle ground.

If that last route matches your project, see how we build custom websites, compare custom work with templates and page builders, or tell us what the site needs to do.