Billing Clients & The IT Scene

This is a topic that’s kinda sore now, but it keeps coming up. I’m gonna use some images once I get PC or laptop access to illustrate the points, but I do want to get feedback on this.

Something that was noticed - well, a few things - include how clients haggle. While everyone wants a good deal, it’s not always acceptable to haggle.

Persons that see a man on the road, or a single tech, or a small company, seem to trend towards asking for discounts. These same persons walk into KFC, Super Plus, Shoppers Fair and other stores and pay whatever they get on the bill. Many don’t shop around or haggle or ask for discounts, but they’re ready to ask you as an individual or small company for a discount. I should mention that the price also doesn’t matter.

Here’s an example for you. Now me personally, I’m certified in various IT areas, but I’m not Apple certified. I do have tools and I do work on Apple devices, but pricing is always based on USA third party company costs. Usually I’ll even charge half or less than what USA companies would, because it’s hard on people to stick out for what international costing would be.

I did repairs to a 2017 iMac. Told the client what it needed. Sent them the links to get the specific kits I’d rather, since those would or should come with all relevant parts. Did the part replacement. Identified improper work done previously. Corrected issues. Cleaned the system. Reinstalled the OS and did basic data recovery off the old (failing) drive. My cost? About half of what it would cost online. Client didn’t want to pay.

Now the above example was a bit on the higher side for some clients - networking and administration is even more - so let’s do something smaller.

Just so you know, at the time of this post the average cost for diagnostics - no work - just checking - is JMD$2,500. That’s still way less than the usual USD$50 (or more) for checks in most stores in the USA. Diagnostic costs are included in repair costs, or waived and added to repair costs in most cases.

Back when I was charging $1,500 for diagnostics, I handed back the system to the client since they needed it. This was May of 2023. I’ve still not been paid for that. Another owes me for work done which was $3,500 in November of 2022. But you probably see where this is going.

Every little bit adds up. The cost isn’t the issue here - it’s the mindset.

If I spend 5 minutes to fix your problem, it’s because I have the experience in the field to do so. Whether or not I have the certification, I have the experience and expertise to get the job done. I’ve had clients that say they’ve taken their system to 3 or more stores and the issue wasn’t resolved, then when I resolve it they don’t want to pay.

What was the statement again? If I do a job in 30 minutes it’s because I spent 10 years learning how to do it in 30 minutes. You owe me for the years, not the minutes.

What was the other? Oh right! LoL!

We offer 3 kinds of service.

  • Good
  • Fast
  • Cheap

You can pick any 2. Good and cheap won’t be fast. Fast and good won’t be cheap. Cheap and fast won’t be good.

I love statements like that, but there’s another side to the IT sphere coin. The fact that everyone is doing it. Technicians are a dime a dozen. Everyone gets into it because installing Windows is easy. Formatting a system is easy. Looking over the shoulder of an experienced person - asking questions or not - qualifies you to get the job done. Purchasing a tool suddenly makes you an expert.

I try to not be “mean” with the knowledge. I mean, I’ve even posted info about techniques and tools freely online. The issue is - much like YouTube - information is out there. Having the knowledge of HOW to use it is another thing.

Lemme leave it at that and leave the discussion open.

Follow-Up: Billing Clients, Diagnostics and Professional Responsibility

The original post came from a point of frustration.

The points still stand, but there is a more detailed and balanced explanation behind them.

When clients look at a repair bill, they may only see the visible result:

  • a part was replaced;

  • Windows was reinstalled;

  • a cable was changed;

  • a setting was corrected;

  • a technician spent only a few minutes with the system.

What they may not see is everything behind that result:

  • years of accumulated knowledge;

  • the cost of tools and software;

  • diagnosis and testing;

  • research and sourcing;

  • operational expenses;

  • the risk involved in handling the equipment;

  • responsibility for customer data;

  • knowing what not to do;

  • accountability if something goes wrong.

A repair that takes five minutes may only take five minutes because the technician spent years learning how to identify and correct that fault.

Clients often see the final repair. They do not always see the diagnosis, preparation, risk and experience that made the repair possible.


Diagnostics Are Work

A diagnostic fee is not a charge for failing to repair a system.

It is payment for determining:

  • what is wrong;

  • what may have caused it;

  • what repair is required;

  • whether the repair is economical;

  • whether data is at risk;

  • which parts are needed;

  • whether the work should be escalated;

  • what the next course of action should be.

Even if the customer decides not to proceed, the diagnosis still has value.

The customer now has information they did not have before.

A diagnostic fee is payment for identifying the problem and establishing the next course of action.

The assessment may involve:

  • reproducing the fault;

  • disassembling the equipment;

  • testing storage;

  • testing memory;

  • checking power;

  • checking temperatures;

  • researching compatibility;

  • testing with known-good components;

  • inspecting previous repairs;

  • checking whether data can be recovered;

  • determining whether repair is practical.

