Start with a free hour
Before anything else, there is an hour that costs nothing and stands on its own.
What it covers. What this actually is. What the choices are between the tools. What an agent is, in plain language. And whether you are even allowed to use it at work.
Nothing to prepare, no account needed. Bring the question you have not asked anybody.
Next sessions. Thursday September 10 and Tuesday September 15, both at noon Pacific. One hour, online. After that it runs the second Thursday of every month.
Teaching only. Come to the hour and stop there if that is all you need.
You already use it. You build it again from nothing every time.
Get to the output you want. Then keep the thing that got you there.
Six weeks, one hour a week, online. Ten people.
Nine hours on your own work, and six in the room with me. The nine is where the result comes from. The hour with me sets it up.
Every session ends with three things to do. Run it on work already on your desk. Fix the instruction rather than the output. Send me the three pieces before we next meet. Sized to be finished in a week alongside a real job.
We work on your accounts, with work already on your desk, while you are at the keyboard. Week one you save an instruction and watch it run again on a second case.
Thirteen fundamentals you will use on work we never discussed.
A number at the start and a number at the end.
Six weeks because that is where people finish.
Every session runs the same shape. Sixty minutes.
10
minutes on last week
15
learning the fundamental
25
building it on your own work
10
setting the next rep
The last ten minutes is where the three things get named, and you write them down in your own words. They arrive in an email the same day.
Your screen, your accounts, nothing to install. Any tool: ChatGPT, Copilot, Gemini, Claude.
The teaching is recorded, so a missed week is recoverable. The building is not, because that is when your own material is open. Miss one and you get that week's teaching recording plus an office-hour block to catch the build up. There are two of those blocks across the six weeks.
Written feedback on what you send comes back inside three business days.
What you walk out with, week by week
| Week | What you walk out with |
|---|---|
| 1 | Accounts set up, one task running, a measured starting point |
| 2 | Three saved instructions for what you ask most often |
| 3 | Writing that comes back send-ready, and the instruction behind it |
| 4 | Mail, calendar, files and CRM connected. A standard for what stays with a person |
| 5 | One finished piece you would put in front of someone |
| 6 | Your own instruction set: everything you saved, what each one does, and when to run it. Plus a handoff someone else could run |
Every piece you build leaves with the instruction that produced it. Each week runs on the week before it. Week 2 takes the instruction you saved in week 1 and splits it into steps. Week 4 grounds what week 3 improved in your real sources. Week 6 is everything from weeks 1 through 5, checked and running.
Once a move has a name you can call it on work the sessions never covered, on whichever tool you use next year. The vocabulary is the most durable thing here, ahead of the finished pieces and ahead of the measurement.
Before you ask.
- Interview me.
- Show three.
- Break it down.
Making it better.
- Set the bar.
- Argue against it.
- Around the table.
When it is big.
- Make it a table.
- Same columns.
- Only from this.
Doing it again.
- Write it once.
- Stop and check.
Trusting it.
- Found or figured.
- Back to the source.
Two land each week, three in week three.
The measurement
Two workflows measured in week one and measured again in week six: how often, how long, who else touches them, and how many rounds of revision before it is accepted. You finish holding your own number.
A one-page record at the end: where you started, where you ended, and the dates and hours behind it.
Week one is the one session to protect. That is where the starting point gets measured, and without it there is no before and after. If you cannot make it, tell me and we will either take the measurement in a twenty minute session before week two or move you to the next cohort.
It fits you if
You write the same kinds of documents over and over: proposals, client reporting, coverage comparisons, board packs.
Your report takes two weeks and hardly any of it is writing. The time goes on pulling and cleaning the data.
You know the material cold and have to make it legible to people who do not, on a calendar you do not control.
You can change your own workflows, and you are about to start deciding what a team may hand to an AI tool.
It does not fit you if
Your week is field work and appointments, and your recurring documents are estimates and invoices.
You want it done for you. That is a different conversation.
You want the six hours and not the nine. The nine hours on your own work is where the result comes from.
Questions people ask
Why six weeks?
Six weeks because that is where people finish. It started at four. Connectors, critique loops and one finished piece pushed it to six, and I asked whether six was one too many. The answer that stuck came from someone who read the outline before any of it was built.
“Big potential comes with big commitments.”
How much work is it between sessions?
Nine hours across the six weeks, about ninety minutes a week. Fifteen hours in all with the sessions.
It is three things after every session: run the instruction on work already on your desk, fix the instruction rather than the output, and send me the three pieces. Not exercises. If a job turns out to be the wrong one for it, swap it and tell me why.
What if I miss a week?
You get that week's teaching recording, plus an office-hour block to catch the build up. The building is not recorded, because that is when other people's own material is open on screen. Week one is the exception and the measurement section says why.
Which tool do I need?
Whichever one you already pay for. ChatGPT, Copilot, Gemini, Claude. Your screen, your accounts, nothing to install.
Do I have to show anyone my numbers?
No. The measurement always happens and the disclosure is always yours. You hold your own record at the end, and there is a version that confirms you finished without showing how you scored.
Everyone in the room is from a different business. Is that a problem?
It is deliberate. Watching how someone in another business solved the same problem you have is one of the more useful things in the six weeks.
What happens in the group, and what happens privately?
Screen sharing is granted by me, one person at a time, so nobody sees anybody else's work unless they choose to show it. What you send for feedback comes to me and goes nowhere else. If your material cannot be open on a shared call at all, the one to one is the right format and we should talk about that instead.
Can I learn this on YouTube?
You can learn the moves. You will not build the habit, and nobody there reads your draft and tells you why it came back generic, inside three business days.
What happens after week six?
You hold your Record of Completion and your one-page measurement. And at week six we talk about what comes next.
Why is it priced where it is?
It is priced to fill the first cohorts while the case studies get built. It goes up after three complete.
Nothing you work on enters a system I control
The program runs on real business material, some of it confidential. It stays with you. Screens stay private until you choose to share one, and what you send for feedback is the output and the instruction behind it.
The discipline taught in week six, applied to Kizata first.
Accessibility
Sessions accommodate screen readers. The teaching recording is captioned. Materials come in accessible formats.
If you need something arranged differently, tell me before we start and we will arrange it. If a full session recording is what you need, we will do a one to one session instead, which is a better accommodation and it keeps everyone else's material private.
Kirk Tramble
Founder and Principal, Kizata LLC.
Thirty years operating, at Chevron, Oracle and Nitro. UC Berkeley, B.S. Electrical Engineering and Computer Sciences. MBA from Dartmouth's Tuck School.
Eight years teaching business and computer science across Cañada College and College of San Mateo, in the San Mateo County Community College District, where he authored four of the five courses in Cañada's Cloud Computing Certificate of Achievement.
Board President, then board-appointed Interim Executive Director, of the Cal Alumni Association at UC Berkeley, serving more than 500,000 alumni. Director of the Foundation for California Community Colleges.
He designed the curriculum and he has run the operation.
Take a seat in cohort 1
Six Tuesdays from September 22, noon Pacific. September 22 and 29, October 6, 13, 20 and 27.
600 for the six weeks. Expensable, or by invoice with a W-9.
Booking closes Friday September 18.
The first two sessions decide it. Cohort one runs six sessions. If after the first two this is not what you came for, tell me before session three starts and I refund the seat in full. Everything you built in those two weeks is yours to keep.
If the cohort does not run, you choose: a full refund, or your seat in the next cohort.
If I have to cancel a session, it moves inside the same week or the cohort runs a week longer. No charge either way.
Ten seats. Anyone past ten starts with the next cohort.
Rather ask first? Fifteen minutes with Kirk