Compared with hiring in-house
A first content hire inherits a job nobody has defined.
The instinct when content becomes the constraint is to hire someone to own it. Sometimes that is right. It goes wrong in a specific, predictable way, and the fix is cheap if you do it first.
The problem
You are hiring one person to be five people.
The job description for a first content hire usually asks for strategy, writing, video editing, design, channel management, and analytics. Those are five different skills and roughly two different personality types. The people who are excellent at all five exist and are not applying to be your first content hire.
So you hire for the skill you feel most acutely, usually writing, and the other four get done badly or not at all. Six months in, the honest assessment is that publishing is more consistent than it was and the ceiling is lower than expected, and nobody wants to say that out loud because a person's job is attached to it.
The deeper problem sits underneath the hire. On day one they are handed a company whose voice has never been written down and asked to reproduce it. They spend their first quarter reverse-engineering it from old posts and from feedback on drafts, which is expensive, slow, and lost entirely if they leave.
What it costs
What the hire costs beyond the salary.
- A quarter of calibration
- Roughly the first three months go into working out what the brand sounds like, largely by producing things that are wrong and being told so.
- Founder review time, indefinitely
- Someone has to be the arbiter of whether output sounds right. Until the standard is written down, that person is the founder, and the review does not taper.
- A skills gap you cover with tools or contractors
- The editing, the design, and the channel operations still need doing. That is either more spend or a writer doing three jobs at a level none of them deserve.
- The whole thing resets on departure
- Average tenure in a first marketing hire is short. When they leave, the calibration leaves with them, because it was never written anywhere.
Why the usual answer does not hold
The hire is not the problem. The order is.
Hiring a person to define the standard and execute against it at the same time asks them to do the hardest part of the job in their least informed quarter, with no way to check whether they got it right except by producing work and watching your face.
Reverse the order and the same person succeeds. If the specification exists before they start, their first week is reading a document rather than guessing from artefacts. Their drafts get checked against something before you see them. Your review becomes judgement about ideas rather than correction of register. And when they eventually leave, the standard stays, because it was never in their head to begin with.
That is the actual argument here. Not that you should never hire. That building the specification and the pipeline first makes the hire land better, and buys you the option of not needing one yet.
Side by side
The same money, two shapes.
| First in-house hire | Build and Run | |
|---|---|---|
| Time to reliable output | One to two quarters, including notice periods and calibration. | Weeks. The specification is written before production starts. |
| Skills covered | One well, the rest at whatever level one person can manage. | Writing, video production, formatting, and channel operations, as one pipeline. |
| How the standard is held | In the hire's head, calibrated by feedback on drafts. | In a written specification with an enforced term list. |
| Founder review burden | Heavy at first and does not taper, because the founder is the only arbiter. | Heavy in month one, then narrows to judgement rather than correction. |
| Capacity changes | Another hire, another calibration quarter. | A scope change to the existing pipeline. |
| If the person leaves | The calibration leaves too. Publishing stops until the next hire is up to speed. | Not applicable. The specification and the runbook stay in your repository. |
| Fixed versus variable | A salary, benefits, tools, and management overhead. Fixed. | A scoped engagement with notice on both sides. |
| Where the hire wins outright | Being in the building. Hallway context, fast internal answers, and a person who cares about the company rather than the account. | Not offered. This does not sit in your standups or know what sales heard last week. |
| Doing both | The hire inherits a specification, a pipeline, and a runbook on day one, and spends their first quarter on strategy instead of calibration. | The intended end state for several clients. |
What gets installed
What a future hire would inherit.
- The specification
- Their onboarding becomes reading a document rather than inferring a standard from six months of old posts.
- The blocked-term list
- They find out a phrase is wrong before they publish it, not in a review afterwards.
- The production pipeline
- One source event becomes every format without them learning video editing.
- The runbook
- Written for someone who was not there when it was built, because that is exactly who a new hire is.
Control and ownership
What stays with you either way.
Stays human
- Positioning, and every claim made publicly
- Approval before anything publishes
- Which topics matter this quarter
- Whether to hire, now or later
Yours to keep
- The specification and the term lists
- The templates and the publishing config
- Every source file and export
- Every account and credential
How it gets done
If you are close to opening the role.
- 01
Pause the job description for a week
Not the decision. Just the posting. The role gets easier to write once you can see what actually needs a person.
- 02
Build the specification
It is worth having whether or not you hire, and it is the artefact you would otherwise ask a new hire to produce in their first quarter.
- 03
Run one cycle against it
You find out what volume is achievable without a hire, and what genuinely needs someone in the building.
- 04
Rewrite the role from what is left
It is usually a narrower, more senior, easier-to-fill job than the original five-skills description.
- 05
Hire into a working system, or do not
Either outcome is fine. The specification is yours regardless.
Proof
A practice with thirty years of expertise and no headcount to put it anywhere.
He never hired a content person. A session filmed Monday afternoon is a live campaign by Tuesday lunch, and stigmatizing language is blocked before a draft can publish.
- Next morning
- Session to live campaignShoot ended Monday 1:30pm. Campaign was live by Tuesday lunch.Internal workflow measurement · July 21, 2026
- 0
- Founder hours on productionHe shows up to the room. He never opens an editor.Internal workflow measurement · July 21, 2026
- Every publish
- Language check before publishStigmatizing terms are blocked at the pipeline, not caught in reviewProduction records · July 21, 2026
- 15+
- Live platforms and micrositesEach lab, masterclass, series, and pitch ships as its own siteProduction records · July 21, 2026
The full account, including reach figures with their capture date and paid spend stated, is on the Insightful Recovery Solutions case study.
How to decide
Which one, and when.
This is the right call when
- Content is a constraint now and the role would take a quarter to fill
- Nobody internally has written down what the brand sounds like
- The job description has more than three distinct skills in it
- You would rather find out what volume is achievable before committing to a salary
It is the wrong call when
- You need someone in standups, in the room, and reachable on Slack all day
- The work is inseparable from internal context that changes weekly
- You have already hired well and the person is succeeding
- The real need is a marketing leader rather than content production
Objections
The reasonable worries.
- An external party will never know our business well enough
- For anything requiring live internal context, correct. That is what the approval gate is for, and it is why the honest recommendation for some companies is to hire. The specification is still worth building first either way.
- We want someone who is invested in us
- A fair thing to want and a real difference. It is listed as a row in the table above rather than argued away.
- This will make hiring harder to justify later
- It usually makes it easier, because you can describe the role in terms of what is actually missing rather than in terms of a general hope that content improves.
- We already have someone doing this part-time
- Then they are the person the specification helps most immediately. It is the document they have been trying to write in their head.
Questions
Asked before the call.
Is this cheaper than a hire?
Usually less than a loaded salary for a mid-level marketer, and that is not the point of the comparison. The point is that a hire takes a quarter to become useful and takes the calibration with them when they leave. Scope and figures come out of the call.
Can we do this and hire?
That is the end state for several clients, and it is the best version of the hire. They arrive to a specification, a pipeline, and a runbook, and spend their first quarter on strategy.
What happens to the specification if we hire?
It is already yours, in your repository. The new hire inherits it and maintains it. Nothing needs handing over because nothing was ever held.
Would you tell us to hire instead?
Yes, when it is true. If the work is inseparable from internal context that changes weekly, this is a worse answer than a person, and hearing that on the first call is worth more than a scoped proposal.
Read next
Where this connects.
- Compared with an agency is the other option most companies weigh at the same moment.
- For founder-led B2B goes deeper on the case where the founder is the only credible voice, which is the hardest version of this to hire for.
- Build and Run sets out what Build produces, which is the part a future hire inherits.
Before you post the role, see what it would actually need to cover.
Thirty minutes. We read what you publish today, say what the specification would have to capture, and say plainly if the answer is a person.