The PEAK Team Workshop
Your team, using AI on their real work.
A half-day, on-site working session for teams in Gwinnett County and metro Atlanta. People bring the work they already do, and leave using AI on it.
The 30-minute audit is free and separate. The workshop is the paid half-day. Either is a fine place to start.
The day
Four parts, one working day.
-
Leadership kickoff
About forty-five minutes with the owner and managers. What the business pays for in busywork, what the workshop will and will not touch, and the ground rules for the day.
-
Hands-on sessions, by department
Office, coordinators, bookkeeping, whoever does the work. People use AI on their actual tasks: the report someone rebuilds every Monday, the inbox nobody clears, the copy-and-paste between three tools.
-
The handoff list
Every session ends the same way: each person names the one task they would hand to AI tomorrow. Written down, in plain language, by the people who do the work.
-
The opportunity map
The day closes with the owner. Everything the sessions surfaced, ranked by cost and time, walked through live with your questions answered. You keep the map. It is never just emailed.
What your team keeps
Yours from the first day.
A library written for your business
Prompts and instructions for your actual tasks, in plain files your team owns. No accounts to rent, nothing to buy back.
Materials in plain files
Workshop notes, walkthroughs and SOPs stay on your systems, where your people can find them next week and next year.
The habit itself
People who have already used AI on their own work, not watched a demo. Adoption starts in the room, not after it.
What you get as the owner
The audit, delivered as a side effect.
The free audit finds this in thirty minutes. The workshop finds more of it, because your team surfaced it while working.
An opportunity map, walked through live
Everything worth automating in your business, surfaced by your own team during the sessions, ranked by cost and time.
Adoption signals
Who on the team is curious, who needs help, and what people will actually use. You cannot get that from a report.
A next step, not an obligation
If something on the map is worth building, we can talk about it. If nothing is, you had a working day and you keep the map.
Where the workshop fits
Each step stands on its own.
PEAK Team Workshop
Half a day. Your whole team working with AI on real tasks, and your opportunity map.
The build
One to two weeks of engineering, proven on your files before you commit. Only if you want it.
You can stop here without a build.
Practical details
Plain facts.
Questions
Answered.
How is the workshop different from the free audit?
The audit is thirty minutes with the owner, free: which processes cost the most and what automating them would look like. The workshop is a half day with the whole team, at a fixed fee: everyone works on their real tasks, and the audit's findings come out of the sessions as your team works. One is a conversation; the other is a working day.
What if nobody on the team has used AI?
That is the normal starting point. The workshop assumes no experience. People learn on their own tasks, at their own pace, and leave with prompts and instructions written for your business.
Is our business data kept private?
Yes. Sessions can run so that your data stays out of public AI training, and anything sensitive can stay in systems you control. What we work on, we agree on first.
Does this obligate us to a build?
No. The workshop is complete on its own. If the opportunity map points to something worth building, you can ask for a proposal. The workshop and any build are separate decisions.
Who should attend?
The people who do the work, plus an owner or manager who can make decisions. Departments can split across sessions so phones keep getting answered.
Next step
Bring the day to your office.
Write with your team size and the work that eats the week. We will agree the date, the fee and the focus before anything is booked.