Workshops · Speaking
We teach people to work with AI on the digital blue-collar labor, to make work life better.
This is where it happens. People working with it for the first time, learning, getting inspired, finding out the shift can be fun. All sides of it welcome, and all the feelings.
shaped to the room
Every room is in a different place.
This technology is new. You keep working with it and figuring things out. Our job is to put everything in its place and make it possible to do something new.
Look at a normal week. An email arrives that a model clearly wrote. A contract gets read in an afternoon, in an account nobody set up. Files that belong on the shared drive never make it there, and the person who needs them can’t find them. None of it is ill-intended, and none of it can be vouched for.
We listen first and build the day from where you are, whether your people are working with AI for the first time or in new ways.
before the day
We start with what you already have.
This is how every engagement begins. Some teams take the day. Others take the whole season, five weeks and beyond, with the same steps in more depth.
Every license and subscription, including the AI that may already be inside them.
The tools your people work in every day, and which of them can work with the AI you choose.
The subscriptions the aligned tools replace, and what that saves.
Then one boundary for the whole team: which tools, what may go into them, and what never does.
Need help with a compliant stack, one set of tools, and a team aligned on cost, compliance and consistency? That’s our consulting, and it’s where most engagements start.

What people walk out with, whatever the room
Your own words, on the screen, before we teach anything.
We do this with your people before the day, so the room opens with itself.
some of what we’ve heard
First, we heard you.
Everyone’s in, at very different levels. All of it in their own words.
“At least half of my time is materials creation for deals I’m on.”
“We pull from four sources: previous deals, the data service, the internet, and what’s in people’s heads.”
“We can’t put sensitive client data into ChatGPT, so I avoid it.”
“We have so much information that we just kind of lose.”
“Investment memos take me about an entire work day. Formatting and pulling content together is honestly about half of that.”
“We don’t have a uniform way we’re implementing it.”
“The systems don’t talk to each other.”
“Anything that puts you in checker mode instead of coach mode is a drainer.”
“I’m really interested in all of this. It just feels too soon.”
We listen with Roux. Before the day, an AI interviewer talks with everyone on your team, by text or voice, asks the follow-ups, and hands us one clear set of what you said. It’s the tool we use for this, and you can see it at helloroux.com.
BUTLER COUNTY, OHIO.
the vocabulary
New things need new words.
A few of the words that come up in every room, said plainly.
The field guide
model
The trained engine underneath the chat window
agent
An AI that takes steps on your behalf
context
What the AI knows about the task at hand
draft
What an AI makes and a person sends
recipe
A working system you can share

what you build
Recipes you take home and tweak.
A recipe is a working system: the rules, the prompt, what it may and may never do. Email is the one everyone needs first, so it’s the one we show. We write them for the work in your room, and you and your AI tune them to your own preferences.
live in the Book
The morning inbox
three tiers, drafts never sent
built in rooms
The daily digest
every client, one page, before the first meeting
built in rooms
The transcript harvest
the meeting’s decisions and asks, pulled while you drive home
built in rooms
Your durable instructions
the one page your AI reads before it starts
built in rooms
Give your AI a soul
an interview that writes your AI’s instructions for you
built in rooms
The weekly report
the numbers you already have, in the format your board reads
built in rooms
The say-back
the listening pass itself, your people’s words in one clear set
built in rooms
The call-request drafter
overnight, every request turned into a draft reply, from a real room
built in rooms
The client update
in your house format, from the notes you already keep
Before
31 unread.
Three asks are buried somewhere in the middle.
The first hour goes to finding them.
After
Three drafts waiting.
Each one with the ask on top.
You read it, change a word, and you press send.
the agreement
Your own usage agreement.
Companies and teams are making decisions about what AI can and cannot do in their systems. Every business and every workplace is different, with different requirements, different risk tolerance, different thresholds. We honor that. It’s why we work with you instead of assuming what you need.
Usage agreement
What we use AI for, and what we never do
Fine
A first draft of an email you will read before sending.
Ask first
Anything with a client’s name, or a person’s health, pay or record.
Never
Passwords, keys, and what a person told you in confidence.
Read and agreed · name
date
The room writes this together, after lunch, before anyone builds. Some teams sign it as an attestation.
half a day, or the whole arc
A morning of listening, say-back and teaching. An afternoon of building on your own work.
1
Saying back what we heard. Your people’s own words from the listening pass, back to the room.
2
Teaching, in your own examples. The tools you have, what happens to the words you type, and where the line sits.
3
First hands-on help. Real work on real screens, starting with email and files, then a few people show the room what changed.
4
Lunch.
5
New ways of working. Together the room decides what AI does for the team and what it doesn’t.
6
The build. Everyone takes one piece of their own work, or a team builds something shared. The afternoon’s building happens inside the line the room just drew.
7
The share-back. What each person built, what they’ll do Monday, and what the room wants next.
Half day
The morning: the say-back, the teaching, and first hands-on help.
Full day
The whole day, through the build and the share-back.
One fixed fee, named up front, travel included. Nonprofits and schools have a nonprofit rate.

COVINGTON, KENTUCKY.
after the day
A few ways on.
A seat at the table.
Weekly time with the people you choose, on their own work. Month to month.
The next training.
Built with you, so your managers can carry it to their teams.
Sessions that fit the work.
A department at a time or the whole organization, on video or another day in the room.
What a team keeps
Every tool and license on one list, aligned.
A boundary the team wrote and holds.
People trained together, each with something built by their own hands.
A rollout plan at a pace people can hold.
Someone on your team who holds the tools when we leave. We build with them from the first week.
three talks, one voice
Technology. Spirituality. Leadership.
Pastor, consultant, product lead, CEO. The boardroom and the break room. The talks bridge the people doing the work and the people overseeing it, because I’ve sat in every one of those rooms.
leadership
The human side of AI.
People who manage people well manage AI well. It works from a role, a boundary and the context you give it, and follows them more accurately than a person would. The talk is the why, not just the how.
boards, companies, conferences
technology
New things require new vocabulary.
The words, said plainly, so you can follow any conversation about AI and ask better questions.
teams, classrooms, panels
spirituality
Who does this create?
Practice over time is formation. Every tool forms the person who uses it. The question to ask before anything ships.
congregations, retreats, universities
Twenty to forty-five minutes. Each leaves a page in your hand.




