TBGF COMMUNITY CONNECT  ·  THURSDAY, JUNE 11

Five ways to use AI to codify your operational intelligence

Capture how your business actually runs. Turn it into documented process you can hand off.

1
2
3
4
5

The problem

Your business runs from memory

The how lives in your team's heads

Pricing rules, job sequencing, client quirks. Undocumented.

You are the answer machine

Same questions. Same explanations. Every week.

Knowledge leaves with people

One resignation can take a whole process with it.

Training means repeating yourself

Every new hire restarts the clock.

The fix

1Capture it once.
2Put it on paper.
3Hand it off.

AI does the heavy lifting. You do the review.

The structure

One meeting. Five assets.

Tonight I take one 30-minute ops meeting and turn it into:

1

Written SOP

From the recording

2

How-to video

Built in Claude Design

3

Process map

Clickable, with branches

4

Field checklist

From docs you have

5

Pre-call brief

Before every call

The rule all night:  every output is a draft. A human reviews it before it goes live.

What you already have

The raw material you already have

One team meeting

The recording and the transcript. Tactiq, Gemini notes, Zoom. Any source works.

One screen recording

Someone doing the task once, narrating as they go. Loom or any recorder.

The job folder

Quotes, scope docs, site notes, photos. Already sitting in your drive.

Tonight's demo client is sanitized.  Your version of these files is sitting in your drive right now.
1

Play 1 of 5

Turn meetings and recordings into written SOPs

You explained it again. That explanation just became documentation.

DEMO CLIP 01  ·  90 SECONDS

Play 1 · The recipe

The recipe: recording in, SOP out

InputMeeting transcript or screen recording
ToolClaude. Or Whale steps-from-video for recordings.
OutputAn SOP in your template, ready for review
Review15 minutes with the process owner. Then publish.
The prompt

Turn this transcript into an SOP.

Layout: Purpose, Trigger, Inputs, Steps, Quality checks, Tools, Owner.

Start every step with a verb. Flag any step you inferred.

2

Play 2 of 5

Turn the SOP into a how-to video

The SOP becomes the script. Claude Design builds the video.

DEMO CLIP 02  ·  WATCH THE FINISHED VIDEO

Play 2 · The recipe

The recipe: SOP in, training video out

InputThe SOP from Play 1. It is already the script.
ToolClaude Design. Describe the video, review the draft, request edits in plain language.
OutputA how-to video for onboarding and training, exported and dropped into your playbook.
ReviewWatch it once. Fix the wording. Publish it where new hires will find it.
The payoff:  new hires watch the video. You stop repeating yourself.
3

Play 3 of 5

Turn the transcript into a clickable process map

Steps. Decision branches. Handoffs by role. Click any step for the detail.

LIVE  ·  CLICK THROUGH THE MAP

Play 3 · The recipe

The recipe: transcript in, map out

The prompt

Build a clickable process map from this transcript.

Show decision points as branches. Mark every handoff between roles.

Let me click a step to expand the detail.

InputThe same meeting transcript from Play 1
ToolClaude artifact first. Lucidchart for the working version.
OutputClickable map: steps, branches, handoffs by role
ReviewWalk it with the owner. Fix the branches they argue with.
4

Play 4 of 5

Generate field-ready checklists

From the documents you already have to the dashboard of the truck.

LIVE BUILD  ·  BACKUP CLIP READY

Play 4 · The recipe

The recipe: job docs in, checklist out

The prompt

Build a one-page field checklist for [job type] from these documents. Order steps by sequence on site. Verb first. End with a quality check.

InputJob docs plus the transcript. Nothing new to write.
OutputOne page. On a phone or printed in the truck.
ReviewA field lead runs it on one job. Then it is standard.
Sample output

Re-roof, Day 1: Field Checklist

Confirm scope against the signed quote
Photo the site before tear-off
Verify fall protection on every worker
Stage materials in install sequence
Final walk: photos, debris check, sign-off
5

Play 5 of 5

Get a clean brief before every client call

Five minutes before the call: what was discussed, what is owed, what to raise.

THE REAL THING  ·  THIS WEEK'S BRIEF

Play 5 · The recipe

The recipe: your tools in, a brief out

Input:  past transcripts, email, calendar. Claude connects to the tools you already use.
1

What was discussed

The last conversation, summarized in plain language. No replaying recordings.

2

Action items by owner

Who owes what. Your open commitments flagged first, so nothing surprises you.

3

What to raise today

Open loops, risks, and the one decision this call should produce.

The habit:  runs five minutes before every client call. Walk in sharper than the client expects.

The guardrails

Make it safe to ship

Draft, not gospel

Every AI output gets a human review before it ships. No exceptions.

Verify with the doer

The person who does the work confirms the steps. They catch what AI invents.

Name an owner

Every published asset has a name on upkeep. Unowned docs rot.

One hub

One source of truth. Not five folders and a group chat.

The commitment

Start this week

1Pick one process that lives in someone's head
2Record the meeting or the screen. You were meeting anyway.
3Run Play 1: transcript in, SOP out
4Review for 15 minutes. Publish it.

The math

One process a week is a full playbook by fall.

One hour. Once a week. That is the whole commitment.

Your turn

Share one way you are already using AI in your business.

Then questions. Bring the hard ones.

1
2
3
4
5