“We need something built, and I don’t know how to tell a good software company from a bad one.” That’s a fair worry. Every company’s website says roughly the same things. The proposals are full of terms you can’t check. And by the time you find out whether you chose well, you’ve spent the money.

You don’t need technical knowledge to choose well. You need to ask the right questions and know what good answers sound like. This guide is a practical checklist you can use with any company, including us.

Start with the business problem, not a technical spec

Many businesses think they need to write a detailed technical specification before they can talk to a software company. You don’t, and it’s often better if you don’t.

Describe the problem in your own words instead. “Our systems don’t talk to each other.” “We re-type every order twice.” “Our customers can’t book online.” A good company will ask questions until it understands what’s really needed, then turn that into a plan.

Pay attention to how they respond. A company that jumps straight to which technology to use, before understanding your business, is solving its problem rather than yours. A company that asks how the work happens today, who does it and what goes wrong is on the right track.

A good company will also tell you when you don’t need custom software at all. Sometimes an off-the-shelf product, or connecting tools you already have, is the better answer.

Who will actually do the work?

This is the most important question, and the one most often skipped. The people you meet in the sales conversation are not always the people who build your software.

Ask directly:

  • Will the work be done by the company’s own staff, or passed on to someone else?
  • How experienced are the people who will build it?
  • Will the same people stay on the project from start to finish?
  • Who makes the technical decisions, and who checks the quality?

There’s no single right answer. But you should get a clear one, and it should match what ends up in the contract.

People also ask what a software engineering consultant is. It’s an experienced engineer who advises on technical decisions: what to build, how, and with which tools. Some consultants only advise. Others, like a development company, also build. Know which you’re hiring, so you’re not left with a plan and nobody to carry it out.

Getting the scope and price in writing before anything starts

A scope is a written description of what will be delivered: what the software will do, what it won’t do, how it will be tested and when it will be finished. Before any work starts, you should have:

  • A written scope in plain language you can understand
  • A price agreed in writing, either a fixed price for the project or a clear monthly figure for ongoing work
  • What happens if things change. New ideas always come up. How are they priced and agreed?
  • What “done” means. How will you both know the work is finished and working?

Be careful with open-ended hourly billing and no estimate of the total. It isn’t always wrong, but it puts all the risk on you. If you’d like to compare the cost of a project with hiring someone, our guide to what a developer really costs sets out the numbers.

Who owns the code, the data and the accounts

Ask this before you sign, not when you want to leave. You should know:

  • Who owns the software that’s built for you, and when ownership passes to you
  • Whose accounts it runs in. Hosting, domains and software subscriptions should ideally be in your name, so you’re never locked out
  • Who owns your data, and how you get it out
  • What happens if you part ways. Will you get everything you need to carry on with another team?

A company that’s confident in its work won’t mind these questions. Vague answers are a warning sign.

One point of contact compared with a rotating team

Some companies give you a different person for every stage: sales, project management, development and support. Each handover is a chance for something you said to get lost, and you end up explaining your business again and again.

One consistent point of contact, who knows your business and stays with you, makes the whole thing calmer. You know who to call, and they already know the background. Ask who your contact will be, and whether that will change once the contract is signed. If you’re still deciding between different kinds of help, we compare the options in how to choose between the ways of getting technical work done.

Questions to ask on a first call

Take this list into any first conversation:

  1. Can you explain what you’d do, in plain English?
  2. Who exactly will build this, and will they stay on it?
  3. Will I get the scope and price in writing before anything starts?
  4. Who will be my one point of contact?
  5. Who owns the code, the data and the accounts?
  6. How will you test it before we rely on it?
  7. What happens after it goes live, if something breaks or needs changing?
  8. Can you show me similar work, or put me in touch with a client?
  9. What would make you say this project isn’t a good fit for you?

The last question is a useful one. A company that can’t think of any reason to turn work down may not be thinking very carefully about yours.

How Agapi answers these questions

Since we’ve asked you to put these questions to everyone, here are our answers. You describe the problem in plain English, with no specification needed. The work is done by Agapi’s own senior engineers, and we manage the developers and the technical decisions, so you never have to. You have one consistent point of contact throughout. The scope and price are agreed in writing before any work starts, either as one flat-price project or an ongoing arrangement sized to the work. You own everything we build, and it runs in accounts you control. You can see the steps in how it works.

Being honest about the limits

No checklist removes all the risk. Software projects uncover surprises, and even a good company will occasionally misjudge something. What the checklist does is make sure that when a surprise comes, there’s a written scope to refer back to, a person who’s accountable, and a clear way to agree what happens next.

The short version

Start with the problem, not a spec. Find out who will really do the work. Get the scope and price in writing, settle ownership before you sign, and choose a company that gives you one consistent point of contact.

If you’d like to ask us these questions directly, book a free 30-minute call. It’s plain English, and there’s no obligation.