How I AI

How a 91-year-old vibe coded a complex church event management system using Claude and Replit

John Blackman, a 91-year-old retired electrical engineer, shares how he used Claude and Replit to build a complex application for his church's community service events—with no prior software development experience and for less than $350. His app allows event organizers to create events, recruit volunteers, and manage sign-ups, with a standout feature for organizing free oil changes for participants. *What you'll learn:* 1. How John used Claude to create detailed product requirements and user stories 2. John's philosophy on embracing new technology throughout his career 3. The exact process for integrating third-party APIs (like VIN lookup for oil changes) with minimal technical knowledge 4. How he automated report generation for volunteer management and resource planning 5. How the software generates personalized "Impact Passports" for event participants 6. Why letting AI build without preconceived notions of "correct" implementation can lead to faster, more functional results 7. How to troubleshoot common development-to-production issues when working with AI coding tools *Brought to you by:* WorkOS—Make your app Enterprise Ready today: https://workos.com?utm_source=lennys_howiai&utm_medium=podcast&utm_campaign=q22025 Orkes—The enterprise platform for reliable applications and agentic workflows: https://www.orkes.io/ *Where to find John Blackman:* Website: http://johnbeng.com/ *Where to find Claire Vo:* ChatPRD: https://www.chatprd.ai/ Website: https://clairevo.com/ LinkedIn: https://www.linkedin.com/in/clairevo/ X: https://x.com/clairevo *In this episode, we cover:* (00:00) Introduction to John Blackman and his background (02:55) John's impressive career (03:59) How the church project started (05:06) Using Claude to create a development roadmap and requirements document (07:29) The concept of the Impact Passport for event participants (08:57) Generating user stories and requirements with Claude (10:32) The multi-tenant architecture with system and local church administrators (12:54) Building the application with Replit (13:32) Demo of the administrator interface and event management features (17:56) Specialized reports for different services (food pantry, vision center, oil changes) (20:30) The participant registration flow with QR code scanning (21:55) Adding new features like volunteer name tag generation (24:40) Troubleshooting AI "rabbit trails" during development (26:09) Challenges moving from development to production (27:13) John's lack of coding experience (29:42) The advantage of having no preconceived notions about implementation (30:25) Total development costs and timeline (31:31) Impact and reception from the church community (32:42) Lightning round and final thoughts *Tools referenced:* • Claude: https://claude.ai/ • Replit: https://replit.com/ • SendGrid: https://sendgrid.com/ • AutoCAD: https://www.autodesk.com/products/autocad/ *Other references:* • OpenAI API: https://openai.com/api/ • VIN (Vehicle Identification Number): https://en.wikipedia.org/wiki/Vehicle_identification_number • Multi-tenant architecture: https://en.wikipedia.org/wiki/Multitenancy • Role-based access control: https://en.wikipedia.org/wiki/Role-based_access_control • Excel: https://www.microsoft.com/en-us/microsoft-365/excel • DocuSign: https://www.docusign.com/ _Production and marketing by https://penname.co/._ _For inquiries about sponsoring the podcast, email jordan@penname.co._

JBJohn BlackmanguestCVClaire Vohost

Jun 23, 2025·40m·Watch on YouTube ↗

📖 CHAPTERS

1. 1

   Meet John Blackman: 91-year-old “vibe coder” building for community impact

   Claire Vo introduces John Blackman, a 91-year-old church volunteer who used Claude and Replit to build a full event-registration and management system. John frames the real-world problem: Impact Weekends with many free services and a paper-based registration workflow that needed to scale.

2. 2

   A career of learning: engineering, AutoCAD pioneer, and “growth mindset” arc

   Claire shares John’s unusually broad background—electrical engineering, running a hardware store, airplane mechanic certification, AutoCAD adoption, fiber optic projects, and even helping with Google Fiber. The chapter sets up why John is comfortable learning new tools late in life and draws a parallel between AI today and AutoCAD adoption decades ago.

3. 3

   How the church app idea started: turning handwritten workflows into software

   John explains that the project began as a desire to stop writing everything by hand for registrations and event logistics. He drafted an outline of what he wanted, then sent it to Claude with explicit instructions to target Replit as the build environment.

