Every software budget conversation eventually lands on the same three options: hire freelancers, hire an agency, or hire employees. Founders usually compare them by hourly rate, which is the worst of the available methods, because the hourly rate answers a different question than the one being asked. The question is not what an hour costs. It is what a shipped, working, maintainable product costs, and who carries the risk along the way.
This guide compares the three models on total cost, speed, and failure modes, with German market numbers throughout. We are an agency ourselves, and we will tell you plainly where we lose.
The three models at a glance
A senior freelancer in Germany bills roughly EUR80-120 an hour. The freelancermap Kompass 2026, surveying over 5,400 freelancers, puts the average across all freelance disciplines at EUR103 an hour, with IT freelancers at a EUR95 median. You get senior hands fast, usually within days, and you supply everything around them: scope decisions, testing, deployment, and continuity planning.
A German agency bills senior hours at roughly EUR95-160. External benchmarks agree: Edvido's 2025 pricing data averages Germany at $110 an hour, with analyst ranges at $65-120. You get a contract partner under German law, a team rather than a person, and someone to call when it breaks. You also pay for the layers between you and the keyboard: account management, process overhead, and bench time.
An employed senior engineer costs EUR95,000-130,000 a year fully loaded, before you count the months of recruiting in a market where Bitkom counted 149,000 unfilled IT positions back in 2023. You get continuity, accumulated product knowledge, and iteration speed no external model matches. You also get fixed cost through quiet periods and a hiring process measured in quarters.
| Freelancer | Agency | In-house | |
|---|---|---|---|
| Cost shape | EUR80-120/h, no overhead | EUR95-160/h, all-in | EUR95-130k/yr loaded per senior |
| Start speed | Days | 2-6 weeks | 3-9 months incl. hiring |
| You must supply | PM, QA, DevOps, continuity | Decisions and feedback | Everything long-term |
| Single point of failure | Yes, acute | No | Medium (bus factor) |
| Best for | Small, specified builds | Deadlines, integrations, accountability | Core products, long roadmaps |
Total cost, not hourly rate
The comparison that matters is cost per shipped outcome. Take a 700-hour build, roughly a mid-size business application with two integrations.
The freelance assembly at EUR80-100 an hour invoices around EUR56,000-70,000. Then add your own time: ten-plus hours a week of scope decisions, testing, and coordination over four months, plus the risk premium of no backup when someone gets sick. Founders consistently underprice their own hours at zero. They are not zero; they are your most expensive hours, spent on your lowest-leverage activity.
The agency at EUR120-140 an hour invoices around EUR85,000-100,000, with management, QA, and continuity inside the number. The premium over freelance buys exactly three things: someone else carrying coordination, a bench behind every seat, and a contract partner your board and procurement recognize. Our app cost breakdown walks through this arithmetic with a worked example.
In-house for the same build means hiring two engineers, waiting a quarter, and paying roughly EUR200,000-plus a year in loaded cost whether or not the roadmap stays full. For a one-off build that is the most expensive option by far. For a product with two years of funded iteration ahead, it becomes the cheapest per feature, because the tenth feature costs a fraction of the first once the team and codebase exist.
When each model wins
Hire the freelancer when the scope fits in one head, the spec is genuinely stable, and someone technical on your side has real weekly hours to direct the work. Small websites, defined integrations, audits, and prototypes are the freelance sweet spot. Our guide to finding developers in Germany covers where to look and how to vet.
Hire the agency when there is a deadline someone else set, more than one integration, compliance scope like DSGVO or BFSG, or a board that needs a contract partner rather than a person. Also hire the agency when nobody on your side can own the build week to week; an unowned freelance build drifts, while an agency brings its own ownership. Before signing, run the selection questions and the contract checklist.
Hire in-house when the software is the product, the roadmap runs past eighteen months, and iteration speed is the business. Marketplaces, SaaS products with product-market fit, and internal platforms the whole company runs on belong in-house eventually. Many teams get there through a dedicated team phase first, which is the honest bridge between external build and internal ownership.
The failure mode of each model
Every model has a characteristic way of failing, and you should pick the failure you can survive.
Freelance fails at the single point: illness, a better-paying client, a departure mid-project. Mitigation is boring and effective: require work on your repositories from day one, demand documentation as deliverables not favors, and never let one person be the only one who can deploy. If a freelancer resists any of that, you have learned what you needed to know.
Agency fails at the padding: process theater, account layers, and change-order warfare on fixed-price contracts when the scope was never stable. Mitigation is structural: fixed scope only when you can describe the core flow in one sentence, time and materials with a weekly demo you actually attend, and acceptance criteria in the contract before the kickoff.
In-house fails at the hiring: the six-month vacancy, the compromise hire, the senior who spends their first quarter learning your domain while the roadmap waits. Mitigation is sequencing: bridge with external capacity while you hire properly, and never start the critical build the same month you start recruiting for it.
How to decide this week
Answer three questions in order. First, is the scope stable enough to describe in one page? No means you need discovery before any build, regardless of model. Second, who on your side owns the build ten hours a week? Nobody means agency or a freelance tech lead with real authority, never a loose freelancer assembly. Third, what happens if the key person disappears in month two? If the answer is catastrophe, you need a bench, which means agency or team, not a soloist.
If you answer those three honestly, the model usually picks itself. And if you want a second opinion from people who have watched all three models succeed and fail, send the outline: talk to us. We regularly tell callers to hire the freelancer. It costs us the project and earns us the next one.
Frequently asked questions
Is it cheaper to hire a freelancer or an agency?
Per hour, the freelancer: senior German freelancers bill EUR80-120 against agency rates of EUR95-160. Per outcome, it depends on who manages the work. With one freelancer you become the project manager, QA department, and DevOps stand-in. For small, well-specified builds that trade is excellent; for deadline-driven projects with integrations, coordination cost usually eats the hourly saving.
When should a company hire in-house developers instead?
When you have at least 18 months of funded roadmap, the software is your core product, and iteration speed matters more than initial build cost. A loaded senior engineer in Germany costs EUR95,000-130,000 a year, and hiring takes months in a market with six-figure unfilled IT vacancies. Below that threshold, external teams are cheaper per shipped feature.
What is the biggest risk of each model?
Freelancer: single point of failure, one illness or departure away from a stalled project. Agency: paying for process and account layers your project does not need, plus knowledge walking out at handover. In-house: slow hiring, fixed cost through quiet periods, and the team you can hire not matching the team you need for a one-off build.
Can I combine models, like freelancers plus an agency tech lead?
Yes, and for mid-size builds it is often the best structure: a senior lead who owns architecture and QA, plus freelance capacity underneath. What fails is the reverse: freelance capacity with nobody senior owning the whole. Whatever the mix, one named person must own the outcome, not just their tickets.