Skip to content
DT Nova

How to choose a software development partner: checks, contracts and red flags

Knowing how to choose a software development partner matters more than any single technology choice: the partner decides how well the software is built, how long it lasts and whether your company can ever take it elsewhere. This guide walks through the kinds of partner, what to check before you shortlist, who owns the code, the data protection and EU rules a good partner should already know, how to compare proposals fairly and the warning signs that should end a conversation.

It is written for business owners and managers who are buying custom software, an app or a system integration, often for the first time. We are a software company ourselves, so the guide ends with how we work; everything before that applies to any partner you consider.

The short version

  • Decide first what you are buying: a finished project, extra people for your own team, or a long-term product partner.
  • Judge partners by work you can see running and references you can talk to, not by the size of their client logo wall.
  • Make sure the contract transfers the rights in the code to your company and that the repository and hosting are in your name.
  • If the software handles personal data, the partner is a processor under the GDPR and needs a written processing agreement.
  • Compare proposals against one written scope, and start with a small paid phase before committing to the whole project.

First decide what kind of partner you need

"Software development partner" covers very different set-ups. Choosing between them first saves a lot of mismatched meetings.

Kind of partnerSuitsWatch out for
FreelancerA small, well-defined piece of work; extra hands for an existing teamOne person is a single point of failure; holidays, illness and other clients
Small or midsize software companyA complete product or system with design, build, testing and running it afterwardsMake sure the people in the sales meeting are the people who will do the work
Nearshore or offshore teamLonger projects where working-hour overlap and language are manageableTime zone gaps, hand-offs between sales and delivery, where the data is processed
Large systems integratorBig programmes around enterprise platforms such as ERP suitesJunior staffing behind senior sales, slower change, high overheads on small projects
Staff augmentationYou already run a team and need more capacity under your own leadYou carry the management, the architecture and the delivery risk yourself

The question underneath is who carries the delivery risk. With a project partner, the partner commits to a result. With staff augmentation, you buy hours and the result is yours to manage. Both are legitimate; mixing them up is where disappointment starts.

What to check before you shortlist

  • Work you can see. Live apps in the stores, systems you can be shown in a demo, and at least two clients you can talk to without the partner present. Ask those clients what went wrong and how it was handled, not only whether they were happy.
  • Similar problems, not just similar industries. A partner who has built integrations with messy legacy systems is more useful for an integration project than one who has built a nice app in your sector.
  • The named team. Who will lead the project, who will write the code, who will test it, and how much of their time is yours.
  • Engineering practice. Version control, code review, automated tests, a test environment you can use, and releases that are repeatable rather than handmade. Ask to see how a recent change went from request to production.
  • Security and hosting. Where the software and data will be hosted, how access is controlled and logged, how dependencies are kept up to date and what happens when a vulnerability is found.
  • Communication. How often you see working software, who you talk to, how decisions and changes are written down, and in which language.
  • Staying power. How long the company has existed, how many people it has and what happens to your system if your contact leaves.

Who owns the code: read this part of the contract twice

Many buyers assume that paying for software means owning it. The law does not say that. The EU Software Directive, Directive 2009/24/EC, Article 2(3), gives the employer the economic rights in a computer program written by an employee in the course of their duties, unless a contract says otherwise. The people building your software are the partner's employees or subcontractors, so without a contract term the rights stay with the partner.

  • Transfer of rights. The contract should transfer the economic rights in the code written for you to your company, or at the very least grant a perpetual, transferable licence to use, change and have others change it.
  • Source code and repository. The code should live in a repository in your company's own account from the first day, not be handed over as a file at the end, if at all.
  • Accounts in your name. Cloud hosting, domains, app store accounts and third-party services should be registered to your company, with the partner given access rather than ownership.
  • Third-party and open-source components. Ask for a list with licences. Permissive licences such as MIT or Apache 2.0 rarely cause trouble; copyleft licences such as the GPL can carry conditions on how you distribute the software.
  • The partner's own framework. If the partner builds on its own platform or libraries, find out what licence you get to them and what happens if the relationship ends.

Data protection: your partner is a processor

If the software handles personal data of your customers or staff, a partner who builds, hosts or supports it processes that data on your behalf. The GDPR, Article 28, requires you to use only processors that give sufficient guarantees, and to sign a contract that sets out what is processed and why, and binds the processor to act only on your documented instructions, keep staff under confidentiality, secure the data, help you answer people's requests, and delete or return the data at the end. Under Article 28(2) the processor may not bring in other processors, such as a hosting provider or an email service, without your prior written authorisation.

In practice, ask every candidate for its standard data processing agreement and its list of subprocessors with their locations. A partner who has neither ready is telling you how they treat data protection.

The EU rules a partner should already know

