When a DACH technology company decides to launch a new product line, the first operational question is who will build it. Three options dominate: build an internal team, buy an existing solution or delivery project, or bring in a managed engineering pod. Each has a different cost profile, speed and risk. The wrong choice rarely fails immediately; it fails twelve months later, when the team is too slow, the bought product does not fit, or the knowledge sits outside the company. This guide offers a scoring matrix and a phase plan to make the decision deliberately.
Why the question is pressing now
Many DACH companies are making this decision under real time pressure. Bitkom reported in September 2025 that 36 percent of German companies with at least 20 employees now use AI, up from 20 percent a year earlier, and a further 47 percent are planning or discussing it. Capital is following: according to the EY Startup-Barometer, German startups raised about EUR 8.4 billion in venture capital in 2025, 19 percent more than in 2024, although the number of financing rounds fell 5 percent to 716. Bitkom expected German software revenue to grow 9.5 percent to EUR 52.7 billion in 2025. Larger rounds and faster-moving markets shorten the window in which a new product line has to show traction.
The constraint is people. In Bitkom's 2025 survey, 85 percent of companies reported a shortage of IT specialists and 79 percent expected it to get worse. A staffing decision for a new product line is therefore also a decision about which bottleneck you accept: hiring time, product fit or external dependency.
The three options
Build: an internal team
You hire a dedicated team, usually a lead plus several engineers, as employees. You gain full control, long-term knowledge retention and cultural alignment. You pay with time: hiring in Germany is slow, and Bitkom's 2025 survey reports an average of 7.7 months to fill an IT role. You also take on permanent fixed cost before you know whether the product line will succeed.
Buy: an existing product or a turnkey project
You license or acquire a product that covers most of the need, or commission an agency to deliver a defined first version at a fixed price. This can be the fastest route to market if a suitable solution exists. The risks are fit, dependency and differentiation: if the product line is meant to be a competitive advantage, a solution your competitors can also buy may not deliver it.
Pod: a managed external team
A small external team, run by the provider under a Werkvertrag (BGB §631) or Dienstvertrag (BGB §611), delivers sprint by sprint against your goals. Start time is shorter than hiring, cost is a predictable monthly fee, and capacity can be reduced if the product line does not take off. The risk is knowledge concentration outside the company, which must be addressed with documentation, code ownership and a transition plan.
A scoring matrix
Score each criterion from 1 (low) to 5 (high) for your situation, then compare the options.
| Criterion | Favours build | Favours buy | Favours pod |
|---|---|---|---|
| Strategic differentiation | High | Low | Medium to high |
| Time pressure | Low | High | High |
| Uncertainty about success | Low | Medium | High |
| Availability of suitable products | Low | High | Low to medium |
| Need for long-term in-house knowledge | High | Low | Medium, with transition plan |
| Capital and fixed-cost tolerance | High | Medium | Low to medium |
| Regulatory or export control constraints | High | Depends on vendor | Depends on scope and controls |
A product line that is strategically central, not time-critical and certain to continue points toward build. A commodity capability with good products on the market points toward buy. A differentiating product line with high uncertainty and time pressure points toward pod, at least for the first phase.
Combining buy and pod
Buy and pod are not mutually exclusive. A frequent pattern is to license a platform for the commodity layer, for example identity, billing or device management, and have a pod build the differentiating functions and integrations on top. This shortens time to market and keeps engineering effort focused on what customers actually pay for. The condition is a clear interface boundary, so that the bought component can be replaced later without rewriting the product.
Phase plan: avoid locking in too early
The decision does not have to be permanent. A staged approach often reduces risk:
- Discovery (internal). A small internal group, typically a product lead and a senior engineer, defines the problem, validates demand and drafts the architecture. This phase should stay close to customers and decision makers.
- First release (pod or buy). Once the scope of a first version can be written down, an external pod builds it sprint by sprint, or an existing product is configured. Internal ownership remains with the product lead.
- Validation. The first release is in customers' hands. Usage and revenue data decide whether the product line continues, pivots or stops. With a pod, capacity can be scaled to the result.
- Scale (build plus flexible layer). If the product line proves itself, you start hiring the permanent team, now with a working codebase and clearer role profiles. The pod hands over in stages or continues as a flexible capacity layer.
This sequence matches the cost profile to uncertainty: fixed cost grows only once the product line has earned it.
Illustrative cost comparison for the first twelve months
The following is an illustrative calculation with assumptions, not market data. It uses the steady-state loaded cost of EUR 8,887 per engineer per month from our separate analysis of a German senior hire.
| Item | Build (4 hires) | Pod (3-person pod) |
|---|---|---|
| Months until team is productive | Hiring lag plus ramp-up; many months in practice | Short onboarding after kick-off |
| Recruiting cost | Fees for 4 hires | None |
| Running cost once in place | 4 x EUR 8,887 = EUR 35,548 per month | Fixed monthly fee per contract |
| Exit cost if product line stops | German notice periods, possible severance | Contractual notice period |
| Knowledge retained in-house | High | Depends on documentation and handover |
The decisive line is often not running cost but time to productive output and exit cost under uncertainty.
Conditions that make the pod option work
- An internal product owner with authority to decide scope and accept results.
- Code in your repositories, under your accounts, from day one.
- A sprint-based Leistungsbeschreibung with acceptance criteria and Abnahme under BGB §640.
- Documentation as an accepted deliverable, not an afterthought.
- A transition clause that defines how knowledge moves to an internal team if you build later.
Whether you choose build, buy or pod, the main recommendation stands: match fixed commitments to proven demand, and keep ownership of the product decisions inside your company.
Legal references in this guide are general information, not legal advice.
For a differentiating product line with an uncertain first year, the pod phase is where most of the risk sits, and it is the phase niogod™ was built for: a three-person pod with a German-speaking Projektleiter, delivering sprint by sprint under a Werkvertrag with Abnahme, with code in your repositories from day one. If a new product line is on your roadmap for next year, it is a conversation worth having early.
Talk to niogod™
Planning engineering capacity in DACH? Book a 30-minute consultation with the niogod™ team.
Book consultation