August 6, 2026
AI didn’t kill the click. It just told users they never needed it.
I was on a call with a founder a few weeks ago, watching him demo his own app to me. And I noticed something he didn’t. Every time he…

By Saif Islam
3 min read
I was on a call with a founder a few weeks ago, watching him demo his own app to me. And I noticed something he didn't. Every time he wanted to show me a feature, he'd pause, tap through two or three screens, hesitate for a second on which button did what, then land where he meant to go. He built this thing. He still had to think about it.
That pause is the whole story I want to tell you today.
Here's a number that should sit with you for a second: 45% of consumers now use ChatGPT or a similar AI tool for local recommendations, up from just 6% a year ago. Researchers are calling it the fastest behavior change search has ever seen. And it's not happening because people suddenly got smarter or lazier. It's happening because the cost of getting an answer just dropped to almost zero.
That's the part I actually want to talk to you about, because I don't think most founders have priced it in yet.
There's a model behavioral scientist BJ Fogg built years ago that I keep coming back to in almost every client conversation I have: behavior happens when Motivation, Ability, and a Prompt converge at the same moment. B = MAP.
Most founders I work with have obsessed over motivation, the pitch, the value prop, the onboarding copy that convinces someone to care. Almost none of them have obsessed over Ability, the actual cost of doing the thing. Typing on a phone, navigating three menus, reading a wall of options someone in a design review once called delightful, all of that is a cost your user pays every single time. Quietly, without complaint, mostly because there was no cheaper way to get what they wanted.
I've watched this happen to founders who are genuinely good people building genuinely good products. Nobody wakes up and decides to build a bad checkout flow. It just accumulates, one "quick add" field at a time, until ordering something requires more taps than it should ever take.
Here's what changes everything: when the cost of acting drops, motivation that used to be too weak to overcome friction suddenly becomes enough. Voice collapses that ability cost close to zero. "Order me a large pepperoni" takes less effort than opening an app and tapping through a topping selector. People who would've given up three taps in now finish the action, because there was no third tap to give up on.
Watch what Amazon actually did, not what they said. In mid-2026 they quietly rolled out Alexa+ Agentic Ads, where someone can order food or buy tickets entirely inside a spoken conversation. No screen tap, no click, no "are you sure" pop-up on the way out.
That's not "we added voice search." That's "we removed the click." And if you're a founder, I think that should genuinely unsettle you a little, the way it unsettled me the first time I really thought it through. Every screen you've designed, every comparison table, every carefully sequenced onboarding flow your team argued about for two sprints, was built on an assumption. That your users would look at things before deciding. That assumption has been doing a lot of unpaid overtime.
Here's the shift I think matters even more, and it's the one I actually want to sit with you on. When people stop clicking through options and start letting an assistant decide or summarize for them, they're not becoming less careful. They're outsourcing the carefulness. 82% of consumers now read AI-generated review summaries before checking individual reviews. They're not skipping research. They're handing it to something they trust to do it for them.
That trust is fragile. And I'd argue it's the actual product you're building now, whether you meant to or not. The old question was "can the user find what they need." The new one is "does the user trust what the system decided for them, and can they tell when to double-check it."
I don't think the founders who win the next few years are the ones who bolt a voice command onto their existing app like a novelty add-on. I think they're the ones who ask a much narrower, more honest question: where in my product is a screen doing a job a sentence could do faster? Where am I asking someone to look, compare, and click, when they'd rather just say what they want and trust me to get it right?
That founder I mentioned at the start, the one hesitating between screens on his own demo, I asked him that same question. He got quiet for a second. Then he said, "Honestly, most of it."
If you're reading this and something in your product just came to mind the same way, I'd genuinely like to hear what it is. That's usually where the real conversation starts.