Your Techs Should Know Exactly What Jobs Cost — All of It

Nobody at Lonestar made a deliberate decision to hide the numbers from field guys. The owner knew the margin, the techs knew the scope, and information stayed in those lanes because that's how it had always worked. Forty trucks, commercial work, project-based everything. Margin was above my pay grade for seven years. I knew the scope, the schedule, what to pull from the warehouse. What the job cost and what we charged were someone else's problem.

I carried that into Reeves Electric in early 2022. Five-truck residential shop. Completely different animal. And my techs were doing exactly what I'd been trained to do — treating the numbers as someone else's problem.

That showed up fast in the call recordings. Month two, my NPS was a 4. Some of that was intake, some was scheduling. But one thing I almost missed: techs improvising in the field because they didn't know what we charged or why. Making it up in real time. Customers can feel that even when they can't name it.

What Actually Breaks When Techs Don't Know the Numbers

A tech gets to a panel assessment. Customer asks what something like this is going to run. If he doesn't know the flat-rate number, he has two moves: he lowballs to avoid the awkward moment, or he goes quiet and calls the office.

Both are bad. The lowball creates a price expectation you'll spend the rest of the job unwinding. The office call signals uncertainty at the exact moment the customer is deciding whether to trust you.

I started a weekly four-call review with my dispatcher — two that booked, two that didn't. We tag what went right and what didn't. What I kept hearing on the lost jobs: a moment where the tech hedged on price. Not because he was dishonest. Because he wasn't sure if the number was right and didn't want to own a mistake.

That's a wiring problem, not a people problem. The tech cannot execute on a number he doesn't have.

The missed-upsell version is quieter and more expensive. A tech who doesn't know the line-item price on an AFCI upgrade is going to skip it. His internal math is: I don't know what we charge, I don't know if I should quote it, and if I get it wrong I look bad. So he says nothing. Customer goes without the upgrade. Three months later they find out from another shop that the work was needed. That review doesn't say "the tech didn't know the pricing." It says "they seemed to overlook something important."

I saw that pattern across multiple jobs in 2023 before we rebuilt the process. Same hesitation, different job types, different techs. That's when I knew it wasn't about any one person.

Your Markup Isn't the Secret You Think It Is

The objection I always hear: "If my tech knows the markup, he'll go start his own shop — or he'll tell customers we're gouging them."

Second one first. At Reeves Electric, a service call has real overhead behind it — two techs on the truck some days, vehicle costs, liability insurance, Jobber, CallRail, QuickBooks Online, NiceJob, the bookkeeper, the CSR, the branded van payment. The margin left over after all of that is not large. I did $1.4M in 2024. We are not sitting on 40-point margins per job. When a journeyman actually sees what's in the number, the reaction is usually closer to "huh, okay" than outrage. The tech who undermines pricing in the driveway is almost always the one who thinks the price is arbitrary because nobody ever explained what it's covering.

The "he'll go start his own company" fear — same logic applies here as with comp transparency. If your only protection against a tech going independent is that he doesn't understand your margins, that's not a business model. That's a retention problem you haven't named yet.

The shops that are genuinely hard to leave are transparent about the numbers and make sure the comp reflects the value the tech is generating. Secrecy on either one is a tax on retention.

---

The tech who can't explain the price will either dodge the question or undercut it. Neither one is the tech's fault.

---

How to Roll This Out Without Handing Over a Spreadsheet and Walking Away

This is a sequence. Not a data dump.

A trusted journeyman should eventually see all three layers — flat-rate price, cost basis, what overhead actually looks like month to month. But you go in that order, with context at each step. Day one, the flat-rate price. A few weeks in, the cost basis so the parts-and-labor math makes sense. Later, once you've had the overhead conversation, the margin picture. The goal at each stage is that they understand it, not just that they've seen it.

Format matters. A tech in the field shouldn't be memorizing numbers. In Jobber, the flat-rate book lives in the system and surfaces on a tablet during the call. Tech opens the line item, sees the price, selects it. The number comes from the system, not from memory. That removes the hesitation. He's not guessing. He's reading.

