In-House Developer or White-Label Partner? An Honest Calculation

If you run an agency, you know the moment: A client asks for a technically demanding build. You have the consulting, the design, the strategy. What you lack is development capacity – right now, in depth, without risk.

Two paths are open: hire an in-house developer or book a white-label partner. Both have advocates, both have market share. What rarely happens: someone does the math honestly.

We at Codeäffchen have been a development partner for agencies for over 20 years. Some of our partnerships have run for 16 years – with Spitzer Onlinemarketing and SEO Agentur Mudra, for example. Others are younger and grew because the need was there – like Alpha Omega Webdesign, with whom we’ve been working together for two years on projects like the Vulkaneifel-Therme. In that time we’ve seen both models up close. This article is the calculation we put in front of agency owners who want to compare honestly.

Up front: We make money with the buy model. So we’re not neutral. But we have no interest in selling you something that doesn’t fit – then you have frustration after six months and we have a burned market. We try to show both sides as honestly as possible.

The Build Side: What an In-House Developer Really Costs

Most agency owners calculate: “A developer costs 70,000 € per year, that’s 5,800 € per month, so 36 € per hour at 160 hours per month. Cheaper than any external.”

That’s the marketing math. The real math looks different.

Direct personnel costs:

Annual salary senior developer (PHP/Laravel/WordPress): 70,000–85,000 €
Employer benefits and taxes: about 22% → 15,000–18,500 €
Total personnel cost: 85,000–103,500 €/year

Material costs:

Hardware (MacBook, monitors, peripherals): about 4,000 € over 3 years = 1,300 €/year
Software licenses (IDE, Adobe, tools): 1,500–3,000 €/year
Proportional workplace (room, electricity, internet, furniture): 3,000–6,000 €/year
Total material cost: 5,800–10,300 €/year

One-time costs:

Recruiting (headhunter, job postings, trial work): 5,000–15,000 €
Onboarding (productivity dip in the first 3–6 months): conservatively estimated 15,000–25,000 € in lost output

Hidden costs:

Training and conferences: 2,000–5,000 €/year
Vacation and sick days: at 30 days vacation + 8 sick days = 38 days without output, but with full cost
Management overhead: 2–4 hours per week by you or your project manager

Year 1 total: 110,000–145,000 € all-in. Year 2 onwards: 95,000–120,000 €/year.

At 1,600 productive hours per year (after deducting vacation, sickness, internal meetings, training), that’s a fully-loaded cost of 60–90 € per productive hour – from year 2. In year 1 closer to 70–95 €.

Anyone calculating with “36 € per hour” is fooling themselves.

The Buy Side: What a White-Label Partner Really Costs

Here it’s specifically about Codeäffchen, because I can only speak honestly about our terms. Other providers calculate differently.

Our hourly rate: 100 €/h. That’s transparent, public, and doesn’t change based on project complexity. We bill precisely – travel, meetings, calls are included, but recorded realistically, not inflated.

Realistic usage patterns we see with our partner agencies:

Model	Booking Volume	Use Case
Mini-job	from 1 hour	Plugin fix, small adjustment, hosting question
Ongoing maintenance	~10 hours/month	Updates, bugfixes, small extensions across multiple client sites
Project booking	40–80 hours	Complete WordPress setup from design, WooCommerce customization, small custom plugin
Large project	120 hours+	Custom Laravel component, complex interface, multi-system integration

So the spectrum realistically ranges from 100 € (a single hour) to 12,000 € (large custom project) per booking.

The Direct Calculation: Three Scenarios

To make it concrete, here are three typical agency scenarios.

Scenario 1: The Small Agency

Profile: 3–5 people, focus on consulting and design, 4–8 client projects per year with technical component.

Actual development need: estimated 300–500 hours per year.

Variant	Cost/Year
In-house developer (1,600 productive hours)	95,000–120,000 € – but 1,100+ hours unused
White-label at 100 €/h (400 hours actual)	40,000 € – paying exactly for what’s needed

Clear build-vs-buy threshold: Below 950–1,200 productive hours of need per year, buy is cheaper. Plus: You carry no utilization risk, no sick-day risk, no recruiting complexity.

Scenario 2: The Mid-Sized Agency with Continuous Need

Profile: 8–15 people, own marketing and design teams, 12–25 client projects per year with substantial technical component.

Actual development need: 1,200–2,000 hours per year.

Variant	Cost/Year
In-house developer (1,600 hours)	95,000–120,000 € – if need matches
White-label at 100 €/h (1,600 hours)	160,000 € – more flexible, but more expensive per hour
Hybrid (1 in-house + white-label peaks)	95,000 € + 30–60,000 € = 125,000–155,000 €/year

