Sample Report — For Executives
Which Vendor Should We Choose for Our Core Infrastructure?
An operating decision example: selecting between two vendors for a business-critical system, weighing cost, risk, and switching cost.
Illustrative example built to match Ascendra's actual output format and depth — not a captured transcript from a specific run. Try it on your own decision to see a live-generated report.
Recommendation
Choose Vendor B, with a defined exit clause
Vendor B costs 15% more annually but has materially lower lock-in risk and a stronger uptime track record. Confidence: 67% (Medium-High) — sufficient to recommend, contingent on securing a workable exit clause given the stated contract term.
Known Facts
Vendor A: €48,000/year, 3-year minimum contract, no published uptime SLA.
Vendor B: €55,000/year, 1-year contract, 99.95% uptime SLA with penalties.
Current system handles ~40% of company revenue-generating operations.
Migration cost estimated separately at €15,000-20,000 regardless of vendor chosen.
Internal team has prior experience with Vendor A's platform, none with Vendor B.
Key Risks
Vendor A's 3-year lock-in
No exit before year 3 regardless of performance issues — high switching cost if the relationship sours.
No published SLA from Vendor A
Without a contractual uptime guarantee, there's no recourse if reliability issues affect revenue-generating operations.
Team unfamiliarity with Vendor B
Zero internal experience adds ramp-up time and short-term execution risk not present with Vendor A.
Migration cost is fixed regardless of choice
This cost shouldn't factor into the vendor decision itself, but does affect timing.
Revenue exposure concentration
40% of revenue-generating operations on one system means vendor reliability has outsized business impact.
No penalty terms confirmed for Vendor B beyond SLA
SLA exists, but actual penalty enforcement process not detailed — worth confirming before signing.
Scenario Map
Best case: Vendor B's SLA holds, team ramps up within 4-6 weeks, and the company gains a materially more reliable system at a modest cost premium.
Base case: Vendor B performs adequately with a short learning curve; the 15% cost premium is offset by avoided downtime incidents over the year.
Worst case: Vendor A is chosen for familiarity, an uptime issue occurs in year 2 with no SLA recourse, and the company is locked into the contract for another year with no exit option.
Action Plan
1. Request Vendor B's specific SLA penalty enforcement process in writing before signing.
2. Negotiate a defined exit clause or shorter initial term with Vendor B if possible.
3. Budget 4-6 weeks of reduced team velocity for the Vendor B ramp-up period.
4. Request 2-3 reference calls from existing Vendor B customers of similar size.
5. Confirm migration cost quote is fixed-price, not time-and-materials.
This is what Ascendra returns for any real decision — not just vendor selection.
Try it on your own decision →