That is work, even where the final answer is that the equipment is not worth repairing.


Why Every Store May Charge Its Own Diagnostic Fee

If the same computer is taken to five different repair stores, each store may charge its own diagnostic or assessment fee.

At current local rates (2026-07), that may be around JMD $2,500, although it may be higher or lower depending on the store, the equipment and the work required.

A customer may reasonably ask:

“Why should I pay another diagnostic fee when another store already checked it?”

The answer is that each technician or business normally needs to perform its own verification before accepting responsibility for the diagnosis and repair.

By the time the equipment reaches Store D, that store cannot automatically rely on what Stores A, B and C said.

There are several reasons for this:

  • The previous diagnosis may have been incomplete.

  • The system’s condition may have changed.

  • Another fault may have developed.

  • The earlier store may not have provided a written report.

  • The report may have been intended only for internal use.

  • The receiving business may not know or trust the previous technician’s methods.

  • The next technician may be expected to warranty or stand behind the repair.

Even where two technicians know each other and are willing to share notes, the receiving technician still has to confirm the findings.

A previous report may reduce the amount of work required.

It does not completely remove the need for assessment.

Another technician’s report can guide the diagnosis. It does not automatically replace verification.


Verification Still Has a Cost

Suppose Store A provides a full report to Store E.

Store E may only need to:

  • inspect the system;

  • power it on;

  • reproduce the fault;

  • confirm the failed component;

  • verify that the recommended repair is appropriate.

That may seem like a small amount of work.

It is still work.

The business is using:

  • the technician’s time;

  • electricity;

  • workspace;

  • testing equipment;

  • software;

  • administrative time;

  • ticketing and record systems;

  • business insurance;

  • internet access;

  • rent;

  • other operational overheads.

The cost of electricity for one test may be small.

The total cost of operating a repair business is not.

Small costs repeated across many customers become part of the business’s operating expenses.

A diagnostic fee does not only pay for the minutes spent looking at the computer. It contributes to the people, tools and environment required to assess it properly.

Depending on the business, the diagnostic fee may be:

  • charged separately;

  • reduced where a previous report is available;

  • included in the final repair price;

  • deducted from the repair cost if the customer proceeds;

  • retained if the customer declines the repair.

The policy may differ between businesses.

What matters is that the customer is told the terms before leaving the equipment.


Sometimes You Have to Pay to Learn

Customers sometimes visit several stores before finding one that:

  • identifies the actual fault;

  • explains it clearly;

  • has the correct tools;

  • has the necessary experience;

  • is willing to perform the repair;

  • inspires enough confidence to proceed.

Each assessment may provide another piece of information.

Unfortunately, this may mean paying several diagnostic fees before reaching the correct answer or finding someone capable of completing the repair.

In simple terms:

Sometimes you have to pay to learn.

That does not mean every diagnosis is correct.

It also does not mean customers should continue paying indefinitely without asking questions.

Where possible, customers should request:

  • a written diagnosis;

  • the tests performed;

  • the recommended repair;

  • the estimated cost;

  • any identified risks;

  • whether the diagnostic fee will be applied to the final bill.

A written report may help the next technician, even where that technician still performs their own checks.


Diagnosis Also Creates Responsibility

Once a technician accepts another person’s diagnosis without verification, they also accept the risk that the diagnosis may be wrong.

For example:

  • The first store says the power supply has failed.

  • The next technician replaces it without testing.

  • The actual fault is a shorted motherboard.

  • The replacement power supply is damaged.

  • The system still does not work.

The customer may then reasonably ask why the technician installed a part without confirming the cause.

That is why verification matters.

The technician who performs the repair must be satisfied that the diagnosis supports the work being recommended.

A competent technician may use previous findings to save time.

They should not surrender their own judgement.

The customer is not only paying someone to repeat a test.

They are paying the technician to decide whether they are willing to stand behind the diagnosis and the repair.


This Is Not Unique to IT

Independent assessment exists across many professions.

A mechanic may not accept another garage’s diagnosis without checking the vehicle.

Their experience, testing process and interpretation of the symptoms may lead them down a different path.

An electrician may inspect previous work and find that it:

  • does not meet code;

  • uses the wrong materials;

  • lacks proper protection;

  • was acceptable years ago but is no longer compliant;

  • was never completed correctly in the first place.

A mason or builder may question why previous work was completed in a particular way, especially where drainage, reinforcement, materials or structural principles were not properly considered.

Building codes and recommended practices may change over time, but some foundational principles should still have been followed.

The same applies to:

  • plumbing;

  • medicine;

  • accounting;

  • legal work;

  • automotive repair;

  • construction;

  • electronics;

  • many other fields.

