Software estimates become unreliable when the request describes screens but not the work those screens need to support. A useful estimate begins with context.
Explain the current workflow
Describe who does the work today, what information they need, where it comes from, and what happens when something goes wrong. Existing spreadsheets, forms, and examples are often more useful than a polished feature document.
Separate needs from possible solutions
“Customers need to see order status” is a need. “Build a real-time dashboard with six widgets” is one possible solution. Keeping those separate gives design and development room to find a simpler approach.
Identify the expensive unknowns
- Legacy data that must be migrated
- Third-party systems with limited integrations
- Complex permissions or approval rules
- Offline, mobile, or hardware requirements
- Compliance and sensitive information
A good estimate makes assumptions visible and shows where discovery is still needed. Precision without that context is usually just confidence wearing a number.
