Vendor Proposal Review: What the Proposal Does Not Say

When this service becomes necessary

• The organisation has received a vendor proposal for a significant technology engagement and wants independent assessment before committing.
• A proposal looks reasonable but something is unclear, the scope, the assumptions, the pricing, or the implementation approach.
• The organisation does not have internal expertise to evaluate the technical or commercial terms of a vendor proposal.
• A previous engagement with a vendor produced cost overruns or scope disputes, and the contract was a contributing factor.
• Multiple vendor proposals have been received and an independent comparative assessment is needed.
• The board or CFO wants independent assurance before a significant technology contract is signed.

What Evoltra reviews

• Scope: what is included, what is explicitly excluded, and what is ambiguous
• Assumptions: whether vendor assumptions are reasonable and what the cost implications are if they prove incorrect
• Pricing: structure, reasonableness, and what the total cost of the engagement is likely to be
• Implementation approach: whether the proposed methodology and timeline are credible for the described scope
• Resourcing: whether the proposed team composition and time allocation are adequate
• Risk allocation: which party carries which risks in the contract terms
• Intellectual property: ownership of deliverables, custom development, and data
• Change request exposure: how scope changes are priced and what the likely change request profile is
• Exit provisions: what happens if the engagement does not deliver, or if the organisation needs to exit
• What the proposal does not say, the gaps that become disputes

How the engagement works

1. 1

   Proposal review

   Read the proposal in full: scope, methodology, pricing, assumptions, team, and terms. Document what the proposal says and, importantly, what it does not say.

2. 2

   Scope and assumption challenge

   Assess whether the scope is adequately defined, whether vendor assumptions are reasonable, and where assumption risk sits. Underspecified scope and optimistic assumptions are the two most common sources of cost overrun and delivery dispute.

3. 3

   Commercial and contract review

   Assess the pricing structure, total cost, risk allocation, IP provisions, and exit terms. Identify the contractual positions that carry risk and the protections that are absent.

4. 4

   Implementation credibility assessment

   Assess whether the proposed approach, timeline, and resourcing are credible for the described scope. Timelines that are too short and teams that are too small are common in competitive proposals, they become the source of cost and time overruns.

5. 5

   Findings and recommendation

   Deliver a written assessment with specific findings, recommended negotiation positions, and questions to put to the vendor before commitment. Clear recommendation: proceed, proceed with conditions, or do not proceed.

Who this is for

Organisations considering a significant technology engagement who want independent assessment of a vendor proposal before committing, particularly where internal expertise to evaluate the technical or commercial terms is limited, where a previous engagement produced cost overruns or scope disputes, or where the CFO or board has asked for independent assurance before sign-off.