Choosing the Known Tweak Over the Unknown Breakthrough: A SaaS Team's Missed AI Opportunity
A real-world example of Ambiguity bias in action
Context
A mid-stage SaaS company serving small-to-medium retailers was deciding how to allocate its engineering budget for the next two quarters. Leadership had a reliable metric history for incremental UI/UX improvements, but a product team proposed building an AI-driven sales assistant that targeted a new use case with unclear adoption probabilities.
Situation
Two concrete proposals reached the executive team: (A) a UX overhaul expected to raise 30-day retention by a reliably estimated 3–6%, with well-understood development costs; (B) an AI assistant that might increase revenue per customer substantially but had no direct precedent and wide uncertainty in adoption (estimates ranged from 5% to 35%). The AI option required longer development and exploratory research with uncertain outcomes.
The bias in action
Decision-makers gravitated toward option A because its outcomes and probabilities were familiar and quantifiable, even though the expected upside of option B could be much higher. Conversations framed the AI path as 'risky' and 'hard to predict,' reinforcing the discomfort with ambiguity rather than evaluating potential value. The team thus prioritized the UI project, allocating the lion's share of the budget to the familiar improvement. Subtle signals—like asking for narrower confidence intervals and giving less credence to expert opinion about new markets—amplified the preference for the known option.
Outcome
The UI update produced the expected retention lift (~4.2%) and a small uptick in short-term metrics. Meanwhile, a competitor launched an AI assistant targeting the same customer segment six months later, capturing attention and accelerating their customer acquisition. Over the next 18 months the competitor's paid conversion improved sharply while the subject company saw slower revenue growth and rising churn among power users.




