Apr 6, 2026 · 31m · startup-ideas
How I use iMessage and AI to run my life
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this episode, host Greg Isenberg and Lindy founder Flo demonstrate Lindy Assistant, an opinionated, iMessage-native AI executive assistant designed to automate scheduling, research, meeting preparation, and cross-platform workflows with turnkey simplicity.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Greg holds 26% of the talking time here. How this is scored →
speaking balance: gold is Greg, purple is the guest (3 minute bins)
Flo firmly rejects the premise that an AI assistant should require user-configured setup, drawing a stark contrast between tinker-heavy PCs and seamless iPhones.
Hardest push from Greg ▶ 11:38 Greg pressure-tests Lindy against human EA workflowsGreg directly challenges whether Lindy can match the nuanced responsibilities of his human assistant across research, scheduling, and high-stakes Fortune 500 sales triage.
Biggest teaching moment ▶ 16:17 Flo breaks down OpenClaw architectural risksFlo educates the audience on the security and architectural differences between OpenClaw running self-modifying agents versus Lindy operating a sandboxed external environment.
Greg holds their own ▶ 19:52 Greg maps out the AI agent market positioningGreg demonstrates sharp product strategy expertise by articulating the precise positioning spectrum from technical power-user tools like OpenClaw and Claude to Lindy's focused executive niche.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Greg as informed peer | Guest teaching | Guest disagreement | Greg pushing back | Why |
|---|---|---|---|---|---|---|
| Origins of Lindy Assistant and the iMessage Integration | 2 | 5 | 1 | 1 | Flo introduces Lindy Assistant as an opinionated iMessage-first AI and walks through a live demo of his daily schedule and automated email triage. Greg listens closely, offering appreciative remarks on how natural and human-like the assistant's tone sounds. | |
| Meeting Preparation, Contextual Memory, and Cross-Tool Execution | 3 | 6 | 1 | 1 | Flo explains the two-minute onboarding process, background inbox ingestion, and how Lindy takes proactive actions across Slack and Google Docs during meetings. Greg draws on his own experience with high email volume to validate the context ingestion approach. | |
| Configuration Simplicity, CRM Sync, and Custom Automations | 2 | 6 | 2 | 1 | Flo uses the iPhone vs. PC analogy to explain Lindy's zero-setup philosophy, demonstrating CRM updating and Appify scrapers for podcast transcripts. The two exchange lighthearted banter about European voice note culture before Flo highlights transcription limitations. | |
| Evaluating Lindy Against Human Assistant Responsibilities | 5 | 6 | 1 | 2 | Greg tests Lindy against the three main responsibilities of his real-world human assistant: research, scheduling, and high-value inbound sales routing. Flo demonstrates live how Lindy pulled background dossier research on Greg and can query past meeting notes via voice shortcuts. | |
| Architectural Comparisons: Lindy vs. OpenClaw and Claude | 7 | 6 | 2 | 2 | Flo provides a detailed technical comparison between OpenClaw's self-modifying code execution, Claude's developer-focused ecosystem, and Lindy's opinionated workflow model. Greg demonstrates strong domain knowledge by clearly synthesizing the trade-offs between horizontal toolkits and specialized executive assistants. | |
| Five-Year Roadmap, Generality Pull, and Practical Boundaries | 5 | 6 | 2 | 2 | Greg proposes expanding Lindy into distinct job roles like social media managers and front-end engineers accessible via dedicated phone numbers. Flo explains why Lindy deliberately resists horizontal generality to excel at the 80% of core executive assistant tasks. | |
| Pricing Model, High-Consumption Whales, and Voice Calling | 3 | 6 | 1 | 1 | Flo outlines Lindy's $49/month pricing structure, token consumption by power users sniping NYC restaurant bookings, and upcoming bi-directional voice calling. Greg inquires about operationalizing Lindy alongside human assistants in shared team workflows. |
Statements from this episode (0)
Nothing in this episode matches those filters. clear them