Here it gets interesting: With continuous 1,500+ hours, an in-house developer is often cheaper. But: You have skill gaps. Your developer knows WordPress, but not Laravel. Or vice versa. Or no DevOps. Then you need both – in-house person for 80% of routine, partner for the 20% peaks with specialized requirements.

Recommendation: Hybrid model. This is how long-standing partner agencies work with us – routine in-house, technically complex projects and peaks external.

Scenario 3: The Specialized Agency with Occasional Tech Needs

Profile: 5–10 people, focus on branding, SEO, or content marketing. Tech isn’t core business, but occasionally required. 3–6 tech projects per year, of which 1–2 are demanding.

Actual development need: 200–400 hours per year, including one complex project at 120+ hours.

Variant	Cost/Year
In-house developer	95,000–120,000 € – almost entirely unused
Freelancer per project	20,000–40,000 € – but availability risk, quality scatter
White-label partner	25,000–45,000 € – plannable, consistent quality

Clear decision: Buy. In this constellation, an in-house developer isn’t economically justifiable.

What Numbers Don’t Show

An honest calculation doesn’t stop at euros. Three factors that aren’t in any table but make the difference:

Availability and Risk

An in-house developer is 1 person. Illness, vacation, resignation – everything goes directly on you. A white-label partner is a team. If someone is out, someone else steps in. With us, that’s four people deep.

With SEO Agentur Mudra, for example, our collaboration has run smoothly for 16 years – including hosting support and technical SEO. In that time, we’ve had no outages, because at least two of us always know the respective client site.

Skill Spectrum

A developer has a profile: WordPress or Laravel, frontend or backend, performance or security. No one can do everything at senior level. Our team covers WordPress (Avada, The7, Hello Biz, Elementor), Laravel (Filament, Livewire, Saloon), Shopify, interface development, plugin development, performance optimization, and DevOps.

With Spitzer Onlinemarketing, we’ve been working together for 16 years – on WordPress projects, static sites, PHP upgrades, and hosting. That breadth would be hard to cover with a single full-time employee.

Strategic Expertise Instead of Just Hands

A junior developer executes what you specify. An experienced partner gives you technical sparring – which also answers the upfront questions no client asks because they don’t know they should ask them.

With Alpha Omega Webdesign, we’ve been working together for two years. The Vulkaneifel-Therme is a good example: We built the Laravel shop with TCP connection to the point-of-sale system, while Alpha Omega maintains the main website. Such constellations only work when both sides can discuss at eye level technically.

The Pitfalls We See with Both Models

Three patterns that cost agencies money – regardless of which path they choose.

With “Build”: The Junior Trap

A junior developer costs 45,000 € salary + benefits = about 60,000 €/year. Sounds affordable. But: A junior needs 6–12 months until productively independent. During this time, someone at senior level must mentor them – that’s either you, your senior developer (if you have one), or an external mentor.

Anyone hiring juniors without senior guidance in-house is accumulating technical debt that will be repaid expensively later.

With “Buy”: The Freelancer Trap

Freelancers are cheaper per hour (50–80 €), but: availability fluctuates, quality scatters, long-term accountability is missing. If your freelancer doesn’t feel like it in 6 months or gets a well-paid position elsewhere, you’re alone with the code. With critical client sites, that’s a risk you need to calculate in a calm phase, not in an emergency.

With Both: The Missing Sparring Layer

Whether in-house or external: Anyone using a developer only as an order-taker leaves 30–50% of their strategic value on the table. Good developers see problems early, propose architectures, warn against dead ends. If you don’t use that, you’re saving at the wrong end.

When What: The Honest Recommendations

If you’re still undecided after these three scenarios, here’s the short version:

Buy is the right choice if:

You need under 1,000 productive development hours per year
Your demand fluctuates seasonally
You need different skill spectrums (WordPress + Laravel + DevOps)
You don’t feel like learning recruiting and personnel management
You’re just getting started and don’t have planning certainty for three years

Build is the right choice if:

You permanently need 1,500+ productive hours
Your demand is in a tech area you want to keep in-house long-term
You strategically want to build your own tech department
You have senior guidance in-house (or hire a senior who takes that on)

Hybrid works if:

You want to cover a routine base in-house, but tech peaks externally
Your tech requirements are broader than one developer can cover
You want to spread risk (outage, skill gap, load peaks)

What You Can Do Now

Before you decide, three concrete questions to answer for yourself:

How many development hours did you really need in the last 12 months? Honestly calculated, including maintenance and bugfixes.
How big is the fluctuation between your strongest and weakest month? With more than factor 2, a full-time employee is inefficient.
What technical expertise do you need permanently? Standard WordPress themes or Laravel architecture? Both? Only occasionally?

If you’re undecided after these three questions: call us or write to us. We do a free assessment of what fits your agency. Even if the result is: “Hire someone yourself, you’re big enough.” We’ve recommended that too.

You can’t reduce the decision to a single Excel row. But you can stop making it from your gut.