The real cost of an in-house digital team
A monthly retainer looks expensive next to a salary. It is not competing with a salary. It is competing with salaries, payroll taxes, benefits, PTO, recruiting, equipment, management time and the risk that one of two people resigns in March. Here is that comparison, with every assumption in your hands.
$32,000 a month for two senior UX and development practitioners, with the studio behind them.
Fully loaded, first year. $397K–$486K a year after that, on conventional employer assumptions you can change below.
The comparison almost everyone makes first
A company sees a monthly agency figure and puts it next to a senior salary. It is an understandable comparison and it is the wrong one, because those two numbers are not the same kind of number.
One is what leaves the business. The other is the portion of what leaves the business that arrives in somebody’s bank account. Everything in between is real money that still has to be budgeted, approved, and managed.
Added on top of the salary
No company pays every one of these at the maximum. The honest comparison is not salary against retainer — it is fully loaded organisational cost against retainer, using assumptions you can actually defend in a budget meeting.
Side by side, per year
An embedded senior team against two senior hybrid UX and development hires. The left column is a price. The right column is an estimate — which is precisely the point.
Two senior UX and development practitioners, with the studio behind them.
$384K
a year · $32,000 a month
Included in that
People who can independently take work from strategy through to production.
$445K–$534K
first year · $397K–$486K a year after that
On top of the salaries
The right-hand figures assume base salaries of $155,000 to $190,000 each, 28% employer overhead, and one-off recruiting and equipment costs in year one. Every one of those is adjustable in the calculator below.
Run your own numbers
Nothing here is weighted in our favour, and you will find combinations where hiring comes out cheaper. When it does, the page says so — because a calculator that always agrees with the company that built it is one you would be right to ignore.
first year. $441,600 a year after that, once recruiting and equipment are behind you.
$32,000 a month. Same figure in year two.
Push Refresh costs about $105,600 less per year.
The gap is worth noticing, and it is not the strongest part of the case. Two employees are two employees; an embedded team comes with the studio behind it, no recruiting cycle, no ramp, and no half-empty department if the workload changes.
In-house $489,600 · Push Refresh $384,000
Push Refresh costs about $105,600 less per year.
Estimates, not quotes. Employer burden varies by state, headcount, benefits plan and seniority; recruiting and equipment are first-year costs, so they land once rather than every year. Salaries and burden are shown separately below so you can see which is which.
What you are actually buying
The comparison so far has been two practitioners against two employees, which understates one side of it. Two employees are two employees. Two embedded practitioners come attached to everyone who has already solved the thing they are about to hit.
UX, product and interface design, design systems and front-end development sit in the same team rather than in two departments with a queue between them.
We build and maintain our own content platform, so content modelling, editor experience and integration are not an unfamiliar dependency we are learning on your budget.
Moving a site between platforms without losing search visibility, content history or a weekend is a specific skill, and it is one this studio already does.
Accessibility, QA, performance and the fiddly launch work are covered by the team rather than by whoever happens to have capacity that week.
Work passes people who have shipped this before. An internal team of two has nobody more senior to check it, which is a quiet and expensive gap.
The obvious objection, answered honestly
One hybrid practitioner is not a full-time designer plus a full-time developer. They have one person’s hours in a week and we are not going to pretend otherwise. What changes is how much of that week survives contact with the process.
The specification a designer writes for a developer is written for somebody else. When they are the same person, that document does not need to exist.
Most of the gap between a design and what ships is somebody making a reasonable guess about intent. There is no guess to make here.
Ideas that will not survive the build get discarded during design rather than three weeks later in a meeting about why they cannot be built.
A question that would take a thread, a call and two calendars to resolve is resolved in the moment it comes up.
What ships resembles what was designed, because the person defending the detail is the person implementing it.
For a large, continuously loaded programme of work, four specialists will out-produce two hybrids. For most companies, the constraint is not hours — it is the coordination tax on the hours they already have.
The cost that never makes the budget
This is the risk that does not appear in the comparison spreadsheet and shows up anyway. With a team of two, a single departure removes half your capability, and the clock on replacing it starts at zero.
Every step above is normal and unavoidable, and together they routinely run a quarter or more before the replacement is producing at the level of the person who left.
Roadmaps, launch dates and stakeholders carry on regardless. The remaining person absorbs it, which is how good hires become former employees.
People change on our side too — we are not selling zero risk. What changes is where the burden sits: continuity is what you are paying us to maintain, and it does not become a headcount requisition.
The strategic distinction
An employee is a permanent position with a salary band, a manager, a career path and a cost that continues whether or not this quarter has work for it. An engagement is an operating expense attached to a business need.
Senior capability when a redesign, migration or launch calls for it, without creating positions the company will still be carrying two years later.
Hiring two specialists means somebody has to lead them, review them, and know enough to tell good work from work that merely arrived on time.
Changing an engagement is a conversation. Changing headcount is a redundancy process, and everyone who watches it happen updates their view of the company.
No sourcing, no interview loop, no ramp. The first week is work rather than orientation.
The conventional alternative
Plenty of companies do not hire hybrids, because hybrids at this level are genuinely hard to find. They hire the conventional shape instead: two senior designers and two senior developers.
Set the calculator above to two designers and two developers and it returns these same figures. It is the same function.
Four-person team
$819K
a year in salaries and employer burden. About $915K in the first year, once recruiting and equipment are counted.
Push Refresh
$384K
a year, for two senior practitioners with the studio behind them.
This is not a claim that two people do the work of four. Four full-time specialists have more hours in a week and deeper individual specialisation, and for a large continuous programme that is the right structure. The comparison here is about organisational cost and multidisciplinary coverage — what it takes to stand the function up, not how many hours it contains.
Where this argument stops
There are situations where building the team is straightforwardly correct, and a page that would not say so is a page selling rather than advising. If any of these describe you, hire.
Enough design and development work to keep a dedicated team busy every week, indefinitely. Utilisation is what makes fixed headcount efficient.
Domains where the context takes a year to acquire and is worth more than the execution — regulated industries, complex internal systems, long-lived products.
Someone in the room for every decision, embedded in internal process, accountable in the way only an employee can be.
If the long-term goal is the organisation itself, start building it. That is a strategy, not an overhead.
If the company can carry these positions through a slow year without difficulty, the flexibility argument does not apply to you.
If none of those describe your situation, building an internal digital team may be solving an organisational problem you do not actually have.
Who this model fits
This is not the right structure for everyone, and it is a very good one for a specific set of situations.
The work has outgrown whoever has been absorbing it, but not yet to the point of standing up a department.
Campaigns, landing pages and site work that need senior design and development rather than a queue with an internal development team.
An existing team that is good and is not big enough for what the roadmap now contains.
A defined, demanding stretch of work that does not justify permanent positions once it is finished.
A designer, a developer, and a project manager translating between them is three relationships to manage and three places for the work to stall.
If the seam between the two is where your projects currently lose time, removing the seam is the fix.
The whole argument, in one place
$32,000 a month · two senior practitioners
fully loaded, first year
fully loaded, first year
The value is not simply that this might cost less. Sometimes it will and sometimes it will not, and you have the calculator above to find out which is true for your numbers.
The value is avoiding the cost, complexity, rigidity and risk of building a department when what you actually needed was the capability. Salaries are the visible part. Recruiting, benefits, management, downtime, turnover and permanent headcount are the part that shows up afterwards.
Most companies do not need to hire a team. They need access to what a team does.
Bring your actual numbers — salary bands, workload, timeline — and we will go through them with you. If hiring is the better answer for your situation, we will tell you that.