Why NDAs precede detailed estimates
Serious procurement requires understanding data flows, integrations, and compliance constraints. Without an NDA, vendors guess — and you get proposals that are either inflated or dangerously optimistic.
What we typically need
- Stakeholder map: who decides, who uses the system daily, who signs off on security.
- Architecture sketch: current stack, SSO, CRM/ERP touchpoints, and data residency rules.
- Success metrics: revenue, cost, risk reduction, or time saved — stated in measurable terms.
Workshop shape
We run time-boxed sessions on goals, user journeys, and technical constraints, then summarise assumptions in writing. That document becomes the backbone of scope and change control.
Deliverables you can take elsewhere
Even if you do not proceed, you should leave with a clear problem statement, option space, and risk register — useful for internal alignment or another RFP.