The bait, then the rug-pull.
Rick Mulready opens by killing the assumption: yes, you've seen Claude artifacts before — and that's exactly the problem. They go stale. You re-prompt. You burn tokens regenerating the same dashboard. Live artifacts flip that: build once, refresh on click, fresh data every time from your connected tools. The rest of the video is one tight loop run seven times — pain, dashboard tour, exact prompt — wrapped in a tutorial that's really a pitch for a new Claude primitive.
What the video promised.
stated at 00:30“In this video I'm gonna explain exactly what live artifacts are, how to set them up, and then walk you through seven use cases that I've been building.”delivered at 18:05
Where the time goes.

01 · Cold open + promise
Names the problem (static artifacts) and the new thing (live artifacts). Promises 'what they are, how to set up, seven use cases.'

02 · What live artifacts actually are
Side-by-side Regular vs Live comparison card. Three reasons they matter: persistence, interactivity, fresh data.

03 · Four caveats up front
Local-only storage, no sharing yet, paid plans only ($20+/mo), no context-window indicator so it silently compacts.

04 · Where to find them + connector setup
Cowork → Live artifacts → New artifact. Walk through Anthropic-native connectors (Gmail, Calendar, Slack, Notion) and permission scopes (read-only / write / always-allow).

05 · Custom + Zapier MCP fallback
If an app isn't in the directory: paste an MCP server URL as a custom connector, or use Zapier MCP (8,000+ apps). Five-minute setup.

06 · Use Case 1: Daily Command Center
One page with calendar, unopened emails, Slack mentions, revenue, tasks, plus a weekly-pulse section (MRR, signups, churn, Q2 projection, refunds). About 10 minutes to set up.

07 · Use Case 1: The prompt walkthrough
Shows the actual prompt — 'looks and feels like Stripe, Linear, or Vercel,' design principles, layout structure. Notes Live Artifacts default to Haiku 4.5 and you can't change the model. Compaction kicks in mid-build.

08 · Use Case 2: YouTube Growth Tracker
Subscribers, goal progress, 90-day forecast, top performers (last 7 days), and the 'format pulling weight' tile that compares shorts vs long-form. Powered by vidIQ MCP.

