What to ask a developer before you pay anything

Six questions that separate accountable developers from the ones who go quiet mid-project.

What to ask a developer before you pay anything

Most project disputes start before the first line of code is written. They start when two people leave a call with different understandings of what was agreed.

Here are six questions worth asking any developer before you transfer a deposit.

1. What exactly is included in the price?

Ask for a written list: pages, features, integrations, third-party services. If the answer is vague, the invoice won't be.

2. How many rounds of revisions are included?

Revisions are where fixed-price projects go wrong. A clear number prevents it. Ask what happens if you need more: is there an overage rate, and is it written down?

3. Who owns the code and credentials on delivery?

You should own your domain registrar, hosting account, code repository, and any third-party services the site connects to. If a developer hosts the site on their own account and you fall out, you may lose the site entirely.

4. What is the timeline, and what are the milestones?

A two-week timeline means nothing without dates attached to deliverables. Ask for a brief that names what you will see and when.

5. What happens after launch?

Does the price include any post-launch support? For how long? At what rate? This is where a lot of clients get surprised by a separate invoice.

6. Can I talk to someone who has worked with you before?

A portfolio shows aesthetics. A reference call shows reliability. Ask for one.

At Bhambri Industries, the answers to all six questions are in writing before any work starts. That is not a competitive advantage. It is the minimum standard.