A good quote starts with a clear brief. You do not need a long document. A few honest answers are enough for a developer to ask the right questions and give you a realistic plan. This is the list we find most useful.
1. What is the one job it must do?
Take orders, bring in enquiries, show your work, or manage your staff’s data. Pick the main job first. Everything else comes second.
2. Who will use it?
Customers on phones, your own team on laptops, people with slow internet? This decides the design, the speed and the language, whether English, Hindi or both.
3. What do you already have?
A logo, photos, written text, a domain name, hosting, an old website, product lists in Excel. Anything that is ready saves time. Anything missing has to be made, and that belongs in the plan.
4. Show us examples
Send two or three websites or apps you like, and one you do not like, and say why. One example explains more than a page of adjectives.
5. Separate must-have from nice-to-have
List the features and mark each one as needed for launch or can wait. Releasing in stages lets you test early and keeps the first release focused.
6. Share a budget range and a deadline
A range is fine. It helps the developer suggest what fits instead of guessing. If there is a fixed date, such as a festival or an event, say so at the start.
7. Decide who will look after it
Websites and apps need updates, backups and security fixes after launch. Decide whether your own team will do this or whether you want a maintenance arrangement.
Send it as a short message
Answer these in a few lines, by email or on WhatsApp. We reply with questions, a plan and a timeline. Start on the contact page.