The better prepared you are, the clearer your quote will be and the fewer surprises you will have later. You do not need technical knowledge. This checklist covers what a development team will usually ask about.
1. The goal, in one or two sentences
What should be different once the project is live? For example: "Customers can book and pay for appointments online, and staff stop taking bookings by phone." Add how you will measure success, such as fewer phone calls or faster order processing.
2. Who will use it
List the types of users, such as customers, staff, managers and admins, and what each one needs to do. This shapes logins, permissions and screens.
3. Must-have and nice-to-have features
Split your feature list into two columns. The must-haves form the first version. The nice-to-haves can come later. This is the single most useful step for controlling cost and time.
4. Your current process and data
Describe how the work is done today, and gather samples of the forms, spreadsheets, reports or documents you use. If existing data needs to be moved into the new system, say how much and where it is kept.
5. Connections to other services
Note any services the system must connect to, such as payment gateways, SMS providers, courier services, accounting software or email. In Bangladesh, for example, this could include local payment options. Each connection adds work, so it is important to list them early.
6. Content and branding
Who will provide text, photos, product information and translations? Do you have a logo and brand colours? Content is often the reason projects are delayed, so plan it from the start.
7. Budget range and timeline
Sharing an honest budget range helps the team suggest what is realistic. Mention any fixed dates, such as a launch event or season, and whether the date or the feature list is more important.
8. One decision-maker
Choose one person who can answer questions and approve designs. Projects move much faster when feedback comes from one place.
9. Examples you like
Collect a few websites or apps you like, and some you do not, with a note on why. This is often the quickest way to agree on style and features.
10. After launch
Think about hosting, domain, security updates, backups and support. Confirm in writing who owns the code and accounts, and what ongoing support will cost.
Have a project in mind?
Tell us what you want to build or improve. We reply with practical next steps.