Stop Using AI to Make Horses Faster: Design for the Future Now | Lazy Leverage #55

Lazy Leverage

AI isn’t here to replace your team—it’s here to give them time back. Join Jon and Peter as they explore how the right interfaces and integrations can supercharge productivity across your org!

Jon kicks things off by sharing his vision: every new client should get a completely customized front end tailored to their needs—think “cars, not faster horses.”

He and Peter riff on the challenge of AI adoption at the ground level—how time-starved teams struggle to learn new tools—and the importance of delivering point solutions that are simple, embedded, and immediately useful. There’s an appreciation for systems thinking here–that true leverage comes from building thoughtful infrastructure.

Peter raises a great point about the power of centralized data. He’s excited about tools like Loveable, but acknowledges their real magic happens when all business data lives in one well-organized database. They reflect on past limitations—splitting data between platforms—and how new tools like Supabase and Airtable now make consolidation more accessible, especially with AI riding shotgun.

Finally, Jon and Peter dive deep into emerging AI tools like Lindy and Perplexity, ways to integrate Notion with natural language, and even the wild potential of GPT-4’s AI-generated images for marketing real estate!

Key Topics:
(01:40) Cars, Not Just Faster Horses
(08:12) Possible Paths to AI Adoption by Teams
(12:54) AI for Enterprise-Level Databases
(20:43) Property Management Applications
(24:31) Using AI to Answer AI-Related Questions
(31:46) Finding an AI Model That Helps You Aggregate Industry-Specific News
(34:42) How Property Managers Can Take Advantage of GPT-4’s New Image Gen Capabilities
(39:20) “The Future Is Here. It’s Just Not Evenly Distributed."

Stay connected for more insights and strategies by following:

Jon: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠@MatznerJon⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ on X and at ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠lazyleverage.beehiiv.com⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Peter: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠@pslohmann⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ on X and at ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠peterlohmann.com