Checklist to prepare a technical or web project
Before requesting an estimate for a website, dashboard, platform, firmware, IoT or custom software project, it is useful to clarify a few questions. You do not need every answer: you need a clearer starting point.
Use it as a base for the first message
The clearer the request, the easier it is to understand whether the next step should be an audit, a web review, a technical roadmap or a complete build.
If the project is a website, dashboard or platform
- What outcome should it create: leads, orders, tickets, reports, documents, data visibility or less manual work?
- Who will use it: customers, administration, technicians, sales, production or management?
- What data already exists and where: spreadsheets, management software, databases, email, APIs or devices?
- Do you need login, roles, a reserved area, notifications, exports, payments or integrations?
- Does the current website generate tracked enquiries or is it unclear what works?
If the project is embedded, firmware or IoT
- Which hardware is already defined: MCU, board, sensors, display, connectivity or FPGA?
- Is there working code, a prototype, a demo or only a requirement?
- What constraints matter most: real time, power, memory, security, OTA, certification or maintainability?
- How will logs, faults, telemetry and support data be collected?
- Does the device need to connect to dashboards, backends, cloud services, APIs or company tools?
If the project is custom technical software
- Which manual workflow should be removed or made easier to control?
- Which systems must talk to each other: ERP, management software, databases, APIs, files, instruments or machines?
- Which errors currently cost time, rework or information loss?
- Who will maintain the tool after release and with which skills?
- Do you need a small first version or a complete platform from the start?
Three signs that it is worth talking now
Email, spreadsheets, manual copying and duplicated information are slowing activities that could be automated.
Pages do not explain services clearly, do not bring qualified enquiries or do not measure contact sources.
Sporadic bugs, difficult updates, complex debugging or missing logs are making release risky.
The product must talk to dashboards, portals, backends, cloud services or internal tools without becoming unmanageable.