In-house vs outsourcing software development: what a German SME really pays for each

In-house vs outsourcing software development: what are you actually choosing?

You are choosing who carries the employment relationship. In-house means the developer is your employee, with a contract under German labour law and social insurance paid by you; outsourcing means you buy results from someone who employs or organises the people doing the work.

There are really three options, not two. You can employ a developer, you can contract an individual freelancer who sits in your stand-ups and works to your instructions, or you can outsource a defined project to a team that delivers against a written scope. The middle option looks like outsourcing on paper but often behaves like employment in practice, which matters in Germany for reasons covered further down.

The in-house vs outsourcing software development question also has a time dimension. A salaried developer is a long-term commitment you make before you know how much work will arrive. An outsourced project is a commitment for one scope. If your backlog is lumpy, with a big push this year and small fixes afterwards, those two cost curves look very different.

Finally, it is a knowledge decision. An employee absorbs your processes over years; an outside team only knows what you tell it and what it writes down. Neither is automatically safer: employees resign, suppliers finish. What protects you is documentation, a repository you own and one person inside the business who understands the system well enough to direct whoever writes the code.

What does an in-house developer really cost a German employer?

The salary is only the start. On top of gross pay, a German employer pays its half of statutory social insurance, which in 2026 comes to just over 21% of gross pay up to the contribution ceilings, and then the costs that no payslip shows.

The statutory part is easy to add up from official rates. The Deutsche Rentenversicherung gives the pension rate as 18.6%, split evenly, so 9.3% for you. The Federal Ministry of Health sets the general health insurance rate at 14.6% plus an average supplementary contribution of 2.9% for 2026, both shared half and half, and long-term care at 3.6% with a 1.8% employer share (Saxony splits it differently). Unemployment insurance is 2.6% under §341 SGB III, again split. Statutory accident insurance and the small levies come on top.

Then come the costs that make in-house vs outsourcing software development comparisons honest:

• Recruiting: job ads, recruiter fees if you use one, and the hours your managers spend interviewing.
• Paid leave: the Federal Leave Act sets at least 24 working days on a six-day week, which is 20 days on a five-day week, and most IT contracts offer more.
• Sick days, public holidays and training days, all paid but not productive on your project.
• Hardware, software licences, cloud accounts and a desk or home-office allowance.
• Onboarding: weeks before a new hire knows your systems well enough to work alone.
• Management time: someone has to set priorities, review work and hold appraisals.

None of this makes employees a bad deal. It means the fair comparison is a full year of employer cost divided by the useful output you expect, set against a supplier's itemised quote for the same output.

How long does it take to hire a software developer in Germany?

Longer than most project plans assume. Between advertising the role, interviewing, making an offer and waiting for the candidate to leave their current job, several months can pass before the first line of code, and IT roles feature in the shortage monitoring of the Federal Employment Agency.

The Bundesagentur für Arbeit publishes an annual shortage analysis (Engpassanalyse) that rates occupations on six indicators, the first being the median vacancy duration: how long advertised jobs stay open. You can look up the current figures for software and IT occupations in its interactive statistics before you plan a hire, rather than relying on anyone's estimate, including ours.

The candidate's notice period adds to that. Under §622 BGB the basic notice is four weeks to the 15th or the end of a month, and when an employer terminates the period grows with tenure, reaching seven months after twenty years. Many contracts also lengthen the employee's own notice, so a senior developer may need a quarter or more to join you. Probation can last up to six months, during which either side may end the job with two weeks' notice, so the first half-year is not settled either.

For in-house vs outsourcing software development planning, the practical question is: what does the delay cost? If a customer portal would save your service desk hours every week, each month without it is a real loss. An outside team does not remove the need to define the work, but it removes the search, the notice period and the probation gamble from the critical path.

Is outsourcing software development cheaper than hiring in-house?

Often, for project-shaped work, yes; for a stable product that needs full-time attention for years, not necessarily. The answer turns on utilisation: how many of the hours you pay for are spent on work you actually need.

An employee costs the same in a quiet month as in a crunch month. If your roadmap has a big build followed by months of small changes, you pay for spare capacity or find other work for the developer. An outsourced project is priced for the scope, and afterwards you pay only for the support you choose. With us, maintenance is included for two months after launch and then starts at US$120/mo.

