Code ownership
The most important point, and the one most often left unsaid. Ask directly: who owns the source code, and can it be moved? If the answer is vague, that's a red flag. Once the work is finished, the code should be yours, and that should be written in the quote.
Fixed price and clear scope
Ask for a written quote with a clearly defined scope and timeline, not rough figures followed by add-ons later. A clearly defined scope protects both sides from misunderstandings.
Portfolio and references
Look at live websites, not just pictures. Open them on your phone, check the speed, click through them. Real projects for real clients say more than pretty mockups.
Communication, including after delivery
Who are you actually talking to: the person who writes the code, or an account management layer? Direct communication speeds everything up. And ask what happens after launch: who fixes the small things, and how maintenance works.
Frequently asked questions
An agency or a freelance developer?
Who you communicate with matters more than size. Things move fastest when questions go directly to the people who write the code, with no middlemen, whether it's an agency or a freelance developer.
What if the developer “disappears” after delivery?
That's why code ownership matters most: if the code is yours and on your account, any other developer can take over. That's why, once the work is done, we hand over the full source code and access to the admin panel, if the site has one.
