When you decide to build or rebuild something on the web, the second question after "what are we building?" is usually "who's going to build it?" There are three common answers — freelancer, agency, or in-house developer — and each has a different profile of cost, control, risk, and output quality.

This isn't a pitch for any of them. The right answer depends on what you're building, how much you're spending, and what your working style is.

The freelancer

The case for it: A good freelancer is often the most cost-effective way to get high-quality work done on a focused project. You're paying for skill and time without the overhead of an agency. If the project is well-defined and you have a clear brief, a freelancer with the right experience can deliver excellent results.

The trade-off: Availability. A solo operator has limited bandwidth, and if your project expands or they get busy with other clients, your timeline is the first casualty. There's also no bench — if the person you're working with doesn't have a particular skill, there's no colleague to fill in.

Best fit: Defined, bounded projects. A new website. A landing page. A specific feature. Projects where the scope is clear and the execution doesn't require multiple specialists working in parallel.

What to watch for: Freelancers who take on more than they can handle, agree to everything, and disappear when it gets complicated. The same red flags apply here as anywhere — know how to vet who you're talking to before you commit.

The agency

The case for it: An agency brings structure, a team, and defined process. Multiple people with different specializations working on the same project. Account management so you're not solely dependent on one person's calendar. An established approach for discovery, design, development, and launch.

The trade-off: Cost and overhead. Agencies have more people to pay, more coordination to manage, and often more process than small projects need. Not all of that overhead adds value. You're also not always talking to the people doing the work — account managers are a layer between you and the developers, which can be good or frustrating depending on the agency.

Best fit: Larger or more complex projects where multiple disciplines need to work in parallel — strategy, design, and development at the same time. Projects with institutional clients that need a formal vendor relationship.

What to watch for: Agencies that pitch well and hand off the actual work to junior staff you never met. Ask who specifically will work on your project before you sign anything.

In-house

The case for it: Alignment. An in-house developer or team knows your business, your systems, and your priorities. They're available on demand. No onboarding cost on every new project. Deep institutional knowledge builds over time.

The trade-off: Fixed cost. Salaries, benefits, equipment, and management overhead exist whether you have work or not. A full-time developer in the $80,000–$120,000+ range is a large commitment for a business that doesn't have continuous development work. And if you only need a few projects a year, that's expensive capacity to carry.

Best fit: Businesses where software is a core, ongoing part of operations — SaaS companies, large e-commerce, businesses with complex internal tools that need constant iteration. If you're shipping features every week, in-house is worth it.

What to watch for: Hiring in-house before you have enough ongoing work to justify it. A developer with nothing to build is a developer looking for problems to over-engineer.

The hybrid reality

Most businesses don't fit cleanly into one box. A common pattern that works well: hire one strong in-house developer to own your core platform and day-to-day needs, and engage outside help (freelancer or small agency) for specialized projects — a major redesign, a specific integration, a campaign microsite.

The in-house person understands the business. The outside team brings bandwidth and specialty. Each fills what the other lacks.

The honest read

For most early-stage and small businesses, the choice is between a freelancer and a small agency. In-house is a later-stage move.

A freelancer makes sense when the scope is clear and the project is bounded. A small agency makes sense when you need more hands, more structure, or higher-stakes execution. A boutique shop that's really a solo operator with close collaborators often splits the difference.

The variable that matters most is actually none of the three options — it's the clarity of your brief. A well-defined project can succeed with any staffing model. An underspecified one will struggle with all three.