Key takeaways
- The salary comparison is the wrong comparison. US private employers spend about 43 cents on benefits for every dollar of wages, before a laptop, software seats or a desk.
- One in-house hire isn't one agency. A content program needs strategy, writing, editing, SEO and design, which is four or five skill sets in one job description.
- In-house wins on product knowledge and availability. Agencies win on breadth, speed to full output and the option to stop.
- For most B2B software companies under 100 people, the honest answer is a hybrid, with one senior owner inside and production and search bought outside.
Most in-house vs agency decisions get made on a spreadsheet with two columns, a salary in one and a retainer in the other, and the salary wins. That spreadsheet is missing most of the cost, and it also assumes one hire can do the work of a team.
Build the comparison properly and a different answer falls out for most B2B software companies under a hundred people, one senior content owner inside, with production and search bought outside. Yes, I run an agency, so weigh this accordingly, though you'll notice I'm not arguing for all-agency either.
What an in-house hire costs once you add everything
A content marketer's salary is the part everyone budgets for, and the rest turns up later.
Benefits come first, and they're bigger than most people guess. In June 2026, US private employers spent an average of $14.07 an hour on benefits against $32.82 in wages, according to the Bureau of Labor Statistics, so benefits add about 43% on top of pay. Then there's equipment, a laptop, a second screen and a desk if you have an office, or a home-working allowance if you don't. Software comes next, which for one content person means an SEO platform, a writing tool, a design subscription, stock imagery and a seat on whatever analytics stack you already run, small individually and a line item together.
Add space if you have any, recruitment fees or your own time spent hiring, and cover when they're on leave, which for a team of one means output stops. Run your own numbers rather than trusting a figure from a blog post (this one included), but run them before you compare anything.
You're hiring a team, not a person
The skills gap surprises people more than the benefits bill. A content program that produces search traffic needs someone who can do keyword research and read a results page, someone who can write well about a technical product, someone who can edit other people's writing, someone who knows technical SEO well enough to argue with your engineers, and someone who can make a graphic. Google's own page on hiring an SEO lists site and content review, technical advice, content development, keyword research and generative AI work as separate services, and job ads routinely ask for all of that under one title and one salary.
People who can do all five exist, and they're expensive, in demand and rarely looking. What you usually hire is someone strong at one or two who'll learn the rest slowly, on your budget.
None of that argues against hiring. It argues against comparing one hire to a full agency team as if they're the same thing.
Where in-house wins
Plenty, and it'd be dishonest to skip it. Someone sitting in your standups hears the roadmap change, the support tickets and the objection that came up in three sales calls this week. They're available the minute something urgent lands, and they build relationships with your engineers, which is usually the difference between getting technical review and not getting it.
Over a long enough horizon, in-house is also cheaper per asset once the person is up to speed. The catch is the horizon, and I'd budget six months or more before a new content hire reaches full output, longer on a technical product.
If what you need is someone in the room every day, an agency is the wrong buy, and that goes for us too. Our Primary Source Content model pulls the insight out of an hour or two of interviews a month, which covers a lot, but it doesn't replace a person who hears the standup.
Where agencies win
Breadth, first. A retainer buys a strategist, writers, an editor and an SEO at once, which is the team you'd otherwise hire one person at a time over two years.
Speed to full output is the underrated one. An agency that already works in your category produces usable work sooner, because it has already paid for the category learning curve, and most of the CMS vendors we've written for never had to explain what a headless CMS was. When Storyblok brought us in to supplement its internal content team, the brief was making headless CMS concepts land with CEOs and CMOs rather than developers, and our years in the CMS space meant the time went on that instead of on learning the category. The Storyblok case study covers what came out of it.
The advantage nobody says out loud is that you can stop. Ending a retainer is a conversation, while ending employment is a process, and in most places a slow and costly one. That asymmetry is worth money when you're not yet sure content is the right bet, which is exactly when most companies are making this decision.
Long engagements don't pile up employment costs
The common objection is that a multi-year retainer ends up costing more than the hire would have. Sometimes it does, but what it buys is different.
We worked with dotCMS for four years on exactly that basis, working insight from its co-founder and CRO into the content rather than replacing its team, and the articles we wrote are now worth an estimated $172k+ a year in traffic value, meaning what dotCMS would otherwise spend on ads for the same clicks. Magnolia CMS ran a three-year partnership with us alongside its own content team, and that content now saves Magnolia an estimated $34,000 a year in paid search.
Neither company carried the overhead of the team that produced that work, with no benefits, no equipment, no desks, no cover during vacations and no rehiring when someone left. The output compounds, and the employment obligations never pile up alongside it. The rest of that work is on our case studies page.
Four questions that settle in-house vs agency
Do you know what to publish?
If you can't name the twenty topics worth owning, hiring a producer is premature. That's a strategy problem, and it's cheaper to buy strategy than to hire someone to work it out.
How much do you publish?
My rule of thumb is that below about four assets a month a full-time hire is underused, and somewhere past eight to ten a month a retainer starts costing more than a small team.
How specialized is your product?
Deeply technical products favor in-house, because context is expensive to transfer, unless the agency already works in your category, which changes the math entirely.
How certain are you?
If content is still an experiment, buy the reversible option. If it's a channel you've already proven, build.
The answer is usually both
For most B2B software companies under a hundred people, the setup that works is one senior person inside who owns strategy, holds the relationships with product and sales and edits the work, with production and search bought outside. You get the context of in-house and the breadth of an agency, and it fails less often than either extreme, since pure in-house stalls when your one person leaves and pure agency stalls when nobody inside owns the outcome. If you go this way, sketch the roles before you post the job, and how to structure a content marketing team walks through the options.
Compare the retainer to the full cost of the hire
Put the retainer next to the full cost of a hire, never next to the salary. Add salary, benefits, equipment, software, space and the months before full output, and the decision usually makes itself in one direction or the other. If you land on agency or hybrid, hiring a content marketing agency covers the process and the contract terms worth pushing on. And if content is still an experiment for you, the cheapest reversible version we sell is the 30-day Traffic Accelerator, $2,500 for a strategy and five assets.
Quick answers
Is an agency cheaper than hiring in-house?
Usually at low volume and rarely at high volume. The break-even moves a lot with what you'd still buy outside anyway, since most in-house content teams keep paying for design help, SEO tools and the odd freelancer on top of the salary.
Should our first content hire be a writer or a strategist?
A strategist who can edit. Writing is the easiest part of the job to buy outside, and a writer hired first ends up guessing at strategy, while a strategist can brief freelancers or an agency from week one.
How long before an in-house content hire is productive?
Longer than the offer letter suggests, because the first months go on learning the product, the buyer and who to ask. Ask candidates what they'd publish in their first ninety days, and budget for a dip if they leave.
Can an agency understand our product?
It depends on whether they already work in your category. One that does starts useful work sooner, and one that doesn't learns on your budget, which costs you even when the invoice looks the same.
When should we bring content in-house?
Once the channel is proven, the topics are known and volume is high enough to keep someone busy. Overlap the hire with the retainer for a month or two, and make sure you own every asset and the keyword map, so the new person inherits a plan instead of a blank page.
