📞
Automating post-call follow-ups from a transcript
After every customer call, I run a single Claude Code agent on the Granola transcript. I've set it up to produce all my post-call tasks in parallel so nothing gets forgotten, even on a busy day.
- Customer asks and bugs from the call → JIRA tickets filed with context from the transcript
- Status and next steps → my Excel tracker updated with this customer's row
- Customer-facing slides → specific sections updated based on what was discussed
- Good quotes from the customer → appended to my running quotes library
- FAQs that came up → added to the FAQ doc I share with field teams
- Follow-up email → drafted with a summary and agreed actions for both sides
Outcome
Post-call admin: 45 min → under 5. Any missing artifact = agent config has a gap.
✍️
Getting a first draft for any document
For anything that involves writing — PRDs, stakeholder emails, exec decks, interview prep — I describe what I need and get a first draft in under a minute. I then spend my time making it better rather than staring at an empty doc.
Outcome
Hours to first draft → minutes. Did I actually use the output or discard it?
🎙️
Turning voice recordings into structured documents
I think better out loud than in writing, so I've built my workflow around voice. I hit record in Granola and just talk — about a product problem, a customer situation, whatever's on my mind. The transcript goes into Claude or Cursor and comes out as a structured document.
- I speak my product knowledge stream-of-consciousness → Cursor + Wiki MCP turns it into a PRD and publishes it to Confluence
- I record a product demo → Claude turns the transcript + screenshots into customer-facing docs
- I record a good customer call → it becomes a reusable demo script for the SC and field team
🗂️
Per-project context files for instant session loading
I create one context file per product I work on. It stores everything relevant — requirements, past decisions, JIRA status, Confluence links, key stakeholders. At the start of any Claude session I load this file and immediately have full context without rebuilding it from memory.
Outcome
Time to get productive on any product at any moment. Re-orienting = broken system.
🔍
Competitive research and market analysis on demand
When I need competitive context or market data, I ask Perplexity rather than opening five browser tabs. For deeper synthesis — like loading an analyst report or a batch of customer call transcripts — I use NotebookLM so I can ask specific questions across all of it at once.
Outcome
No longer blocking decisions on "let me get back to you."
🥊
Preparing for high-stakes conversations
Before any high-stakes conversation — exec alignment, a difficult customer call, a job interview — I describe the context to Claude and ask it to argue against my position as hard as it can. The goal is to find the holes in my thinking before someone else does.
Outcome
Zero surprises in the room. Every unexpected objection is a gap to close next time.
⚙️
Building complete apps without an engineering team
I use Claude Code to build complete web apps by myself. I act as the PM and designer — I describe what I want, review what gets built, and redirect. Side projects I used to shelve because I couldn't build them fast enough now actually ship.
Outcome
The bottleneck is now whether the idea is worth building, not whether I can build it.
🎨
Prototyping on top of existing Figma screens
When I want to prototype something that builds on an existing product, I use Figma MCP to pull the real screen designs into Claude Code. That way I'm iterating on top of the actual design system rather than building something that looks completely different from the product.
Outcome
Time from idea → shareable prototype. More than a few hours = something to fix.
🖼️
Generating UI designs from a text description
When I have a rough idea for a new screen or flow, I describe it in Google Stitch and get a full UI design back in seconds. I use it to explore 2–3 directions before deciding which one to prototype or take to engineering — much faster than doing wireframes by hand.
Outcome
Did seeing the generated screens change the design direction? If not, the prompt wasn't specific enough.
🤖
Self-hosted AI assistant running on a local model
I set up OpenClaw on a VM and connected it to Ollama, which runs open-source LLMs locally. The result is a personal assistant I can message on Telegram from anywhere — and since everything runs on my own machine, no data leaves my environment. Useful for anything I don't want going to a cloud API.
Outcome
Did the bot answer something I'd have had to look up manually? Zero cloud API = zero data exposure.
🎤
Practising presentations using voice AI
Before a big presentation I open Grok voice and speak through my talk as if I'm in the room. Grok asks me questions, pushes back on vague points, and tells me where I lost the thread. It's closer to real rehearsal than reading slides to myself.
Outcome
Did the real presentation go better than it would have without rehearsal? Fewer filler words and better structure are the markers.
📊
Screening my stock watchlist against fundamental criteria automatically
My watchlist lives in Google Sheets. A Make.com scenario iterates through each ticker, sends it to Perplexity AI with my fundamental analysis criteria — things like P/E ratio thresholds, revenue growth, debt levels — and writes a pass or fail against each criterion back into the sheet. I run it before deciding whether to research a stock further or ignore it.
Outcome
Initial stock screening that used to take an afternoon now runs in minutes. I only spend time on stocks that clear all the criteria.
🧠
Building a RAG chatbot that answers questions from my own documents
I built a pipeline in n8n that takes documents, chunks them, generates vector embeddings, and stores them in Supabase. A chatbot sits on top — when someone asks a question, it retrieves the most relevant chunks via vector similarity search and passes them to an LLM to answer from that context. No backend code written by hand.
Outcome
Answers are grounded in the actual documents so hallucinations drop significantly. Anyone can query a knowledge base I've set up without having to read through the source material.