External or internal? How custom development works

Development is not a sprint, but a wave

Every large-scale project has its rhythm. At the beginning, everything moves at full speed. Analysis, architecture, implementation, testing. Once completed, however, the demand for resources drops significantly: a smaller team is sufficient for maintenance and minor adjustments. This is the first challenge internal teams face. If new staff are hired for a major project, they may become under-utilised after a few months. Keeping them is costly, letting them go is difficult, and redeploying them elsewhere is not always an option.

Key takeaways

• Software development demand often varies throughout a project. Resource needs may peak during analysis, architecture, implementation and testing, then decline after delivery, potentially leaving newly hired internal staff under-utilised.
• External development offers flexibility to adjust capacity as project needs change. An experienced partner can also bring expertise from other sectors, helping identify risks and make informed architectural decisions.
• Outsourcing does not have to mean losing control. Access to source code and repositories, regular progress updates, clearly defined deliverables and documented interfaces help maintain transparency and reduce dependency on a single supplier.
• Where software forms the core of the business, such as a pricing algorithm, CRM or proprietary platform, or where a project is long-term and experimental, it usually makes sense to keep development in-house.
• Total cost of ownership (TCO) includes development, operation, maintenance, training, HR overhead and the cost of unused capacity. A hybrid model combining external development with internal expertise can offer a useful balance, depending on project requirements and long-term responsibilities.
• Development contracts should clearly address intellectual property rights, access to source code and documentation, responsibilities for support and maintenance, and a defined handover process. These arrangements help preserve continuity if the organisation changes suppliers or brings development in-house.

External development as flexible capacity management

The key advantage of outsourced software development is flexibility. Capacity can be adjusted to the project phase. When demand peaks, you can scale up quickly; once deployed, only minimal support is needed. No fixed costs, no lengthy HR decisions. An experienced development partner also brings know-how from other sectors. They can identify risks earlier, suggest proven architectural patterns, and optimise both development and maintenance. In practice, this accumulated expertise often provides more value than simply adding extra hands.

What external development looks like in practice

A typical scenario might look like this: a company needs to develop a specialised application, for example, a data-monitoring tool or an internal portal. The in-house team is busy maintaining existing systems, so delivery would take months. An external partner provides a ready-to-use solution faster, and after deployment, only a small internal team maintains it.

This model allows organisations to focus internal resources on strategic initiatives while external experts handle implementation and integration. The same principle is often applied when developing application layers on top of IoT platforms or integrating systems for smart metering and data management.

Worried about control? There’s another way

Loss of control is one of the main concerns about outsourcing. The key, however, lies in how collaboration is structured: access to repositories, regular progress updates, clearly defined deliverables, and a service-level agreement (SLA). These ensure the project remains transparent and predictable.

In practice, a hybrid model works best. The organisation retains its critical core team and outsources peripheral components. This approach preserves know-how while keeping capacity flexible. A clearly defined data interface also plays a major role. Open data interface, open APIs and standardised communication protocols significantly reduce vendor lock-in risk.

When to think twice about outsourcing

Custom development is not the right answer to every challenge. If the software forms the heart of your business, for example, a pricing algorithm, CRM, or proprietary platform, it usually makes sense to keep development in-house. The same applies to long-term, experimental projects that require quick decision-making and deep domain knowledge. Outsourcing delivers the greatest value when you need a solution designed, built, deployed, and maintained efficiently, with predictable costs and clear ownership.

Estimating the impact on TCO

Beyond strategic considerations, cost remains a decisive factor. The choice between internal and external development often depends on the total cost of ownership (TCO). TCO covers not only direct development costs but also operations, maintenance, training, HR overhead, and the risk of idle capacity.

In the short term, outsourcing may appear more expensive per hour, but overall it often reduces costs by removing fixed overheads and improving scalability. Conversely, for long-term systems under continuous development, an in-house team may prove more economical, particularly if its capacity can be used across multiple projects. A combined model typically offers the best balance:

• External development for implementation phases, integrations, and MVPs
• Internal teams for long-term operation, optimisation, and development of core functionality

This approach minimises TCO while maintaining independence.

Checklist: what to check before selecting a vendor

1. Transparency: do you have full access to code, documentation, and metrics?
2. Experience: does the vendor have references in similar industries or project types?
3. Communication: are reporting channels and responsibilities clearly defined?
4. Flexibility: can the vendor scale the team up or down as needed?
5. Continuity: what happens if the project ends or team members change?

Legal aspects and ensuring independence

A frequent pitfall is when clients lack access to source code and documentation. If everything resides solely with the vendor, each change brings delays and dependency. The solution is straightforward: ensure that contracts explicitly grant you access to repositories, source code, and documentation. It’s not just about control – it’s about future independence. If the partnership ends, you retain everything required to continue development with another vendor or your internal team.

The contract should clearly define who owns the source code, documentation, and data. Key clauses to include:

• Intellectual property: all rights to the code must transfer to the client once payment is complete.
• Repository access: the client must have ongoing access to project sources, enabling continuity if the partnership ends.
• Service level agreement (SLA): specific metrics for availability, response times, and issue resolution.
• Project termination: defined handover process and post-contract obligations.

A well-crafted contract not only protects your intellectual property but also preserves operational independence.

Outsourcing vs in-house: quick comparison

Glossary of terms used

• CRM (Customer Relationship Management): software for managing a company’s relationships and interactions with its customers
• Hybrid model: a collaboration model that combines internal expertise and decision-making with external development resources
• Intellectual property (IP): legal rights relating to creations such as software, designs and documentation, including rights that govern their use, modification and distribution
• KPI (Key Performance Indicator): a measurable value used to track how well a project or service meets its objectives
• MVP (Minimum Viable Product): a first version of a product with just enough functionality to be used and tested with real users
• Open API: a documented application programming interface that allows other systems to integrate with a solution and access its data or functions
• Outsourcing: assigning work, such as software development, to an external supplier rather than performing it internally
• Repository: a central storage location for source code and its version history, typically managed with a version control system
• SLA (Service Level Agreement): a contractual agreement defining expected service levels, such as availability, response times or maintenance commitments
• TCO (Total Cost of Ownership): the full cost of a solution over its lifetime, including purchase, installation, operation and maintenance
• Vendor lock-in: dependence on a single supplier or proprietary technology that makes switching to another solution difficult or costly