Choosing a developer: 8 questions to ask when hiring an agency or freelancer

You've decided to have a website, a mobile app, or custom software built for your business. Now comes the hard part: who do you give the job to? Quotes vary wildly, everyone says "we can do it," and the technical details are hard to judge.

A wrong choice is usually not noticed right away. The project stalls, the budget doubles, or once the work is done nobody picks up your calls. Making the right developer choice is the first decision that shapes the fate of your project. In this article, I've gathered the questions to ask when meeting a developer or agency and the warning signs to stay away from.

8 questions to ask in the meeting

1. Have you done similar work before?

Instead of a generic portfolio, ask about work that resembles your need. If you want a booking system, ask to see a booking system; if you want e-commerce, ask for an e-commerce example. If possible, open the live link and try it yourself.

2. What is included in the price, and what is not?

Two quotes for the same "website" may actually describe very different jobs. Ask one by one whether design, content entry, domain name, hosting, SSL, email, number of revisions, and post-launch support are included. Ask for the answers in writing.

3. Who will do the work?

Will the person you're talking to write the code, or will the work be handed to someone else? Subcontracting is not bad in itself, but know from the start who your contact is and who will answer technical questions.

4. How will the process go, and how will I see progress?

A good developer breaks the work into stages and shows you something working at each one. Working with someone who says "I'll deliver in three months" and shows nothing in between is risky. Ask for short weekly or biweekly demos.

5. Who will own the source code, domain name, and accounts?

This is the most overlooked question and the most expensive one. The domain name, hosting, server, and app store accounts should be opened in your name. When the project is finished, you should have access to the source code. Otherwise, when you part ways with the developer, you may not even be able to reach your own site.

6. What happens after launch?

Who will handle bugs, updates, security patches, and small changes, and at what price? Is there a monthly maintenance plan, or is it hourly work? Clarify this before the project starts.

7. What is the payment plan?

Neither paying everything upfront nor paying everything on delivery is healthy. The common and fair method is to split the work into stages and pay as each stage is completed (for example, a portion at the start, a portion at an interim delivery, and the remainder at launch).

8. Can you give references?

Ask for the contact details of one or two previous clients and have a short phone call. The answers to "Did they deliver on time? Could you reach them when problems came up?" are worth more than any portfolio.

5 warning signs to stay away from

• They quote a price without asking you questions. A price given without understanding your need is either inflated or will grow later through extra fees.
• A quote far below the market. The difference usually comes back as poor-quality work, a stalled project, or hidden costs.
• They don't want to make a written agreement or scope document.
• They insist on keeping the domain name, hosting, or source code under their own name.
• They reply to your messages late and irregularly even during the meeting stage. Once work starts, this usually doesn't improve; it gets worse.

A short checklist

If you prepare the following before requesting quotes, both choosing the right person and comparing offers become much easier:

• A short one- or two-page description of what you want
• A few example sites or apps you like and dislike
• Your approximate budget range and target date
• A separation between must-have features and "can wait" features

The right developer is not just someone who writes code, but a partner who helps you clarify your need. If you're working with someone who asks you many questions in the meeting, can say "you don't need this feature for now," and puts everything in writing, you're on the right track.