What stays out of the field: your vendor cost sheets, your overhead model, your net margin by truck. That's a meeting conversation with context attached. Not something that sits open in the Jobber catalog at 2pm on a job site.

The Monday Morning Sequence for a Five-Truck Shop

Week one: At your next tech meeting, pull up the flat-rate book. Don't share the whole thing. Pick three line items — something common, something that comes up on upgrades, something your techs hesitate on. Walk through how each one is built: parts cost, labor time, one sentence on overhead. Take questions. Write down what they ask. The questions show you exactly where the gaps are.

Weeks two through four: Add three more line items per week. Four weeks gets you through the core catalog. If a tech pushes back on a number, good. That means he's thinking about it instead of just nodding.

Month two: Start the overhead conversation. A one-pager with five line items — trucks, insurance, software, admin, advertising. Not a full P&L. Enough that the flat-rate number has a reason behind it. The reason isn't "the owner wanted a boat."

Ongoing: The call recordings are your feedback loop. I pull two calls per week where price came up — Thursday afternoons with my dispatcher. Listen for hesitation. Listen for a tech going off the flat-rate number. Coach against the recording, not against memory. "I heard you say 'it'll probably be around four-fifty' on the job Thursday" is a coachable moment. "I feel like you're sometimes not confident with pricing" is just a complaint.

Small weekly meeting. Same time every week. Three line items. This is how habits change — not in a big Monday reveal, but in repetition until the behavior is normal.

Do the first meeting this week. Three line items, twenty minutes, take questions.

---

FAQ

My tech found out what we charge versus what he makes and got angry — isn't that proof that transparency backfires?

It's proof that the conversation happened late and out of sequence. If a tech finds out the gap by accident rather than through a deliberate walk through what the overhead actually is, of course it lands wrong. Show what it costs to run the truck he drives before the margin number ever comes up. Once someone understands what the gap is paying for, the anger usually goes somewhere more productive. If it doesn't, that's a retention conversation worth having directly.

How do I handle a tech who starts quoting customers informally in the driveway based on what he knows the flat-rate price is?

Clarify the role explicitly: the flat-rate book is a field tool for presenting approved quotes through the system, not a license to improvise at the truck. If he's free-handing numbers outside Jobber, check whether the tool is easy enough that he'd actually choose it over mental math. If the system is clunky enough that he's working around it, fix the system first. Then pull the recording and coach the specific behavior.

What's the difference between showing techs the flat-rate price and showing them the cost and margin breakdown — do they need both?

Eventually, yes. But in sequence. Flat-rate price first — it gives them what they need to do the job without hesitating. Cost and margin come later, after the overhead conversation. Without that context, a tech who sees a $480 outlet call and a $60 net margin is going to do math that looks like you're taking him. With it, he understands that's what keeps the trucks running and the raises coming. Don't skip the overhead conversation. It's what makes the margin number make sense.

Should apprentices have the same access as journeymen?

No. A first-year apprentice should know the flat-rate price on the work they're touching — enough to answer a basic customer question without panicking. The overhead and margin conversation doesn't land until you've run enough jobs to understand what goes into one. Give apprentices the line items relevant to their current scope and expand from there as they progress.

We use Jobber — can I surface pricing in the field without giving every tech full backend access?

Yes. Jobber has role-based permissions. Techs on the mobile app can see jobs, line items, and prices without getting into account settings, client financials, or reporting. Set them to the field technician role. Go through the admin panel permissions before the rollout and verify exactly what's visible at that level. Takes about fifteen minutes and it's worth doing before the first meeting, not after.

How do I roll this out if I trust one tech completely and I'm not sure about the other two yet?

Start with the journeyman you trust. Run the first two weeks with him — the three-item meetings, the overhead conversation. Let him become the reference point. When the other techs see a peer engaging with the pricing system confidently and without drama, they have something to calibrate against. Don't announce a tiered rollout. Just sequence it practically. By the time you bring the other two in, the process has been tested once and you'll have a clearer read on whether your uncertainty about them is real or just unfamiliarity.