Agency vs freelancer for web design: which is right?
A freelancer is the right call for a small brochure site with a clear brief and someone in-house to direct it. An agency earns its cost when the site has to carry search infrastructure, integrations, and accountability for lead volume after launch, work that spans more disciplines than one person sustains.
What you are actually buying in each case
With a freelancer you are buying execution. You bring the brief, the decisions, and the review cycle, and a skilled person produces the thing. When the brief is clear and someone internally can direct the work, this is efficient and often excellent.
Where freelance projects most often stall
Rarely on design. The usual failure points are the parts that are not design: schema written into templates, a performance budget actually met, form routing that survives contact with the office, redirects mapped page by page, and measurement that continues after launch.
Where agencies waste your money
On projects that needed five pages and a clear brief. If you know what the site should say, have no search ambitions, and simply want it built well, agency process is overhead with no return.
Continuity, and what happens in month four
Most contractor websites are not finished at launch; they are started. Position has to be maintained, content added, forms adjusted, and the reporting read and acted on. The question that separates the two options is who does that in month four.
The honest decision framework
Count the pages, count the integrations, and count the disciplines. One or two of each points to a freelancer. Search infrastructure, multiple templates, tracked lead routing, and accountability for lead volume point to an agency.
A cheaper way to decide
An audit costs a fraction of a build and settles the argument, because it produces the page architecture, the keyword and competitor map, and the location matrix as a document you own.