Who Builds Websites? Roles on a Real Web Development Team

A real web project has at least five distinct roles: project manager, designer, frontend, backend, and QA. If one person tells you they handle all of it, they’re doing some of it badly.

Here’s what each role does and how many you actually need based on project size.

The “webmaster” misunderstanding

The solo “webmaster” died fifteen years ago. A mid-sized website in 2026 requires visual design, accessibility, performance, security, technical SEO, infrastructure, databases, and at least two programming languages. Nobody is senior in all of that.

When someone pitches as a one-person full-stack webmaster, one of three things is true: they’re senior in one or two areas and junior in the rest, they’re using templates and plugins to cover the gaps, or they’re subcontracting without saying so. None of those are automatically bad. But you should know what you’re buying.

We covered the bigger picture in what is web development. This post drills into the roles.

The required roles

These five exist on any serious project, even if one person covers two.

Project Manager (PM). Owns the schedule, runs meetings, coordinates between client and tech team, blocks scope creep. If there’s no PM, somebody else is doing that job poorly (usually a senior dev who bills twice as much to sit in meetings).

UI/UX Designer. Defines how the site looks and how it works. UX (how it works) and UI (how it looks) are different skills. On small teams the same person covers both. On larger teams they’re two people. On why this role isn’t cosmetic, see the role of UX in software.

Frontend developer. Codes everything you see in the browser. HTML, CSS, JavaScript, frameworks like React, Vue, or Astro. In 2026, a good frontend dev also knows accessibility, performance, and technical SEO.

Backend developer. Codes what you don’t see: API, database, authentication, business logic. If your site has login, payments, dashboards, or any data that changes, you need backend.

QA (Quality Assurance). Verifies things work before production. Manual for complex flows, automated for regressions. Most broken projects we inherit never had real QA. Just “the dev tests their own code”, which is not QA. Self-testing is a known anti-pattern: the person who built the feature is the worst person to find the holes in it, because they think the same way they thought when they built it.

For small sites, one person can cover two roles (PM + design, or frontend + backend) and an external provider (5e Labs, another agency) can run targeted QA. But all five roles exist whether or not you see them on the org chart.

Roles that help but aren’t required

These show up when the project grows.

DevOps / SRE. Manages servers, deploys, monitoring, scaling. For a site running on Vercel or Netlify, you don’t need a dedicated DevOps. For a web app with real traffic and SLAs, you do.

SEO specialist. Keyword research, on-page optimization, link building. If the site exists to capture organic traffic, you need this role. If it’s institutional presence only, you don’t.

Copywriter / content strategist. Writes copy that sells and ranks. Most quotes assume you provide content. When you ask the agency to handle it, this role gets added.

Accessibility specialist. Audits and fixes WCAG 2.1 AA. Mandatory for legally regulated sites (US public sector, ADA). For the rest, ideally the frontend dev handles it.

Data analyst. Sets up GA4, events, conversion dashboards. For e-commerce, nearly required. For a corporate site, optional.

What a team of 1, 3, and 8 looks like

Team of 1 (freelancer): one person handles PM, design, frontend, backend, and self-tests. Works for landings and small sites where you control scope and can review the code. High risk if the person vanishes.

Team of 3 (small agency): PM/designer, frontend, backend. QA is handled by the PM or subcontracted. Fits corporate sites, platform-based e-commerce, projects up to about $20k. The most common size in Costa Rica.

Team of 8 (serious project): PM, UX designer, UI designer, two frontends, two backends, QA, DevOps. This is what a web app, a SaaS, or a custom e-commerce build actually needs. Costs more, but ships faster with less rework.

If a vendor wants to charge $30,000 with a one-person team, something is off. If they want $30,000 with a team of 8 over four weeks, the math holds.

When to build an in-house team vs use staff augmentation

After staffing several teams in Costa Rica, this is what we see:

In-house team works if you have continuous workload (more than one full-time developer for 12+ months), a tech lead who can hire and onboard, and patience for the 3-6 months it takes the team to hit stride.

Staff augmentation with 5e Labs works if you need capacity now, not in 6 months; if the project has a clear end date; if you handle technical direction and just need hands; or if you want to try a developer before bringing them on full-time. That’s exactly what we covered in what is technical staff augmentation, applied to web work.

There’s a third option: hire a turnkey agency. We covered that in how much a website costs in Costa Rica. For one-off projects with closed scope, it’s the right call. For sustained product growth, it isn’t.

If you’re missing one of these roles for your project, tell us which one and we’ll send profiles in five business days. Tell us the role you’re missing →