A previous report may be useful.

It may save time.

It may help narrow the investigation.

However, the next professional still has to decide whether they agree with it before accepting responsibility for the work.

Independent verification is not unique to IT. It is part of professional accountability.

The person performing the final repair, installation or correction is the one expected to stand behind the result.

That is why another assessment may still be required.

That is also why another assessment fee may still apply.


The Technician Is Also Accepting Risk

When I accept a client’s equipment, I take responsibility for handling it with reasonable care.

My general position is that the equipment should be returned in the same or better condition, except where:

  • authorized repairs require changes;

  • pre-existing damage is documented;

  • deteriorated components fail during necessary work;

  • known risks were explained beforehand.

Professional service includes responsibility.

It does not mean that the technician is automatically responsible for every failure that occurs while the equipment is in their possession.

There must be a distinction between:

  1. damage clearly caused by the technician;

  2. failure caused by an existing condition;

  3. situations where responsibility is uncertain or shared.


When the Technician Clearly Causes the Damage

I once installed a replacement screen for a client.

The screen itself cost more than USD $200.

The full cost also included specialized adhesive designed for that curved screen and bezel, with the adhesive alone costing approximately USD $80.

The screen was installed successfully.

However, I attempted to snap one section into place instead of disassembling it again because doing so would require additional adhesive that I did not have available.

The screen broke.

That was my fault.

I purchased the replacement screen at my own expense.

The client was not responsible for paying for damage caused by my decision.

When my actions clearly cause damage, the cost of correcting that damage belongs to me—not the client.

This is part of professional integrity.

If I short a board because I forgot that it was powered on, that is my responsibility.

If I damage a connector, screen, cable or component through an avoidable mistake, I should correct it.

The customer is paying for professional service.

That includes accountability where the technician is clearly at fault.


When Cleaning Exposes an Existing Failure

Another situation is equipment that arrives working but is heavily contaminated.

The system may contain:

  • caked-on dust;

  • corrosion;

  • rust;

  • moisture-related residue;

  • conductive contamination;

  • weakened traces or connections.

In some cases, dirt and corrosion may be physically holding weakened areas together.

Cleaning the board may disturb an already deteriorated connection and cause the system to stop working.

This is why my disclaimer explains that cleaning a working system may expose existing faults or cause deteriorated components to fail.

The system may have worked immediately before cleaning.

That does not automatically prove that the cleaning created the underlying damage.

Correlation is not causation.

The fact that equipment failed after cleaning establishes a sequence of events.

It does not automatically establish responsibility.

The real question is:

Did the technician create new damage, or did the cleaning expose an existing failure that was already developing?

If the board was already corroded, rusted or held together by years of accumulated contamination, cleaning may reveal the true condition of the equipment.

That is different from electrostatic discharge or careless physical damage.

The technician must still:

  • work carefully;

  • photograph severe contamination where appropriate;

  • explain the risk beforehand;

  • document the original condition;

  • stop if the risk becomes excessive.

However:

Professional integrity means accepting responsibility for what I damage. It does not mean accepting responsibility for every pre-existing weakness that reveals itself while I am working.


Reasonable Care, Not Unlimited Liability

A technician has a duty to exercise reasonable care.

That does not mean guaranteeing that deteriorated equipment will survive every diagnostic or repair process.

Examples of pre-existing weaknesses may include:

  • brittle plastic clips;

  • corroded connectors;

  • failing storage;

  • damaged solder joints;

  • liquid exposure;

  • swollen batteries;

  • cracked hinges;

  • loose ports;

  • aged insulation;

  • previous poor-quality repairs.

A failing drive may become unreadable while being tested.

A brittle clip may break during necessary disassembly.

A corroded connector may separate when unplugged.

A screen already under physical stress may worsen during removal.

The technician should identify foreseeable risks and disclose them where possible.

However, the existence of a failure during repair does not automatically establish negligence.

Responsibility should be based on reasonable control, reasonable knowledge and reasonable precautions—not simply on who was holding the equipment when it failed.


When Responsibility Is Not Clear

Some cases are not straightforward.

Consider a desktop power supply with an incorrect voltage-selector setting.

The client asks the technician to plug in the machine but does not mention that:

  • it came from another country;

  • someone changed the power supply;

  • the voltage selector was adjusted;

  • the system previously smoked or behaved unusually.

The technician may still be expected to perform basic checks.

However, the customer may also have important information that was not disclosed.

Responsibility would depend on questions such as:

  • Was the incorrect setting visible?

  • Was checking the selector standard practice in that situation?

  • Were there warning signs?

  • Did the client provide incomplete or misleading information?

  • Did the technician continue despite an obvious risk?

  • Was the failure caused by an avoidable mistake?

These situations can become a chicken-and-egg problem.

