A low-stakes place to grab a starter prompt from this program and run it in your own AI. Copy one, paste it into Claude, Gemini, or NotebookLM, and see what comes back. Each one lives in full (with steps and checks) inside its module.
Live · voice
Practice out loud with the Voice Simulator
Copying prompts is one way to practice. Speaking is another. Rehearse a hard conversation by voice with an AI partner, then get a debrief.
Build a Clean, Line-Item Estimate Worksheet (You Keep Every Number)
Best in Claude
You are the GC on a roughly $3.0M ground-up medical office building, lump sum, prime contract directly with the Owner. You self-perform concrete (about $420K) and rough carpentry, and you sub out MEP, site work, and finishes. Bid day is close and your takeoff is scattered across notebooks, a spreadsheet, and three sub bids that just landed. You want AI to turn the mess into a clean, organized estimate worksheet so nothing falls through the cracks. AI is the new apprentice that sets up the columns and carries your quantities into the right rows. It never sets a price, a unit cost, a total, or invents a quantity. Every number stays yours, and you sign the bid.
I am the GC putting together a line-item estimate worksheet for a [PROJECT TYPE] bid worth about [CONTRACT VALUE]. I self-perform [SELF-PERFORM SCOPE] and I am rolling up my own takeoff plus [NUMBER OF SUB BIDS] sub bids.
Before we touch any numbers, help me draw a clean line between two things:
1. What MUST stay mine as the estimator: every quantity, every unit cost, every total, the fee, the markup, which scope each sub covers, and the signature on the bid.
2. Where you can help: structuring the worksheet, carrying the quantities I give you into the right rows, keeping categories consistent, and flagging anything that looks missing or double-counted.
List what falls on each side of that line. Then ask me where my own estimating judgment is most essential on this job so we both know where you stop and I take over.
Draft the Scope-Clarification Letter You Send Before You Commit a Price
Best in Claude
You are the GC bidding a roughly $3.0M ground-up medical office building, lump sum, prime contract with the Owner. You self-perform concrete (about $420K) and sub out MEP, site work, and finishes. The plans and spec have soft spots that could blow your margin: the soils report hints at rock or unsuitable material at the footings, two divisions disagree on who furnishes a piece of equipment, and the spec references a detail that is not on the drawings. Before you commit a number, you send a scope-clarification letter to the Owner and Architect that states your inclusions, exclusions, and assumptions in writing. AI is the apprentice that helps you hunt the ambiguities and draft clean, professional language. It never sets a price and it never makes a binding commitment. You find the risk, you make the calls, and you sign the letter.
I am the GC bidding a [PROJECT TYPE] worth about [CONTRACT VALUE], lump sum. Before I commit a price, I am sending a scope-clarification letter to [WHO IT GOES TO] that states my inclusions, exclusions, and assumptions and asks for answers on the ambiguous parts.
Before we draft anything, help me draw a clean line between two things:
1. What MUST stay mine: deciding what is in or out of my scope, what assumptions I am willing to bid on, what I refuse to carry without an answer, anything about price or money, and the signature on the letter.
2. Where you can help: reading the plans and spec for conflicts and gaps, organizing my inclusions and exclusions, drafting clear and professional language, and making sure the tone stays firm but collaborative.
List what falls on each side. Then ask me where my own construction judgment is most essential on this bid so you know where you stop and I take over. Remember: you help me clarify words and questions, you never set or imply a price.
Respond to an RFP With a Cited Compliance Matrix and an Honest Proposal Outline
Best in NotebookLM
You are the GC on a roughly $3.0M ground-up medical office building, a single-story lump-sum job direct with the Owner. The Owner just put out a long RFP (or a solicitation packet) and the response is due in days. Somewhere in 60 pages of instructions, scope, specs, and forms are the requirements that decide whether your proposal even gets read: insurance limits, bonding, prequalification, a specific submittal format, mandatory forms, a hard deadline, maybe set-aside or local-hire language. Miss one and you are non-responsive. You want AI to read the whole document, pull EVERY requirement into a compliance matrix you can prove line by line, surface the ambiguities as RFI questions before the deadline, and draft an honest proposal outline in your voice. AI claims nothing you cannot back up.
I am the GC preparing a response to an RFP for a roughly $3.0M ground-up medical office building, lump-sum, direct with the Owner. The response is due soon.
Before we touch the document, help me split this work into two columns:
1. What MUST stay my professional judgment: which capability or past-project I claim, every number (price, bonding capacity, insurance limit, schedule duration), what scope I commit to, what is a real qualification versus a stretch, and the signature on the proposal.
2. Where you (AI) can guide: reading the full RFP, organizing requirements into a matrix, drafting structure, checking my draft against the instructions, surfacing ambiguities as questions.
Push back on anything I am tempted to hand you that should stay mine. Then ask me to name, in my own words, the parts of this RFP response where my expertise and my proof are non-negotiable.
Draft a Change-Order Narrative for a Hidden Condition
Best in Claude
You are the GC on a roughly $3.0M ground-up medical office building, lump-sum prime contract with the Owner. You self-perform concrete and rough carpentry. While excavating for footings, your crew hits unsuitable soils and rock that nobody planned for. This is a hidden condition worth about $85K to deal with, and you need to get a change order moving before it eats your schedule. AI is going to help you write the NARRATIVE only (what was there, what changed, what caused it, what it impacts) so the Owner's Rep cannot wave it off. The price stays yours, prepared separately, and it never goes in the AI draft.
I am the GC on a roughly $3.0M ground-up commercial project and I need to draft a change-order NARRATIVE for a hidden condition we hit at the footings. I am NOT asking you to price it. I price it myself, separately.
Before we do anything, help me draw a clean line. Make two lists:
1. What only I, the contractor, can own here: [FOR EXAMPLE: the dollar amount, the scope I commit to, which contract clause applies, what I am willing to sign].
2. Where you, as my apprentice, can actually help: structuring the narrative, drafting language from facts I give you, checking the story holds together, organizing impacts.
Then ask me: where on this job is my own field judgment most essential, and where am I tempted to let you guess? Do not draft anything yet.
Turn Messy Walkthrough Notes into a Clean Punch List
Best in Claude
You are the GC on a roughly $3.0M ground-up medical office building, lump-sum prime contract with the Owner. You are near closeout, walking the building with the Owner's Rep and the Architect. You scribble notes fast: door 112 sticks, paint scuff in the corridor by radiology, missing cover plate in exam 4, HVAC grille loose over the nurse station, caulk gap at the sill in the lobby. Now you have two pages of messy field notes that need to become a clean punch list, grouped by area and by trade, that you can actually track to closeout. AI structures the raw observations. You confirm every item is real and assign it to the right trade, because the wrong assignment sends the wrong sub and burns a day.
I am the GC on a roughly $3.0M medical office building, near closeout. I have two pages of messy walkthrough notes and I need a clean punch list grouped by area and by trade. I will NOT have you decide what counts as a defect or which trade owns an item. I decide that.
Before we start, help me draw the line. Make two lists:
1. What only I can own: [FOR EXAMPLE: whether an item is a real defect, which trade is responsible, whether the fix meets my quality standard, what is ready to sign off at closeout].
2. Where you, as my apprentice, can help: reading my shorthand, grouping items by area and trade, formatting a trackable list, spotting duplicates, asking when a note is unclear.
Then ask me: where on this list am I most likely to let you guess at a trade assignment I should be making myself? Do not structure anything yet.
Turn Jobsite Intake Into a One-Page, AI-Assisted SOP
Best in Claude
You are the GC standing up a new project: a roughly $3.0M ground-up, single-story medical office building, lump-sum prime contract directly with the Owner (a private developer). Right now your project intake lives in your head and in three other people's phones. Last job, the mobilization went sideways because nobody confirmed the soils report, the right permits, or who owned submittals before crews showed up. You want to turn new-project intake into a documented, repeatable workflow (a one-page SOP) that a PM or even a first-year apprentice could run the same way every time, with a human checkpoint before every money, safety, or commitment step.
I am a general contractor and I want to turn a recurring job into a documented, repeatable workflow (a one-page SOP). The job is: [THE RECURRING JOB, e.g. standing up intake for a new project].
Before we draft anything, help me draw a clear line down the middle of this work.
On one side, list the parts of this workflow that must stay with a human (me or my PM) because they involve money, a scope or schedule commitment, a safety call, a written commitment of the company, or a relationship with the Owner, a sub, or an inspector. On the other side, list the parts where AI can genuinely help: structuring the steps, drafting checklists and templates, catching missing steps, organizing what already exists.
Do not write the SOP yet. First show me that split as two columns, then ask me where you think my own field judgment is most essential so I can confirm or correct you.
Write a Tight Subcontractor Scope of Work and Audit It for Dispute Bait
Best in Claude
You are the GC on a roughly $3.0M ground-up, single-story medical office building, lump-sum prime contract directly with the Owner. You are about to issue a subcontract for the electrical work to Sub A. The number looks fine. The danger is in the scope. A loose scope of work is where change-order fights are born: the gaps over what was included, what was excluded, what was furnished by others, and who owned the gray areas turn into money arguments six months in. You want to write a tight scope of work (included, excluded, furnished-by-others, plus site, schedule, and quality expectations) and then have AI hunt it for "dispute bait," the gaps that cause change-order fights later, framed as questions you still need to answer.
I am a general contractor about to write a subcontractor scope of work for [WHICH SUB, e.g. the electrical sub, Sub A] on a commercial project. Before we draft anything, help me draw a line.
On one side, list what must stay with me because it is a commitment, a dollar, a risk allocation, or a judgment call: what I decide is included vs excluded, who furnishes what, how I allocate risk on the gray handoffs between trades, and my signature on the subcontract.
On the other side, list where AI can genuinely help: structuring the scope into included / excluded / furnished-by-others, drafting clean and consistent language, and later auditing my draft for gaps and ambiguity.
Do not write the scope yet. Show me that split as two columns, then ask me where my own field judgment about this trade is most essential, so I can confirm or correct you.
Turn a Transcript Into a Repeatable SOP for the Company Brain
Best in NotebookLM
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.
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.
Run a Project Post-Mortem and File the Lesson in the Company Brain
Best in NotebookLM
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.
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.
Prep for a Live Negotiation Before You Sit at the Table
Best in Claude
You are the GC on a roughly $3.0M ground-up medical office building, lump-sum (stipulated-sum) prime contract with the Owner, self-performing concrete and rough carpentry. A negotiation is coming and you are going to prep for it here, then rehearse it live in the Module 7 Deal & Negotiation Simulator. Pick which one you are prepping. SCENARIO A: the UPFRONT BID & AWARD, where you lock the roughly $3.0M lump sum and the terms with the Owner or the Owner's Rep before signing. SCENARIO B: the CHANGE-ORDER negotiation, where you get the roughly $85K unsuitable-soils change recognized and paid by the Owner's Rep mid-project. AI is your prep partner: it structures the prep, maps the other side, and drafts your scripts. Your number, your walk-away, the relationship, and the signature stay yours.
I am the GC on a roughly $3.0M ground-up commercial project and I am prepping for a live negotiation. I am going to rehearse it afterward in a simulator. The negotiation I am prepping is [SCENARIO].
Before we do anything, help me draw a clean line. Make two lists:
1. What only I, the contractor, can own here: [FOR EXAMPLE: my anchor and target number, my walk-away, which terms I will and will not accept, how hard I push given the relationship, and my signature].
2. Where you, as my apprentice, can actually help: structuring the prep, mapping the other side and their likely tactics, drafting scripts I can say out loud, pressure-testing my plan.
Then ask me: on THIS negotiation, where is my own judgment most essential, and where am I tempted to let you decide a number or a concession for me? Do not build a plan yet.