Ask a web developer five things before hiring. What exactly will you build, and what is left out? Who owns the code, the domain and the accounts? What does the quote include, and how are changes handled? Who fixes things after launch? Will you show working progress every week? Get the answers in writing. The 18 questions below work for a website, store or app, and for a freelancer, agency or small studio.
Scope and process
| Question | Good answer | Warning sign |
|---|---|---|
| 1. What will you build, and what is not included? | A written scope: main user steps, a screen list, an out-of-scope list. See writing a requirements document. | A quote after one short chat, or "an app like X" with nothing written down. |
| 2. Will you show working progress every week? | A live link you can try on your own phone, on a regular day each week. | Screenshots only, or "you will see it when it is done". |
| 3. Will we see a prototype before the build starts? | A clickable prototype of the key screens, approved first. | Straight to coding, with no agreed screens. |
Ownership and access
Create every account that matters under your business, with your email and billing, and invite the builder in as a member. Moving accounts later adds steps and risk.
| Item | Should be in | Check at handover |
|---|---|---|
| Code repository | Your organisation's account | You are owner or admin |
| Domain and DNS | Your registrar account | You can log in and see records |
| Hosting and database | Your cloud accounts | Your billing, backup restore tested |
| Service accounts | Your business email | Builder is a member only |
| App store accounts | Your Apple and Google accounts | Apps listed under your name |
| Design files | A folder you control | Editable, fonts noted |
| Secrets and keys | Your password manager | Old keys rotated |
| Documentation | Inside the repo | A new developer could follow it |
DNS records say where your domain points. Whoever controls them can take the site offline or intercept email, so protect the domain first.
| Question | Good answer | Warning sign |
|---|---|---|
| 4. Which account will the repo, domain and hosting be created in? | "Your organisation's account, you as owner, us as collaborators, from day one." | Everything on the builder's personal accounts, or vague answers about the domain. |
| 5. For an app, who owns the app store accounts? | Your own. Apple says an organisation must have a D-U-N-S Number, and for individuals your personal legal name will be listed as the seller. Google says an organisation account needs a D-U-N-S number. Start early. | "We publish under our account and transfer later." Transfers have conditions: Apple's app transfer overview, Google's transfer guide. |
| 6. What do you hand over at the end? | Code, editable design files (not only images), plain documentation on running and deploying, a record of where each secret lives, and a list of licensed fonts, images and paid libraries. Old keys rotated. | "We will explain it at handover." |
| 7. If we part ways, can everything be taken elsewhere? | Yes: code, data and accounts, with steps written down. | "We host it for you" with no export of code or data. |
| 8. What does the contract say about ownership of the work? | Wording that assigns the intellectual property in the deliverables to you once paid, and says what the builder keeps, such as general tools they reuse. Have a lawyer read it. | No clause, or ownership only after an open-ended condition. |
Cost and contract
For what drives cost, see app development cost in India.
| Question | Good answer | Warning sign |
|---|---|---|
| 9. What does the quote include, and what does it leave out? | A list by deliverable: design, build, testing, content entry, launch, handover. | One lump sum with no breakdown. |
| 10. Is the scope fixed, or billed by the hour? | A clear statement of which, and what happens if the estimate changes. | A fixed price with no written scope behind it. |
| 11. How are changes handled once the build starts? | Write it down, say what it touches, then swap it for something in scope, price it, or move it to version two. | "No problem, we will fit it in", with no note. |
| 12. What is the payment schedule, and what triggers each payment? | Stages tied to things you can check, the last one after launch or handover. | Everything up front, or payments tied only to dates. |
| 13. What running costs follow launch, and in whose name? | Each service (hosting, domains, payments, email, maps, AI providers) listed, billed to your account. | Bundled "maintenance" with no list of what it covers. |
After launch and fit
| Question | Good answer | Warning sign |
|---|---|---|
| 14. What happens if something breaks after launch? | A stated period of fixes, how to report a problem and how fast you get a reply. | No support terms at all. |
| 15. Who handles updates, security patches and backups? | Named owners, backup frequency, where backups are kept and who can restore one. | "It does not need maintenance." |
| 16. Which changes can we make without a developer? | An admin area or content editor for routine changes, and a short guide. | Everything is hard-coded. |
| 17. Can you show similar work that we can try ourselves? | Live examples, each labelled a client project, a concept or a prototype. For client projects, someone you can talk to. | Screenshots only, or concept work passed off as client work. |
| 18. When would you say this is not a good fit? | Honest limits, including "you may not need custom work". See WordPress vs custom website. | Yes to everything, timelines included. Compare with how long an app takes to build. |
Freelancer, agency or small studio
- Who does the work. A freelancer is usually one person who talks and builds. An agency or studio may split roles. Ask who, by name.
- Continuity. If one person is away, a solo project can stall. Ask what happens then, and keep code and accounts in your name.
- Overhead. Larger teams add process time. Solo work has less, and less cover.
A project with us starts with an intro call, then a written scope and a quote. Code and accounts are set up in your name. Tell us about your project.
Frequently asked questions
What are some good questions to ask a web developer?
What is included and excluded, who owns the code, domain and accounts, how changes are handled, what happens after launch, and whether you will see working progress each week. Good answers are specific and written down.
What should I ask a web developer before hiring them?
Ask for a written scope, a quote that says what it includes, the account where your repo, domain and hosting will sit, and the support terms after launch. Ask to see similar live work. Put the answers in the contract.
How do I choose a web development company?
Compare written scopes, not headline quotes, and check each covers the same things. Ask for live examples you can try, and prefer the team that asks questions before it quotes.
Should I hire a freelancer or an agency?
Neither is better for every project. A freelancer often means less cover if they are away. An agency or studio may offer more continuity and more process. Either way, keep code and accounts in your name and get the scope in writing.
Who should own the code and domain of my website?
You should. Create the repo, domain, hosting and service accounts in your business name from the start, with the builder invited as a member. The contract should assign the intellectual property in the deliverables to you once paid. Ask a lawyer to review the clause.