09 · Use Case 3: Community Member Question Radar
His favorite. Scans new-member intake Google Sheet weekly. Returns AI-level distribution, discovery channels, top 5 feedback themes with mention counts, plus content recommendations for newsletter / YouTube / school posts. Compounds with growth.
10 · Mid-roll: Zone of Genius app
Soft CTA tucked right after the high-engagement use case. Pitches the AI Playbook membership + Zone of Genius app (pre-built AI workflows trained on Rick's IP).
11 · Use Case 4: Competitor Watch
No native connector needed — Claude uses web search to track 3 competitors for uploads, blog posts, pricing changes, social posts. Adds vidIQ MCP for YouTube. Outputs competitor cards + 5 content ideas based on competitor activity.
12 · Use Case 5: Launch Dashboard
For live product launches — pulls from Stripe / Gmail / Bitly / Slack / affiliate platform. Units sold, total revenue, pace-to-goal, daily sales momentum, refund rate. Demoed with CSV uploads since not currently launching.
13 · Use Case 6: Sponsor & Collab Triage
Points at his collaborations-only Gmail inbox. Classifies inbound sponsor/affiliate emails as good-fit / maybe / not. Surfaces ~$14K of opportunity. Fit criteria baked into the prompt.
14 · Use Case 7: Journal + Goals + Habit Tracker
Saved for last as 'most surprising.' Three tabs — today's reflection (energy/mood sliders, what worked, tomorrow's focus), goals progress, and pattern analysis (30-day energy/mood trends, habit streaks, monthly key-action recommendation). Cross-references journal entries with Google Calendar.
15 · Close + final CTA
Restates the unlock: build once, lives in sidebar, updates on demand. End-roll pitch for AI Playbook + Zone of Genius app.
Visual structure at a glance.
Named ideas worth stealing.
Three reasons live artifacts matter
- Persistence (sidebar across sessions)
- Interactivity (filters, search, drill-downs, toggles)
- Fresh data via connectors
Rick's framing of why this primitive is different from regular artifacts.
Four current limitations
- Local-only storage (doesn't follow you between devices)
- No sharing yet
- Paid plans only ($20+/mo Claude plan)
- No context-window indicator — silently compacts
Caveats stacked up front so the rest of the video isn't fighting objections.
Use-case loop
- State the pain
- Tour the finished dashboard
- Show the exact prompt
The same three-beat structure repeats verbatim across all 7 use cases.
Connector setup ladder
- Native Anthropic connectors (Gmail, Calendar, Slack, Notion, etc.)
- Custom MCP server URL
- Zapier MCP (8,000+ apps as fallback)
Three tiers of how to wire any app into Claude.
Format Pulling Weight tile
Custom dashboard widget comparing how much short-form vs long-form is contributing to subscriber growth. Outputs a recommendation ('prioritize depth over velocity').
Lines you could clip.
“You build it once, it stays in your sidebar, and it pulls in fresh data from your actual tools every time you open it. No re-prompting needed.”
“Takes about five minutes to set that up if you've not already.”
“This is the kind of insight that changes what I decide to publish next week or even in a few days.”
“The simple truth is this — the thing that makes these different is, again, you build them once and they stay alive.”
“No re-prompting, no burning tokens to get the same dashboard every day.”
How they spent the runtime.
Things they pointed at.
How they asked for the click.
“If you're an online business owner and you're looking to leverage AI in your business and you're looking for the easy button, I've created an entire AI team that is at your disposal... all inside of my Zone of Genius app which all my members in the AI Playbook have access to. I'll link to it in the description below.”
Soft tie-back to the same product mentioned mid-roll. Frames the membership as 'the easy button' for the 80% of busy work — cleanly extends the video's thesis (don't re-prompt, build once) into the offer (don't build at all, use mine).
Word for word.
Steal the 'one micro-pattern, repeated seven times' structure.
The whole video is one three-beat loop — pain, demo, prompt — replayed seven times. Pick a primitive your audience just got access to, stack seven applications of it, and front-load the gotchas.
- Pick a new primitive (model, feature, MCP) your audience just got access to and could use today.
- Build 7 use cases that all follow the same three-beat micro-pattern — pain → dashboard tour → exact prompt. Don't vary the rhythm; viewers settle into it.
- Front-load 3-4 gotchas before any demo. 'It's local-only, no sharing yet, paid plan, silently compacts' — saying it up front buys trust for the rest of the video.
- End every use case with the exact prompt visible on screen. The prompt IS the gift; the dashboard is the proof.
- Specify aesthetic by reference — 'looks and feels like Stripe, Linear, Vercel.' Three brand names beat ten adjectives every time.
- Save the most surprising / most personal use case for last (his was the journal+habit+goals tracker). Recency-effect closer.
- Plug your offer mid-roll right after the highest-engagement use case, then echo at end-roll. Two soft beats > one hard pitch.
- Joe-relevant: build a JoeFlow 'morning command center' live artifact that pulls overnight transcripts + Batch run output + Sessions activity into one sidebar dashboard.
What you can actually build this weekend.
Pick one dashboard from the seven, copy the prompt structure, point it at the data you already have, and you've got a sidebar tool you'll use every morning.
- Open Claude desktop → Cowork → Live artifacts → New artifact. That's the whole entry path.
- Start with the Daily Command Center — it's the lowest-friction win. Calendar + email count + revenue + tasks on one page, ~10 minutes.
- Wire up Anthropic-native connectors first (Gmail, Calendar, Slack, Notion). Only reach for Zapier MCP if your app isn't in the native directory.
- Write the prompt like a brief, not a question — name the dashboard, specify the aesthetic ('Stripe / Linear / Vercel'), list the sections you want.
- Don't trust the demo data. Test the refresh button immediately after first build to see what your connectors actually return.
- The journal + goals + habit tracker is the highest-leverage one if you've never journaled consistently — calendar cross-reference is what makes it stick.
- Caveat to plan around: artifacts are local-only and don't sync between machines (yet). Build on the laptop you actually use every morning.







































































