There is a task you dread every week. The spreadsheet you rebuild by hand. The tool you have always wished existed but assumed you would need to be a programmer to make. You don't.
Lunch and Build, the LAB, is where non-technical people build real, working software with Claude. Every Thursday I build something from scratch on camera while members watch, ask questions, and steer it.
A smaller group is using it to build the thing they needed. An invoice tracker that matches how they actually invoice. A tool that reads their inbox at tax time and pulls out every receipt. A website for the side business, with a pricing calculator that gets the margins right.
None of those people learned to code first. They learned how to run the work. They know how to describe what they want, how to tell when the answer is wrong, and how to keep a project somewhere it will survive past the end of a chat window. That is a skill you can watch someone do and then copy, which is exactly what the LAB is for.
You stay the boss. Claude does the engineering.
Thursdays at 12:30 ET, one hour. Most weeks that means opening an empty folder and finishing with something that runs. You watch the false starts and the fixes, which is the part no tutorial ever shows you. Come with a question and ask it while it is happening.
Every session is recorded and dropped into the classroom, so the catalogue gets bigger every week whether you make it live or not. Start at the beginning if you have never seen code before, or jump to the build that looks like your problem.
Post what you are building, show the error you are stuck on, get unstuck the same day. Members bring their own projects and the answers get reused, so the community is where the week between sessions actually happens.
When you want hands-on help, book one-on-one time and we work on your project together. I watch you work, guide the design, and troubleshoot the real thing you are trying to ship. Members only, and kept deliberately scarce.
Not slides. Not a demo of somebody else's finished app. These are the real sessions, and several of them shipped a kit members can re-skin for their own work.
The first one. Built on camera to prove the format holds up: a real thing finished inside the hour, with the recording going straight into the library afterwards.
Paste in one post, get it rewritten for X, LinkedIn, email, YouTube and short form. Built live as a small app that runs on your own machine, with the Claude call kept server-side so your key never sits in a browser. Packaged as a download members can point at their own writing.
A member hit the wall on a project that lived entirely inside a chat window, so the session became a rescue. We spent the hour moving the whole thing onto a real machine, where the work sits in files you own. The line members kept repeating back afterwards: the chat window is not where your work should live.
A community news and events publication, built live for Trinidad and Tobago. The interesting half was the events importer, which reads calendars off real pages because clean feeds barely exist in the wild. The live run pulled 24 real events onto the page.
A workflow that reads a Gmail account and pulls out the receipts and invoices you need at tax time. Also the session where we learned that a half-connected email account fails silently, which looks exactly like broken code and is not.
Version two of the news site, with a hard rule set mid-session: nothing invented. Five researchers ran in parallel to find real current stories, every article cites its sources inline, and the test suite fetched all thirteen source links against the live internet before anything shipped.
A signup card that appears when a reader is about to leave or has read far enough to care, then sits quietly in the corner instead of nagging. Collects names properly so the list is usable in a CRM, and exports to a spreadsheet. This is the session that turned a good-looking site into one that grows an audience.
I built the site for my own leathercraft business on camera, including a pricing calculator for commissions and workshop batches. The moment worth the hour: a pricing mistake that costs makers real money, where a 40 percent margin means dividing by 0.60 rather than multiplying by 1.40. The second version undercharges every single job.
Or $290 for the year, which is two months back. Cancel anytime.
Runs on Skool. You'll see the community, the classroom and this Thursday's session as soon as you're in.
No, and the sessions assume you haven't. What you need is the ability to describe what you want clearly and to say when the result is wrong, which you already do at work every day.
Every session is recorded and posted to the classroom, so the library is the main asset and the live hour is the bonus. Watch the replay when it suits you and bring your questions to the community instead.
Real, small, useful software. Look at the session list above for the honest answer. Members suggest what gets built next, so if your problem is common enough it becomes a session.
An hour on Thursday if you come live, plus whatever you spend on your own project. Members who get the most out of it touch their build once or twice between sessions and post when they get stuck.
Yes. Private build sessions are open to members, where we work on your project together for an hour. They are capped on purpose so they stay available to the people who need them.
No. The LAB is its own thing, for building software with Claude. If you're here for leadership work, the private coaching and the Executive Leadership Experience pages are what you want.