---
title: "Software outsourcing not delivering: causes | QMates"
source: https://qmates.tech/en/services/engineering-transformation/embedded-teams/outsourced-development-not-working
description: "The vendor closes tickets, deliveries slip, the code gets redone. In software outsourcing, part of the problem sits on your side of the contract."
updated: 2026-11-21
---

Software outsourcing problems

# Our external vendor isn’t delivering, and what they do deliver has to be redone

When an external vendor isn’t delivering, the natural move is to replace them, and the new one starts from the same place: specifications written by someone else, code nobody on your side reads, technical decisions made by one party. These causes feed each other, because code that is never checked accumulates debt, and debt nobody can see makes the work ever more dependent on the people who wrote it.

## Does this sound familiar?

-   Delivered code needs fixing as soon as it arrives, and our team spends its days reviewing it.
-   Tickets get closed, yet the feature we needed doesn’t arrive.
-   Every change to a certain part of the system comes back with a regression, and the vendor’s estimates swing.
-   On our side we lack the time and the skills to discuss the vendor’s technical choices.
-   If the contract ended tomorrow, the code would be left with a team that doesn’t know how to evolve it.

## Where does the vendor’s work get lost?

The vendor works within the rules they were given, so the causes sit in those rules and in what goes unchecked on your side.

1.  ### Only the vendor makes the technical decisions

    If nobody in the company can read the code and discuss the architecture, the vendor decides alone and is judged only on dates. Senior people working inside your team read the code with you and understand the choices behind it, so knowledge of the system stays in house.

    Feeds into

    -   

    [

    Handled by

    Embedded Teams](https://qmates.tech/en/services/engineering-transformation/embedded-teams)

2.  ### The vendor gets specifications without the product context

    A team that receives tickets written by others builds what the ticket describes, and a ticket says little about what the people using the product really need. When the people who know the business and the people who write the code don’t share the words and boundaries of the domain, every handover loses something and the work comes back.

    Feeds into

    -   

    [

    Handled by

    Domain-Driven Design and EventStorming](https://qmates.tech/en/services/engineering-transformation/domain-driven-design-event-storming)

3.  ### The feature is tested and the code is ignored

    At delivery, the check is that the feature works. Debt builds up out of sight until even a simple change becomes slow and risky, and an independent reading of the code shows where it concentrates and how much it slows everything else.

    Feeds into

    -   

    [

    Handled by

    Technical Debt Assessment](https://qmates.tech/en/services/engineering-transformation/technical-debt-assessment)

4.  ### Sometimes one module blocks everything else

    In some cases the delays pile up in one place, a module that grew in a hurry and breaks something else with every change. When that happens, we stabilise that spot by working in the code alongside your people, until your team can evolve it on its own.

    [

    Handled by

    Targeted Intervention](https://qmates.tech/en/services/engineering-transformation/unblock-software-delivery)

- [The service that tackles it](https://qmates.tech/en/services/engineering-transformation/embedded-teams)
- [Not sure which cause weighs most?](https://qmates.tech/en/services/engineering-transformation/technical-debt-assessment)

## What changes when outsourced work is back under control

You know the state of the code you receive, and your team has people who read it with you and understand its decisions. Deliveries are judged by how they are built as well, and problems surface while they are still small.

Renewing the contract, changing its terms or ending it becomes a decision taken on code that stays in house. If one part was blocking progress, it is reworked and your team can evolve it.
