You do not need to know technical terms. Just describe your idea, needs and expectations. The DROPLINE team can help clarify the requirements and choose a practical way forward.
1. Project goal
Explain why you need a website or app and what problem it should solve. For example, attracting customers, increasing sales, automating work processes or launching a new online service.
I want to create a website for online orders so customers can choose services and submit requests themselves.
2. Target audience
Tell us who will use your product. They might be potential customers, company employees, partners or a particular group of users.
Understanding the audience helps define the necessary features, page structure and a convenient way to interact with the product.
3. Required features
List what your product should do. At this stage, it is enough to describe the desired capabilities in plain language.
You do not need to define every feature right away. If you are unsure what is needed, describe the outcome you want — technical solutions can be discussed during planning.
- pages describing the company, services or products;
- contact and enquiry forms;
- a product or service catalogue with search and filters;
- registration, sign-in and a user account;
- an admin panel for managing content;
- online payments and third-party integrations;
- an API, server-side logic or business process automation.
4. Design and examples
If you like the style of a particular website or app, share a link and explain what you would like to use as a reference.
Also mention whether you have a logo, brand colours, a Figma design or other visual materials.
Not having a finished design is fine. What matters is understanding the impression the product should make and how complex it needs to be.
5. Content and materials
Tell us what is already ready for the project. If some materials are not available yet, mention that so any additional work can be identified early.
- copy, photos and videos;
- a logo and brand identity;
- finished layouts or a Figma design;
- business process and requirement notes;
- an existing website, API or code that needs further work.
6. Timeline and budget
Share your preferred launch date and an approximate budget for the project.
This helps set the right feature scope, prioritise work and propose a realistic development plan.
If you have not set a budget yet, describing the main requirements is enough. Possible implementation options can be discussed once they are clear.
A short brief preparation checklist
Before discussing the project, it helps to prepare:
- the goal and expected outcome;
- a description of the target audience;
- a list of the main features;
- design examples you like;
- available copy, images and other materials;
- your preferred timeline and approximate budget.
You do not need to have every answer. Start with the idea — you can clarify the rest with DROPLINE.