---
title: What Was Impossible That's Now Cheap?
synced_from_vault: true
vault_source: 03-living-docs/patterns/What-Was-Impossible-Now-Cheap.md
public: true
name: What Was Impossible That's Now Cheap?
description: >-
  The most generative AI strategy question. Don't ask "how do I automate the
  existing process?" Ask "what previously-impossible question can I now ask?"
  Existing-process automation is incremental; new-question discovery is
  transformative.
type: pattern
category: strategy
origin: >-
  Benedict Evans, "AI eats the world" (May 2026 deck). The framing complements
  [[AI-Planning-Inflection-Point]] — different stage, same insight family.
created: 2026-05-18T00:00:00.000Z
tags:
  - pattern
  - ai
  - strategy
  - product-discovery
  - generative-questions
---

> **Core question:** When a technology drops the cost of something by a factor of 1000, the interesting move isn't "do the old thing faster." It's: *what could nobody ever afford to do before that's now trivial?* The new question is the strategy.

---

## The articulation

Benedict Evans, May 2026: contrast the two prompts —
- **Old, automatable question:** *"Listen to every call and tell me if the customer sounds strange."*
- **New, previously-impossible question:** *"Listen to a million calls every day — what do you notice?"*

The first question existed before AI; AI just makes it cheaper to answer. The second question was *not askable* before. The cost was prohibitive, and so the question never made it into anyone's roadmap.

Same pattern for any deterministic question that becomes probabilistic-tractable:
- "Show me the data Bob's talking about on this call." (was: impossible during the call)
- "What were the top concerns on customer calls in the last six months?" (was: ten analysts × eight weeks)
- "What pricing changes would improve our churn?" (was: never asked because nobody could answer)

The third one is the most interesting because it has no deterministic answer — only an LLM could attempt it. It's a question that *did not exist as a question* in the prior era.

---

## How to apply

1. **List the questions your team would love to answer but doesn't bother asking** because the cost or labor would be absurd. ("If I had ten analysts for a month, what would I have them do?")
2. **For each, run the cost-collapse test:** if I could ask this question for $5 and get an answer in 30 seconds, what would I do with the answer?
3. **The winners are questions whose answer changes a decision** that's currently being made on gut or pattern-matching.
4. **The biggest winners are questions that nobody is asking yet** because the cost has been infinite for so long that they fell out of the discourse.

---

## Why this beats "automate the existing process"

Automating the existing process is the [Absorb stage](/patterns/absorb-innovate-disrupt) — useful, table-stakes, but symmetric (everyone does it).

Inventing new questions is the [Innovate / Disrupt stage](/patterns/absorb-innovate-disrupt) — asymmetric, defensible, transformative. The Innovate stage is where Spotify ("get all the music there is") beat iTunes ("don't have to buy the CD"). iTunes asked the old question with new technology. Spotify asked a *new* question.

---

## The 1997 test

> *"Imagine asking 'What will be changed by the internet?' in 1997"*
> — Benedict Evans, channeling Yogi Berra

Most answers in 1997 were "online versions of existing things." The real answers — search-as-default, social graphs, smartphones, cloud as substrate — were unaskable as questions at the time. The same is almost certainly true now for AI. The dominant 2030 use cases are not on anyone's roadmap in 2026.

That's not a reason to wait. It's a reason to *ask questions* that don't yet have product categories.

---

## Failure modes

- **Asking only the old questions faster.** "What if our existing dashboard had AI?" produces an absorb-stage product. Useful, but not strategy.
- **Asking questions with no decision attached.** A million-call analysis that doesn't change pricing, hiring, or product roadmap is a parlor trick.
- **Confusing volume for novelty.** "Analyze 10x more data" is still the old question. Novelty is in the *shape* of the question, not the size of the input.

---

## Cross-References

- Companion frames: [Was-Cost-of-Task-Your-Moat](/patterns/was-cost-of-task-your-moat), [Task-vs-Job](/patterns/task-vs-job), [Absorb-Innovate-Disrupt](/patterns/absorb-innovate-disrupt)
- Related patterns: [AI-Planning-Inflection-Point](/patterns/ai-planning-inflection-point), [Augmentation-Over-Automation](/patterns/augmentation-over-automation)