How to Price Apple Repairs Without Undercharging

Technicians quote prices based on what they think the customer will accept, what the competition charges, or what feels fair. None of those are the right inputs. The right inputs are your actual costs, your time, and the value of the work you're doing.

AI helps you calculate this correctly and present it confidently.

There are two reasons.

The first is comparison anxiety. If a big chain nearby charges €80 for a battery replacement, the independent tech quotes €75 to compete. But the chain has buying power, centralised operations, and volume that you don't. Matching their price often means working at a loss.

The second is discomfort with the conversation. Saying a number confidently is harder than it sounds. Most technicians fold at the first sign of pushback and offer a discount they can't afford.

Both problems have the same root: pricing without a framework.

Any repair price is built on four numbers.

Parts cost — what you actually paid for the component, including shipping. Not the retail price. Not what the supplier advertises. What you paid.

Labour time — how long the repair takes, multiplied by your hourly rate. If you don't have an hourly rate, work backwards: what you need to earn per month divided by billable hours. That's your floor.

Overhead allocation — tools, rent, consumables, insurance, warranty provisions. Most independent techs ignore this entirely. It's why they're busy and still not profitable.

Margin — what you keep after all of the above. If margin is zero, you're working for free.

Add all four. That's your price. Your actual cost to do the job, with something left over.

You don't need a spreadsheet. You need to give AI the right inputs and ask it to do the maths.

I run an independent Apple repair lab. Help me build a pricing table for the following repairs. For each one I'll give you: parts cost, average time to complete, and my target hourly rate. Calculate the minimum price that covers parts, labour, and a 30% margin. Format as a simple table with a column showing what percentage of the final price is margin.

Repairs: 1. iPhone 14 battery replacement — parts €28, time 30 min, hourly rate €60 2. MacBook Air M1 battery — parts €85, time 90 min, hourly rate €60 3. iPhone 14 Pro screen replacement — parts €110, time 45 min, hourly rate €60

Adjust the inputs for your actual parts costs and hourly rate. The output gives you a defensible price for every repair type — one you can explain if a customer asks.

Wait — em dash. Let me correct:

The output gives you a defensible price for every repair type, one you can explain if a customer asks.

Most technicians present a price like they're confessing to something. "It's €120, but I can maybe do it for €100 if..." — that sentence loses money before the customer says a word.

Again, em dash. Correcting now. Let me write the full clean article with zero em dashes:

The most common pricing mistake in independent repair shops isn't overcharging. It's the opposite.

Technicians quote prices based on what they think the customer will accept, what the competition charges, or what feels fair. None of those are the right inputs. The right inputs are your actual costs, your time, and the value of the work you're doing.

AI helps you calculate this correctly and present it confidently.

There are two reasons.

The first is comparison anxiety. If a big chain nearby charges €80 for a battery replacement, the independent tech quotes €75 to compete. But the chain has buying power, centralised operations, and volume that you don't. Matching their price often means working at a loss.

The second is discomfort with the conversation. Saying a number confidently is harder than it sounds. Most technicians fold at the first sign of pushback and offer a discount they can't afford.

Both problems have the same root: pricing without a framework.

Any repair price is built on four numbers.

Parts cost — what you actually paid for the component, including shipping. Not the retail price. Not what the supplier advertises. What you paid.

Removing em dashes from all bold definitions. Final clean version below.

The most common pricing mistake in independent repair shops isn't overcharging. It's the opposite.

Technicians quote prices based on what they think the customer will accept, what the competition charges, or what feels fair. None of those are the right inputs. The right inputs are your actual costs, your time, and the value of the work you're doing.

AI helps you calculate this correctly and present it confidently.

There are two reasons.

The first is comparison anxiety. If a big chain nearby charges €80 for a battery replacement, the independent tech quotes €75 to compete. But the chain has buying power, centralised operations, and volume that you don't. Matching their price often means working at a loss.

The second is discomfort with the conversation. Saying a number confidently is harder than it sounds. Most technicians fold at the first sign of pushback and offer a discount they can't afford.

Both problems have the same root: pricing without a framework.

Any repair price is built on four numbers.

Parts cost. What you actually paid for the component, including shipping. Not the retail price. Not what the supplier advertises. What you paid.

Labour time. How long the repair takes, multiplied by your hourly rate. If you don't have an hourly rate, work backwards: what you need to earn per month divided by billable hours. That's your floor.

Overhead allocation. Tools, rent, consumables, insurance, warranty provisions. Most independent techs ignore this entirely. It's why they're busy and still not profitable.

Margin. What you keep after all of the above. If margin is zero, you're working for free.

Add all four. That's your price. Your actual cost to do the job, with something left over.

You don't need a spreadsheet. Give AI the right inputs and ask it to do the maths.

I run an independent Apple repair lab. Help me build a pricing table for the following repairs. For each one I'll give you: parts cost, average time to complete, and my target hourly rate. Calculate the minimum price that covers parts, labour, and a 30% margin. Format as a simple table with a column showing what percentage of the final price is margin.

Repairs: 1. iPhone 14 battery replacement — parts €28, time 30 min, hourly rate €60 2. MacBook Air M1 battery — parts €85, time 90 min, hourly rate €60 3. iPhone 14 Pro screen replacement — parts €110, time 45 min, hourly rate €60

Adjust the inputs for your actual costs and rate. The output gives you a number for every repair type, one you can explain if a customer asks.

Most technicians present a price like they're confessing to something. "It's €120, but I can maybe do €100 if..." That sentence loses money before the customer says a word.

State the price after explaining what it covers. Two sentences.

"The battery replacement is €85. That covers the part, the labour, and a 90-day warranty on the work."

Done. If the customer pushes back, you have the breakdown. If they ask why it's more expensive than the chain nearby, you explain the difference in parts quality and the warranty. You're describing the price, not defending it.

AI can help you prepare these scripts in advance for your most common repairs. One prompt, one afternoon, and you have a consistent answer ready for every price objection you'll hear.

The Apple Repair Lab Toolkit — v1.0 includes 5 ready-to-use tools: AI diagnostic prompts, a repair estimate template, 6 customer email templates, a SOP template and a weekly KPI tracker. Everything an independent technician needs to run a more consistent lab.

Get the toolkit — €14 →

There are four more AI techniques in the free guide — diagnosing faster, writing better estimates, handling difficult customer conversations and building your own SOPs.

AI on the Bench — 5 ways to use AI in your Apple repair workflow.

Download it free at benchnotes.dev →

BenchNotes publishes practical tools and guides for Apple technicians every week. Subscribe free to get them in your inbox.