Program
What attendees see — share-friendly. Copy verbatim for the landing page, registration confirmation email, and pre-event reminder.
What you'll get
Two live sessions, a week apart, designed to take you from “AI sounds important but I don't know where to start” to “I have a working prototype I can show my team.”
- →A method to identify your most valuable AI opportunity in under 60 minutes.
- →A worksheet you'll fill in live (Friction Map + Time × Impact matrix + Flow Designer).
- →A live build: we'll take a real attendee's flow and prototype it in 25 minutes using no-code tools.
- →Recordings of both sessions, kept evergreen.
“Find your AI starting point”
You'll leave with a prioritized quick win and a designed flow — on paper, before any tools.
A worksheet you can re-use across your team: one prioritized quick win + one fully-designed flow.
“Prototype it in under 2 weeks”
One attendee's flow gets built live in 25 minutes using no-code tools. You see the method in action, errors included.
A working reference prototype you can adapt to your own flow, plus a mental model for prototyping the rest in under two weeks.
Pre-session checklist
- ▸Download the Friction Map worksheet (sent 3 days before).
- ▸Block 60 minutes — uninterrupted. The activities only work if you actually do them.
- ▸Camera optional. Chat is where the action happens.
Two Mondays. One method. A working prototype.
Seats are limited. We pick attendees who'll actually do the work.
Facilitator minutes
Run-of-show with timing, speaker prompts, activity instructions, and contingency notes. Private.
“Find your AI starting point”
backbone — "You don't have an AI problem. You have a friction problem."
Hook + intro
- ›70% of SME AI initiatives never reach production — not because of tech, because of where they start.
- ›Anchor: AI doesn't replace humans. It replaces inefficient processes.
- ›Self-intro: CTO Amalgama, ~14 years, wellness ops focus, 30+ products in production.
- ›Slides 1–4 (title / stat / anchor / Tom intro).
3-step framework
- ›Today: steps 1 + 2. Next Monday: step 3 — live build.
- ›Common failure: jump straight to "what tool", skip the diagnosis.
- ›Slides 5–6 (framework + what we cover today vs next week).
- I don't know where to start
- I tried and it failed
- I have pilots but they don't scale
- I'm just exploring
Friction Map
- ›Define: list of repetitive / costly / error-prone tasks across your op.
- ›Lenses: time lost, money lost, customers lost, quality inconsistent.
- ›Show case: real Amalgama wellness client with 30% weekly hours on X task.
- ›Trap: only thinking digital. Best frictions usually live in handovers between people.
- ›Slides 7–10. Show real before/after numbers from the case.
Time × Impact matrix
- ›Four quadrants: quick wins / strategic / minor / discard. Start with quick wins.
- ›Why: build momentum, generate case, learn the tools.
- ›Trap: smart founders fall in love with strategic. Fine — but AFTER the first quick win.
- ›Anchor: what 20% of focus drives 80% of the impact?
- ›Slides 11–14 (matrix + trap + anchor).
Design the flow
- ›Pick ONE flow. Not five.
- ›Three non-negotiables: one flow / one owner / one metric.
- ›Pencil and paper first — tool second.
- ›Show the before/after of a real Amalgama flow (6 steps → 2 steps).
- ›Slides 15–19. Show the actual hand-drawn before/after.
Pre-close + Q&A
- ›Today you leave with: Friction Map + quick win + flow designed.
- ›Next Monday we take one real flow from the audience and build it live.
- ›Homework: finalize your flow, reply to tomorrow's email with it. Most interesting one is built live.
- ›See you Monday. (NO mention of AI Blueprint W-A yet — that's S2.)
- ›Slides 20–23.
What happens in the 7 days
- T+1 (Tue):Email out — recording S1 + worksheet PDF + CTA to send the flow back to Tom's inbox.
- T+3 (Thu):Reminder email — “send your flow by Friday for a chance to be built live”.
- T+4 (Fri):Tom reviews submissions. Picks 3 candidates. Confirms 1 with the author.
- T+5 (Sat):Tom does a dry-run build of the chosen flow. Catches any blockers. Confirms Plan B pre-built.
- T+6 (Sun):S2 reminder email — “see you tomorrow + bring your laptop”.
Drop-off risk: 30–50%. Mitigation = real homework + worksheet value self-contained in S1.
“Prototype it in under 2 weeks”
backbone — "You don't need to build it. You need to validate it. Tools come last."
Recap + warm-up
- ›Reactivate session 1: worksheet → quick win → flow.
- ›Rules today: hands-on. If something breaks live — that's the point.
- ›If you applied to the series, you've done 60% of the work. Today we finish.
- ›Slides 1–4.
- Yes, fully designed
- Half-done, still thinking
- No flow yet, just observing
Prototype mindset
- ›Definition: smallest thing that validates the hypothesis.
- ›Why under 2 weeks: longer than that = you're still designing.
- ›Expensive trap: hiring a dev / custom build before validating.
- ›Why no-code first: speed, cost, reversibility, learning.
- ›Stack tour: orchestration (Zapier/Make/n8n), forms (Typeform), AI (OpenAI/Anthropic), storage (Airtable/Sheets/Notion).
- ›Decision tree: simple trigger→action = Zapier. Branching logic = Make/n8n. Generated text = LLM in the right step. Scale > 10k users = sales call.
- ›Slides 5–10.
- Zapier
- Make / Integromat
- n8n
- OpenAI API directly
- None of the above
Failure case "Sofía"
- ›Hypothesis: bot that calls inactive users to bring them back.
- ›Initial build: simple prototype in N days.
- ›What went wrong: bot called every 20 minutes. Users hated it.
- ›What went RIGHT: the first calls did recover users.
- ›Lesson: the prototype failed as a system, but validated the hypothesis. That's success.
- ›Amalgama parallel: a real prototype of ours that failed but validated. (Pick the case in advance.)
- ›Rule: if your prototype can't fail, it's not a prototype. It's production.
- ›Slides 11–14. Show real numbers from the Amalgama case.
★LIVE BUILD
- ›Announce the flow chosen from the audience (sent during the week-gap).
- ›Read trigger / steps / output / metric out loud.
- ›Ask the author to confirm we can build it (if present).
- ›Build live: Zapier trigger → OpenAI classify → filter → Airtable/Sheets row → WhatsApp reply → end-to-end test.
- ›Every 10 min, prompt chat: "What would you change?" Read 1–2.
- ›If something breaks, show the debug LIVE. That's the lesson.
- ›Close: if you built this from zero today, it took ~15–20 real minutes. That's the point.
- ›Slides 15–18 (build map / step indicators).
- ›Share screen with creds pre-loaded.
- ›PLAN B running in another tab: pre-built version of the same flow. If Zapier or APIs fail, switch tabs and demo from there.
- ›If everything collapses: walk through one real Amalgama prototype already in production.
When to scale
- ›Prototype runs out of room when: > 100 executions/day, tools-can't-handle-logic, sensitive data (PHI/PCI), cross-functional 3+ areas.
- ›If your business grows and a Zap isn't enough — not a problem, a signal. You validated.
- ›When to leave this method and level up: 2–3 quick wins live, cross-flow patterns visible, you want a 90/180/365 roadmap.
- ›Slides 19–21.
CTA + close
- ›Implement your first quick win this week.
- ›Wellness operators: deeper conversation specifically for you — AI Blueprint Webinar A.
- ›Not wellness? Stay in the loop — recording + worksheet. Email opt-in.
- ›Thank you. Break things this week.
- ›Slide 22 (W-A application + QR). DO NOT mention $4,900 — that's W-B.
Post-webinar sequence
- T+1 day: thank-you email + S2 recording + apply to W-A link.
- T+7 days: nudge to wellness ops who didn't apply yet.
- T+14 days: final CTA / nurture sequence for non-wellness attendees.
- T+30 days: review attendance → W-A application conversion. Adjust mid-funnel messaging.
Materials checklist
Everything that has to exist before T-3 days. Status, owner, link. Updated live during prep.
- Slide deck S120–23 slides. Reuse framework from W-A web deck in `ai-blueprint` monorepo.
- Slide deck S221–22 slides. Live build screens included.
- Friction Map worksheet (PDF, 3 pages)Page 1 = friction list / Page 2 = matrix / Page 3 = flow template. Bloqueante de S1.
- Real Amalgama case study for S1 block 3Wellness client with quantified time saved. Needs permission to share.
- Real Amalgama failure-mode case for S2 block 3Prototype that failed but validated. Needs permission.
- Zapier account (paid tier active)Avoid task limits during live run.
- Make.com account (backup orchestrator)
- OpenAI API key with billing activeAnthropic also pre-loaded as fallback.
- WhatsApp Cloud API sandboxOr Twilio WhatsApp test number.
- Google Sheets / Airtable test base
- Plan B pre-built flow in second browser tabSame as the chosen audience flow. Tested 24h before.
- Backup case (Amalgama-built prototype) ready to walk through if everything collapses
- Landing page /starter-map (registration to the series)In `ai-blueprint` monorepo. Form: name, email, role, biggest manual process.
- Tomspot contact + deal mapping for new signupsSync with Gon. Tag: "AI Starter Map S1 Mon DDMMYY".
- Recording infra (Zoom Webinars / Demio / RiversideFM)Decide once across AI Blueprint + Starter Map.
- T-3 days (pre-S1): reminder + worksheet attached
- T+1 (gap day 1): S1 recording + worksheet + "send your flow"
- T+3 (gap day 3): reminder — last call to send flow
- T-1 day (pre-S2): "see you tomorrow + bring laptop"
- T+1 (post-S2): thank-you + S2 recording + apply to W-A
- T+7: nudge wellness ops to apply to W-A
- T+14: final CTA / nurture for non-wellness
- Dry-run of S1 with one Amalgama colleague
- Dry-run of S2 LIVE BUILD with stopwatch25-min cap is tight. Run it twice.
- Promo plan — LinkedIn (Tom, Gon, Joe) + cold list + partners
- Date lockedBlocked by: W-A must be evergreen-recorded before Starter Map launches.
- Final worksheet spec (PDF / Notion / mini-app / Sheets)blockingDefault proposed: PDF 1-page worksheet (3 pages). Pending Tom's ok.
- Webinar platform (Zoom / Demio / Riverside)blockingDecide once across both AI Blueprint and Starter Map.
- Owner of post-S2 W-A application reviewblocking