Key Takeaways

  • The in-house vs agency for AI marketing decision is not really about headcount or cost, it's about which side can rebuild its workflow fastest as the tools change under it every quarter.
  • Build in-house when AI marketing is core to your product story and your buyers expect you to be visibly ahead; hire an agency when you need a working system in ninety days and your team is already at capacity on the current plan.
  • The hybrid model most B2B SaaS teams land on: a small internal owner who holds the strategy, prompts, and brand voice, plus an agency that runs the build, the skills library, and the plumbing across HubSpot, Webflow, and GitHub.
  • The right test is not "can they do the work" but "can they show you their skills, their repos, and the last three things they shipped in Claude Code or a similar agentic tool this month."
  • Whatever you choose, put the work in GitHub from day one so the capability lives with the company and not on someone's laptop.

Many marketing leaders I talk to are stuck on a trick question. They ask whether to hire an AI marketer or two, create them from their own team, or bring in an agency that does AI work, as if this were the same build-vs-buy call marketers have been making for twenty years. It's not. The tools are moving faster than any hiring plan can keep up with, and the skills that mattered in July are already table stakes by November.

The way I think about whether to build AI marketing in-house or hire an agency isn't which one is cheaper or which one is faster. It's which one gives you a system that can be rebuilt every ninety days without breaking your brand, your data, or your team's confidence. That's the real question, and once you frame it that way, the answer looks different than most of the comparison posts on the first page of Google would have you believe.

I want to walk through how we think about this, the honest cases for each, the one where we'd tell you not to hire an agency at all, and a hybrid model that's quietly become the default for the B2B SaaS teams doing this well.

The old comparison is broken

The old comparison was straightforward. In-house meant a team of employees running your marketing from inside the building, close to the product, close to sales. Agency meant a group of specialists you rented by the month to do the things your team couldn't or didn't want to do. Indeed's guide on the two models still frames it that way, and it's a fine baseline if you're staffing a demand gen function in 2019.

But AI marketing is a capability, and capabilities have to be built and rebuilt. The real work is standing up an agentic system that writes, personalizes, publishes, and measures across your channels, using your voice, your data, and your brand tokens. That system has parts. It has skills files, prompt libraries, design tokens, a component system, source of truth in something like GitHub, and connectors into HubSpot or Marketo or whatever CMS you're on. It has a voice that has to be trained and refined every month as the models shift underneath you.

So when a marketing leader asks me in-house vs agency, my first question back is what they're actually trying to own — the output, or the machine that makes the output. Those are two very different asks, and the answer changes which side of the decision you land on.

A scene at the pivot

Here's why this matters in lived time. A year ago, a team I know well was running its content workflow off a shared Mural board and a rotating cast of freelancers. The board was the source of truth, briefs went out in Google Docs, drafts came back in Google Docs, and someone on the marketing ops side would paste the winners into the CMS on Fridays. It worked. It also took two weeks to move a campaign from idea to publish, and every piece sounded a little different because the voice lived in a PDF nobody re-read.

Last week the same team shipped a full campaign in a day. Not because they hired more people, but because the workflow had been torn down and rebuilt twice in the intervening months. The Mural board is gone. The Google Docs shuffle is gone. In its place is a repo with skills files, a prompt library the whole team edits, and design tokens that flow from a component system into the CMS without anyone pasting anything. The person who used to spend Fridays copying and pasting now spends Fridays writing new skills.

That's the shift. Not a faster version of the old workflow, a different machine underneath it. And the teams doing this well have rebuilt their internal stack two or three times in the last eighteen months, because each rebuild teaches something the next one bakes in. If you're evaluating in-house vs agency without a plan for the rebuild, you're evaluating the wrong thing.

The case for building in-house

Build in-house when AI marketing is not a supporting function but part of the story you're telling customers. If you're selling AI-native software to other marketing teams, you can't credibly outsource the thing your buyers expect you to be visibly ahead on. Your website, your campaigns, your sales collateral, they are all proof points, and your buyers will look at what you shipped last week and decide whether to trust you with their stack.

The harder case is when you have someone, usually a director-level marketer with a technical bent, who genuinely wants to be in Claude Code every day, who's curious enough to build skills, and who understands that this is a craft. That person is rare, and if you have one, keep them. Give them a budget for tools, a lane to experiment, and cover from the CFO when the first three months look messy. The Reddit thread on r/b2bmarketing has an honest read on this: internal stakeholders often listen to agencies more readily than they listen to internal experts, so your in-house person needs air cover to be heard.

There's also a version of this where your data, your customer conversations, and your product roadmap are moving fast enough that a weekly agency check-in creates lag you can't afford. That's the real cost of outsourcing at velocity. It shows up on the calendar, not the invoice.

The catch is that building in-house means committing to a rebuild cycle. The prompts, the skills, the workflow you set up in Q1 will need to be reworked by Q3. If you build in-house, budget for the rebuild, not just the build.

The case for hiring an agency

