Syed Abbas Ali (Abby)
Full Stack Developer · Delhi, India
The brief is where a good project begins — before any code is written.
A significant portion of my client work begins with the same opening line: 'My previous developer disappeared' or 'The agency delivered something we can't edit' or 'We paid ₹2 lakh for a website that doesn't show up on Google.'
These situations are avoidable. The mistakes that lead to them are consistent and predictable. Here's what I'd want to know if I was on the other side of the table.
Ask to see the source code of previous projects
Any competent developer should be able to show you a repository or code preview of something they've built. If they deflect this question, that's important information.
You don't need to understand the code. What you're looking for is: does it exist, is it organised, and can you take ownership of it? A developer who builds sites inside a platform you don't control can't hand over the underlying code — they're building you a dependency, not an asset.
Ask specifically: 'Can I get the full source code and Git repository at the end of the project?' If the answer is anything other than a clear yes — pause.
Portfolio should match what you're building
A developer who has only built landing pages should not be your first choice for a complex booking system. A developer who has only built WordPress blogs is probably not the best fit for a React-based SaaS.
Ask: 'Have you built something similar to what I'm describing?' If the answer is no, ask how they'd approach it. Informed uncertainty is fine — blind confidence is a red flag.
Get the scope in writing before any money changes hands
This is the single most common cause of project disasters. 'You said you'd include a blog' versus 'I quoted for a static site only' is a conversation that ends relationships and projects.
A written scope document should include: exactly what pages are being built, what functionality is included, what content you need to provide, what constitutes 'done', the timeline, and the payment structure.
If a developer won't put the scope in writing, don't work with them. A good developer protects themselves with documentation the same way they protect you.
"The most expensive words in web development are 'I thought that was included'."
— Every project dispute, ever
Understand the payment structure
Paying 100% upfront gives you no leverage if something goes wrong. Paying 0% upfront is unfair to the developer spending weeks on your project.
A reasonable structure: a deposit on agreement (25–50%) with the remainder on final delivery and approval. Final payment should only be made when you have reviewed and approved the work.
Be sceptical of anyone who wants full payment before starting. Be equally sceptical of anyone who agrees to deliver a complete project with zero deposit — it suggests either desperation or a model where they half-finish and move on.
Final thought
Hiring a web developer is a meaningful business decision. The right one builds you an asset that generates leads for years. The wrong one costs you time, money, and the opportunity cost of a website that doesn't work. The questions above are ones that good developers answer confidently and clearly. If you're going through this process and want a second opinion on a quote or brief you've received, reach out. I don't charge for a 20-minute conversation.
Syed Abbas Ali(Abby)
Full Stack Developer & Web Architect based in Delhi, India. 3+ years building websites and web applications for founders, startups, and growing businesses. I handle everything: design, frontend, backend, and deployment.
READY TO BUILD SOMETHING?
Full stack engineering, clean code, 6–7 day delivery. Let's talk.