When to Hire a Web Design Agency - and When Not To
Signals it is time to hire a web design agency versus keep work in-house: scope, SEO risk, conversion failure, and when a retainer is the wrong first buy.
From the archive. First published January 29, 2024.
Not every project needs an agency. Some will fail without one. The decision is capacity, budget, and risk, not whether agencies are “worth it” in the abstract.
Here’s a framework that stays useful when the pitch deck is closed.
Hire an Agency When
- You need a full rebuild: Strategy, design, development, and technical SEO in one flow. Split vendors and you become the integration layer. Handoffs drop redirects, tracking, and the pages sales actually uses.
- You lack the bench: No one on staff owns Core Web Vitals, conversion architecture, and a CMS migration. One generalist or a freelancer who “does WordPress” won’t cover IA, engineering, and launch QA.
- Stakes went up: Brochure site to lead engine. New product line. Site is in the sales cycle and the current one leaks. Complexity and downside both rose. You want weekly delivery, not a nights-and-weekends side project.
- You want one throat to choke: One partner, one backlog, one staging URL. When something breaks after launch, you don’t referee designer vs. developer vs. SEO. Full-service exists for this.
Don’t Hire an Agency When
- It’s a small fix: A landing page, a form field, a banner. In-house or a freelancer. Agency kickoff overhead will cost more than the work.
- You won’t fund it: A proper rebuild takes budget and calendar. Half a rebuild, new homepage, old templates, no redirects, wastes both. If the number only covers “a refresh,” buy a refresh. Don’t dress it up as a transformation.
- You’re sampling SEO: SEO compounds over months. If you’re testing whether organic is even a channel, buy a technical audit, not a 12-month retainer. A retainer without a backlog and a ship cadence is a subscription to PDFs.
- Nobody inside can decide: Agencies don’t replace a product owner. If legal, sales, and marketing will each veto in week eight, hire a facilitator or delay. You don’t have a vendor problem. You have a decision problem.
Capacity, Budget, Risk
If two of three are true, no capacity, you can fund a real build, a bad launch would hurt, you probably hire.
Capacity
Do you have a designer and a developer and someone who can own SEO and analytics for 8–15 weeks without dropping the day job?
If the answer is one person and a contractor in another timezone, you don’t have capacity. You have hope.
Also count review time:
- Weekly demos: Need a decision-maker with 2–3 day turnaround.
- If that’s you and you’re in back-to-back sales: The timeline will slip even with a great team.
- Content owner: Separate from the signer if possible. Otherwise both jobs stall.
Budget
Price the fully loaded internal path: salaries, contractors, tools, the month you ship late, the ranking drop if redirects are amateur. Agency fees look large until you add that.
Then pick the engagement shape:
- Build only: Rebuild, handoff, you maintain.
- Build plus retainer: Site, then SEO/conversion cadence.
- Overflow: You have a team. You need a hard slice (migration, design system).
If budget only covers design files, stop. Files without a build and launch plan are a souvenir.
Risk
What’s the downside of a bad launch?
- Lost inbound: Forms break. Nobody notices for a week.
- 404 month: Organic you spent years on, gone.
- Sales sends PDFs: Because the site can’t be trusted.
High risk argues for a team that has run migrations and weekly staging, not the cheapest bid.
Low risk (internal tool, tiny brochure, no organic to protect) argues for cheaper, smaller help.
The Middle Ground
Common splits that work:
- Agency builds, you maintain: They ship the system and the documentation. You own day-to-day pages. Works if you have a capable CMS owner after handoff.
- You build, agency owns growth: Strong internal web team; weak content/SEO operating system. Don’t force a redesign into that contract.
- Agency for the hard slice: Migration, headless, design system. Then freelance for extras.
Match the model to the gap.
- Don’t buy a full-service retainer because the homepage is tired.
- Don’t DIY a rebuild because last year’s freelancer was cheap.
Unsure? Map pages, integrations, reviewers, writers, and what happens if launch slips. The gaps are the hiring brief.
What we build now
Lead systems for high-ticket contractors and custom portals for growing teams.
Contractor lead systemsCustom portalsPricingBook paid discovery