The reverse holds too. When software is the product you sell, when features ship every week and the developers need to sit with sales and support, the in-house team earns its cost through speed and context. Paying an outside supplier indefinitely for that kind of continuous work can end up costing more and teaching you less.

We cannot give you a like-for-like euro comparison because salaries and supplier quotes vary widely across Germany, by skill and seniority. What we can do is make our side precise: an itemised quote in about two working days, starting at US$900 for custom software, US$600 for an app and US$600 for an automation. Set that beside your own salary benchmark and the cost list above, and the in-house vs outsourcing software development maths becomes your own, not a sales pitch. For wider budget ranges, see what software development costs in Germany.

In-house vs outsourcing software development for the Mittelstand: a simple decision rule

Keep work in-house when it is continuous, core to what you sell and full of knowledge only your people have; outsource when it is bounded, specialist or urgent; and use a hybrid when it is important but not full-time.

Most Mittelstand firms are not software companies. They make machines, move goods, run clinics or sell to trade customers, and software supports that business. For them the in-house vs outsourcing software development choice usually lands on the hybrid: someone inside owns the "what" and the "why", and an external team handles the "how".

If the answer is clearly "outsource", the next question is where: our page on offshore software development for German firms explains the India route in detail.

Scheinselbstständigkeit: why individual freelancers carry a hidden risk

Hiring one freelancer and treating them like staff can turn a contract into employment in the eyes of German social insurance law. That risk, known as Scheinselbstständigkeit or bogus self-employment, is the reason many SMEs think twice before filling a gap with a solo contractor.

§7 SGB IV defines employment as non-independent work and names two indicators: working to instructions, and being integrated into the organisation of the person giving those instructions. A developer with a company laptop, fixed hours set by you, a place in your team chat and tasks assigned daily by your lead can match both, whatever the contract calls them. If the relationship is classed as employment, the contribution obligations of an employer follow.

There is a formal way to get clarity. Under §7a SGB IV, the parties can ask the Deutsche Rentenversicherung Bund for a status determination (Statusfeststellungsverfahren) on whether an engagement is employment or self-employment. Many firms do this for long engagements with individuals.

An outsourced project is structured differently: you agree deliverables, the supplier organises its own people, tools and hours, and you accept or reject results rather than directing daily tasks. That is how we work, and it tends to look different from a solo freelancer embedded in your team. We are not lawyers, though, and cross-border set-ups have their own questions, so please have your Steuerberater or employment lawyer look at your specific contract. This is one more line in the in-house vs outsourcing software development ledger, not a reason for panic.

How do you keep knowledge when you outsource software development?

By making the knowledge a deliverable. If documentation, a readable repository and handover notes are part of what you pay for, the system stays understandable when any person, internal or external, moves on.

The fear behind many in-house vs outsourcing software development debates is dependency: "what if the supplier disappears?" The honest reply is that the same thing happens when your only developer resigns and serves four weeks' notice. Protection comes from habits, not from the employment contract.

• The Git repository lives in an account your business owns, from the first commit.
• Cloud, domain, app store and database accounts are registered to you; we get access, not ownership.
• A README explains how to run the project locally and how to deploy it.
• Architecture decisions are written down briefly, with the reason, so a successor knows why a choice was made.
• Environment variables and third-party services are listed in one place, without secrets pasted into documents.
• A handover call is recorded, and a written runbook covers backups, restores and common failures.

Ask any supplier to show you what their handover looks like before you sign. If they hesitate, that tells you how the exit would go.

The hybrid answer to in-house vs outsourcing software development: one product owner plus a remote team

For most German SMEs, the best answer to in-house vs outsourcing software development is both: hire or appoint one person who owns the product, and let a remote team build it. You keep decisions and domain knowledge inside while buying capacity from outside.

The internal person does not need to code. They need to know the business, write down what users need, set priorities, test releases and say no to scope creep. In a small firm this might be the head of IT, an operations manager with a technical streak, or a new hire whose profile is product ownership rather than programming.

