I Made Opus and Fable Grade Each Other. Opus Admitted It Lost.
The creator demonstrates real-world AI applications in their productivity business using Claude Fable and Opus, showing how Fable excels at comprehensive analysis of complex systems while comparing its performance to Opus on specific tasks. The key finding is that Fable's holistic understanding justifies its higher cost for business-critical audits and optimizations.
Summary
The video documents the creator's practical use of Claude Fable 5 API access for auditing and optimizing the ICOR Journey courses—a comprehensive productivity education platform with interconnected lessons spanning note-taking, PKM, task management, and automation. The creator emphasizes real business applications rather than toy examples, explaining how their productivity system includes deep course content (up to 30,000 words per lesson), growth assignments, explainer videos, and cross-referenced connections.
The primary use case involves auditing the courses to ensure proper "golden thread" progression where earlier lessons are referenced by later ones without forward references that would confuse learners. Using Claude in VS Code with custom prompts, the creator generates interactive HTML visualizations using React Flow showing course dependencies and connections—a capability they demonstrate works across complex knowledge bases.
The critical comparison emerges when the creator tests both Fable and Opus on the same tasks. For a password reset issue diagnosis, Opus completed analysis in 3 minutes while Fable took 8 minutes, but Fable discovered a more elegant, proper solution rather than just a UI workaround. The creator demonstrates this by having each model review the other's session, with Opus acknowledging that Fable "went one layer deeper" and found superior solutions.
The creator addresses the cost-benefit analysis explicitly: while Fable API access is expensive (costing potentially thousands of dollars for comprehensive audits), the return on investment is clear when it prevents wrong conclusions in complex system analysis. They draw parallels to hiring human experts who also produce variable quality outputs and can become bottlenecks. The folder structure and standard operating procedures the team uses enable consistent results while allowing AI systems to think outside the box differently.
Throughout the video, the creator emphasizes that success with AI depends on having proper foundational systems (single source of truth, clear information architecture) in place first—attempting to automate broken processes only amplifies problems. The real power emerges when AI is layered on top of already-optimized workflows.
Key Insights
- Fable's advantage over Opus is not speed but depth—it took longer (8 minutes vs 3 minutes) to analyze a password reset issue but discovered a proper architectural solution rather than just a UI workaround, and Opus acknowledged that Fable 'went one layer deeper'
- Fable justifies its high API costs for business-critical analysis because it prevents wrong conclusions that could send entire teams down incorrect paths, similar to how human experts on billion-dollar projects can cause significant losses with faulty analysis
- The creator's return on investment calculation for expensive Fable audits depends entirely on whether optimizations will improve user retention and content completion rates, requiring understanding of overall business numbers rather than just token costs
- Fable excels at analyzing complex interconnected systems holistically—understanding how all 168 gigabytes and 160,000 files in a knowledge base connect together—which is where the creator sees the real competitive advantage over other models
- AI layered on top of already-broken processes only amplifies problems, so proper foundational systems with single source of truth and clear information architecture must exist first before automation or AI optimization can be effective
Topics
Transcript
[0:00] Fable 5 is back. I'm really happy about it. The only thing that I see on YouTube and other channels, whenever people talk about these models, I rarely see real use cases where they are - getting applied in real life work. And that's why in this video I will show you the first thing that I did in my business the moment I got access to Fable again and I can tell you already, Fable didn't disappoint. It is really insane, And I really hate the fact that we will only get access through API to Fable in the future because that's very expensive and that's why I [0:33] take this time where I have access to it…
Full transcript available for MurmurCast members
Sign Up to AccessMore from ICOR with Tom | AI Productivity
My AI team took 8 hours. Claude Sonnet 5.5 took 15 minutes.
A creator comparing an 8-hour AI team project with a 15-minute Claude Sonnet 5.5 solution reveals that excessive guardrails and restrictions paradoxically hindered the multi-agent system's performance. The speaker demonstrates how reducing constraints and context allows AI to produce more creative and functional results, though both approaches have significant limitations for production use.
Your knowledge should outlive every AI tool you use.
The speaker clarifies the distinction between the ICOR methodology (a tool-agnostic productivity framework) and its implementations like the ICOR for Life scaffold and myPKA AI team, emphasizing that users can adopt the core principles in any tool they prefer. They announce plans to restructure their membership platform by separating these components to reduce confusion and help users understand they're not locked into specific tools or systems.
Claude alone took 3 minutes. With Jev, 21 seconds.
A demonstration comparing AI slide deck creation using Claude alone versus Claude integrated with Jev, showing that the hybrid approach completed the task in 21 seconds for $8 with proper formatting, while Claude-only took 3+ minutes and cost $49 with poor formatting.
Why I stick to Claude for work (most of the time)
The creator demonstrates why Claude is their preferred AI for work by comparing it with ChatGPT across multiple tests, showing that Claude better adheres to custom instructions and agentic workflows defined in local folder structures. The key advantage lies in using organized, LLM-agnostic folder systems with agents.md files rather than relying on auto-memory features.
You are using the wrong Claude for work! (Here is proof)
A video demonstrating that Claude Code is significantly more powerful than Claude Cowork for professional knowledge workers, showing how Claude Code better understands folder context, enforces safety rules, orchestrates sub-agents with different models, and creates persistent file outputs rather than temporary artifacts.