Hire an agency when you need a working system in ninety days and your team is already at capacity keeping the current plan running. This is where most B2B SaaS marketing teams actually are. The CMO has a mandate to "do more with AI," the team is stretched, and there's no one internally who's built a skills library or shipped a component through Claude Code into a headless site. Trying to learn all that in-house while also hitting pipeline targets is how you get a mediocre version of both.

The second reason is breadth of exposure. A good AI marketing agency is running through dozens of tool combinations across dozens of clients every quarter. They see what breaks, what scales, and what quietly gets deprecated. Marin Software's piece on managing digital marketing teams frames this as an access-to-expertise argument, and that's still true, it's just that the expertise now is less about media buying and more about which agentic workflow actually holds up in production.

The third reason is that hiring an agency lets you skip a generation of tooling. The teams doing this well have rebuilt their internal platforms two or three times in the last eighteen months, and each rebuild taught them something they now bring to client work on day one. You don't have to pay for those lessons twice.

The honest version of when NOT to hire an agency: don't hire one if you're looking for a headcount replacement and expecting the same person on your account for three years. That's not how this works anymore. The team you engage with should be rotating tools, rotating skills, and occasionally telling you the thing you built with them six months ago should be scrapped. If you want stability, hire in-house. If you want velocity and a willingness to burn down what isn't working, hire an agency.

The hybrid model that most teams actually land on

Here's what I keep seeing with the B2B SaaS teams doing this well. They hire one senior internal person, usually a director of marketing operations or a head of content with a technical streak, and they give that person ownership of the strategy, the brand voice, and the prompt library. That person is the keeper of the taste. They decide what "on brand" means when the model gives back three versions, and they hold the relationship with the rest of the org.

Then they bring in an agency to run the build. The agency stands up the skills, the component system, the GitHub repo, the connectors into HubSpot or Webflow, and the measurement layer. The agency also holds the rebuild cycle, because they're seeing what's working across other accounts and can move faster than any single internal team.

The internal owner and the agency work in the same repo. This is the part most teams miss. If your agency is delivering finished assets over email or Dropbox, you're not building a capability, you're renting output. If they're committing to a GitHub repo you own, with pull requests you review, you're building something that lives with the company even if the agency relationship ends.

Both Socialq.us and Ironhack land in similar territory when they describe the tradeoffs each pure model forces on the people inside it: in-house gets depth of context but narrow tool exposure, agencies get breadth but shallow product knowledge. Hybrid is how you stop making that trade.

How to actually evaluate an AI marketing agency

If you're leaning toward hiring, the evaluation criteria have changed. Case studies and client logos are the old test. The new test is: show me your skills repo, show me your last three commits, show me a prompt you wrote this week that you're proud of. If the agency can't show you the work at that level of specificity, they're selling you the 2019 version of themselves.

Ask what tools they've killed in the last six months. A good AI shop is opinionated and willing to walk away from a stack that isn't holding up. Sharp Instincts makes a related point about how in-house teams tend to get comfortable with what they know, and that comfort becomes a liability when the tools change this fast. The same test applies to agencies: if they can't name what they've killed, they're probably still running it.

Ask how they handle brand voice at scale, and whether they use voice tokens or just paste style guides into prompts. The former is real infrastructure, the latter is theater. And ask them to walk you through how they'd stand up your first workflow, in specifics, not slides. Any agency worth hiring should have a written point of view on how they build, not just what they've built.

The next shift we're watching

The rebuild cycle is going to compress again. What's a quarterly rebuild today will be a monthly rebuild by next fall, and the teams that survive that pace are the ones who put the work in a repo they control from day one. Keep the prompts and skills in files you can read. Make sure the person on your side who holds the taste is a full-time employee, not a contractor. If you want to see the artifact we hand clients on day one, it lives at the Mighty and True Blueprint. Everything else is negotiable.

Frequently Asked Questions

Is it cheaper to build AI marketing in-house or hire an agency?

Neither is reliably cheaper once you account for tool churn. In-house looks cheaper on the spreadsheet but hides the cost of rebuilding your stack every two quarters. Agencies look more expensive per month but amortize the rebuild across clients. The right question isn't cost, it's which model gives you a working system in the timeframe you need.

What size company should build AI marketing in-house?

If you're under fifty employees and marketing is not your product, don't try to build in-house. You won't get the depth of tooling exposure. From about fifty to five hundred employees, hybrid is the sweet spot. Above five hundred, if AI is central to your positioning, in-house with agency support for specific builds tends to work.

How do I know if my agency is actually doing AI work or just adding it to their pitch deck?

Ask them to open their laptop and show you a live workflow. Ask what's in their GitHub. Ask which skills they wrote this month. If the answers are vague, or if everything is described at the level of "we use AI to make things faster," they're marketing AI, not doing it.

Can one senior hire replace an agency for AI marketing?

Rarely. One person can hold strategy, voice, and taste, but the build surface is too wide for a single hire to cover well. Content, design system, component library, CMS integration, measurement, and the rebuild cycle every quarter is more than a job. It's a small team's work.

Sources