The first conversation with a developer usually comes down to price and timing, and the important things surface later, after the money is gone. These 15 questions help you choose a web developer and understand up front how they work, and each comes with a hint: what a good answer sounds like and what should worry you.

How to use these questions to ask a developer

You don’t need to run an interrogation. Pick the questions that matter for your project and ask them in a relaxed call or by email. Written answers are better: they are easy to compare across several developers and later move into the contract.

Pay attention to the manner, not only the content. A specific answer with examples is almost always better than general words, and an honest “we don’t do that” beats a promise to do everything.

Experience

1. Have you built similar projects

A good answer: they show one or two projects close to your task and explain how they are similar. If there are none, they say so directly and explain what relevant experience they have.

What should worry you: “We do everything”, without a single example.

2. What exactly did you do on those projects

A good answer: a clear split of roles, such as “we did the design and development, the client wrote the copy, and we still maintain it”.

What should worry you: confusion about the details of their own project, or reluctance to answer. How to dig deeper is covered in “How to check a developer’s portfolio and reviews”.

3. Can I talk to one of your clients

A good answer: they give you one or two client contacts, or promise to ask clients for permission.

What should worry you: not a single contact, whatever the excuse.

Process

4. How will the work be split into stages

A good answer: a clear sequence, for example brief, prototype, design and build, launch, support. Each stage has a result you will see and sign off.

What should worry you: “We’ll build it and show you at the end.”

5. When will I see the first result

A good answer: a specific date and a specific result, such as “in two weeks we’ll show a clickable prototype of the main screens”. At NOVO, for example, we start every project with a prototype so the client sees the main screens before development begins.

What should worry you: a vague “soon”, or a first demo months away.

6. Who will work on the project, and who will I talk to

A good answer: they name who handles design, development, and communication with you, and how fast they usually reply.

What should worry you: a manager who will “pass everything along” but can’t name a single person doing the work, or the whole job going to unknown subcontractors.

7. How do you handle revisions and new ideas

A good answer: how many revisions each stage includes, how out-of-scope work is estimated, and a promise that nothing extra is done without your agreement on the new price and timeline.

What should worry you: “unlimited revisions” (which usually means they will be done reluctantly), or a refusal to discuss any changes at all.

Money

8. What is included in the price, and what costs extra

A good answer: an itemized estimate: pages or screens, features, admin panel, mobile layout, content migration. Anything not included is listed separately.

What should worry you: one total with no breakdown.

9. How will payment work

A good answer: payment in parts tied to stages and results, against invoices and with acceptance acts. Sensible schemes are covered in “Prepayment and staged payments”.

What should worry you: a demand for the full amount upfront, or transfers only to a personal card with no paperwork.

10. What will I pay after launch

A good answer: a full list: domain, hosting, paid services, support, and for apps the developer accounts in the App Store ($99 per year) and Google Play ($25 one-time). An approximate monthly or yearly total.

What should worry you: “You won’t have to pay anything”, or a mandatory “platform license” without which the site stops working.

Ownership and access

11. Whose name will the domain, hosting, and accounts be in

A good answer: yours or your company’s, with the developer given access while they work.

What should worry you: “We’ll register it to us, it’s easier.” Whoever the domain is registered to owns it. A full list of what should belong to you is in “Who owns your website”.

12. Will I get the source code and design files

A good answer: yes, after payment you receive the code, the design source files, and the rights to them, and this is written into the contract.

What should worry you: “The code stays with us”, unless this was explained honestly from the start, for example when the project runs on the developer’s own platform.

13. What happens if we stop halfway

A good answer: you pay for completed stages and receive everything finished in them: files, access, code. This is fixed in the contract.

What should worry you: vagueness, or threats to keep everything.

After launch

14. What do you do if a bug shows up after launch

A good answer: there is a period during which bugs are fixed for free, and it is written into the contract. It is clear where to report issues and how fast they will respond.

What should worry you: “We don’t have bugs”, or every small fix after handover billed separately from day one.

15. How does support work, and what does it cost

A good answer: a few clear options, such as a monthly plan or hourly billing, with a description of what each covers. Plus a willingness to hand the project to another provider if you decide to leave. What to reasonably expect from support is covered in “What happens to a website after launch”.

What should worry you: support is only possible with this developer, and you can’t leave without losing the site.

How to choose a web developer by their answers

Ask the same questions to two or three developers and put the answers side by side in a simple table. The difference usually shows right away: one answers specifically with examples, another in general terms.

What matters is not only the answer but the willingness to put it in the contract. A verbal promise the developer refuses to write down is worth nothing.

The cheapest option isn’t always the worst, and the most expensive isn’t always the best. Compare what you get for the money: stages, demos, paperwork, ownership, and support.

In short

  • Ask your questions in writing: the answers are easier to compare and move into the contract.
  • A good answer is specific: dates, stages, examples, numbers.
  • Always ask about staged payments, costs after launch, and whose name the domain and accounts are in.
  • Find out what you get if the work stops halfway.
  • Ask for every important promise to be written into the contract.