Several EU laws are changing what software suppliers and their clients are responsible for. You do not need to master them, but your partner should be able to explain what they mean for your project.

  • Product liability for software. The new Product Liability Directive, Directive (EU) 2024/2853, defines software as a product and applies to products placed on the market or put into service after 9 December 2026.
  • Cyber Resilience Act. Regulation (EU) 2024/2847 applies to products with digital elements from 11 December 2027, with the duty to report actively exploited vulnerabilities and severe incidents applying from 11 September 2026. Manufacturers must set a support period of at least five years, unless the product is expected to be in use for less.
  • AI Act. If the software includes AI features, the EU AI Act has applied in general since 2 August 2026, with obligations for high-risk uses listed in Annex III applying from 2 December 2027.
  • Accessibility. Consumer-facing services such as online shops, banking and e-books are covered by the European Accessibility Act, which has applied since 28 June 2025.

How to compare proposals fairly

Proposals for the same project can differ several times over, mostly because they do not describe the same work. Write one scope document, even a short one, and send the same text to every candidate: the problem, the users, the must-have features, the systems to connect, what is out of scope, and your timeline. Then compare line by line. Our guide to writing a software requirements specification gives a template.

CheckWhat to look for
What is includedDesign, build, testing, deployment, store submission, documentation, training and a warranty period, or only some of them
AssumptionsWhat the partner assumed about your data, your systems and your availability; these decide the real cost
Pricing modelFixed price per phase, time and materials, or a capped budget, and what happens when scope changes
MilestonesWhen you see working software, and what you can stop with if you stop early
After launchHosting, monitoring, security updates and support, with response times in writing
ExitHandover of code, documentation and accounts, and help moving to another team

Be wary of a proposal that is far below the others without saying what it leaves out. The difference is usually paid later, in change requests. For how costs build up, see our guides to custom software development cost and app development cost.

Start with a small paid phase

The best test of a partner is working with them. A discovery phase that ends in a written scope, a clickable prototype and an estimate, or a first build phase that delivers one working feature, shows how a team asks questions, writes, estimates and keeps its promises. If the fit is wrong, you have lost little and kept a scope document you can give to someone else. If it is right, the rest of the project starts from a shared understanding. For the different ways a project can be organised once it starts, see software development methodologies.

Red flags

  • A firm price before anyone has asked about your users, your data or your existing systems.
  • No references you can contact, or only references the partner wants to be present for.
  • The code stays in the partner's repository and you get access "at the end".
  • Hosting, domains or store accounts registered in the partner's name.
  • No data processing agreement, or no idea where the data will be hosted.
  • Weeks of meetings without any working software to look at.
  • Every question answered with "yes, no problem", including the ones that should have been "it depends".
  • Pressure to sign quickly because of a discount that expires.

Questions to ask every candidate

  1. Which of your past projects is closest to ours, and can we talk to that client?
  2. Who exactly will work on our project, and for how much of their time?
  3. Where will the code live, and when do we get access?
  4. Does the contract transfer the rights in the code to us?
  5. Where will the software and data be hosted, and who are your subprocessors?
  6. How often will we see working software, and how do we give feedback?
  7. How do you test, and what does a release look like?
  8. What happens when we want to change the scope?
  9. What do you do after launch, and how fast do you respond to an outage?
  10. If we part ways, how does the handover work?

How we work at DT Nova

For the record, this is how we answer those questions. Every project starts with a written scope and a fixed price per phase. The code is in a repository in the client's own account from the first commit, the rights are transferred to the client, and hosting is in the client's name in an EU data region. A data processing agreement covers our access, which the client can revoke at any time. Clients see working software every two weeks, and after launch we either run the system on a maintenance plan or hand it over. See how we work as a custom software development company, software consulting for a second opinion on a current supplier, and nearshore software development if you are comparing teams across borders.

Questions people ask

What should I look for in a software development partner?

Work you can see running and references you can talk to, the named people who will do your project, sound engineering practice such as version control, code review and automated tests, a written view on security and hosting, and a contract that gives your company the source code and the rights to it. Fit matters too: language, time zone, the size of projects they usually take and how they report progress.

Who owns the code a software partner writes?

It depends on the contract. Under the EU Software Directive the employer gets the economic rights in a program written by an employee, but a supplier's staff are the supplier's employees, not yours. Without a clause that transfers the rights, or at least grants a broad licence, and an obligation to hand over the source, the code may not be yours to change or move. Ask for the transfer in writing and for the repository to sit in your own account.

Should we choose a fixed price or time and materials?

Fixed price per phase suits work that can be described well in advance: you know the cost of each step and can stop between phases. Time and materials suits work whose scope will change as you learn, but needs closer follow-up. Many projects combine them: a fixed-price discovery phase, then fixed-price phases or a capped monthly budget for the build.

Is it safe to choose a partner in another country?

It can be, if the contract, the data protection terms and the working rhythm are right. Check where the data will be processed and hosted, whether a data processing agreement and any transfer safeguards are in place, how much the working hours overlap, and whether the team can work in your language. Distance matters less than clarity.

How do we test a partner before a big project?

Start with a small paid piece of work: a discovery phase that ends in a scope and an estimate, or a first phase that delivers something working. You see how they ask questions, write, estimate and deliver, and the result is useful even if you choose someone else for the rest.

Sources