Copied to clipboard!
Module 11 For Construction advanced 60 min

Build Your Company's Second Brain

The next level: transcribe everything, so the company gets smarter and nothing lives in anyone's head.

What you'll be able to do

  • See the upsell: move from AI on one task to a company that captures everything
  • Start transcribing the three domains: client projects, sales calls, and workflows
  • Turn transcripts into SOPs and post-mortems in one shared system, so nothing lives in one head

The next level: nothing lives in anyone's head

Everything before this taught you to use AI on the task in front of you. This is the level above it, and it is where the real leverage is: a company that captures everything. Your best estimator knows why a bid wins. Your lead super knows how the last change order got paid. Your top closer knows what lands on a sales call. Today that knowledge lives in their heads and walks out the door when they do. A second brain captures it, so the company keeps getting smarter even as people come and go. Most contractors never build this. That is exactly why it is an edge.

The loop: capture, document, share, pull

  • Capture. Transcribe what already happens: the owner meeting, the jobsite walkthrough, the sales call, the how-we-bid discussion. The transcript is the raw material you used to lose.
  • Document. AI turns those transcripts into SOPs and post-mortems, the repeatable work written down once.
  • Share. It all lives in one system the whole company can reach, not scattered across heads, notebooks, and inboxes.
  • Pull. Before the next estimate or sales call, you pull the relevant SOPs and past lessons back in, so each one is sharper than the last.

Start transcribing across the business

Most company knowledge is spoken and then lost. Start recording and transcribing the three places it actually lives: projects with clients (kickoffs, owner meetings, walkthroughs, closeouts), sales calls (what won the work, what objections came up, what you promised), and your workflows (how we bid, how we run intake, how we handle a change). That is the capture layer. Turn evaporating talk into a durable source, and the Turn a Transcript into an SOP exercise takes it from there.

Post-mortems feed the brain

After every job, capture what went right, what went wrong, and what you would do differently, while it is fresh. Filed and tagged into the shared system, each post-mortem becomes institutional knowledge the next bid can pull. The Run a Project Post-Mortem into the Brain exercise makes it a habit, not a someday.

The payoff: better bids and sales

A second brain is not a filing cabinet, it is a competitive edge. When the next estimate pulls in the lesson from the job that went sideways, and the next sales call pulls in what won the last one, your company stops repeating mistakes and starts compounding what works. Keep it where the whole team can query it, a shared NotebookLM, a Claude Project, or a shared drive, and keep names, signed dollars, and PII out, using role labels.

What stays human

  • The decision to file. A person confirms an SOP or a lesson is real before it becomes how you do things.
  • The checkpoints. Every SOP keeps a human gate before any money, safety, or commitment step.
  • The privacy line. Role labels only. No client or sub names, no signed dollars, no PII in the shared brain.

Turn a Transcript Into a Repeatable SOP for the Company Brain

You are the GC on a roughly $3.0M ground-up medical office building, lump-sum prime contract with the Owner. Last week your team handled something well: when the crew hit unsuitable soils at the footings, your project manager ran a clean play, called the right people, documented the condition, and got a change order moving before it ate the schedule. That whole play lives in one person's head right now. You recorded the debrief (or the project-intake meeting where the team walked the process), and you want to turn that transcript into a clean, numbered SOP that anyone on your next job can follow. This is how expertise stops living in one head and starts living in the company. AI builds the SOP only from what is in the transcript, flags every undefined step as an OPEN QUESTION, and you put a human checkpoint before every money, safety, or commitment step. Then it gets filed into the shared system so the company can pull it later.

Recommended tool

notebooklm

NotebookLM is built to stay grounded in sources you upload, so it will not wander off the transcript and invent steps. It also becomes the shared, queryable company brain: you load the transcript and the finished SOP as sources, and anyone on the next job can ask the notebook how you handled this and get an answer with citations back to the actual SOP, not a guess.

Bring to the exercise

  • The transcript of the meeting, jobsite walkthrough, client call, or workflow discussion (PII redacted, role labels only, no party legal names)
  • Your Construction Context Document (project type, contract type, your scope, key role labels)
  • What this SOP is supposed to accomplish in one sentence (the trigger that starts it and the done state that ends it)
  • Which steps in this workflow touch money, safety, or a binding commitment (those get a human checkpoint)
  • Any company standard, contract clause, or code reference the workflow has to honor
  • Where the finished SOP gets filed (the shared system: NotebookLM notebook, shared drive folder, or company wiki) and what to name it
  • A past version of this workflow that went sideways because a step was skipped or undefined

Step 1 of 8

Build Your Approach

Step 1

Build Your Approach

Before any drafting, draw the line between what needs YOUR professional judgment (which steps are load-bearing, where money and safety live, what the company commits to) and where AI can help (transcribing structure, sequencing, drafting numbered language). AI is the new apprentice; you stay the foreman.