4. 4

   Using Claude to create a roadmap and PRD-style requirements

   The team begins with a broad prompt—asking Claude how to create a development roadmap—then lets Claude ask clarifying questions. From the outline and Q&A, Claude produces a structured MVP plan, phases, and a requirements-style document that can be handed off to an agentic builder.

5. 5

   The “Impact Passport” concept: participant-facing artifact + QR-driven signups

   John introduces the “Impact Passport,” inspired by another church’s paper process, as a printable guide for attendees that lists their chosen services/stations. The passport idea evolves into QR-code-based registration that makes it easy for participants to sign up from flyers and phones.

6. 6

   User stories and roles: designing for pastors, ministry leaders, and attendees

   Claude generates user stories that John finds largely accurate, with minor edits as development progresses. The conversation highlights how the system must serve multiple stakeholders—participants, local church admins, system organizers, pastors—plus non-functional needs like usability and reporting.

7. 7

   Multi-tenant architecture: system admins vs. local church admins (RBAC)

   The app’s structure becomes notably sophisticated: a multi-tenant, role-based system where system administrators can see all churches and approve admins, while local church admins only see their own events and data. Claire calls out the complexity—this is a real “enterprise-style” access model built from a community need.

8. 8

   From spec to build: handing Claude output to Replit Agent

   John describes the handoff: copy Claude’s structured requirements into Replit, then let the agent generate the codebase rapidly. Claire notes the project’s “meaty” structure (docs, migrations, generated assets), signaling a full-stack application rather than a simple form.

9. 9

   Admin interface demo: managing churches, events, services, and participants

   John tours the system admin login and shows how it drills into individual churches and events. Admins can view participants, toggle services on/off per event, and generate operational reports used both before the event and for pastoral follow-up after.

10. 10

    Operational reporting deep dive: food pantry, vision center, oil-change logistics

    The system produces specialized reports tailored to different service stations. Food pantry/lunch reports help order supplies; vision center reports capture participant details; waiver flows reduce liability; and oil-change reports combine check-in tracking with parts planning based on vehicle info.

11. 11

    Participant registration flow: mobile-friendly forms, VIN lookup, waiver + signature

    The participant journey starts with scanning a QR code, opening a mobile form, selecting services, and completing required fields. For oil changes, the app performs a lookup and then collects a waiver acknowledgement and a captured signature—ending with a completed registration.

12. 12

    Adding features after launch: volunteer tracking + name-tag generation

    John explains how new needs emerge once the core system exists—like printing volunteer name tags on label sheets instead of using sticky notes and markers. The change requires extending the schema (new volunteer table/model) and adding new admin flows, which Replit Agent implements in large chunks.

13. 13

    Managing AI “rabbit trails”: prompting, checkpoints, and stopping the agent

    John describes the practical reality of agentic building: sometimes the AI goes off-track, so he intervenes with simple commands (“wait,” “stop”) and redirects. A key technique is reverting to a previously working point in history (a checkpoint mindset) and reapplying known-good code.

14. 14

    From development to production: deployment friction, PDFs, email attachments, secrets

    The hardest problems appear during production deployment: behaviors that work in development may fail in production. John recounts debugging email delivery with attached passport PDFs (solved by changing PDF format) and ongoing issues with environment variables/secret keys (OpenAI key caching) affecting VIN lookup in production.

15. 15

    No prior coding background: why “no preconceived notions” can be an advantage

    John clarifies he hasn’t coded traditionally (no TypeScript), aside from some logic scripting in CAD contexts. The group observes that not being opinionated about stack choices can help: John accepts the agent’s defaults and focuses on outcomes, while more experienced engineers may overconstrain the solution.

16. 16

    Cost, timeline, and real-world impact: a complex system built fast

    John reports surprisingly low costs—hundreds of dollars total, with early rapid progress in the first two days—and contrasts it with estimates of months of traditional development. Church leaders are impressed, eager to use it, and the system promises to reduce admin burden while enabling better follow-up ministry.

17. 17

    Lightning round: product feedback for Claude/Replit and advice on embracing AI

    John’s “asks” include smoother production deployments, better secrets management, and clearer UX for finding Claude chat history. He closes with practical optimism: AI can be scary, but used correctly it helps people and expands what volunteers can build—echoing how learning AutoCAD extended his career and enjoyment.