I spent a morning with the Knowledge Perk Coffee Company team running a Lovable and AI training session. Ryan Sanderson invested the time. His team showed up ready to build. A few hours later, they had real tools solving real problems. That was the whole thing.

Knowledge Perk is a thriving, local coffee shop (and my personal favorite in Rock Hill, full disclosure). Owner, Ryan Sanderson, wanted to add some tools to his team's tool belt, specifically around sales and operations. They knew AI could help but weren't 100% sure how to get started.

Most teams I talk to are in the same spot. They know AI is a real edge for a company their size. They've heard about vibe coding. They've seen what's possible. But they don't know where to start.
The morning wasn't about theory and me explaining. It was about building. We mapped the current landscape of tools, talked through what's changed in the last year, and then got specific about where the real gaps were inside the business. Sales insights. Franchise build-out schedules. Actual problems with actual impact.
I was just a guide. Twenty years of industry experience layered on top of what I've learned this past year working with AI across SDH and our client work. Nothing more complicated than that.

One of my favorite moments of the morning had nothing to do with a screen.
We took a walk around town. No laptops. No templates. Just voice memos and conversation. Everyone spoke their idea out loud into their phone, the way you'd tell a friend about something you're excited about. No pressure to structure it. No pressure to sound smart. Just talk.
Then we came back, ran the transcripts through Claude and Gemini, and asked them to turn the voice memos into proper PRDs. Problem, user, solution, scope, acceptance criteria. Clean and actionable. That became the brief we handed to Lovable.
The whole thing took about an hour from walk to working prompt. Way faster than staring at a blank doc waiting for the right words to come. And the ideas were better for coming out of a conversation instead of a cursor blinking on a page.
Get away from the screen. Talk it through. Let AI do the structuring once you've got the raw material.
In one morning, the team:
It was awesome seeing real things getting built in real time. Not theoretical. Not "maybe someday." Actual tools the team could keep using the next day.
Teaching and learning alongside a small, excited, passionate team is one of the most fulfilling parts of the job. Knowledge Perk is the kind of team that's going to keep building long after the morning ended. Can't wait to check in and see what they've put together.
If your team is stuck at the same speedbump, we've built a framework for this exact kind of work. And if your team could use a little collaboration on this front, give us a shout. Happy to help.
=====
Big thanks to Ryan Sanderson and the entire Knowledge Perk Coffee Company team for the hospitality, the excellent Latte, and the energy.