You've sat through forty demos. You bought the seats. Everyone nods in the all-hands. And on Wednesday morning nothing in the company is actually different.
Talk in, talk out.
The fix is one real job. Your team picks it, we write the worker's job description together, and you leave with the prompt that builds it. Once your team has seen that happen with their own files, they can't unsee it.
What happens in the hour
- 1Minutes 0 to 10Pick the jobYou brought one. We check it against the four-question test below, name the worker, and agree on what a good output looks like. Your team talks, I type.
- 2Minutes 10 to 35Write the job description, togetherWhat good looks like. What it reads. The rules it follows. The last three versions your team did by hand, as its examples. Your team talks, I type. This is the part most people skip, and it's the whole reason their AI hands them to-do lists.
- 3Minutes 35 to 50Get the promptI write the kickoff prompt for your job, live. It makes the AI interview your team before it builds anything, then build the worker from the answers. You leave with it word for word, in your inbox, before the call ends.
- 4Minutes 50 to 60First run, or the plan for itIf someone has Claude or ChatGPT open, we paste the prompt and start the first run in the room. If not, you'll have the exact steps for that afternoon. No installs, no jargon. Then I'll tell you what the next eleven look like, and you decide.
What you walk out with
- One job, chosen and named, that passes the four-question test below.
- The worker's job description: what good looks like, what it reads, the rules it follows, written down so anyone on the team can run it or improve it.
- The kickoff prompt, written for your job, in your inbox before the call ends. Paste it into the AI your team already pays for and the build starts.
- The first run started in the room if your tool's open. Otherwise, the exact steps to start it that afternoon.
- A leadership team that watched it happen and knows how little magic there is.
- The recording, so the people who couldn't make it can see exactly what happened.
What to bring
One job
Something your team did by hand at least three times last month. The weekly report nobody wants to write. The first-draft proposal. The inbox triage. The follow-ups that never happen.
The last three versions
The three most recent times a human did the job. Those become the worker's examples of what good looks like.
Your team
Two to five people, including whoever would actually run the worker day to day. The CEO alone is the one setup that doesn't work.
The AI your team already pays for, open on one laptop
Claude, ChatGPT, Copilot, or Gemini. Whatever your team already has seats on, logged in before we start. No installs, no setup. If nobody has one yet, that's fine too: we'll still write the job description and the prompt, and I'll tell you which tool to get.
Does your job pass? Four questions.
- 1.Your team did it by hand at least three times last month.
- 2.It has inputs you can point at: emails, a spreadsheet, last month's version.
- 3.It has one output a human reads: a doc, a list, a reply.
- 4.Someone checks it before it goes out.
Four yeses and it’s a worker. Name it, give it a job description, show it the last three you did by hand, run it once, fix the ugly part, run it again. Sixty minutes is generous.
Passes
- “Monday pipeline recap”
- “First-draft proposal”
- “Inbox sorter”
- “Weekly client status email”
- “Meeting-notes to action items”
- “Job-post first draft”
Doesn’t pass
- “Help us with marketing”
- “Make us more efficient”
- “Do AI”
That’s talking about AI. A worker has a job.
Who it’s for
- CEOs, founders, and owners of companies with roughly ten to two hundred people.
- Leadership teams who've bought the AI seats and aren't getting real work out of them yet.
- Any industry. The job is the unit, not the vertical.
- Teams who'd rather watch one thing get built than sit through another overview.
Who it isn’t for
- Anyone who wants a demo on my data. The hour only works on yours.
- Anyone looking for an AI strategy deck. You'll leave with one worker's job description and the prompt that builds it. No roadmap.
- Engineering teams who already ship agents. You don't need me for this.
Your Facilitator
Greg Rosner · PitchKitchen
Author of StoryCraft for Disruptors, creator of the Magnetic Messaging Framework, and the facilitator of the AI Workforce Clinic for Business Owners. He isn’t an engineer. He runs a working AI workforce of eight that scouts signals, writes, runs outreach, watches his systems, and hands him a morning brief, and he built every one of them by starting with a task.
Steve Jobs couldn’t code and couldn’t design. He hired the people who could and told them what to build. That’s the seat you sit in now. The hour shows your team how to sit in it.
Questions CEOs ask before booking
Why is it free?
I'm testing a format: can a CEO and a few non-technical leaders leave one hour with their first AI worker's job description, the prompt that builds it, and enough confidence to run it that afternoon? I think yes. I'm doing five companies a month to find out, and I'll ask your permission to share what got built (nothing confidential, just the shape of it).
Will we actually have a worker running at minute 60?
Sometimes. If someone on your team has Claude or ChatGPT open and is comfortable pasting a prompt, we'll start the first run in the room. More often you leave with the job description and the prompt and run it that afternoon. I'd rather promise the prompt and surprise you with the run than the other way around. The worker itself usually takes a few more conversations to get right. That's normal, and it's what the Clinic is for.
Is this a demo?
No. We work on your job, your files, your words. If the job you brought can't become a worker, I'll say so at minute five and we'll pick a better one.
We've never installed anything. We don't know what an MCP is.
Good. You don't need to. The hour happens in the plain chat your team already uses. No installs, no plugins, no jargon. The technical doors (Claude Code, Codex, MCP) come later, in the Clinic, once the first worker has earned its keep.
Which AI do we need?
Whatever your team already pays for. Claude, ChatGPT, Copilot, or Gemini all work for the first worker. Claude Code and Codex are where my own workforce lives, and if you have either, we'll use it.
What happens after the hour?
You run the prompt, the worker takes shape over the next few conversations, and you correct it like a new hire. If your team wants the other eleven shifts, that's the AI Workforce Clinic: a weekly, live, hands-on cohort where owners build their AI workforce in front of each other. First Clinic is free, and I'll tell you about it at minute 58, not minute one.
How many people can join?
Two to five is the sweet spot. Bring whoever would actually run the worker. A CEO alone doesn't get the full effect because the person who'd use it isn't in the room.