Nobody really talks about this side of working in technology.
The emotional side.
The part where you spend hours:
- researching hardware,
- designing solutions,
- checking compatibility,
- comparing pricing,
- revising infrastructure plans,
- updating quotations,
- and trying to genuinely help someone solve a problem…
Only to watch the client take your work, buy everything themselves, and hand it off to somebody cheaper.
Sometimes a family member.
Sometimes “a guy who knows computers.”
Sometimes the infamous nephew with a crimping tool and confidence. 😄
And if you work in IT long enough?
This will happen to you.
Recently, I spent time building out a detailed infrastructure recommendation for a client.
Not once.
Three times.
Each revision included:
- updated parts,
- revised recommendations,
- compatibility adjustments,
- and careful consideration of the client’s actual operational problems.
Because after COVID, money is tight for a lot of people.
That’s reality.
Businesses are more cautious.
Households are more cautious.
Everybody wants to stretch every dollar.
I understand that.
Honestly, most small businesses today are surviving in ways people don’t openly admit.
The painful part wasn’t even losing the job.
It was realizing the parts list itself became the product.
The client used the exact hardware recommendations, purchased the equipment independently, and had their nephew install everything instead.
And here’s the plot twist:
The major outages mostly stopped.
So from the outside?
It probably looked successful.
But underneath?
The network design ended up inconsistent:
- configurations varied,
- standards weren’t followed properly,
- structure became fragmented,
- and future troubleshooting likely became harder.
The difference between:
“working”
and
“engineered properly”
is massive in IT.
But not everybody sees that immediately.
Sometimes problems don’t appear until:
- six months later,
- during expansion,
- after a firmware update,
- or when troubleshooting becomes a nightmare because nothing follows a consistent design philosophy.
And honestly?
I don’t think the client will call me back.
Not because they’re angry.
Probably because they feel guilty.
That’s the weird human side of business people don’t prepare you for.
Sometimes clients know:
- you put real effort in,
- your recommendations solved the root issue,
- and they benefited from your expertise…
Even if they didn’t hire you fully in the end.
That creates awkwardness.
The older I get, the more I realize something uncomfortable about technology work:
A lot of engineering labor is invisible.
People see:
- the switch,
- the access point,
- the server,
- or the cable.
They don’t see:
- the research,
- the planning,
- the architecture,
- the troubleshooting experience,
- the mistakes you already learned from years ago,
- or the operational thinking behind the design.
They see the hardware.
Not the thought process.
That’s why many people underestimate technical work until something breaks badly.
And truthfully?
This stuff hurts more when you actually care.
If you’re the kind of person who just throws random equipment together for a paycheck, maybe it doesn’t matter.
But when you genuinely try to:
- design stable systems,
- build properly,
- and help people avoid future headaches…
It stings a little when your work becomes unpaid consultation.
Especially when you know the final deployment could have been cleaner, safer, and easier to maintain long-term.
But there’s another side to this too.
The fact that the outages improved means something important:
The recommendations were correct.
That matters.
Even if the outcome wasn’t financially rewarding.
And over time, that consistency of thinking is what builds reputation.
Not every quote becomes a project.
Not every client becomes long-term business.
Sometimes your role in somebody’s story is simply:
helping point them in the right direction.
Even if they never fully realize it.
Technology after COVID became strange.
People are more cautious with spending.
More DIY-focused.
More willing to mix professional work with “family favors.”
And honestly?
Sometimes that’s understandable.
People are trying to survive.
That doesn’t make it painless.
But it does make it human.
At the end of the day, working in technology teaches you something few industries talk about openly:
Expertise alone does not guarantee business.
Trust matters.
Relationships matter.
Timing matters.
Economics matter.
And sometimes the best you can do is:
- provide honest recommendations,
- do solid work,
- stay professional,
- and accept that not every opportunity becomes a win.
Even when part of you wishes it had.