By Evince Technologies. Published 5 November 2026.
Start with your own clarity
Before contacting anyone, write down the problem, who will use the software, what systems it must connect to and what success looks like. It does not need to be a full specification.
Also decide who on your side will answer questions and make decisions. Slow decisions on the client side are a common cause of delays.
Check relevant experience
Ask for work similar to yours, not just a long client list. Ask what the problem was, what they built and what happened after launch. If you can, speak with a past client and ask how the company handled problems.
A strong team should be willing to tell you when something is outside its experience.
Test communication early
How they behave before the contract is a good guide to how they will behave later. Do they ask useful questions? Do they explain risks in plain language? Do they push back when something is a bad idea?
Agree on who your contact is, how often you will meet, how updates are shared and how much overlap you need across time zones.
Look past the lowest price
Compare what each quote includes: discovery, design, testing, deployment, documentation, training and support. A low price with vague scope can become expensive through change requests or rework.
Ask how the quote was calculated and which assumptions it depends on. A partner who has thought about the risks will be able to explain them.
Protect your code, data and IP
Your agreement should say who owns the source code and when ownership transfers. Make sure that you have access to the code repository, hosting accounts and domain names, preferably under your own accounts.
Check how credentials and personal data are handled, and whether your industry or country has legal requirements. An NDA helps, but it does not replace good security practices. Take legal advice for important contracts.
Start small
A paid discovery phase or small first module is a low-risk way to test a working relationship. You will see their estimates, code quality, communication and reliability before committing to the whole project.
Consider asking an independent developer to review the first code delivery if you do not have technical staff.
Warning signs
Be careful if a company agrees to everything without questions, gives a fixed price before understanding your process, avoids discussing code ownership, or will not show working software until the end.
Other warning signs are no named contact, no testing process and no clear plan for support after launch.
Plan for the end as well as the start
Agree on how the work will be handed over: source code, database structure, deployment steps and documentation. Ask what would happen if you moved to another provider. A good partner will not be worried by this question.