✦ Official Example
Review Complete
📋 Request
Enterprise SaaS Proposal for an IT Department — Is the AI's Structure Effective for Real Enterprise
We're submitting a SaaS solution proposal to a large corporation's IT department. The AI gave me a proposal structure, but I'm not sure it reflects how enterprise purchasing decisions actually work across multiple stakeholders with different priorities. I want to understand how to structure this so it speaks to each decision-maker effectively.
Business Document200 pts
Overall Assessment
The AI's structure is improved by recognizing the multi-stakeholder dynamic and the Implementation Plan placement issue. The ROI and Implementation Plan questions — which are the most practically important for converting enterprise proposals — need more specific guidance to be actionable.
Key Findings
✅ What's accurate: - The multi-stakeholder analysis and their different evaluation criteria are accurate and important - Moving Implementation Plan before Pricing is correct — implementation risk is the primary purchase objection - The three-tier pricing recommendation is correct ❌ What's inaccurate or misleading: - The proposal structure still opens with Company Overview, which reads as self-promotional — enterprise buyers want to see that you understand their situation first, not your credentials ⚠️ What's missing or overlooked: - The "Understanding" section: opening the proposal with a demonstrated understanding of the buyer's specific situation — including 2–3 pain points not explicitly stated in the RFP — is the first filter enterprise buyers apply and is the section most commonly missing from SaaS proposals - ROI credibility requires a named reference customer in the same industry and company size — numbers without a case study read as vendor projections; numbers anchored to a named customer's outcome are significantly more persuasive
Action Items
1. Open the proposal with "Understanding Your Situation" before Company Overview — demonstrate you understand their specific challenges, including ones they didn't put in the RFP 2. For ROI: structure as current cost (staff hours × hourly rate × annual frequency) → post-implementation savings → annual solution cost → ROI percentage and payback period, and pair every number with a named reference customer at similar scale 3. For Implementation Plan: use a three-phase timeline visual (Onboarding / Configuration / Go-live) with vendor and customer responsibilities listed side by side for each phase, plus explicit risk reduction language — dedicated CSM, zero-downtime migration, 30-day post-launch support, exit conditions 4. Replace single price with three tiers: Starter (entry point), Professional (recommended, visually distinguished as "Most Popular"), Enterprise ("Contact us")
Additional Resources
- MEDDIC enterprise sales qualification framework: https://www.meddic.com - Bonterms standard services contract templates: https://bonterms.com - Gartner on enterprise software evaluation: https://www.gartner.com/en/sales/insights/b2b-buying-journey