A week in a hybrid set-up might look like this: on Monday the product owner and our project lead agree the week's priorities on a call during the German morning. Through the week, work lands as pull requests on a staging environment that the product owner can click through. On Thursday there is a short demo. Questions that come up in our afternoon are written into the ticket, so the answer is waiting the next day rather than lost in a chat.

This model also answers the knowledge concern. The product owner builds up understanding of the system over time, sees every change and holds the accounts. If you later decide to bring development fully in-house, that person is the one who onboards your first developer, using the documentation that already exists.

In-house vs outsourcing software development: control, speed and quality compared

In-house wins on daily presence and informal knowledge; outsourcing wins on speed to start and breadth of skills; quality depends on process on either side, not on the employment model.

Control. With employees you control hours and tasks directly. With an outside team you control scope, priorities, acceptance and the accounts, which in practice is the control that matters for the result. What you give up is the ability to tap someone on the shoulder at 4 pm on a Friday.

Speed. In-house is faster at small changes once the person knows the system. Outsourcing is faster to begin because there is no hiring cycle, and a team of three can work in parallel on front end, back end and cloud in a way one new hire cannot.

Quality. Code reviews, automated tests, staging environments and clear acceptance criteria produce good software. A lone employee without review can write fragile code just as an unvetted supplier can. When you weigh in-house vs outsourcing software development on quality, ask each option how work gets reviewed and tested, and ask to see it.

Security. An outside team should get the minimum access needed, separate accounts rather than shared passwords, and no production personal data where test data will do. Those rules suit employees too.

Is outsourcing software development to India allowed under GDPR?

Yes, it can be done lawfully, but it needs the right paperwork. India does not have an adequacy decision from the European Commission, so if a supplier there handles personal data for you, the transfer normally needs Standard Contractual Clauses and a transfer assessment on your side.

The European Commission's list of adequacy decisions covers countries such as Japan, Switzerland and the United Kingdom; India is not on it. That does not rule out an Indian team. It means you, as controller, choose a transfer tool and document it, usually with help from your data protection officer.

Much software work needs no personal data at all. We can build and test against anonymised or synthetic data, with production databases hosted in an EU region of your own cloud account, so real customer records never have to leave Germany or the EU during development. When access to live data is genuinely needed, for example to debug a production issue, it can be limited, logged and time-boxed.

What we do on the build side: access control by role, encryption in transit, hosting in EU regions of the provider you choose, audit logs where the application needs them, and data minimisation in forms and exports. What we do not do is give legal advice or sign anything as a certified processor. Compliance is your responsibility, confirmed by your own counsel. For website-level requirements, see our GDPR-compliant website guide.

What should stay in-house and what can you outsource?

Keep ownership, priorities and domain knowledge inside; outsource build work that can be described, tested and handed back. A useful test is whether you could write acceptance criteria for it.

This split is how in-house vs outsourcing software development stops being a yes-or-no question. You decide task by task.

If the outsourced part will grow into a standing squad, compare it with a dedicated team arrangement rather than a string of separate projects.

Working with an Indian team from Germany: overlap, calls, payments and the first two weeks

It works best when you use the shared hours for decisions and the rest of the day for building. India is 3.5 hours ahead of German summer time and 4.5 hours ahead in winter, so your morning into early afternoon meets our afternoon and evening.

Calls are by video, in English, booked in your morning. Day-to-day questions go on WhatsApp or into the ticket system you prefer, and we reply seven days a week. We do not visit offices in Germany, so kick-off workshops happen on screen, with a shared document that becomes the written scope.

Quotes and invoices are in USD and come from India; payment is by Wise, bank wire or PayPal. We do not advise on how you book or tax those invoices, so check with your accountant. Nothing is billed before you approve the quote in writing, and the terms that apply are on our terms page or in the quote itself.

Risks of outsourcing software development, and red flags to watch

The real risks are vague scope, missing documentation, supplier-owned accounts and silence; each has a simple countermeasure you can demand in writing.

A fair in-house vs outsourcing software development comparison lists the risks of both. Hiring risks a bad fit, a long vacancy or a resignation just as the project peaks. Outsourcing risks the items below.

