Most writing about invisible AI treats invisibility as a destination, get there and you've won. Using these products myself taught me something different, invisibility isn't a constant state, it's a timing problem, and most products that get called invisible haven't actually solved it.
granola gets the timing right
Granola is the clearest example I've actually lived inside of what invisibility should look like, and it isn't invisible all the time, on purpose. Right as a meeting is about to start, it shows up, a notification, one click to start taking notes and join the meeting at once. Then it disappears. It takes notes diligently in the background for the whole call, and I don't think about it again unless I need something from it mid-meeting, at which point it's easy to pull back up. That's the actual design, visible exactly when I need it to act, invisible exactly when it shouldn't get in the way, on a schedule that matches the meeting itself, not a blanket rule.
wispr flow, the honest counter-example
Wispr Flow gets held up, including by me in an earlier essay, as the model of an invisible AI product, and using it myself, I don't think it actually is one yet. It's the product I most wanted to disappear into my thinking, and it hasn't, not for me. I have real ideas for the product changes that would close that gap, and I'm not ready to lay them out here, they're still taking shape. But I'd rather say that honestly than credit a product with an invisibility it hasn't earned just because the pitch is right.
invisibility is earned, not assumed
The lesson from putting these two side by side is that invisibility isn't a property a product has or doesn't, it's a sequence a product has to get right, when to show up, when to disappear, and when to be reachable again without demanding attention. Granola got that sequence right for a meeting. Wispr Flow hasn't gotten there yet for how I think. Most AI products getting called invisible right now haven't actually earned the word, they've just adopted the pitch.
conclusion
The best AI products won't feel like products, but that's a result, not a starting assumption. It has to be built, moment by moment, not claimed in a positioning line. Granola's proven it's possible. I'm still waiting on the rest, Wispr Flow included.
Get new essays and theses by email
More essays
- The Liability Wall Stopped Being Hypothetical Oct 4, 2026
- The Personal Assistant Landscape, Right Now Sep 30, 2026
- The Home Doesn't Have One User, So Its Assistant Shouldn't Either Sep 26, 2026
- Qualities of Great AI Coding Agents Sep 22, 2026
- The AI Bubble Deflates, The Technology Doesn't Sep 22, 2026
- The Boring Levers That Actually Run A Boutique Agency Sep 15, 2026
- India's Seed Stage Is Missing Its Powerhouse Sep 13, 2026
- What Not To Do In A YC Interview Sep 8, 2026
- Code Review Was Never The Bottleneck Sep 7, 2026
- An AI Assistant That I Actually Want Sep 1, 2026
- The Small Things I Keep for Myself Aug 31, 2026
- What Changes When You Go From Operator to Investor Aug 10, 2026
- The Wow Moment Shouldn't Take Two Weeks Apr 21, 2026
- The Three Moments That Will Make or Break Littlebird Apr 14, 2026
- Voice at Work, Why It's Harder Than It Looks Mar 31, 2026
- Top of Funnel for Voice-First Tools Is Not Signups. It's Someone Else's Product Mar 27, 2026
- When Thinking Outruns Writing Mar 26, 2026
- Why Voice-First Tools Struggle in India Mar 23, 2026
- The Tiny Feature That Saves Your Users and Your Metrics Feb 5, 2026
- Anatomy of a CLI-Based Code Assistant Jan 20, 2026