# Inspirations — Raw Dump > Everything here is unfiltered. Capture now, polish later. Each entry is a real AI workflow I've shipped. New fields added: situation, keyMove, timeEstimate, complexity, cost, whatWasHard, whatNextTime. --- ## [C01] Code → Trello Board **Date:** [fill in] **Tools:** Claude Code, Trello API, Python **Summary:** [One punchy line — what was the headline outcome] **Situation:** [What triggered this? What problem were you trying to solve? What constraints existed? 2-4 sentences.] **Workflow** 1. [What did you do first?] → [What happened?] 2. [Next step] → [What happened?] 3. [And then] → [What happened?] 4. [Result] **What came out:** [Concrete output — board, deck, doc, code, etc.] **The Key Move:** [The single most important prompt, step, or decision that made the whole thing work. One sentence.] **What made it satisfying:** [Why was this satisfying? Speed? Accuracy? The novelty?] **What was hard:** [The hardest part. Be honest — what almost stopped you?] **What I'd do differently:** [Next time I'd...] **Time:** [e.g. "45 minutes", "2 hours", "an afternoon"] **Complexity:** [Low / Medium / High] **Cost:** [e.g. "$0", "$5 API calls", "$20 Trello Power-Up"] --- ## [C02] Transcript → Proposal → Deck **Date:** [fill in] **Tools:** Claude, Markdown, Marp CLI **Summary:** [One punchy line] **Situation:** [What triggered this? Meeting transcripts → what happened next? What was the deadline pressure?] **Workflow** 1. [What did you do first?] → [What happened?] 2. [Next step] → [What happened?] 3. [And then] → [What happened?] 4. [Result] **What came out:** [Concrete output — proposal doc, deck, slides, etc.] **The Key Move:** [The single most important prompt or step] **What made it satisfying:** [Why?] **What was hard:** [Be honest] **What I'd do differently:** [Next time...] **Time:** **Complexity:** **Cost:** --- ## [C03] HubSpot Portal → Portal Email Template Copy **Date:** [fill in] **Tools:** HubSpot API, Claude, Node.js **Summary:** Two portals. One template. Zero manual rebuild. **Situation:** Two separate HubSpot portals. Needed to replicate an email template exactly from Portal A to Portal B. Manual copy-paste would mean rebuilding every setting from scratch — HubSpot has no native cross-portal template copy function. **Workflow** 1. Grabbed API keys from both HubSpot portals 2. Prompted Claude to generate a Node script — authenticate against Portal A, fetch the email template via API, then POST it to Portal B 3. Ran the script 4. Verified the template appeared in Portal B with all personalization tokens, styling, and settings intact **What came out:** Exact copy of the email template in Portal B, pixel-perfect. **The Key Move:** [Fill in — what was the exact prompt or the critical API call?] **What made it satisfying:** No manual rebuild. Took minutes instead of hours of trial-and-error clicking through HubSpot's UI twice. **What was hard:** [Fill in] **What I'd do differently:** [Fill in] **Time:** [fill in] **Complexity:** Medium **Cost:** $0 --- ## [C04] HubSpot MCP → RevOps Dashboard Audit **Date:** [fill in] **Tools:** HubSpot MCP, Claude **Summary:** [Fill in — what came out of it?] **Situation:** [Had a HubSpot portal with data but no clear view of what's happening. Wanted a RevOps-style dashboard audit — what's working, what's not, where are the gaps.] **Workflow** 1. Connected Claude to HubSpot via MCP — gave it direct API access to the portal 2. Prompted it with a RevOps persona — "you are a revenue operations analyst, audit my HubSpot setup and build me a dashboard" 3. Claude queried the portal live — contacts, deals, pipelines, email performance, etc. 4. Claude synthesized the data and produced a structured dashboard view or report **What came out:** [A RevOps dashboard — stage breakdown, conversion gaps, email engagement metrics, deal health summary. Or a structured audit report highlighting key issues.] **The Key Move:** [Fill in] **What made it satisfying:** No manual data export, no spreadsheet wrestling. Claude read the live portal and thought like a RevOps person. **What was hard:** [Fill in] **What I'd do differently:** [Fill in] **Time:** [fill in] **Complexity:** [fill in] **Cost:** [fill in] --- ## [C05] Baby Expense Tracker — Sheets + Claude + GCP Dashboard **Date:** [fill in] **Tools:** Google Sheets, Claude, GCP (Service Account), Google Sheets API **Summary:** A spreadsheet habit turned into a live dashboard — no backend, no separate app. **Situation:** Track all expenses related to the baby — school fees, hospitalization, doctor fees, prenatal/PD purchases from before birth. Needed a consolidated view but didn't want a separate app or complex setup. Sheets was already the habit. **Workflow** 1. Set up a Google Sheet with categories: school fees, medical, hospitalization, PD, etc. Kept it updated manually or via form 2. Prompted Claude to build a dashboard on top of the sheet — visualizations, summaries, category breakdowns 3. Created a GCP service account and generated a sheets API key, added it as a "user" in the sheet 4. Connected the dashboard to pull live data via Google Sheets API using the service account credentials **What came out:** A live expense dashboard for the baby — monthly burn, category splits, trend lines. Always current because the underlying sheet is still the source of truth. **The Key Move:** [Fill in — GCP service account for clean API access? The dashboard prompt?] **What made it satisfying:** Took a spreadsheet habit and turned it into a real dashboard without building a backend. GCP service account gave clean API access without exposing personal OAuth. **What was hard:** [Fill in] **What I'd do differently:** [Fill in] **Time:** [fill in] **Complexity:** [fill in] **Cost:** [fill in] --- ## [C06] Client Quiz Engine — Gemini + AWS Amplify + DynamoDB + Mailgun ✓ (published) **Date:** 2025-11-10 **See:** `06-quiz-engine.mdx` for the live published version. This entry is done. --- ## [C07] **Date:** **Tools:** **Summary:** **Situation:** **Workflow** 1. **What came out:** **The Key Move:** **What made it satisfying:** **What was hard:** **What I'd do differently:** **Time:** **Complexity:** **Cost:**