Journal · Checklist

Software outsourcing checklist: ten questions to ask before you sign

ArmTri Team · Oct 16, 2026 · 4 min read

Most outsourcing problems trace back to questions nobody asked at the start, and these ten cover the people, the process, the contract and the exit.

Why software outsourcing needs a checklist

Software outsourcing can save you months, or cost you months, and the difference is often decided before any code is written. Most problems that appear later, such as missed deadlines, unclear quality or disputes about who owns the code, trace back to questions nobody asked during vendor selection.

Here are ten questions to ask before you sign, grouped into people, process, contract and the end of the relationship. Write the answers down, and compare vendors on the same list.

Questions about the people

One: who exactly will work on my product? Ask for names, roles and profiles of the actual people, not the people from the company's showcase projects. Ask whether those people can change during the project and how you will be told.

Two: have they built something similar? Industry experience matters. A team that has built a booking platform before already knows about time zones, cancellations and double bookings.

Ask for an example from a comparable project and what they learned from it. Specific answers about real problems are a better signal than a long list of past clients.

Three: how many hours will they share with us each day? Overlapping working hours decide how quickly questions get answered and decisions get made.

As a rule of thumb, a few hours of daily overlap with the person who answers product questions is enough for most projects. Ask the vendor to name those hours in the proposal, so they become a commitment rather than a hope.

Questions about the process

Four: how will we see progress? Look for regular demos of working software, not just status reports. You should be able to click through what was built every week or two.

Five: how is quality checked? Ask about code review, automated testing and who tests releases before they reach your users.

Ask to see a recent code review, with names removed if needed. The way reviewers comment and the way authors respond tell you more about quality than any description of the process.

Six: what happens when requirements change? They will. A good partner has a clear way to handle changes in scope, cost and timeline without a negotiation every time.

Questions about the outsourcing contract and code ownership

Seven: who owns the code? The outsourcing contract should state clearly that the intellectual property in everything built for you transfers to your company. Code ownership should not depend on a final payment milestone that might become a dispute.

Eight: where does the code live? Ideally in a repository your company owns from day one, with the team invited as collaborators. The same applies to cloud accounts, domains and app store accounts.

Nine: how is pricing structured, and what is not included? Fixed price, time and materials or a monthly team fee can all work, but each shifts risk differently. Ask explicitly about hosting, third-party services, maintenance and support after launch.

A short review by a lawyer who knows software contracts is worth it before you sign.

The question most people forget

Ten: what happens when we stop working together? Ask how the handover works: documentation, access, and a walkthrough for your next team or your in-house engineers. A good partner plans for the end from the beginning, because it makes them easy to work with, not hard to leave.

It also helps to agree on a notice period that gives both sides time to wrap up properly, and on who pays for which accounts and services during the transition.

If a vendor gets uncomfortable with this question, that tells you something.

The short version

Before you sign a software outsourcing deal, ask about the actual people, their relevant experience and time zone overlap; about progress, quality and changes; about code ownership, where the code lives and what the price includes; and about how the relationship ends.

At ArmTri, several of these questions are part of how we assemble teams: each person is matched for skill, personality and industry knowledge, with reviews from earlier work and overlapping working hours. If you want to see who would build your product, describe it and we will assemble the team.