🎙️ How I AI: How this PM uses Claude to handle 70% to 80% of his workday
- ID
- 19875
- Status
- summarized
- Published
- 31 Aug 2026, 11:01 PM
- Fetched
- 01 Sep 2026, 12:33 AM
- Provider
- Lenny's Newsletter
- Category
- product-startup
- Original URL
- https://www.lennysnewsletter.com/p/how-i-ai-how-this-pm-uses-claude
- Source URL
- https://www.lennysnewsletter.com/feed
Summary
- Score
- 7.0
- Created
- 01 Sep 2026, 12:33 AM
- Tags
- Audience
- ai_agent_usersdevelopersvibe_coderssaas_founders
What happened
Daniel Blum, a PM at Melio, built a self-improving Claude + Cowork system that handles 70-80% of his workday by managing his Notion board, scanning Slack/email, and generating daily briefs. The system identifies gaps in its own context files, asks targeted questions to fill them, and refreshes context every few weeks through recurring updates fed by voice memos, links, and brain dumps. He packaged the setup into a 15-minute onboarding for other Melio employees using tools the company had already licensed.
Why it matters
The key architectural insight is that the system can update its own core files and connect to tools you already use (Notion, Slack, email) — meaning the platform choice matters less than the architecture of self-updating context. If you're building personal AI workflows, invest in a recurring context-refresh mechanism and a 'identify what I don't know' loop rather than one-shot prompting, even though the first few weeks will feel slow and low-quality.
Discussion angle
How would you replicate Daniel's 'gap detection' pattern — where the AI scans your Slack and email for unfamiliar terms and asks you to confirm meaning before saving to context files — using tools available today in Malaysia, and is the months-long context-building investment realistic for a solo founder versus a PM inside a company that already licenses the tools?