Token Intelligence

Eric Dodds & John Wessel
  • 5.0 (1)
  • TECNOLOGÍA
  • CADA SEMANA

Two friends break down AI, technology, and entrepreneurship through mental models, real-world experience and the pursuit of a life well-lived.

  1. HACE 5 DÍAS

    The honest scorecard for what AI can actually do

    Eric and John rate five AI use cases on a scale from 1 to 10: deep research, running an autonomous company, creative work, coding, and voice. The results are not what most people expect. Summary Eric and John open with a question they get constantly: what can AI actually do? It sounds simple, but the honest answer swings wildly depending on who's asking and what they're trying to accomplish. Before scoring anything, they work through how AI actually works, using Google Translate as an accessible entry point into why context is everything. Then John runs five use cases and asks Eric to react with a live score before he weighs in. Deep research scores an 8 from both. Running a fully autonomous company scores a 2. Creative work splits them. Coding lands at a 7. And voice, which almost nobody is using to its potential, scores a 9. The episode closes with an observation that cuts against most AI coverage: the most impressive capability on the list is also the most underutilized, and the use case everyone talks about, the autonomous AI company, is the one that works almost nowhere in the real world. Key takeaways AI's power scales with how specific your context is: the Google Translate analogy shows why; a vague prompt draws on everything, a specific one draws on exactly what you need, and the results are dramatically different. Deep research is genuinely an 8 out of 10, but only if you pay: the capability is there, but it requires a paid tier and an intentional mode most people forget to activate. The autonomous company works for one-dimensional content businesses and almost nowhere else: AI handles research-to-publish pipelines remarkably well, but real businesses are multi-dimensional, and context shifts too fast for full automation. AI raises the floor on creative and software work, not just the ceiling: the average quality of design and code will improve because AI lets skilled people iterate through more options faster, even if the best human work remains out of reach. Voice is the most underrated capability on the list: talking to AI while driving, walking, or thinking out loud is a 9 out of 10 experience that most people still haven't tried, and it is likely to become the dominant way people interact with AI. Your plan tier changes what AI can actually do for you: deep research, voice integrations, and enterprise features are meaningfully better at paid and enterprise levels, which means people on free tiers often form impressions based on a limited version of the tool. Notable mentions and links Google Translate opens the episode as Eric's preferred analogy for explaining how AI works: predicting the next word from an enormous dataset, which is accessible, accurate, and extends naturally to explain why context makes results better. The MacBook Neo is Eric's hypothetical research example, illustrating how an AI model issues 30 to 40 web searches, visits each page, reads the content, and returns a cited summary instead of making you do it yourself. ChatGPT and Claude are the two tools Eric and John use daily and reference throughout as the primary benchmarks for each use case scored in the episode. Grok gets a specific mention for releasing a new voice model the week of recording, which John calls out as genuinely good even though GPT remains his preference for voice. WhisperFlow is mentioned as a tool that can bridge some of the voice integration gap by cleaning up spoken input and feeding it directly into an AI model as a prompt. The reddit post about an AI-generated Monet which got millions of views and hundreds of comments critiquing what made it inferior to the original, only to turn out to be an actual Monet, becomes the episode's clearest illustration of how close AI image generation has gotten to professional-grade creative work.

    39 min

  2. 10 MAY

    Can AI actually replace an employee?

    The headlines say AI is replacing workers. Eric and John dig into what's actually working, what isn't, and where the real ceiling is right now. Summary Eric opens with a viral post from David Cramer, founder of Sentry, pushing back on the idea that people are running fleets of AI agents doing real work overnight. John responds from firsthand experience, explaining that his company has run dozens of internal experiments, and the honest answer is that almost none of them are used to do real client work. They map the landscape by use case, from personal productivity tools to team-wide deployments, and find that the team tier is where almost everyone stalls. The tools are developer-focused, the adoption problem is real, and getting AI to work reliably across a group requires far more investment in guardrails and oversight than the demos suggest. The episode ends with guidance on what’s practical today. The most compelling near-term model is not a zero-person company but a "co": a single AI assistant that one person owns, trains over time, and stays responsible for. Key takeaways Impressive demos and production deployments are two different things: most agent experiments stay internal, and the gap between "kind of works" and "works with real clients" is larger than most AI coverage admits. What works at home does not automatically work at work: personal AI tools, team tools, and company-wide deployments each have different friction points, and almost everyone has figured out the personal tier and almost no one has figured out the team tier. AI tools are built by developers, for developers, and it shows: most frameworks default toward building and generating, with not enough support for planning, quality checks, and oversight, which limits what they can reliably do. AI will try to answer even when it shouldn't: agents respond by default even without enough context to be accurate, and building the guardrails to prevent that is harder and more expensive than it looks. Owning a single AI assistant beats managing a fleet: a one-to-one "co" that you prompt carefully, iterate over time, and stay responsible for is more practical and more trustworthy right now than trying to orchestrate autonomous teams of agents. AI helps analysts work faster, but it cannot replace what they know: giving AI access to data and asking it to run queries works well when a skilled human with domain knowledge is in the loop; without that, the answers are unreliable. Notable mentions and links David Cramer's post on X is the episode's opening provocation, in which the founder of Sentry argues that nobody doing serious work is running 20 agents overnight, and that the real benchmark is whether you can reliably ship one production-quality fix at a time. Block, Inc. is the financial services company behind Square and Cash App, and its high-profile layoff of over 4,000 employees in February 2026 became a recurring example in the AI-is-replacing-workers news cycle that frames the episode. OpenClaw is an open-source personal AI assistant that runs on your own hardware, connects to messaging channels like iMessage and Telegram, and can be given broad access to your computer, including, for those who push it furthest, credit cards and prediction markets. Zo Computer is described as a middle ground between OpenClaw and a consumer app: AI running inside a secure cloud computer with built-in limits, more powerful than a chat interface but without the security exposure of a fully local setup. Poke is a consumer-facing personal agent that works entirely through existing messaging apps like iMessage or Telegram, with no separate interface of its own. ... (Read more at the episode page)

    25 min

  3. 25 ABR

    Outshining the master is the silent career killer

    Why talented people stall out: going around your boss can break trust long before it creates opportunity, and the consequences simmer under the surface for a long time. Summary Eric and John start with a Reddit post from someone convinced he has been “outshining the master” for years, then reframe the idea in practical workplace terms: not just looking smarter than your boss, but stepping into authority above your level without clear approval. From there they unpack modern versions of the mistake, especially in startups and flat org structures, where skip-level access, cross-functional complaints, and ambitious side channels can feel efficient or principled while quietly breaking trust. They contrast insecure, kingdom-building managers with secure leaders who gladly create exposure for strong people and channel initiative instead of punishing it. The episode ends on blunt career advice: if you crossed the line, own it and repair the relationship; if your boss is blocking you, transfer or leave; and in either case, remember your boss usually sees more of the organization than you do. Key takeaways Define the line correctly: Outshining the master is less about looking talented and more about operating in authority lanes above your level without alignment. Trust is the real issue: The fastest way to look threatening is to make your manager unsure how you will handle information, visibility, and upward communication. Skip-levels are expensive: Going around your boss can feel efficient or principled, but it usually reduces the trust that creates real opportunities later. Great bosses channel initiative: Secure managers align first and then create exposure, which is far better than forcing ambition underground. Pursue craft, not ladder-climbing: Politics are unavoidable, but treating status games as the job will distort your work and your judgment. Bad managers create dead ends: If your boss is kingdom-building and blocking your growth, the realistic answer is usually a team change or an exit. Repair early and stay inside context: If you crossed a line, own it quickly, because your boss usually sees risks, budgets, and political context you do not. Notable mentions and links The 48 Laws of Power is the book that supplies “Never Outshine the Master”, giving the episode its core workplace frame. Circle of competence explains why bosses often see budget, staffing, and political context their reports do not, which makes unauthorized moves riskier than they look. Eric wrote a blog post about “pursuing craft, not politics,” which serves as shorthand for keeping organizational maneuvering in its proper place.

    47 min

  4. 19 ABR

    Notion won't build HubSpot, their users will

    Eric flips his own thesis: Notion doesn't need to out-build HubSpot, it just needs to become the platform where everyone else does. Summary Eric returns to his controversial take that Notion could threaten HubSpot, and after a new product development, expands it into something bigger. With the launch of Notion's custom agents and Notion Workers (running on Vercel Sandbox), Notion isn't racing to build CRM, marketing automation, or customer support itself. It's becoming the platform where its users, template creators, and developers build those tools on top of it. Along the way, John confesses that Notion stresses him out. He can't find what he creates, and he's migrated his own workflow into Git repositories and Granola-synced markdown files. That tension, approachable form factor vs. power-user control, frames the real debate: whether Notion's AI finally solves the "can't find anything" problem at scale, or whether the best survival strategy for the AI hurricane is still plain text files. They land by predicting that Notion's real play isn't replacing HubSpot feature-for-feature, it's turning the workspace into a business operating system, then letting a marketplace of agents, templates, and Workers fill in everything from CRM to eventually ERP. Key takeaways The platform beats the product: Notion's biggest advantage isn't shipping a CRM, it's giving users the primitives to build one themselves. Workers change the ceiling: once arbitrary code runs inside agents, the addressable surface area expands from "docs and databases" to "any workflow between any two systems." Form factor is the moat: Notion's approachable UI plus agents that clean up messy structure could finally make the "find anything" problem a solved one at scale. Git is the power-user escape hatch: for technical teams, plain text in version control remains the most durable substrate because AI reads and writes it natively. Integration quality is the real differentiator: deep, sanctioned partnerships with tools like Slack are what make agent workflows feel magical instead of brittle. Brilliant strategy beats brute force: rather than out-building HubSpot feature by feature, Notion is positioning to become the layer HubSpot alternatives get built on. Notable mentions and links Eric's original blog post framed Notion as HubSpot's biggest threat because AI changes competitive dynamics, letting a document tool expand into CRM, marketing, and support. Notion Calendar, built from the Cron acquisition, adds the time layer to the emerging business operating system. Notion Mail extends the workspace into communications, another piece of the HubSpot-style surface area. Notion's template marketplace, where some creators reportedly earn millions, is cited as proof the ecosystem can produce commercial products on top of the platform. Notion's custom agents, positioned as "the AI team that never sleeps," are framed as a more connected, integration-native successor to OpenAI's GPTs. Notion Workers let developers run arbitrary code inside agent flows to sync external data, hit APIs, and power custom automations. Vercel Sandbox, the compute primitive underneath Notion Workers, provides the isolated cloud environments needed to safely run third-party code inside enterprise workspaces.

    24 min

  5. 11 ABR

    If Notion beats HubSpot, will they still lose to Claude?

    Notion could take out HubSpot, but the frontier providers are fighting a bigger war over who owns the interface, the context, and eventually the whole stack. Summary Eric opens by restating the case for Notion as a serious long-term threat to HubSpot: a database-first product with connected apps, strong AI, and enough cash to close obvious gaps fast. John then challenges that thesis after watching a real Notion AI workflow struggle under a more ambitious content-planning use case, which leads to a deeper question about architecture: whether markdown-native systems are better suited to AI, and how much re-engineering incumbents may still need. From there, the episode widens into a broader prediction about software itself: fewer standalone tools, more orchestration, heavier bundling, and a real possibility that the ultimate winner is not the best app suite at all, but the model layer that becomes the place people naturally work. Key takeaways Key takeaways Connected context is the real wedge: Notion’s shot at HubSpot is less about matching every feature and more about owning the information that makes agents feel magical. Architecture may become strategy: If AI works best on simpler and more file-like systems, some incumbents may need painful re-engineering before they can fully capitalize on it. Simpler interfaces may win: As models improve, many businesses may prefer chat, docs, search, and spreadsheets over ever-larger stacks of specialized software. Orchestration is the new battleground: Project management tools and AI workflow platforms are starting to converge around coordinating people, systems, and agents. Bundling is back in force: AI makes it cheaper to expand across categories, which could turn today’s focused tools into tomorrow’s full-stack business suites. Frontier models can eat the app layer: Notion may pressure HubSpot, but Anthropic and OpenAI could pressure Notion by becoming the default place where work happens. Notable mentions and links The article Why OpenAI Should Build Slack is used as an example of how AI is creating counterintuitive competition that makes once-strange product moves logical. Obsidian, a markdown editor, matters because its markdown-on-disk architecture may be more naturally compatible with current AI systems than Notion’s nested page model. Postgres and Notion’s past sharding crisis come up as a reminder that architecture choices can become company-level constraints when growth and new workloads collide. Notion AI is described as promising but uneven in aggressive one-shot workflows where users want it to generate and structure a full month of content in one pass. Vercel enters the discussion because John’s enterprise use of Notion through MCP and Claude shows how AI can turn a workspace into a searchable database rather than a primary interface. Claude artifacts are cited as an early hint that a model-native document experience could expand beyond chat and start absorbing traditional software surfaces.

    32 min

  6. 5 ABR

    Fences, flagpoles, and the comeback of the generalist

    AI is removing the barrier of specialization, giving generalists the ability to span more domains and solve the most important problems faster. Summary Eric and John unpack a shift many knowledge workers can already feel: AI is changing which kinds of people create the most value. Their frame is the “fence-shaped” generalist, someone with broad range and multiple usable areas of depth, rather than one towering specialty. That kind of operator has always been valuable in startups and zero-to-one work, where bottlenecks move constantly and dependencies kill speed. But they also explore the risk of burning out, topping out, and getting trapped by taking on too many responsibilities. They land on the real shift: AI lets generalists execute across more domains without waiting on specialists, shrinking the gap between seeing the bottleneck and solving it. Key takeaways Breadth matters most when bottlenecks move: the best generalists keep shifting toward the current constraint instead of clinging to yesterday’s valuable work. The trap is taking on too much: range becomes a liability when a generalist spreads effort across many useful tasks instead of the highest-value one. AI deepens adjacent skills: tools now let broad operators reach workable depth in coding, analysis, and research without full specialization. Depth still matters for trust: organizations still reward visible expertise, even if AI lowers how much specialist help is needed to get real work done. Context beats syntax: AI can write SQL or Python, but knowing what to ask, what to filter, and what to trust remains the durable edge. Notable mentions and links T-shaped skills describe broad cross-functional awareness plus deep expertise in one domain, and they give the baseline model Eric and John are reacting against in this episode. X-shaped skills extend the older metaphor toward leadership and people skills, and they come up as an example of how organizations keep inventing new shapes to explain modern work. Zero-to-one projects inside larger companies also favor generalists because they can move quickly with fewer dependencies and get new initiatives off the ground. Regression analysis is the episode’s clearest example of adjacent expertise, because AI now helps non-specialists do work that previously required more dedicated technical support.

    28 min

  7. 4 ABR

    AI burnout: the hardest parts of your job all day

    AI is sold as a productivity miracle drug, and many have tasted the power. But in private conversations, they talk about redlining: higher expectations, more context switching, and smaller teams. Summary Eric opens with a report from a longtime founder-investor friend returning from Silicon Valley: “AI burnout is real.” From there, he and John split the issue into two pressures at once: rising expectations per worker, and the constant workflow thrash of keeping up with changing models, tools, and methods. They then get specific about why AI productivity can feel worse before it feels better. Faster execution means more projects in parallel, more indeterminate waiting loops, and more time spent on architecture, judgment, and review, which can turn the hardest part of the job into the whole job. By the end, the conversation zooms out from fatigue to identity. If AI lets two people do the work of 20, the risk is not just displacement for the 18, but a harsher kind of work for the two who remain. Key takeaways More leverage means higher expectations: AI efficiency often becomes a new baseline for output rather than a source of extra slack. Context switching is the hidden cost: Faster tasks create more parallel work, more waiting loops, and a harder-to-plan day. Automation concentrates work the hard stuff: As AI absorbs implementation, people spend more of their time on judgment, architecture, and review. Smaller teams can feel heavier: Replacing 10 people with 2 does not remove ownership, it compresses it onto fewer humans. Burnout is both personal and market-wide: The pressure comes from daily workflow thrash and from the fear of falling behind in a shifting labor market. The identity risk may outlast the productivity gain: For knowledge workers, the deepest disruption may be losing the sense of who they are at work. Notable mentions and links Vercel is Eric’s day-to-day reference point for how AI changes expectations inside a real software company, grounding the conversation in lived experience rather than abstraction. Markdown is mentioned as a surprisingly durable AI workflow format, showing how newer tools often push people back toward older, simpler conventions. Sahaj Garg, co-founder and CTO of Wispr, is quoted at length because the framing in his essay on cognitive labor displacement shifts the conversation from efficiency and headcount to identity, status, and despair. Wispr Flow is the speech-to-text company Garg cofounded, and its essay becomes the bridge from personal burnout to the wider social consequences of AI adoption.

    39 min

  8. 28 MAR

    Why the longest-running tech CEO still fears failure

    Jensen Huang built NVIDIA into a trillion-dollar AI giant, but still works like survival isn’t guaranteed. Eric and John unpack fear, humility, market timing, and ingredients for enduring leadership. Summary Eric and John use Jensen Huang’s Joe Rogan interview to explore a kind of leadership that feels rarer than vision-talk or AI bravado: a founder who still sounds driven more by the fear of failure than the glow of success. What follows is part NVIDIA origin story, part meditation on timing, likability, humility, and the surprising honesty of someone who has won big without ever acting like the outcome was guaranteed. Along the way, they revisit NVIDIA’s near-death moments with Sega and an emulator gamble, connect Huang’s immigrant story to his emotional posture, share personal stories about giving money back to investors, and land on a broader takeaway: the best leaders may be the ones least blinded by the illusion of control. Key takeaways Fear of failure is a real engine: Huang comes across as someone driven less by the upside of winning than by the responsibility of not failing, and that honesty gives his leadership more weight. Likability matters more than people admit: The Sega story lands because trust and personal credibility, not just technical merit, helped keep NVIDIA alive. Timing matters more than strategy: A lot of success looks cleaner in hindsight than it felt in the moment, and the episode keeps returning to how much depends on market windows, luck, and circumstance. Good AI leadership makes room for fear: Huang’s answers stand out because he treats people’s concerns about AI as understandable rather than naive or beneath him. Humility makes conviction believable: He talks like someone who has survived bad bets, close calls, and uncertainty, which makes his confidence feel earned instead of performative. Survival is a better frame than inevitability: One of the deepest themes of the episode is that enduring leaders never fully assume they’ve arrived, and that mindset may be part of why they last. Notable mentions and links Jensen’s Joe Rogan interview mattered to John because he had heard Huang quoted for years but had never heard him talk at long-form length. The book Creativity, Inc. by Ed Catmull enters the episode as a parallel survival story, especially the famous Toy Story 2 anecdote where Pixar nearly lost the movie to an accidental deletion. Oneida Baptist Institute in Kentucky becomes one of the most memorable details in Huang’s backstory, because the hosts can’t get over what it must have meant for a nine-year-old immigrant to land there.

    41 min
Ver todo (20)

Acerca de

Two friends break down AI, technology, and entrepreneurship through mental models, real-world experience and the pursuit of a life well-lived.

Información

  • Creador
    Eric Dodds & John Wessel
  • Años de actividad
    2 k
  • Episodios
    20
  • Clasificación
    Apto
  • Copyright
    © Copyright 2026 Token Intelligence
  • Mostrar sitio web
    Token Intelligence