FREEFirst project with us? Your landing page design is on the house.See the offer

Process

In-house hire or agency?

In-house web hire or agency? A fair comparison for marketing leads, with a 4 week request log, a full cost formula and the cases where hiring clearly wins.

By Abdul QuadirUpdated 2026-11-147 min read
TL;DR
  • Hire in-house when the site has a full week of work, every week, and depends on deep product knowledge.
  • Use an agency when the work comes in bursts, or needs skills that one person rarely has.
  • Log your requests for 4 weeks before you decide. Guessing the workload is an easy way to choose wrong.
  • Compare the full cost of a hire, including recruiting, tools, management and cover when they are away.
  • Many teams end up with both: an owner on staff, plus outside help for the build and the overflow.

The short answer

Hire in-house if your website has enough work to fill a full week, every week, for the foreseeable future, and that work needs close contact with your product and team. Use an agency if the work comes in bursts, needs a mix of skills such as design, build and SEO, or you need it going within weeks. In both cases, one person on your staff should own the site.

We are an agency, so read this knowing that. Hiring really is the better answer for some teams, and we have written down which ones.

This is a different question from agency or freelancer

If you already know you want outside help and are choosing who, read agency vs freelancer or Kookies vs a freelancer. If you have decided to hire a Webflow person, read how to hire a Webflow developer.

This post is for the step before: should this work sit inside your company at all?

Side by side

In-house hireAgency
Knows your productDeeply, over timeLearns it, and depth varies
Time to startRecruiting and onboarding firstOften within weeks
Skill rangeUsually one or two strong skillsSeveral people with different skills
Cost patternFixed salary, busy or quietPer project or per month, can stop
When they are awayWork stops unless someone coversSomeone else usually picks it up
Day to day contactIn your meetings and channelsThrough a queue or set calls
Biggest riskToo little work, or they leave with the knowledgeLess context, more briefing
ManagementYou manage a person and their growthYou manage requests and quality

When hiring is the better answer

  • The work fills the week. Pages, tests and fixes are steady enough to keep one person busy.
  • The site is close to the product. Signup flows, in-app pages or docs that need the product team every day.
  • Speed of small changes matters most. Someone in the room can fix a thing in minutes.
  • You have someone to manage them. A lone web developer with no technical lead can get stuck, and often leaves.
  • Your rules require it. Some companies limit outside access to systems. Check yours.

If most of those are true, hire. An agency would be an awkward and costly stand-in for a person who should be in your team.

When an agency is the better answer

  • The work comes in bursts. A big build, then a quiet stretch, then a launch.
  • You need several skills. Design, build, copy, SEO and tracking are rarely found in one person.
  • You need it soon. Recruiting takes time you may not have.
  • The site is a marketing site, not the product. It needs care, but not a person's full week.
  • You are not sure yet. You can stop an agency much more easily than you can reverse a hire.

Run the 4 week log

It is easy to guess this wrong, so measure it. For 4 weeks, write down every website request, including the ones you did not ask for because you knew nobody had time.

RequestSkill neededRough hoursHow urgent
New webinar landing pageDesign, buildTo be filled inDate fixed
Fix a form that stopped sendingBuildTo be filled inToday
New pricing tableDesign, build, copyTo be filled inThis month

Then read it:

  • Total hours. If the log would fill most of a working week, every week, a hire starts to make sense. If it fills a few days a month, it does not.
  • Skills. If no single person could do most rows, a single hire will leave gaps.
  • Shape. Even or spiky? Salaries suit even work. Outside help suits spikes.

Compare the real cost

Salary is only the first line. We have left out figures here, because pay varies too much by country and level. Fill in your own.

  • Hire: salary + taxes and benefits + recruiting + tools and licences + manager's time + months before they are fully useful + cover or outside help for skills they lack.
  • Agency: monthly or project fees + your time writing briefs and reviewing + a bit of extra time for context.

For the agency side, our own figures are public. A care plan is $4,000 a month, or $3,000 a month on a 6-month term, and hourly work is $35 an hour. A project gets a fixed price before work starts. Compare any figures over 12 months, and include what happens in your quiet months. If a hire comes out ahead on a full cost and your log shows the workload, that is a strong sign to hire.

The mix that often works

This is rarely all or nothing. Three common setups:

  1. Owner plus agency. A marketer owns the site and the priorities. An agency does the design and build. This is the simplest setup for a small team.
  2. Hire plus specialists. Your web developer runs daily work. Outside help comes in for a redesign, a migration or SEO work.
  3. Agency first, then a hire. An agency builds the site and its section system. Once the log shows steady work, you hire, and that person starts with a clean system instead of a blank page.

Whichever you choose, write down who owns what after launch. A site without a named owner drifts, whoever builds it.

Plan your exit either way

Good arrangements can be left without drama. Before you start:

  • All accounts sit under your company, not under the person or the agency. See who owns my website.
  • The site uses a documented class system or component library, so that another developer can work on it.
  • Key decisions, tools and logins are written down in one place.
  • If a person leaves or a contract ends, you could brief someone new within a day.

What to do next

Start the 4 week log today, and fill in the cost lines with your finance lead. If the log points to a hire, go and write the role. You will know exactly what the job is, and you can show the log to candidates.

If it points to outside help, choose between a project and a subscription next. If you would like a second opinion on the log, send it to us on a free 20 minute call. If it says you should hire, we will say so.

Abdul Quadir
Abdul QuadirFounder of Kookies. Builds Webflow and Astro sites for startups and growing teams.

Terms used: Webflow, Core Web Vitals

FAQs

Questions
people ask.

Abdul Quadir
Still have a question?Ask us directly. We reply within a day.
Book a callPick a timehello@kookies.io

It depends on the workload. A hire is often better value when work fills every week. An agency is often better value when work comes in bursts, because you are not paying through quiet months.

When a 4 week request log shows steady work that fills most of a working week, and someone can manage that person. Before that, outside help is usually easier to start and to stop.

For daily changes, often yes. For design, build, copy, SEO and tracking together, one person rarely covers all of it, so plan for outside help on the gaps.

Yes, and many teams do. A common split is an owner on staff who sets priorities, with outside help for builds, migrations and overflow.

Someone on your staff, usually in marketing. They set priorities and sign off the work, while the agency does it. All accounts stay under your company.

It is easy if the accounts are yours and the site uses a clear class system or component library. Ask for a handover call and written notes before the contract ends.

Your turn

Let's kook
what you krave.

Hi Kookies, I need a built on . I'd love to launch . Reach me at
or book a callSent. We reply within one working day.