AI that actually gets used in your business.
Trevor Davis’s field notes on practical AI: picking the right job, giving it your context, and getting your team to use it after the workshop ends.
For Entrepreneurs and their teams, online or in person: coaches and consultants, clinics and service businesses, real estate developers, course creators, and the programs that run workshops.
Field notes on practical AI. Free, plain, no hype.
No spam. Unsubscribe anytime.
Running a team or a program? Ask about a workshop
Five steps. What worked tells you the next job.
“We’re using AI.” Just not getting much from it.
The problem is rarely the tool. It’s a step that got skipped.
Scattered tools
A chatbot here, a notetaker there, a subscription nobody remembers buying.
Fixed at 1 · PickGeneric output
It writes like everyone else, so people rewrite every draft or stop asking.
Fixed at 2 · GroundLives in another tab
It works when someone remembers to open it. Most days nobody does.
Fixed at 3 · BuildNobody trusts it
One wrong reply went out. Now it isn’t allowed near anything that matters.
Fixed at 4 · CheckNothing sticks after the workshop
A good afternoon, lots of ideas. Two weeks later, everyone’s back to the old way.
Fixed at 5 · Teach
What it looks like when it actually gets used.
Not AI everything. One job, grounded in how you already work, with a person checking what matters.
- 1 · Pick the job
- Session recaps and follow-ups after every call.
- 2 · Ground it
- Your frameworks, past recaps and the call notes, so it sounds like you and names their next step.
- 4 · Check it
- You read every recap before it goes to a client.
- What changes
- Every client leaves with a recap in your words, and the notes stop piling up.
Illustrative examples, not client stories. Steps 3 and 5 (set it up where you work, teach the team) apply to every one.
Five steps. Then round again.
Judgement before automation. Context, not tools. Most AI projects stall at the step nobody planned for.
- 1 · Pick
One job worth handing to AI.
Not “AI everything”. The task that eats your week: the enquiry replies, the session notes, the Friday report.
- 2 · Ground
Give it your context.
Your voice, your past work, your rules. Generic in, generic out.
- 3 · Build
Set it up where you already work.
Your tools, not another app. If it lives in a new tab, it gets forgotten by Thursday.
- 4 · Check
A person approves what matters.
Automate what’s easy to undo. Check what isn’t.
- 5 · Teach
Your team uses it without you.
A short guide, a practice session, one owner.
- 6 · Round again
Back to Pick: what worked tells you the next job.
Most AI projects stall at the step nobody planned for.
One step at a time, in your inbox.
The field notes go deeper on each step, with real setups you can copy and the mistakes worth skipping.
Field notes on practical AI. Free, plain, no hype.
No spam. Unsubscribe anytime.
Three AI tools, two paid subscriptions, one workshop. Six weeks later, nobody’s using any of it.
A made-up composite, not a client. The pattern is common enough that you might recognize it.
- 5 Hasn’t tried it
- 7 Tried it once
- 0 Uses it weekly
- 0 Uses it daily
Illustrative team of 12. Not real data.
- Stalled at Ground: No context
The tools wrote like a brochure. People rewrote every draft, then stopped asking.
- Stalled at Check: No check step
One wrong reply went to a client. After that, nobody trusted it with anything that mattered.
- Stalled at Teach: No owner
The workshop was good. Then everyone went back to their week and nobody owned the follow-up.
Generic in, generic out.
Same task, same tool. The only thing that changes is how much it knows about you. Add a layer and watch the reply change.
Made-up example. [BRACKETS] are placeholders.
- VoiceHow you actually write
- Past workWhat you’ve done before
- RulesWhat you never do
- ExamplesReplies you were proud of
Where’s your AI stuck?
Five yes/no questions. The first “no” shows you the step to fix next.
Hands-on, on your real work.
For teams, schools and programs. One session per step of the loop, built around the tasks your people already do.
Sample sessions
- SESSION 01
Pick the job
Map a normal week and choose the one task worth handing to AI.
- Format
- [FORMAT]
- Length
- [LENGTH]
- Price
- [PRICE]
- You leave with
- One job, written down, with an owner.
- SESSION 02
Build your context pack
Voice, past work, rules and examples on one page. The gap between generic drafts and useful ones.
- Format
- [FORMAT]
- Length
- [LENGTH]
- Price
- [PRICE]
- You leave with
- A first context pack your team can edit.
- SESSION 03
Set it up where you work
Put it inside the tools you already use, with a check step on anything hard to undo.
- Format
- [FORMAT]
- Length
- [LENGTH]
- Price
- [PRICE]
- You leave with
- One working setup, tried on real tasks.
- SESSION 04
Make it stick
A short guide, a practice session and one owner, so it still gets used next month.
- Format
- [FORMAT]
- Length
- [LENGTH]
- Price
- [PRICE]
- You leave with
- A one-page guide and a named owner.
Want one of these for your team or program? Ask about a workshop
“Judgement before automation. Context, not tools.”
Trevor Davis writes the field notes and runs the workshops. They’re what he’s actually setting up with Entrepreneurs and their teams, written plainly. More about Trevor
Start with the field notes.
Practical AI for Entrepreneurs and their teams. What to pick, how to ground it, and how to make it stick.
Field notes on practical AI. Free, plain, no hype.
No spam. Unsubscribe anytime.
Running a team or a program? Ask about a workshop