Business · Procurement

How to choose a software development partner: a checklist for business owners

Most disappointing software projects were decided at the selection stage. Ten things to check before you sign, none of which requires you to read code.

Pikabyte Engineering 3 min read

A business owner choosing a software vendor is buying something they cannot inspect, from people who know far more about it than they do, to be delivered months later. It is no surprise that many projects disappoint.

You cannot judge the code. You can judge almost everything else. These are the ten checks we would make, including the ones that might count against us.

Before the proposal

1. Did they try to understand the business?

Count the questions. A vendor who quotes after one meeting has priced their assumptions, not your problem.

A good partner asks to speak to the people who do the work, not only the person paying. They ask to see the spreadsheet, the form, the old system. They ask what happens in the awkward cases.

2. Can you see it before you sign?

This is the most useful test, and few buyers apply it.

The usual order is proposal, quotation, contract, then months of building before you see anything. By the time you learn the vendor misunderstood, you have paid for it.

Ask for a working demo of your system first. Not a generic product tour. A demo built around your workflow, that you and your staff can open in a browser and use.

We build one for every prospective client before sending a proposal or a price. It is the fastest way for both sides to find out whether we understood the problem, and it gives you something concrete to compare against any other quotation.

3. Will you talk to the people who build it?

If the person you meet will not be writing the software, ask to meet the person who will. Requirements lose detail every time they pass through someone.

In the proposal

4. Who owns what?

Three things should belong to your company, in writing:

  • The source code, in a repository you can access
  • The data, exportable at any time
  • The cloud account it runs in, registered to you

If the vendor holds any of these, leaving them means starting again. We have seen businesses that did not hold the credentials to their own production data.

5. Is the price for a defined thing?

A fixed price needs a defined scope, and the scope should be written in terms you understand: which screens, which documents, which rules. If you have used a demo, the scope can refer to it.

Ask how changes are priced. There will be changes.

6. What does it cost after launch?

Hosting, support, security updates, and the hourly rate for future work. A cheap build with an expensive retainer is not cheap.

About how they work

7. How often will you see progress?

Weekly, on a working environment you can log into, is the standard to expect. Monthly status reports are how projects go wrong quietly.

8. How do they know it works?

Ask whether the software has automated tests, and whether releases go through a deployment pipeline or someone copies files by hand. You do not need to understand the answer in detail. You need to hear a confident, specific one.

Ask for a number. One of our platforms has more than a thousand automated tests. That is what lets it be changed safely years later.

9. How do they handle security?

Ask how access to your production system is controlled, and whether anyone uses shared passwords or long-lived keys. Ask what happens to access when one of their staff leaves.

A vendor with administrator access to your systems is part of your security. Their habits are your risk.

10. Can you talk to a client?

Ask to speak to one, and ask the client two questions: what went wrong, and how was it handled? Every project has problems. The response is what you are buying.

Warning signs

  • A quotation within a day of the first meeting
  • “We can do everything”
  • Reluctance to put ownership in writing
  • No working software until the end
  • A team you never meet
  • Pressure to sign quickly

A way to compare quotations

Prices differ because assumptions differ. To compare fairly, ask each vendor the same things: what is included, what is excluded, what running costs will be, who owns the code and the account, and when you will first use working software.

The cheapest quotation is often the one that has understood the least. The best protection is to have used something real before you choose.

Written by

Pikabyte Engineering

Pikabyte builds custom business systems, applied AI and secure cloud infrastructure from Malaysia. Talk to us.

Start a conversation

Want this applied to your business?

Tell us what is slowing the business down. You will talk to an engineer, not a salesperson, and get a straight answer on whether software is the right fix.