A development proposal is the cheapest document in the whole project and the most expensive one to read badly. The parts that hurt later are almost never wrong; they are absent. Nobody signs a contract intending to lose their repository. They sign one that does not mention it.
This review reads a proposal against a fixed list of questions every proposal has to answer, and reports what the document did not say as clearly as what it did.
It is built for one situation: you have a real proposal in front of you and a decision to make about it.
It is not built for a landing page quote or a small e-commerce job. The questions below would be overkill and the review would tell you so.
Twenty-five questions, weighted, of which five are treated as critical: a proposal that leaves any of those unanswered cannot score well however good the rest of it is. Scoring is arithmetic, not opinion, and the method is shown with the result.
What is included, what is explicitly excluded, and what is neither. The third category is the one that becomes a change request.
Who owns the source, the repository and the infrastructure; who holds the backups; when intellectual property assigns, if it does. All five are treated as critical questions.
What happens if you leave, or they do. Handover contents, access, and whether another team could pick this up.
Recurring costs, third-party costs, the payment schedule, and dependencies that turn into somebody else's invoice.
What is included after delivery, what is a separate contract, and which security obligations sit with whom.
Architecture, stack, team, timeline, declared assumptions and declared risks — and whether the timeline is consistent with the scope.
The Analyzer is not open for self-service yet. The review described above is not a plan — it runs today inside FinMV Workspace, on a project, against the same list of questions. What is missing is the door: a way to use it without an account, and the published data-handling description that has to come before anyone hands over a commercial document.
