Short answer
Look at experience with similar projects and references, at whether the developer understands your business (asks questions instead of promising straight away), at the process and communication, source code rights, documentation and maintenance terms. The price should be justified by the scope, not just be low.
What to check
- Experience with similar projects — ask to see real systems and results.
- References — talk to their clients.
- Business understanding — a good developer asks about your process first.
- Process — how planning, demos, testing and handover work.
- Team — who exactly will work on the project.
- Technologies — widespread and maintainable. See programming languages.
- Rights — source code, data, access. See who owns the source code.
- Maintenance — response times, updates, costs after launch.
Warning signs
- A price without looking at the requirements.
- Promises that “it will all be ready very quickly”, without a clear scope.
- No demos during the project.
- Avoiding questions about source code and documentation.
Our approach
We start with a conversation and a process analysis, work with regular demos and stay with you after launch. Our clients range from public institutions and large companies to small and medium businesses. See our IT projects.