Each month, three of your people build working Claude workflows for their real jobs. Live, 1:1, and measured in hours saved.
Book an intro callThe licenses are live. Somebody ran a lunch-and-learn. And most of your team still uses Claude like a search box with better manners: paste something in, copy something out, back to the old way of working.
This is normal. It is also expensive.
The gap between what you pay for and what your team does with it doesn't close on its own. The licenses renew either way.
Every month, three people on your team go end to end. I audit their actual workload, we build their workflows together in live sessions with their hands on the keyboard, and we measure the hours that come back. The rest of the company watches it happen at a monthly demo hour, then asks when their month is.
When a workflow needs plumbing you don't have yet (connected data, MCP servers, a shared skills library), my delivery partners build that foundation in parallel. Your people keep building while the ceiling rises.
We walk their real to-do list and pick three workflows worth building.
Live 1:1 sessions. They drive, I direct. Every session ends with something working.
Hours saved per person, per workflow, reported monthly.
Builders show their work to the whole company. The queue fills itself.
45 minutes per person. We pick three workflows from their actual workload and record how long each task takes today.
One hour a week, 1:1. No homework between sessions. The practice is doing their job with what they built.
Hours saved per person against their baseline, with a 30-day follow-up to confirm the builds stuck. Leadership sees the number compound every month.
This month's builds, shown by the people who built them. Everyone sees the program work while three people get the deep work.
The exact number depends on team size and what the audit finds. Scope gets set on the intro call.
Every engagement opens with a kickoff audit: your team scored by hours-back potential, your security pathways mapped, and a build queue you own outright whether or not we continue. The monthly cycle then takes three people per month through scoping, live 1:1 builds, and the measured hours-back report, plus the company demo hour. Cancel anytime after month 3.
Foundation infrastructure (data connections, MCP servers, shared skills libraries) is quoted from your audit's roadmap and runs in parallel. It never blocks your team's builds.
I'm Jenna Potter, founder of prompt as hell. Former Head of Marketing turned marketing engineer: I build AI systems that do real work for marketing teams, and I teach the people who keep them running.
I've built 100+ AI agents and skills for marketers, and I share the builds with 23,000 followers on LinkedIn and 4,300+ newsletter subscribers. I've worked with teams at Notion, Webflow, Descript, Granola, Ahrefs, Profound, ElevenLabs, and Productboard.
Yes, on purpose. Deep 1:1 work is what makes new workflows stick; spreading thin is how AI training fails. The whole company gets the monthly demo hour, and the queue means everyone knows when their month is coming. A 15-person team is fully through in five months.
No slides and no homework. Every session builds a workflow for work that's already on that person's plate, and it works before the call ends. They learn by building the thing they'll use the next morning.
Good. The audit maps your review pathways before anything gets built, and your program champion clears tool access before each person's month starts. If security blocks a workflow mid-month, we swap to that person's next-ranked build instead of stalling.
Most teams don't, and plenty of high-value workflows need none of it. Your first cohorts build those while the foundation work runs in parallel. By month three, people are building on top of it.
For each person, one 45-minute scoping call and three one-hour build sessions in their month. Everything else is them doing their normal job with the workflows they built.
30 minutes on Zoom. We walk through your team, the tools you already pay for, and what would be worth building first. If it's not a fit, I'll tell you.
If the calendar doesn't load, book directly at cal.com/video-jenna/intro-call-with-jenna.
