- The number of exceptions in the process
- The most consistently underestimated driver. A process described in three sentences usually has five exceptions nobody mentioned because "everyone knows". Each is a separate path through the system. The discovery workshop exists mainly to surface them before the quote rather than after it.
- Integrations with systems you don't control
- Integrating with an API that has documentation and a sandbox is a line in a schedule. Integrating with a system whose access has to be negotiated and whose documentation doesn't exist is a risk — and it is usually what explains the spread between competing offers.
- Data migration
- Moving data out of spreadsheets and an old system is often more expensive than the feature that data feeds. Historical data is always inconsistent; the only question is how badly, and how much of it has to be repaired before the system can trust it.
- The number of roles and permissions
- A system where everyone sees everything is many times cheaper than one where five roles see five different slices of the same data. This rarely appears in a requirements document and shows up sharply in a quote.
- Availability and performance requirements
- An internal tool for twenty people and a platform that has to survive a campaign are two different projects at the same feature list. Committed uptime and expected traffic change the architecture, not just the hosting bill.