They should be evaluated based on what was reasonably knowable and what precautions were reasonably expected.

If I am clearly responsible, I will deal with it.

If I am not reasonably responsible for the damage, I am not going to pay for something I did not cause.


Documentation Protects Both Sides

Before beginning work, especially on damaged, dirty or fragile equipment, the technician should document the original condition.

This may include:

  • photographs;

  • visible cracks;

  • missing screws;

  • damaged clips;

  • corrosion;

  • liquid exposure;

  • swollen batteries;

  • loose hinges;

  • damaged ports;

  • failing drive health;

  • previous repair attempts;

  • unusual power configurations.

The customer should also be informed where normal inspection, disassembly, cleaning or testing may expose further faults.

A useful disclaimer may state:

The equipment has pre-existing damage, contamination or deterioration. Normal inspection, disassembly, cleaning or testing may expose additional faults or cause weakened parts to fail. Such failures are not automatically considered technician-caused.

This is not an attempt to avoid responsibility.

It establishes the condition of the equipment before work begins and ensures that the customer understands the risk.


Pricing Includes Responsibility

Independent technicians are often compared only by the visible price.

However, professional pricing also reflects:

  • expertise;

  • tools;

  • testing equipment;

  • software;

  • sourcing;

  • research;

  • electricity;

  • transport;

  • workspace;

  • risk;

  • responsibility;

  • warranty;

  • communication;

  • the possibility of absorbing the cost of genuine mistakes.

The replacement-screen example is important here.

The labour charge on a repair may be far lower than the technician’s potential loss if something goes wrong.

The technician is not only being paid to install a part.

They are being paid to:

  • select the correct part;

  • install it safely;

  • protect the rest of the equipment;

  • test the result;

  • take responsibility for their own work.

The customer is not only paying for the repair. They are paying for someone willing to stand behind the work.


Being Understanding Does Not Mean Financing the Repair

Independent technicians often try to accommodate clients.

They may reduce prices, delay payment or release equipment because the client urgently needs it.

That may be done in good faith.

However, understanding a client’s financial situation does not require the technician to finance the repair personally.

A clear service process should include:

  • an explained assessment fee;

  • written approval before repairs;

  • deposits before ordering parts;

  • approval when the scope changes;

  • clear payment terms;

  • payment before equipment is released;

  • documented policies for abandoned equipment.

Assessment identifies the work. Authorization permits the work. Payment completes the transaction.

Without a clear process, the technician may complete the repair, absorb the risk and still be left chasing payment.


Tools and Information Do Not Equal Competence

Technical information is more available than ever.

People can search for error messages, watch repair videos and purchase specialized tools.

That is useful.

It has lowered the barrier to attempting technical work.

It has not removed the knowledge required to do that work responsibly.

Someone may reinstall Windows without checking:

  • drive health;

  • customer data;

  • drivers;

  • activation;

  • hardware stability;

  • the reason the original installation failed.

Someone may purchase a programmer or soldering station without understanding:

  • electrical risk;

  • board design;

  • heat control;

  • firmware;

  • data protection;

  • when to stop.

Access to tools and instructions has lowered the barrier to attempting technical work. It has not lowered the knowledge required to do it safely and professionally.

A professional is not simply someone who produces a working result.

A professional also:

  • explains the scope;

  • protects the client’s data;

  • obtains approval;

  • uses reasonable care;

  • documents limitations;

  • knows when to stop;

  • escalates when necessary;

  • accepts responsibility for genuine mistakes.


Responsibility Exists on Both Sides

Professional service requires accountability from both the technician and the client.

The technician is responsible for:

  • using reasonable care;

  • protecting the equipment;

  • explaining risks;

  • obtaining authorization;

  • documenting the work;

  • being honest about mistakes;

  • correcting damage they clearly caused;

  • knowing when to stop or escalate.

The client is responsible for:

  • disclosing known faults;

  • providing accurate information;

  • maintaining backups;

  • approving the work;

  • understanding documented risks;

  • paying agreed charges;

  • recognizing that failing equipment may deteriorate during necessary testing.

The relationship must be fair in both directions.

The technician must own genuine mistakes. The client must understand that repair cannot reverse every pre-existing weakness or guarantee that failing equipment will survive the process.


Final Position

My position is simple.

If I clearly break it, I replace it.

If my actions directly cause avoidable damage, I accept responsibility.

If the equipment fails because of an existing condition outside my reasonable control, I document it and explain it—but I do not accept responsibility for damage I did not cause.

That is not avoiding accountability.

It is applying accountability fairly.

Clients should expect technicians to stand behind their work.

Technicians should expect clients to respect the value, cost, risk and responsibility involved in professional technical service.

Professional integrity means doing what is right when you are responsible—not accepting blame for every failure simply because it happened while the equipment was in your care.