AI Opportunity Scanner vs Durable Sessions UX: Which?
// TL;DR
Use the Greg Isenberg AI Opportunity Scanner if you're deciding what AI business to build, how to price it, and how to structure a lean agent-powered company. Use the Christensen Durable Sessions Framework if you've already committed to building an AI product and need to fix the streaming, reconnection, and multi-device UX layer. They solve completely different problems at different stages — Isenberg is business strategy and opportunity identification; Christensen is product infrastructure and real-time architecture. Most people exploring AI business ideas should start with Isenberg. Most engineers shipping an AI chat product should reach for Christensen.
// HOW DO THEY COMPARE?
| Dimension | Greg Isenberg AI Opportunity Scanner | Christensen Durable Sessions AI UX Framework |
|---|---|---|
| Best for | Evaluating, validating, and structuring new AI business ideas | Diagnosing and rebuilding streaming AI product UX architecture |
| Stage of use | Pre-build and early exploration (idea to first customer) | Mid-build and post-launch (product already exists or is being engineered) |
| Primary audience | Founders, solopreneurs, consultants, indie hackers | Product engineers, frontend/backend architects, technical PMs |
| Complexity | Moderate — 12-step strategic workflow, no code required | High — requires understanding of SSE, WebSockets, pub/sub, agent topologies |
| Time to apply | 1–3 hours to run through full opportunity scan | Days to weeks for full architectural redesign |
| Prerequisites | A business idea or audience; no technical skills required | A working or in-progress AI product with a streaming layer |
| Output type | Business opportunity map, pricing model, org structure, go/no-go decision | Architecture diagnosis, failure-mode map, Durable Sessions redesign plan |
| Creator background | Greg Isenberg — serial entrepreneur, startup studio operator, community builder | Mike Christensen (Ably) — real-time infrastructure engineer, AI UX specialist |
| Key framework | Vertical AI vs Vertical SaaS, Micro Monopoly Math, 1-Hour Company Stack | Durable Sessions, Three Foundational Capabilities, Agent-Client Decoupling |
| Overlap with the other skill | None — does not address product architecture or streaming UX | None — does not address business viability, pricing, or market selection |
What does the Greg Isenberg AI Opportunity Scanner do?
The Greg Isenberg AI Opportunity Scanner is a 12-step strategic framework for mapping any business idea against AI-era opportunity patterns. It helps you decide what to build, who to build it for, how to price it, and how to structure a company around AI agents rather than human employees.
The core insight is that the biggest AI opportunity is not selling software tools (Vertical SaaS) but replacing the work humans are paid to do (Vertical AI), tapping into the labor P&L rather than the IT budget. It introduces concepts like the Micro Monopoly Math (100 customers × $50/month + agent-run operations ≈ $60K profit for one person), the Ghost Team Org Chart (named AI agents replacing departments), and outcome-based pricing (charge per result, not per seat).
You walk away with a scored evaluation of your idea, a pricing model recommendation, a distribution strategy, an honest assessment of your Founder-Agent Fit, and either a green light to validate with the 1-Hour Company Stack or a clear signal to pivot. It is business strategy, not engineering.
What does the Christensen Durable Sessions AI UX Framework do?
The Christensen Durable Sessions Framework is a 10-step architectural playbook for diagnosing and fixing the real-time streaming layer of AI chat and agent products. It solves the problem that most AI products work in demos but break under real conditions — network drops kill response streams, second devices can't see live responses, and stop buttons are unreliable.
The core architectural move is introducing a Durable Session: a persistent, shared pub/sub channel that sits between agents and clients. Agents write events to the session; clients subscribe to it. Neither holds a direct pipe to the other. This single change unlocks three foundational capabilities simultaneously: Resilient Delivery (streams survive disconnections), Continuity Across Surfaces (sessions follow users across tabs and devices), and Live Control (clients can steer or cancel agents mid-generation).
The framework is deeply technical. It requires understanding of SSE limitations, WebSocket architecture, pub/sub patterns, and multi-agent topologies. You walk away with a failure-mode diagnosis of your current architecture and a concrete redesign plan. It is infrastructure engineering, not business strategy.
How do the AI Opportunity Scanner and Durable Sessions Framework compare?
These two skills operate at entirely different layers of the AI product stack and have zero functional overlap.
The Isenberg AI Opportunity Scanner answers: Should I build this? For whom? At what price? With what team structure? It lives upstream of any code. A non-technical founder with a newsletter audience and an idea can run the full 12-step workflow in a few hours and walk away with a validated (or killed) business concept.
The Christensen Durable Sessions Framework answers: Why does my AI product feel broken, and how do I fix the streaming architecture? It lives deep inside the engineering layer. A product engineer who's already shipping an AI chat experience and dealing with dropped streams, SSE ambiguity, or multi-agent relay bottlenecks is the target user.
Isenberg is broad — it spans pricing strategy, audience analysis, competitive positioning, org design, and security hygiene for agent permissions. Christensen is narrow and deep — it focuses exclusively on the real-time delivery layer but covers it exhaustively, from the Single-Connection Trap through multi-agent session flattening.
If you don't have a product yet, Christensen's framework has nothing to audit. If you already have a product and the streaming UX is breaking, Isenberg's framework won't fix your architecture.
Which should you choose?
Choose the Greg Isenberg AI Opportunity Scanner if you are exploring AI business ideas, evaluating whether to pivot an existing product, choosing a pricing model, or trying to identify which AI-era niche to target. It is the right starting point for anyone who hasn't yet committed to a specific product build. It is also valuable for existing SaaS founders who need to stress-test whether their product is headed for the SaaS Graveyard.
Choose the Christensen Durable Sessions Framework if you are actively building or maintaining an AI-powered chat, assistant, or agent product and your users experience dropped streams, can't resume conversations across devices, or can't reliably stop a generation in progress. It is the right tool when your business decision is made but your infrastructure is holding back the product experience.
Use both sequentially if you're going from zero to shipped product. Run the Isenberg scanner first to validate the opportunity, pick your niche, set your pricing model, and design your Ghost Team. Then, when you're engineering the product, apply Christensen's framework to ensure the AI UX layer is resilient, multi-surface, and controllable — especially if your product involves streaming agent responses to end users.
Neither skill replaces the other. Isenberg without Christensen gives you a great business idea with a fragile product. Christensen without Isenberg gives you bulletproof infrastructure for a product that may not have a viable market.
// FREQUENTLY ASKED QUESTIONS
Can I use the Isenberg AI Opportunity Scanner and the Durable Sessions Framework together?
Yes, and you should if you're building from scratch. Use Isenberg first to validate the business opportunity, pick a niche, set pricing, and design your agent team structure. Then use Christensen when you're engineering the product to ensure your streaming architecture handles disconnections, multi-device use, and live agent control. They cover completely different layers — strategy and infrastructure — so they complement each other naturally.
Which framework should a non-technical founder use?
The Greg Isenberg AI Opportunity Scanner. It requires no technical knowledge — just a business idea and information about your audience. The Christensen Durable Sessions Framework requires deep understanding of streaming protocols, WebSockets, SSE, and pub/sub architecture. A non-technical founder would need an engineer to apply it.
Is the Christensen Durable Sessions Framework only for chat products?
No. It applies to any AI product that streams agent responses to clients in real time — coding assistants, research automation tools, customer support bots, multi-agent dashboards, and collaborative AI workspaces. If your product has an agent generating output that a user needs to see live, the framework is relevant.
Does the Isenberg AI Opportunity Scanner help me actually build the product?
It helps you validate and structure the business, not write the code. Step 6 references the 1-Hour Company Stack for rapid prototyping, but the framework itself focuses on opportunity identification, pricing model selection, org design, and competitive positioning. For the actual build, you'll need engineering tools and potentially the Christensen framework for your real-time layer.
What if I already have an AI SaaS product with revenue?
Run Isenberg's SaaS Graveyard check and Vertical AI filter to assess whether your product is at risk of commoditization and whether you should shift pricing from seat-based to outcome-based. Simultaneously, run Christensen's three-capability audit to check whether your streaming UX is holding back retention. Both frameworks have specific workflows for existing products, not just new ideas.
Which framework addresses AI agent security?
The Isenberg AI Opportunity Scanner covers the Agent Attack Surface, including prompt injection, poisoned context windows, permission escalation, and quarterly agent cleanses. Christensen's framework does not address security — it focuses purely on the real-time delivery and connectivity architecture. For agent security guidance, Isenberg is the relevant framework.
How long does it take to apply each framework?
The Isenberg scanner can be completed in 1–3 hours for a thorough pass through all 12 steps. The Christensen framework takes significantly longer — the audit and scoring steps may take a day, but the full architectural redesign (introducing Durable Sessions, replacing SSE, flattening multi-agent relay) can take days to weeks depending on your codebase complexity.
Do these frameworks conflict with each other in any way?
No. They have zero overlap. Isenberg operates at the business strategy layer — market selection, pricing, org structure. Christensen operates at the infrastructure layer — streaming protocols, session persistence, agent-client decoupling. A decision in one framework never contradicts a recommendation in the other. They are fully complementary.