Most contractors finish a sales call, open a blank estimate template, and start typing from memory. It takes hours. It misses things. And it builds a budget based on what you remembered instead of what the client actually said. There's a better way — and it starts with the recording you're already making.

Andrew Nuhfer of AKN Interiors built a workflow he calls the "budget factory": sales recordings get transcribed, run through Claude, and turned into a structured starting budget based on the client's own words. Manual data entry drops to near zero. The estimate reflects the actual conversation, not a reconstruction of it. This issue walks through the exact workflow — transcription, prompt structure, output format, and how to get it into your project management system. Watch episode →

Andrew Nuhfer runs a 15-person interior construction team at AKN Interiors. Like most builders, his team was spending significant time after every sales call manually entering project scope, material preferences, and client expectations into Job Tread.

The information existed. It was in the recording. Nobody was using it.

Nuhfer built a simple workflow: transcribe the sales call, paste the transcript into Claude with a structured prompt, and let the AI extract scope, materials, timeline, and client priorities into a formatted starting budget. That budget drops directly into Job Tread.

The manual data entry didn't get faster. It mostly disappeared.

Here's the exact sequence from sales call to starting budget.

Step 1 — Record and transcribe the call (5 minutes setup, automatic after).

Use a tool like Otter.ai, Fireflies, or your existing video call platform to record and auto-transcribe every sales call. Most tools do this with one toggle. If you're already recording, you already have the raw material.

Step 2 — Paste the transcript into Claude with this prompt structure.

Open Claude and use this framework:

"I'm a [trade] contractor. Below is a transcript from a sales call with a prospective client. Extract the following and format it as a structured project brief: scope of work, specific materials or finishes mentioned, timeline expectations, budget signals, and any concerns or priorities the client raised. Flag anything that needs clarification before estimating."

Paste the transcript below the prompt. Claude returns a clean, organized brief in under a minute.

Step 3 — Review and flag before estimating.

Read the output before building the estimate. Claude will surface things you glossed over during the call — a specific finish the client mentioned once, a timeline constraint buried in small talk, a concern they raised and then moved past. These are the items that become change orders if you miss them now.

Step 4 — Use the brief to build your starting estimate.

Take the structured brief into Job Tread, BuilderTrend, or your estimating tool of choice. You're not starting from a blank template. You're starting from a documented scope that reflects the actual conversation. Line items get added faster. Scope gaps show up earlier.

Step 5 — Store the transcript and brief in your project notebook.

Drop both the original transcript and the Claude-generated brief into a NotebookLM notebook or Claude Project for that client. When a scope dispute comes up later — and it will — you have the client's own words as the reference point, not your notes.

1. The transcript is the raw material. Start treating it like one. Most contractors record sales calls for liability protection and never open the file again. That recording contains the client's actual priorities, their exact language around budget, their timeline expectations, and the concerns they raised. It's the most accurate project brief you'll ever have — and it's already sitting in your cloud storage.

2. Let Claude flag what you missed. The prompt structure above asks Claude to flag anything that needs clarification before estimating. Pay attention to that list. It consistently surfaces the items that generate the most expensive change orders — a finish that was mentioned but not priced, a timeline constraint that conflicts with your schedule, a scope assumption the client made that you didn't catch in the moment.

3. Build the prompt once. Use it every time. Save your Claude prompt as a template — in a Claude Project, a NotebookLM notebook, or a simple text file. Every sales call runs through the same structure. Every starting budget comes out in the same format. Your estimating process gets faster every week because the input is consistent.

4. The brief becomes your scope of work. The Claude-generated project brief isn't just an estimating starting point. It's a pre-scope document you can send back to the client before the estimate is finalized: "Here's what I heard on our call. Does this reflect the project you have in mind?" One email. Scope aligned before a number is attached to it.

5. Run it on past calls first. Before building this into your live workflow, run three or four past sales call transcripts through Claude and compare the output to the estimates you actually built. You'll see what you captured, what you missed, and what the client said that never made it into the scope. That gap is your change order history.

Beyond the Bid Circle is a peer community for builders scaling with systems and AI—the same builders who've escaped the 60-hour grind. Swap war stories, shortcuts, and real strategies with people who get it.