Home Portfolio How I Use AI Two Cents Book a call
Living document — updated as I learn

How I use AI
every day

I only keep workflows that change something measurable — a decision faster, a question not asked, a document actually used. If I can't point to the signal, I haven't built a system.

3 sections · 23 use cases · updated July 2026
Tools in my stack
Claude Code
Cursor
Claude.ai
Granola
Perplexity
Copilot
Figma
n8n
Lovable
NotebookLM
Ollama
Make
Stitch
OpenClaw
Grok
Supabase
01
✍️
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?
Claude.ai Copilot
🎙️
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
Cursor Granola Wiki MCP
🗂️
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.
Claude Code
🔍
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."
Perplexity NotebookLM
🥊
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.
Claude.ai
⚙️
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.
Claude Code Lovable Replit
🎨
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.
Figma MCP Cursor
🖼️
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.
Google Stitch Figma MCP
🤖
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.
Ollama OpenClaw
🎤
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.
Grok
📊
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.
Make.com Perplexity Google Sheets
🧠
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.
n8n Supabase
02
📋
Capturing decisions and action items from every meeting
I run Granola for every meeting. It captures audio in the background and produces a structured note with decisions, open questions, and action items — not a word-for-word transcript. By the time the call ends, the note is ready to forward or feed into the next session.
Outcome Did we re-discuss something from a previous meeting? That's a failure state.
Granola
📡
Scheduled weekly briefing across all active products
I have a scheduled Claude Code agent that runs every Monday morning. It scans my email, Jira, Slack, and SharePoint across all my active products and sends me a structured briefing — RAG status, open decisions, what each team needs from me this week. It arrives before I open my laptop.
Outcome Did the briefing surface something I'd have missed? If never — sources or prompts need rework.
Claude Code n8n
🏆
Drafting positioning docs and sales collateral
When the sales or field team needs a positioning doc, competitive comparison, or battle card, I describe the product situation and the audience to Claude and get a solid first draft immediately. The team gets consistent messaging faster and I'm not a bottleneck between deals and content.
Outcome Are field teams using the collateral in conversations, or asking for changes?
Claude.ai Copilot
📊
Tracking which AI workflows are actually working
I built an HTML dashboard that auto-updates every time I or a teammate runs one of my skills. It logs which skill was used, how long it would have taken manually, and what I'd change. Without this, I'd have no way to know if any of it was actually working.
Outcome A rarely-used or weak-output skill gets revised or retired. Usage data drives the loop.
Claude Code
03
📰
Automated customer meeting summary sent to leaders weekly
I have a Copilot prompt scheduled to run every Sunday night. It reads the transcripts from all customer meetings that week and writes a structured update — which customers I met, what they said, what's at risk, and what I'm doing about it. Leaders get it in their inbox by 8am Monday without me writing a single word.
Outcome Did a leader ask "what happened last week?" If yes, the update wasn't useful enough.
Copilot n8n
Building a working prototype before writing requirements
Instead of writing a lengthy spec for every new idea, I build a rough working prototype with Claude Code or Lovable first. I put it in front of a customer or stakeholder, learn from their reaction, and then write the real requirements based on what I observed. All prototypes live in a central hub so stakeholders can find them without asking.
Outcome Did the prototype change a design decision before production code was written? Every change here is a sprint saved.
Claude Code Lovable
🧪
Automated demo environment setup using an MCP server
Before a product demo I need a clean Marketo environment with realistic campaigns and forms — not my production data. I set up an MCP server for Marketo so I can tell Claude exactly what test setup I need and it creates everything programmatically. Demo prep that used to take 30 minutes now takes under 2.
Outcome Did the demo env require any manual fix before the call? Zero manual setup is the goal.
Marketo MCP Claude Code
🤝
Replacing recurring status meetings with scheduled AI briefings
For teams or partners who need regular status updates, I set up a scheduled AI briefing instead of a recurring meeting. It pulls from the same sources as my Monday briefing and sends a summary on a cadence. Most of the time, the meeting never gets booked because the briefing answered what it would have covered.
Outcome A recurring sync that never got scheduled is the best outcome. I track how many were cancelled directly because of this.
Claude Code
🔭 Still figuring out

The frontier

Use cases I've identified but haven't fully solved. If you've cracked any of these, I'd love to talk.

Proactive push agents

Competitor moves and churn signals landing in my inbox before I think to look. Currently I pull. I want it to push.

Customer intelligence river

Weekly synthesis → "3 things customers are saying this week that weren't true 4 weeks ago."

One output → five surfaces

A LinkedIn post that automatically becomes a Slack message, exec talking point, and newsletter item. Publish once, distribute intelligently.

Voice → everything, everywhere

Every meeting auto-transcribed, decisions surfaced, actions distributed — zero manual work at any point in the flow.