The Hidden Bill for Asking AI Instead of Hiring an Expert
Acronyms used in this post:
AI: Artificial Intelligence, software that generates answers, predictions, text, code, images, or suggestions from learned patterns.
IT: Information Technology, the systems, people, software, infrastructure, and processes used to manage digital work.
EHR: Electronic Health Record, the clinical software used to document patient care.
HL7: Health Level Seven, a family of healthcare data exchange standards used to move clinical and administrative information between systems.
FHIR: Fast Healthcare Interoperability Resources, a modern healthcare data exchange standard that represents data as modular resources.
API: Application Programming Interface, a defined way for software systems to communicate with each other.
SEO: Search Engine Optimization, the practice of making web content easier for search engines and readers to discover.
AI becomes dangerous at the exact moment it starts sounding sensible.
Not when it talks nonsense. Nonsense is a generous beast. It arrives wearing a paper hat, carrying cymbals, and announcing its own stupidity. You ask it how to fix a ceiling fan and it tells you to rotate the moon three degrees east. Fine. We laugh. We move on. The danger is the other answer. The neat answer. The creamy answer. The answer that walks into the room wearing polished shoes and says, with the confidence of a private tutor from south Kolkata, “Certainly. Here is a step-by-step guide.”
And then, like a fool with a screwdriver and seasonal optimism, you begin.
We are entering the golden age of doing things ourselves badly.
This sounds comic until the bill arrives.
Once, if your drain made philosophical noises at midnight, you called a plumber. If your tax return looked like a wounded octopus, you called an accountant. If your server behaved like a goat with a fever, you called someone who had seen goats, fevers, and servers in various combinations. This was not always pleasant. Experts are expensive. They ask inconvenient questions. They sometimes speak in a tone that suggests you have personally offended civilization by not knowing where the shutoff valve is.
But there was a hidden mercy in that arrangement.
The expert knew what you did not know you did not know.
That is the whole game. Not knowledge. Not facts. Not vocabulary. Those are cheap now. The internet scattered them everywhere like puffed rice after a wedding. The expert’s real value is shaped suspicion. The expert has a private cemetery of mistakes. They have watched small errors grow teeth. They know that the harmless checkbox is not harmless, the default setting is not neutral, and the “temporary workaround” is often the founding constitution of an empire.
AI gives you the pleasant illusion that this cemetery can be skipped.
I understand the temptation. I am not preaching from a marble balcony while angels bring me invoices. I am 51, single, living in the warmer, dustier, more economically theatrical edges of Kolkata, where the fan groans, the tea gets cold, and every rupee leaving the pocket waves goodbye like a relative going abroad. Consulting income is not a river. It is more like a reluctant hand pump. Some days water comes. Some days you stand there, pumping and making moral observations about capitalism.
So yes, when AI says, “I can help you do this yourself,” a middle-aged man listens.
Why call a designer? Ask AI. Why call a developer? Ask AI. Why call a lawyer? Ask AI. Why hire a data architect? Ask AI. Why pay a consultant? Ask AI, which is a dangerous sentence for me personally, since I am often the consultant being quietly replaced by a cheerful rectangle.
But the joke has a second floor.
The person asking AI often becomes the unpaid apprentice, the unpaid reviewer, the unpaid tester, the unpaid project manager, and finally the unpaid victim of the thing they half-built. The money saved from not hiring an expert is quietly paid back in time, stress, rework, embarrassment, and occasionally real damage. Nobody puts that in the spreadsheet. Your own time, especially when you are anxious or unemployed or trying to hold life together with tape and tea, is treated as free.
It is not free.
It is your life, cut into small pieces.
The strange thing is that AI does not usually fail by being lazy. It fails by being helpful beyond its competence. It keeps going. It offers another fix. Then another. Then a revised fix. Then a “more robust” fix. It behaves like a cheerful friend who has never repaired a bicycle but has watched seventeen videos and is now holding a wrench near your brake cable.
You think you are getting closer.
Sometimes you are.
Sometimes you are just walking deeper into the mangrove with better formatted instructions.
This is the self-service trap. AI does not merely automate work. It seduces non-experts into expert-shaped activity. There is a difference. A person who uses AI to learn enough to speak intelligently with an expert is doing something wise. A person who uses AI to avoid the expert entirely may be building a chair that looks perfectly fine until a guest sits on it and discovers gravity in a personal way.
The key distinction is simple: AI can answer a question, but an expert can challenge the question.
That sounds small. It is not small. It is the hinge on which the door swings.
You ask, “How do I migrate this database?” AI gives you a plan. An expert asks, “Why are you migrating it, who uses it, what breaks if the timestamps shift, what does the old system mean by inactive, who owns the master record, what reports depend on this dirty little field nobody mentions, and why is there a column called final_status_2?”
You ask, “How do I integrate two healthcare systems?” AI explains HL7, FHIR, APIs, mapping, validation, authentication, and testing. Very good. Very educational. Then the expert says, “Show me the real messages from a bad week.”
There goes the party.
Because real systems do not behave like diagrams. Diagrams are polite. Real systems are old neighborhoods. Someone extended a balcony in 1998. Someone joined two wires during a crisis. Someone’s cousin added a form. A report depends on a misspelled value. A nurse developed a workaround because the official workflow required twelve clicks and a small act of devotional patience. Then the workaround became practice. Then practice became data. Then data became truth. Then AI arrived and said, “I have detected a pattern.”
Of course it has.
It has detected the fossil of a compromise.
In healthcare IT, this can become serious very quickly. An EHR does not contain pure reality. It contains documented reality, billed reality, remembered reality, copied reality, rushed reality, legally required reality, and occasionally reality’s badly dressed cousin. A medication list may show what was prescribed, what was dispensed, what the patient says they take, what was administered, what was discontinued, or what nobody dared remove because the last person who removed something got a phone call from a cardiologist.
These are not small differences. They are the difference between a recipe, a grocery bill, a restaurant order, and what you actually ate at 11:30 at night standing in front of the fridge.
When non-experts look at these records, they often call the mess “data quality.” That is a comforting phrase. It sounds like sweeping the floor. Clean the data. Standardize the data. Deduplicate the data. Put some governance on it, like coriander.
But much of this is not dirty data. It is failed representation.
That is a different animal.
A data quality problem is when a date is malformed, a code is missing, a duplicate record exists, or someone entered “M” where the system expected “Male.” A representation problem is deeper. It happens when the system’s categories do not match the world they claim to describe. The record is not merely untidy. It is structurally unable to say what happened without bending the truth into the shape of available fields.
This is where experts earn their inconvenient fees.
An expert knows that moving data is not the same as preserving meaning. You can send an HL7 message across town in milliseconds. Splendid. The message arrived. The transport worked. The little digital parcel rang the bell and entered the house.
But did the receiving system understand it?
That is another matter.
Transport says, “The parcel arrived.” Meaning says, “Was it medicine, a birthday cake, or someone’s left shoe?” FHIR can improve structure. APIs can standardize access. Validation rules can catch obvious mistakes. None of that guarantees that two organizations mean the same thing by “active,” “resolved,” “final,” “encounter,” “primary diagnosis,” or “home medication.”
A truck can deliver a piano.
It cannot tune it.
The non-expert sees a successful transfer. The expert asks what was lost in translation. The non-expert sees a green dashboard. The expert asks who is lying to it. The non-expert sees clean JSON. The expert asks whether the clean JSON is faithfully carrying nonsense.
That is not cynicism. That is maintenance of civilization.
The same thing happens outside healthcare. Ask AI to draft a legal agreement, and you may get something that sounds like a lawyer who has swallowed a dictionary and is trying to impress a magistrate. It may be enough for a harmless first draft. But if the agreement decides who pays when something burns, breaks, leaks, collapses, defaults, disappears, or marries into litigation, you want a human expert with a pulse and malpractice insurance.
Ask AI to help with accounting, and it may explain deductions with great charm. But tax rules are not general knowledge wearing spectacles. They are local, temporal, and booby-trapped. Ask AI to repair a household appliance, and it may be useful for diagnosis. But when water, electricity, gas, height, structural load, or poison enters the room, the romance of self-reliance should quietly put on sandals and leave.
This is not cowardice. It is proportion.
You can cut your own hair. Many people did during lockdown. Society survived, though not all photographs deserved survival. But there is a difference between cutting hair and rewiring a kitchen. There is a difference between drafting a blog outline and designing a patient identity system. There is a difference between asking AI to explain chest discomfort and using it as your only doctor while your body is sending telegrams in red ink.
One is assistance.
The other is gambling with better typography.
The modern economy encourages this gambling because it hides the cost. Companies love self-service when the service has been moved from payroll to your nervous system. You print your own boarding pass. You troubleshoot your own router. You scan your own groceries. You fill your own forms. You become clerk, technician, cashier, receptionist, analyst, and complaint department. AI adds a new costume: instant amateur expert.
This looks like empowerment from a distance.
Up close, it often looks like unpaid labor wearing a party hat.
There is another danger, quieter and worse. When AI gives us a fluent answer, we stop feeling the right amount of uncertainty. Uncertainty is useful. It is the smoke smell before the fire. It slows the hand before the knife slips. A good expert often increases uncertainty at the beginning of a project because they reveal hidden complexity. This is annoying, but healthy. They make the unknowns visible.
AI often does the opposite. It reduces discomfort too early.
It gives closure before investigation.
And premature closure is where many bad systems are born. The team asks AI for an architecture. The architecture looks reasonable. Someone turns it into a plan. The plan becomes a budget. The budget becomes a project. The project becomes a deadline. Then, three months later, a tired analyst discovers that the source system does not capture the one field the whole design quietly assumed existed.
By then, the slide deck has become archaeology.
I have seen this pattern in healthcare systems, data warehouses, research databases, analytics projects, and integrations that should have had warning labels. The failure rarely begins with stupidity. It begins with a plausible simplification. Someone says, “Basically, we just need to map X to Y.” That word, “basically,” has caused more damage than several minor storms.
Basically, patients are unique.
Except they are not, because names change, numbers get reused, addresses drift, and people arrive without documents.
Basically, a diagnosis code means the patient has the condition.
Except sometimes it means rule-out, billing, history, risk adjustment, quality reporting, or the fastest available click.
Basically, this timestamp is the event time.
Except it may be entry time, update time, interface time, system time, local time, corrected time, or the time a server in another building woke up and remembered its duties.
Basically, the AI answer is correct.
Except correctness in real work is not only whether a statement is true in a textbook. It is whether it survives contact with actual people, actual incentives, actual machines, actual law, and actual Tuesday afternoons.
Here is the practical rule I trust: use AI freely where errors are cheap, reversible, visible, and reviewable. Use experts early where errors are expensive, hidden, irreversible, regulated, safety-related, or dependent on context you cannot fully describe.
AI is excellent for first drafts, explanations, comparisons, checklists, test ideas, code sketches, learning paths, summarization, and making you less helpless before a conversation. It is like a fast, bright assistant who has read a thousand manuals and never personally been shouted at by a surgeon because the lab feed dropped during rounds.
That assistant is useful.
Do not make it the chief engineer.
The best use of AI is not replacing experts. It is making your meeting with experts less foolish. Ask AI what questions to ask. Ask it to explain the vocabulary. Ask it to produce a risk checklist. Ask it to show possible failure modes. Then bring that preparation to a person who has actual responsibility and actual scars.
The scar matters.
A scar is memory with skin over it.
The world does not need a priesthood of experts guarding their temple from ordinary people. That is old nonsense. Experts can be arrogant. They can be wrong. They can defend obsolete systems because the obsolete system contains their youth, their habits, and their favorite chair. I have met experts who treated a database table like family property.
So no, “hire an expert” does not mean “surrender your brain.”
It means know when your brain is missing the map.
AI can help you draw a map. The expert knows which bridge is washed out, which road floods in July, which shortcut is illegal, and which cheerful path takes you to a goat shed instead of the airport.
That is the whole point.
For a middle-class person, a small business, a clinic, a school, a startup, or a struggling consultant in Kolkata trying to stay afloat without selling his kidneys to the stationery shop, AI is a gift. It gives access. It reduces fear. It teaches. It drafts. It makes the first rung of the ladder lower.
But ladders still have height.
At some point you must know whether you are climbing a wall, a tree, or the wrong building entirely.
So ask AI. Absolutely. Ask it often. Ask it shamelessly. Make it explain like a patient tutor. Make it produce alternatives. Make it challenge your assumptions. Make it simplify the fog.
Then pause.
Ask one more question, the human question, the costly question, the question that saves you from becoming the hero of a small preventable tragedy:
Is this a place where a wrong but plausible answer can hurt someone, cost serious money, create legal trouble, damage trust, corrupt data, break a system, or hide a risk?
If yes, call the expert.
Not because AI is useless.
Because plausibility is cheap, and consequences are not.