How to choose a custom software development company

Choosing a software development partner is one of the biggest decisions in a custom software project. The right partner turns a rough idea into a dependable system. The wrong one can leave you with something late, over budget and hard to support.

Here is how to compare suppliers on the things that actually decide how a project goes.

The most convincing proposal is not always the safest

A polished proposal with a low fixed price can look like the obvious choice. But a price is only meaningful against a clear scope. If a supplier quotes confidently without asking many questions, the risk has not gone away; it has moved into change requests, assumptions and disputes later in the project.

Look for experience with similar problems

Technology matters less than you might think. Most capable teams can learn a framework. What is harder to find is experience with the kind of problem you have: complex workflows, integrations with older systems, regulated data, multi-location operations or high volumes of transactions.

Ask for examples of similar problems they have solved, and what went wrong along the way. A team that can talk honestly about difficulties usually understands the work.

Check that they understand your business

In early conversations, notice who is doing the talking. A good supplier asks about your users, your exceptions, your data and your goals before discussing technology. Questions like these are a good sign:

  • Who will use the system, and what do they do today?
  • What happens when something goes wrong or does not follow the normal path?
  • Which systems must this work with?
  • How will you know the project has succeeded?

Compare quotes on the same scope

Quotes are only comparable when they cover the same scope and the same assumptions. Ask each supplier to state what is included, what is excluded and what they have assumed. Look in particular at data migration, integrations, testing, training, hosting and support, which are often left out of headline prices.

It also helps to understand the commercial model. A fixed price suits a well-defined scope. Time and materials suits products that will evolve as you learn. Neither is wrong, but you should know which one you are buying.

Understand how discovery works

Serious suppliers want to understand the problem before committing to a price, usually through a discovery or requirements phase. Ask what it involves, who takes part, how long it takes and what you receive at the end. A good discovery phase produces a plan you could take to another supplier if you chose to.

Agree ownership early

Before you sign, be clear about:

  • Who owns the source code and intellectual property
  • Whether the code is kept in a repository you can access
  • Whose name the cloud and hosting accounts are in
  • What documentation you will receive
  • How a handover to another team would work if it were ever needed

You should never be locked in because nobody else can see or understand your system.

Check communication and governance

Find out who your day-to-day contact will be, how often you will see working software and how decisions and changes are recorded. If the team works in another time zone, ask how many hours overlap with your working day and how urgent issues are handled.

Regular demonstrations of working software are one of the best protections you have. They expose misunderstandings while they are still cheap to fix.

Look closely at testing and quality

Ask how the supplier tests: automated tests, manual testing, user acceptance testing with your team, and how they handle performance and security. Independent certifications can also help. For example, ISO/IEC 27001 covers how an organisation manages information security, and ISO 9001 covers quality management. InfoForte holds both, and you can ask any supplier for evidence of theirs.

Ask about support after launch

Software needs maintenance. Operating systems, browsers and third-party services change, and your business will want improvements. Ask what support looks like after go-live, how quickly issues are handled and how improvements are priced.

Warning signs worth investigating

  • A detailed fixed price before anyone has asked about your process
  • Little interest in your users, data or exceptions
  • Vague answers about who owns the code and data
  • No testing or acceptance stage in the plan
  • Reluctance to show working software until the end
  • No references or examples of similar work

A practical selection process

  1. Write a short brief: the problem, the users, the systems involved and what success looks like.
  2. Speak to three or four suppliers and note the quality of their questions.
  3. Ask for comparable quotes with assumptions and exclusions listed.
  4. Check references and examples of similar work.
  5. Consider a paid discovery phase with your preferred supplier before committing to the full build.
  6. Agree ownership, governance and support in writing.

If you have not written requirements before, our guide to what to include in a software requirements specification is a good place to start.

Talking to several suppliers?

We are happy to be one of them. Bring your requirements and we will tell you honestly whether we are the right fit.

Similar Posts