How to choose a software development agency.

The short answer

Judge an agency on four things: whether you own the code, whether the price and date are commitments or estimates, who you actually talk to during the build, and how they handle change. Technical skill is important but rarely the differentiator — most competent firms can build most things. Delivery behaviour is where they diverge.

The questions that predict outcomes

1. Who owns the code, and when do I get it?

The correct answer is: you do, and on delivery. Watch for agencies that host your product on their own platform, retain the repository, or make handover conditional on continued payment. This is the single most common way clients become trapped, and it is invisible until you want to leave.

Ask specifically: will I receive the Git repository, the design files, and the infrastructure credentials? Will the app be published under my developer accounts or yours?

2. Is the price fixed, and is the date a commitment?

An estimate is not a price and a target is not a date. Ask what happens if the project takes longer than expected — the answer tells you who is carrying the risk. Ask for the delivery date in the written quote.

3. Who will actually build it?

Ask whether the people in the pitch are the people who will write the code, whether they are employees or subcontractors, and whether you can speak to the engineers directly during the build. Sales teams and delivery teams being entirely different people is a well-known failure pattern.

4. How are changes handled?

Requirements always change. The question is whether change is quoted in writing before work begins, absorbed silently until quality suffers, or resisted until you stop raising things. Ask to see how a change order works in practice.

5. What happens after launch?

Ask what is included, for how long, and what maintenance costs afterwards. An agency with no answer has not thought past the invoice. An agency whose only answer is a mandatory expensive retainer is selling lock-in.

6. Can I speak to a past client?

Not a testimonial on a website — an actual conversation. Agencies confident in their delivery will arrange one. Ask that client specifically: did the date hold, what happened when something went wrong, and would you use them again.

Red flags

Green flags

• They argue features out of your first version rather than agreeing to everything.
• They tell you when an off-the-shelf product would serve you better than a custom build.
• The quote names a delivery date and a specific feature list.
• Code ownership and handover are stated in writing without being asked.
• You can message the engineers directly.
• They ask questions about your business, not only about your feature list.
• They are specific about what they are not good at.

Local, offshore, or freelance?

The honest summary: offshore is genuinely cheaper and works well when the supplier is senior and communication is structured. It works badly when the price was the only selection criterion.

A practical evaluation process

1. Write down what the software must do on launch day. One page is enough to start.
2. Approach three or four suppliers with the same brief so the quotes are comparable.
3. Compare inclusions before comparing prices — design, backend, QA, submission, handover.
4. Ask every supplier the six questions above and note who answers directly.
5. Speak to at least one past client of your shortlist.
6. Read the contract for code ownership, change handling, and termination.
7. Start with a smaller scope where possible, so the first engagement is also a test.

Where Qalmax stands on each

Code ownership

100% yours on delivery — repository, designs, credentials, no licence

Price

Fixed, written, within 24 hours of your brief

Delivery date

Named in the quote, matched to scope

Who you talk to

The senior engineers building it, on WhatsApp

Change handling

Re-quoted in writing before we build it

Payment

50% to start, 50% on delivery

References

We will put you on a call with a past client