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._

John BlackmanguestClaire Vohost

Jun 23, 202540mWatch on YouTube ↗

WHAT IT’S REALLY ABOUT

A 91-year-old builds church event software via Claude and Replit

John Blackman, a 91-year-old church volunteer, describes turning a manual paper-based “impact weekend” registration process into a full web app by using Claude to generate a roadmap, user stories, and requirements, then feeding that into Replit Agents to implement the system.
The app supports multiple churches and events with role-based admin levels, participant registration via QR codes, service toggles, waivers and signature capture, and printable “impact passports” (PDFs) that attendees can bring to the event.
It also generates operational reports (demographics for pastoral follow-up, service usage counts, food pantry/lunch ordering, vision center details) and includes an oil-change workflow that looks up oil/filter specs from a VIN using an API.
They discuss practical realities of agentic coding—fast progress and low cost (hundreds of dollars), but real deployment pain around dev vs production differences, PDF/email attachment issues, and secrets management—plus broader advice about embracing new technology as they did with AutoCAD decades earlier.

IDEAS WORTH REMEMBERING

5 ideas

Start with a clear outline, then force the AI to ask questions.

John began with a Word document describing the workflow and explicitly instructed Claude to ask for missing details (“If you need more information… ask me the questions right away”), which produced more complete requirements and fewer gaps during building.

Using Claude as a product manager accelerates agentic coding success.

Claude generated an MVP roadmap, user stories, and non-functional requirements; those artifacts became the “source of truth” that Replit Agents could reliably implement.

Agentic tools can produce “enterprise-like” patterns from community needs.

The app includes multi-level admins, multi-church data separation, approvals for administrators, and reporting for ministry follow-up—capabilities that mirror multi-tenant SaaS design despite originating from a paper process.

Operational reporting is where the real value lands for events.

Beyond “a form,” the system outputs demographics lists for follow-up ministry, service-usage summaries, oil-change shopping lists, and food/vision center prep reports—reducing manual planning and errors.

The dev-to-prod gap is the biggest vibe-coding reality check.

John repeatedly hit issues where features worked in development but failed in production (PDF email attachments, environment variables/OpenAI key reuse), highlighting deployment, caching, and secrets-management as key pitfalls.

WORDS WORTH SAVING

5 quotes

We started at 10:00 and finished about 3 o'clock in the morning.

— John Blackman

I just took and copied what Claude had put together and put it into Replit… and then it started going bloo-whoop, and there it was.

— John Blackman

Sometimes he goes off on a rabbit trail, and I have to bring him back.

— John Blackman

It always doesn't work in production what works in development, and that was very frustrating.

— John Blackman

It's just like AutoCAD… A lot of my friends didn't want to learn AutoCAD… I was still having fun.

— John Blackman

Impact weekend workflow digitizationClaude-generated PRD, roadmap, user storiesReplit Agents implementation (end-to-end app)Multi-tenant architecture and role-based accessParticipant QR-code mobile registrationPassports (PDF generation) and email deliveryReporting: demographics, service usage, inventory planning (oil/food/vision)Dev vs production bugs, deployment, secrets managementPrompting tactics: stop, reset, “go back in history” checkpointsGrowth mindset and learning parallels (AutoCAD → AI)

High quality AI-generated summary created from speaker-labeled transcript.

Get more out of YouTube videos.

High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.