5 min read

Choosing a software development agency: the criteria

The criteria for choosing a software development agency: references, the real team, code ownership, maintenance, questions to ask and warning signs.

Three quotes side by side, with notes in the margin

When choosing a software development agency, check five things before you even compare prices: references you can actually verify, the team that will really work on your project, the delivery approach, who owns the code, and what is planned after delivery. A low quote that stays vague on those points often ends up costing more.

There are plenty of agency rankings. They can help you build a first shortlist, but they are much less useful when it comes to making the final call. This guide brings together the criteria that matter, the questions to ask in the first meeting, and the warning signs to watch for.

Before you look for an agency: know what you want built

An agency cannot respond well to a vague need. Before the first meetings, put this on one page:

  • the problem to solve, and who deals with it day to day
  • what already exists, whether that is tools, spreadsheets, or data
  • what is essential for launch, and what can wait
  • the constraints you already know about: timeline, available budget, security, hosting

Even before that, one question needs a clear answer: do you really need a custom build, or could existing software be enough? We covered that in our article on custom software development or off-the-shelf software, which helps you decide when custom business software is worth it.

Criteria for choosing a software development agency

  1. Verifiable references. Ask for projects similar to yours and, if possible, the contact details of a client you can call. A logo on a website does not tell you what the agency actually delivered. Check: the agency’s exact role in the project, and whether the software is still in use.
  2. Suitable technology, clearly explained. The agency should justify its technical choices based on your needs, not its habits. Check: whether another provider could take over the code if needed.
  3. The actual team. Who will really do the development work: the agency itself, freelancers, an overseas subcontractor? None of these models is a problem in itself, but you need to know. Check: the name and role of the people who will work on the project.
  4. A clear way of working. Regular deliveries, demos, and the ability to adjust along the way. Check: how often you will see the software running.
  5. Ownership of the code. In France, rights to software developed by an external provider do not automatically transfer to you. The assignment must be written into the contract (article L131-3 of the French Intellectual Property Code). Check: a clause assigning the rights, and access to the code repository from the start.
  6. Maintenance after delivery. Software keeps evolving after it goes live: security updates, fixes, and changes. Check: what is included, under what terms, and what happens if you switch providers.
  7. Hosting and data. Where will the data be hosted, who will have access to it, and how will it be backed up? If the agency processes personal data on your behalf, the GDPR requires a contract that governs this processing (Article 28 GDPR). Check: the hosting region and whether this clause is included.

Questions to ask in the first meeting

QuestionReassuring answerRed flag
Who will actually be working on my project?Specific names, clear roles, and one person clearly accountable“Our team,” with no further detail
Can you show me a similar project?A real walkthrough, with a client you can contactScreenshots shown without any context
Who will own the code?You will, with an assignment clause included in the contractA vague answer, or only a usage licence
How will I track progress?Regular demos on a working versionOnly a progress report, then the software delivered at the end
What happens after launch?Maintenance clearly described, with the terms set out“We’ll deal with that when we get there”
What could cause the project to go off track?Concrete risks tied to your specific needs“Nothing, everything is under control”

Comparing quotes: what drives the price

For the same project, two quotes can be far apart. That gap does not necessarily come from the agency’s margin. It mostly comes from what each quote includes:

  • the scope covered: two agencies do not always understand the need in the same way
  • the discovery and scoping work: a quote that starts with an analysis phase is often more reliable than one priced immediately
  • connections to other tools: management software, payments, tools already in place
  • the expected level of quality: automated testing, security, accessibility, documentation
  • hosting and deployment
  • maintenance, whether included or not

To compare quotes properly, bring them back to the same baseline: the same list of features, the same quality level, and the same post-delivery services. A very detailed fixed-price quote when the need is still unclear should raise a flag. Either the agency has made assumptions you do not know about, or change requests will come later.

Warning signs

  • The agency gives you a quote without asking any questions about your business.
  • No one can tell you who will actually build the project.
  • The code stays with the agency, and you have no access to it during the project.
  • The contract says nothing about transferring rights or maintenance.
  • The references cannot be verified.
  • They promise everything, fast, with no caveats at all.

Agency comparison platforms: useful, within limits

Platforms that match companies with agencies can save time when you are building an initial shortlist, reading reviews, and collecting several proposals. They do not replace your own due diligence.

Rankings may reflect factors other than the quality of the work, and reviews do not always tell you whether the project was comparable to yours. Use them to build that first shortlist, then apply the criteria above.

Local agency or remote agency

Part of the project can be handled very well remotely. Other stages are often easier in person: the initial scoping, workshops with future users, and difficult decisions. A nearby agency makes those exchanges easier, especially if your teams are not very comfortable with video calls or if the software is tied to a hands-on field role. If you are in Normandy, our team works from Caen: see our page on web agency in Caen.

Proximity does not replace any of the previous criteria. It goes on the list when you are hesitating between two agencies that are otherwise comparable.

Assess your project

If your needs are already clearly defined, you can browse our projects as well as our web development and mobile development services. If you still need to clarify the scope, an audit can help frame the project before requesting quotes. Depending on the case, part of the project may also be funded through public grants.

Frequently asked questions

How do you choose a software development agency?

Check for comparable references, the actual team that will work on the project, the reporting process, code ownership, and the planned maintenance. Then compare quotes on the same basis.

Agency or freelancer to build software?

A freelancer can be a good fit for a limited scope. An agency brings multiple skill sets and ensures continuity if one person is unavailable. In both cases, the same criteria apply.

Who owns the code for software developed by an agency?

In France, the rights remain with the agency unless the contract includes a written transfer. Check that clause before signing.

Why are software development quotes so different?

Because they do not always cover the same scope. Discovery, connections to other tools, testing, hosting, and maintenance may or may not be included.

Book a meeting

Talk about your project

Take 15 minutes to review the process and the next step.

Book a meeting with Perfusion.dev
Back to blog