• A quote with no line items. Ask what each feature, integration and environment costs.
• The supplier registers your domain, cloud or app store accounts. Insist they sit in your name from day one.
• No staging environment. You should see work in progress, not only a finished release.
• Code shown only as screenshots. You should have repository access throughout.
• Promises of guaranteed rankings or delivery dates for unscoped work. Nobody can guarantee search rankings, and dates depend on scope.
• Pressure to pay large sums before any written scope exists. Scope first, approval second, billing third.
• One person holding everything. A single freelancer is a single point of failure; ask who covers illness.

We also say plainly what we do not offer: on-site visits, hardware installation, teams of twenty developers or legal advice. If you need any of those, a local partner or a larger supplier is the better choice.

Tech choices that keep you free to switch between in-house and outsourced

Choose mainstream, well-documented technology and you can move work between employees and suppliers without a rewrite. Exotic stacks lock you to whoever knows them.

For web applications we typically use TypeScript with React or Next.js on the front end, Node.js or Python on the back end and PostgreSQL for data. Mobile apps are built with Flutter or React Native and published under your own Google Play Console and App Store Connect accounts. Hosting sits on AWS or another provider of your choice, in an EU region if you prefer.

These are the skills German developers are most likely to have, which matters for the in-house vs outsourcing software development decision: if you hire later, candidates will recognise the code. Automated tests, a CI pipeline and infrastructure written as configuration rather than clicked together by hand make the next handover easier still.

If you already run an ERP, accounting software or a shop system, integration is usually the core of the work. We build against documented APIs and keep the integration code in its own module, so a future in-house developer can change it without touching the rest.

Worked example: a hypothetical machine builder weighing in-house vs outsourcing software development

Say a 70-person machine builder near Bielefeld wants a service portal where customers log spare-part requests and see repair status. This is a hypothetical scenario to show the reasoning, not a client story.

Option one, hire. HR opens a full-stack developer vacancy. The firm budgets salary plus just over a fifth again for social contributions, plus a laptop, licences and recruiting time. The best candidate accepts after several weeks of interviews but has a contractual notice period of three months. The portal work starts, realistically, the following quarter, and the developer will need other work once it launches.

Option two, a solo freelancer. Faster, but the freelancer would work daily to the IT lead's instructions inside the team chat for a year. The managing director asks the tax adviser about status risk and considers a status determination request.

Option three, hybrid. The IT lead becomes product owner, writes the ten key workflows and sends them to us. We reply with an itemised quote starting from the custom software price, US$900, listing the ERP interface, customer log-in, notification emails and hosting in an EU region of the firm's own cloud account. After written approval, the first screens are on staging within two weeks, and the IT lead demos them to the service team every Thursday.

The firm keeps the knowledge (the IT lead saw every change), owns the accounts and pays only for the scope. If the portal later grows into a product, hiring a developer becomes easier because the code, docs and runbook already exist.

Does outsourcing affect SEO and AI-search visibility for customer-facing software?

Only if nobody owns it. Whoever writes the code, public pages need fast loading, clean HTML, structured data and a sitemap, and someone must watch Google Search Console after launch.

For customer-facing portals and websites we build pages that render on the server, meet Core Web Vitals targets on mobile, carry sensible headings and schema markup, and keep log-in areas out of the index. Those same habits help AI search tools such as Google's AI Overviews find and quote your public content, because clear, well-structured pages are easier to read for machines as well as people.

If search visibility is part of the goal, say so in the brief and we price it in. Monthly SEO starts at US$150/mo. For a relaunch of an existing site, read website relaunch SEO first so traffic is not lost in the move.

Checklist: before you decide between in-house and outsourcing software development

Answer these questions on one page and the in-house vs outsourcing software development decision usually makes itself.

• How many developer-months of work do you really have this year, and next year?
• Is the software what you sell, or what supports what you sell?
• What would a full year of one developer cost you, with contributions, leave, equipment and recruiting included?
• How long have similar vacancies stayed open in your region, and what is the likely notice period of a good candidate?
• Who inside your business will own priorities and test releases?
• Would a solo freelancer be embedded in your team in a way that raises status questions?
• Will personal data be involved during development, and can test data replace it?
• Are all accounts, repositories and domains going to be in your name?
• What does handover look like if you switch model in two years?

If you would like a second opinion on your answers, send them to us on WhatsApp or through the contact page. We will tell you if in-house looks like the better route for your case.