PROJECT SCOPE AND ESTIMATION
What should you prepare for a device software estimate?
You do not need a complete specification for an initial conversation. You do need to distinguish what already works, what needs to be built and what remains uncertain. That makes it possible to estimate a defined scope or propose a discovery phase instead of offering a deceptively precise price.
Renau Digital

1. Describe the application and project stage
Explain what the device does, who uses it and under which conditions. Is the goal a demonstration, pilot, upgrade to an existing product or a new deployment? If a trade show, customer trial or other commitment sets the deadline, include that context.
Share a budget range if you have one. It helps shape the first stage, but does not replace requirements analysis.
2. Outline the available hardware and software
Identify the platform, operating system, sensors, actuators and interface documentation. Explain whether a test unit is available and whether it can be accessed on site or remotely. If the electronics are still evolving, flag the planned changes.
For an existing codebase, it matters whether it can be built, what documentation and tests exist and whether you have the right to modify it.
3. Separate software layers and responsibilities
Specify what Renau Digital should deliver and what remains with your team or other partners. The phrase 'an application for the device' can describe very different tasks.
- Embedded software or firmware: platform, peripherals and communication.
- Device logic: processes, states, start conditions and fault handling.
- HMI: display, interaction method, languages and user scenarios.
- Backend and APIs: local or cloud scope, external systems and documentation.
- Servicing and updates: diagnostics, permissions and release deployment.
- Hardware, mechanics and conformity requirements: responsible partners and dependencies.
4. Define acceptance, not just a feature list
For the most important functions, describe the expected behaviour and how it will be checked. If response time, offline operation, device count or data retention matters, state the requirement or flag it as a question to resolve.
List the external systems to integrate with and the test environments available. Missing documentation, hardware or test accounts can affect task order and integration timing.
5. Separate known work from uncertainty
Break the estimate into stages with assumptions, dependencies and exclusions. If a critical integration is uncertain, an initial review or proof of concept may be the right first step. Its results provide a firmer basis for planning the remaining work.
There is no reliable single price for 'machine software' without a defined scope. Devices that look similar can have very different process, hardware, integration and maintenance requirements.
- Start with a description of the device and its users.
- Explain the current stage, available hardware and what already works.
- Identify the scope you need and the main unknowns.
- Include the target date, acceptance approach and any budget range.