In short: Choose a partner who asks about your business goals, shows real references you can visit, prices the work clearly, and commits to a system that another developer can take over.
What to check in references
A reference is only worth something if you can look at it and the developer can explain what the task was.
- A live product or website, not just screenshots.
- A project similar to the one you have in mind.
- A concrete answer on who worked on it and what their own role was.
Which questions to ask
Ask these in the very first conversation:
- How does planning work, and what do I get before work starts?
- Who will be my contact, and can I talk to the developer directly?
- What happens if my requirements change during development?
- How do you test the system, and what do you hand over at the end (code, documentation)?
- Who runs the system and fixes bugs after launch?
Warning signs
Not every bad offer looks bad at first glance. Watch for these:
- They do not ask about your business goals and quote a price straight away.
- They cannot or will not show a real reference you can visit.
- An unrealistically low price or short deadline with no explanation.
- No word about testing, documentation or handover.
- They promise everything and never say that something is not worth doing.
Agency or direct developer?
At agencies there are often several layers between you and the code: an account manager, a project manager, a go-between. That is not always a problem, but it can slow decisions and add misunderstandings. With direct contact, the person who hears your request is the one who builds it. Both have their place; the point is to clarify up front who is responsible for the result.
How to get started
Ask two or three partners for a free consultation, describe the same task to each, and compare the questions they ask. The one who understands your business best is usually the best choice.
With us, the first consultation is free and without obligation.