Start by writing down what you need
Before you compare anyone, write a page on the problem, the users, what success looks like, your budget range and your deadline. Decide who on your side can make decisions, since that affects a project as much as the vendor does.
Questions to ask every company
The answers matter less than whether they are specific.
- Who owns the code?
- It should be assigned to you in writing, including work by subcontractors.
- Who will actually work on it?
- Ask to meet them, rather than only the sales team.
- Can I see the work as it happens?
- Look for repository access and a staging environment from early on.
- How are changes handled?
- There should be a written process with a clear effect on cost and time.
- How do you test and secure the work?
- Ask for a specific description of what they actually do.
- What happens if we part ways?
- You should receive the code, accounts and documentation without a dispute.
How to check their claims
Ask to speak directly with past clients about similar work, including what went wrong. Look at real code or architecture documents if you can, and have an independent engineer review them if you are not technical. Directory reviews help, but check how recent they are and note that placement on some directories can be paid for.
Warning signs
Be careful if you see any of these.
- A quote with no questions
- They cannot have understood the work.
- Promises with no trade-offs
- Every project balances scope, time and cost.
- Code kept on their systems
- You should have access to your own code throughout.
- Accounts in the vendor's name
- Domains, hosting and app stores should belong to you.
- Large payment up front
- Payments should follow delivered stages.
Contract terms that protect you
Have your own lawyer review the agreement. It should cover ownership of the work, confidentiality, payment stages, the change process, warranties, termination and handover. For work across borders, also check the governing law and how a dispute would actually be resolved.
Start with a small paid phase
The best test is real work. A paid scoping phase or small first release shows you how a company communicates, estimates and delivers, while limiting what you can lose. If it goes badly, you still keep what you paid for and can take it elsewhere.
Common questions
Should I choose the cheapest quote?
Not by itself. Compare what each quote includes and assumes. The cheapest proposal often leaves out testing, documentation or handover.
Does company size matter?
Fit matters more. A small firm can give you senior attention, and a large one can add capacity quickly. Ask who would actually work on your project.
Should the company be local?
Not necessarily. Enough overlap in working hours, clear communication and a contract you can enforce matter more than location.
Looking for help with this? See Web application development.