Choosing between an agency, a freelancer, and a builder
When each option is right, and the trade-offs nobody admits to upfront.
Three different ways to get a website built. Each has a place. The wrong choice for your situation is the most expensive mistake in this category.
The builder route
You sit down with Framer, Webflow, or Squarespace and build it yourself.
Cost: $0-50/month in subscription, 40-100 hours of your time depending on scope.
Right when: budget is tight, you have design instincts, the project is small and well-defined, and you don't mind learning curves.
Wrong when: you don't have design experience, the project is complex, your time is worth more than a freelancer's hourly rate.
The hidden cost is opportunity cost. Many founders spend 80 hours building a website that they could have got a freelancer to do for $3K, while their actual job (the business) waited. The math rarely works out in favour of DIY when you account for what else you could be doing.
The freelancer route
You hire one person — designer, developer, or generalist — to build the site.
Cost: $2K-25K depending on scope and experience level.
Right when: the scope is well-defined, the timeline is reasonable, you can manage the freelancer (briefs, feedback, scope control), and the freelancer's skills match the work.
Wrong when: the project needs multiple specialisations (design + dev + content + strategy), the scope keeps growing, you don't have time to project-manage.
The hidden cost is that you become the project manager. Freelancers don't manage themselves into a successful project; you do. If you can't or won't, the freelancer route fails not because of the freelancer but because of the management gap.
The agency / studio route
You hire a team that handles design, development, project management, and often strategy.
Cost: $15K-200K depending on scope and reputation.
Right when: the project is meaningful to the business, you want one accountable team, you have budget for craft, you'd benefit from outside strategic perspective.
Wrong when: the project is small (you're paying for overhead you don't need), you have strong opinions on every detail (you're paying experts to override), or you need it done in two weeks (studios book months ahead).
The hidden cost is decision velocity. Agencies want approval, milestones, sign-offs. If you need to ship in days, the process is overhead. If you have time, the process is a feature — it ensures things don't get missed.
How to decide
Score the project on three axes:
Scope complexity. Simple landing page vs. multi-page, CMS-driven, integrated with your systems.
Strategic stakes. Will this site materially affect the business? A coffee shop's homepage is one bar; a SaaS company's pricing page is another.
Your time and skills. Do you have 60 hours and the design instincts to DIY? Or is your time and judgment better spent elsewhere?
Simple + low stakes + you have time = build it yourself. Medium + meaningful + you can manage = freelancer. Complex + high stakes + budget exists = studio.
Most teams default to the option they're most comfortable with rather than the one the project requires. Bias check: notice which one you find yourself rationalising toward, and ask whether it's actually the right fit.