What to substitute before pasting

  • [FOR EXAMPLE: ...] Your own list of the calls only you can make. Edit it to match this workflow.
I am the GC on a roughly $3.0M ground-up commercial project. I have a TRANSCRIPT of how my team handled a workflow (the unsuitable-soils condition at the footings), and I want to turn it into a clean, numbered SOP that anyone on my next job can follow. This is for our company brain, so expertise stops living in one person's head.

Before we touch the transcript, help me draw a clean line. Make two lists:

1. What only I, the contractor, can own here: [FOR EXAMPLE: which steps are load-bearing, where money and safety checkpoints belong, what the company is willing to commit to, what gets a human sign-off].
2. Where you, as my apprentice, can actually help: pulling the steps out of the transcript in order, drafting numbered language, spotting steps that are vague, organizing it into a usable SOP.

Then ask me: in this workflow, where is my own field judgment most essential, and where am I tempted to let you fill a gap the transcript never actually covered? Do not build the SOP yet.
What good output looks like
  • Two clear lists that put money checkpoints, safety calls, commitments, and the final sign-off squarely on your side.
  • AI names extracting, sequencing, and drafting from the transcript as its lane, not deciding which steps matter or filling undefined gaps.
  • AI asks you where your field judgment is most essential before it does any work.

Verify before using AI's output

Run a Project Post-Mortem and File the Lesson in the Company Brain

You are the GC on a roughly $3.0M ground-up medical office building, lump-sum prime contract with the Owner. The job is closing out. It went fine overall, but one thing cost real money: while excavating for footings you hit unsuitable soils, the change order for about $85K got slow-walked, and you carried the exposure for weeks before it was resolved. You do not want the next job to repeat that. So you run an honest post-mortem: sort the debrief into What Went Right, What Went Wrong, and What We Would Do Differently, find the root cause behind each item (and mark anything you cannot prove as a HYPOTHESIS, not a fact), then TAG the lesson and file it into the company brain with a PULL THIS WHEN trigger, so the next geotech review or bid walk surfaces it automatically. AI helps you sort, dig for root cause, and organize. It does not assign blame, it does not spin, and it never invents a number or a cause you did not give it. Role labels only, no party legal names.

Recommended tool

notebooklm

NotebookLM stays grounded in the debrief you upload, so it sorts and digs for root cause without drifting into a generic "lessons learned" template. It also becomes the company brain: once the tagged lesson is loaded, your estimator can ask the notebook "what did we learn about geotech on the last medical office job" before the next bid and get this lesson back with a citation, which is exactly the PULL THIS WHEN moment this exercise is built for.

Bring to the exercise

  • Your raw debrief notes or transcript from the close-out conversation (PII redacted, role labels only)
  • Your Construction Context Document (project type, contract type, your scope, key role labels)
  • The hard numbers you are willing to use, kept illustrative and round (for example the unsuitable-soils change was about $85K, retainage about 10 percent)
  • The timeline of the soils issue: when it was found, when the change order went out, when it resolved, what it cost in carry and schedule
  • What actually went right that you want to repeat on purpose, not by luck
  • What you genuinely are not sure about (a cause you suspect but cannot prove) so it can be marked as a HYPOTHESIS
  • Where the finished lesson gets filed (the shared system: NotebookLM notebook, shared drive, or company wiki) and which future bid or sales call should reference it

Step 1 of 8

Build Your Approach

Step 1

Build Your Approach

Before any sorting, draw the line between what needs YOUR judgment (which items are true, what the numbers really were, what the root cause actually is, what you would commit to changing) and where AI can help (sorting, structuring, pushing on root cause, organizing for retrieval). AI is the new apprentice; you stay the foreman.

What to substitute before pasting

  • [FOR EXAMPLE: ...] Your own list of the calls only you can make. Edit it to match this project.
I am the GC on a roughly $3.0M ground-up commercial project that is closing out. I want to run an honest post-mortem so the next job does not repeat our mistakes. The central lesson is an unsuitable-soils condition where the change order (about $85K) got slow-walked and we carried the exposure for weeks.

Before we touch the debrief, help me draw a clean line. Make two lists:

1. What only I, the contractor, can own here: [FOR EXAMPLE: whether an item is true, what the real numbers were, what the actual root cause is versus a guess, what I would actually change next time, what I am willing to put my name on as a company lesson].
2. Where you, as my apprentice, can actually help: sorting the debrief into Right / Wrong / Do Differently, pushing me on root cause, separating proven cause from hypothesis, organizing it so the company can find it later.

Then ask me: where am I most likely to spin this in our favor or duck blame, and where do I need you to keep me honest? Do not sort anything yet.
What good output looks like
  • Two clear lists that put truth, the real numbers, root cause, and the company lesson on your side.
  • AI names sorting, root-cause questioning, and organizing for retrieval as its lane, not judging fault or inventing causes.
  • AI asks you where you are most tempted to spin, before any work starts.

Verify before using AI's output