The proposal is read by people who will not be using the system
In the capital, work of this size is bought through a process rather than a conversation. A proposal is circulated to procurement, to an IT function, occasionally to a legal or risk reviewer, and each of them is looking for something different. The technical lead wants the integration surface. Procurement wants a fixed, comparable price with defined deliverables. Risk wants to know what the system can do without a person's approval.
A submission that answers all three in writing tends to move; one that relies on a persuasive meeting tends to stall between reviewers who never met. So the deliverable at the end of our scoping phase is a document written for that audience — architecture, data flows, the permissions model, the acceptance criteria and a price that does not move afterwards. It is yours whether or not the build follows.



