Based on a LinkedIn post originally published on 23 January 2026
In the 2000s, while I was living in southern Brazil, an acquaintance contacted me about a technical problem.
He was working with Porsche and needed help resolving an issue affecting a Windows NT server. He suggested that helping with the problem could open the door to future professional opportunities.
The arrangement sounded reasonable.
I agreed to investigate.
The technical problem was eventually resolved. The professional lesson lasted much longer.
The request
The server had lost its reference to one of its internal disks following an incorrect configuration change.
From the outside, the situation initially appeared serious. Part of the storage was no longer accessible, and the system’s behaviour created the impression that a significant failure had occurred.
After examining the configuration, I determined that the problem was not a mysterious hardware fault. The server had lost the correct relationship with the disk because of the change that had been made.
I restored the system to a healthy state.
While working on it, I also improved aspects of the configuration so that the system would be more resilient to a similar problem in the future.
From a technical perspective, the engagement was successful.
The server was operational, the underlying issue had been identified and the environment was left in a better condition than I had found it.
What happened afterward
Nothing happened afterward.
There was no follow-up.
There was no acknowledgement.
There was no professional opportunity.
The acquaintance who had suggested that this work might lead to future engagements simply disappeared from the conversation.
Over time, I came to believe that the request had not really been the beginning of a professional collaboration. It appeared instead that my involvement had helped resolve a difficult situation after changes were made without sufficient technical understanding.
I cannot know every motivation involved, but the practical outcome was clear: I had provided professional work based on an informal promise that had no substance behind it.
The experience changed the way I approached similar requests.
The problem with “future opportunity” as payment
Promises of future work are common.
A person asks for help today and suggests that the favour will lead to:
introductions;
paid engagements;
referrals;
business partnerships;
employment;
visibility;
or future reciprocal support.
Sometimes those promises are genuine.
Many long-term professional relationships begin with one person helping another. Trust and generosity are important parts of business and personal life.
The difficulty is that a possible future opportunity is not the same as an agreed exchange.
It has no defined value, timeframe or obligation.
The person receiving the work obtains an immediate and measurable benefit. The person providing it receives a possibility.
That imbalance becomes particularly significant when the work requires specialist knowledge, carries operational risk or creates responsibility for an important system.
A favour can still create professional liability
Informal work is often treated as if it carries no consequences.
In reality, the risks may be substantial.
If someone asks a technology professional to repair a server, database, network or application, the work can affect:
business operations;
customer data;
availability;
security;
regulatory obligations;
and future system behaviour.
If the repair succeeds, the requester benefits.
If something goes wrong, the fact that the work was performed as a favour may not prevent blame or conflict.
Questions can arise immediately:
What exactly was the person authorised to change?
Was a backup available?
Who accepted the risk?
Which outcome was promised?
Who owns the system afterward?
Is the person expected to provide continuing support?
What happens if another problem appears a week later?
Was the original environment already damaged?
Who is responsible for documenting the work?
Without explicit terms, each person may hold a different understanding.
Informality does not remove accountability. It makes accountability ambiguous.
The hidden expansion of scope
Technical favours rarely remain as small as they initially sound.
A request may begin with:
Could you take a quick look at this server?
After investigation, it becomes clear that the issue involves several components. The requester may then expect the person providing help to:
diagnose the root cause;
restore service;
correct earlier changes;
improve resilience;
document the solution;
monitor the result;
and remain available if anything else fails.
The original “quick look” becomes a professional engagement without professional terms.
This is especially common when specialist knowledge makes difficult work appear easy.
A problem may take only a short time to fix because the engineer has spent decades developing the ability to identify it quickly.
The value lies not in the number of minutes spent typing commands. It lies in knowing which evidence matters, which changes are safe and how to avoid making the situation worse.
Expertise is easy to undervalue when the solution looks simple
Many technical problems are difficult until someone understands them.
Once the cause is known, the correction may appear obvious.
This creates a misleading impression that the work itself was simple.
The visible repair may take twenty minutes. The capability behind it may depend on years of experience with:
operating systems;
storage;
hardware;
configuration management;
failure recovery;
and production troubleshooting.
Clients do not pay only for activity.
They pay for judgement, responsibility and the ability to reach the correct result without unnecessary risk.
A short successful intervention may be more valuable than many hours of uncertain experimentation.
The decision I made
After that experience, I established a clear personal rule:
I would no longer perform professional work for friends or acquaintances based solely on informal promises.
Any substantial engagement would need to be:
discussed explicitly;
scoped;
assigned clear responsibilities;
and financially recognised.
This was not because money had become my primary motivation.
It was because clear terms protect everyone involved.
They force the participants to discuss what the work actually includes and what each person expects.
What clear terms provide
A professional agreement does not need to be unnecessarily complicated.
Even a small engagement should clarify several points.
The problem
What is the requester asking the professional to investigate or deliver?
The scope
Which systems and activities are included?
What is explicitly excluded?
Authority
Which changes may be made, and who approves them?
Risk
Are backups available?
Who accepts service interruption or other potential consequences?
Deliverables
Is the expected result a diagnosis, a repair, documentation, an implementation or ongoing support?
Time
When will the work begin, and how much availability is expected?
Payment
How will the work be valued and paid?
Completion
When is the engagement considered finished?
Continuing support
What happens if a related problem appears afterward?
These questions reduce the chance that a favour becomes an undefined and permanent obligation.
Payment changes behaviour
Financial recognition does more than compensate the person performing the work.
It signals that the requester considers the engagement real.
When someone pays for professional work, they are more likely to:
explain the requirement properly;
provide access and information;
respect the agreed schedule;
participate in decisions;
review the result;
and accept their own responsibilities.
Payment establishes that both sides have made a commitment.
By contrast, unpaid requests are easier to postpone, expand or abandon because the requester has little investment in the process.
This does not mean paid engagements are always well managed. It means the exchange has at least been recognised explicitly.
Friends and professional work can coexist
Refusing informal professional work does not mean refusing to work with friends.
Friends can become excellent clients, colleagues or business partners.
The relationship simply needs clear boundaries.
In fact, formal terms may be even more important when a personal relationship exists.
A written scope protects the friendship by preventing assumptions such as:
“I thought you would continue supporting it.”
“I assumed this additional work was included.”
“I expected a different result.”
“I believed payment would happen only after future business arrived.”
“I did not realise the change involved risk.”
Clarity allows the personal and professional relationships to coexist without one being used to pressure the other.
Free work can still be deliberate
There are legitimate situations in which a professional may choose to work without payment.
Examples include:
open-source contributions;
mentoring;
community projects;
charitable work;
emergency assistance;
and carefully selected support for someone who genuinely needs it.
The important difference is that the decision is conscious.
Pro bono work should still have:
a defined scope;
clear expectations;
appropriate risk controls;
and an agreed endpoint.
“Free” should describe the financial arrangement, not the absence of professional discipline.
Boundaries are not hostility
People sometimes interpret boundaries as a lack of generosity.
A request for scope or payment may be treated as overly formal, particularly when the requester frames the work as a small favour.
A professional boundary is not an accusation.
It is a way of preventing resentment and misunderstanding.
A clear response might be:
I am happy to help, but because this involves a production system, we should treat it as a professional engagement. Let us define the scope, responsibilities and commercial terms before I begin.
That statement is respectful.
It also gives the requester an opportunity to decide whether the work is genuinely important.
A useful warning sign
One of the strongest warning signs is resistance to defining the arrangement.
If someone expects valuable technical work but objects to:
a written scope;
agreed responsibilities;
payment;
access requirements;
or risk clarification,
the problem may not be excessive formality.
The person may be relying on ambiguity.
A genuine prospective partner should not be threatened by basic professional clarity.
The technical result was not the whole result
For many years, I viewed successful technical work primarily in terms of whether the system was repaired.
That experience taught me that a successful engagement has another dimension.
The technical outcome matters, but so do:
the agreement;
the communication;
the recognition of value;
the allocation of responsibility;
and the way the relationship continues afterward.
I repaired the server correctly.
What I failed to protect was the professional context around the work.
That was the more important lesson.
Professional work deserves professional terms.
Not because every interaction must become transactional, but because clarity protects trust—and trust is much harder to repair than a server.
This article is based on my original ideas, experience, analysis and conclusions. Artificial intelligence tools were subsequently used as editorial and research assistants to review grammar and wording, improve structure and presentation, organise some arguments into clearer logical sections, and help review references to legal, regulatory and technical concepts.
Where relevant, factual and regulatory references were checked against the sources cited in the article. AI assistance does not replace professional legal, regulatory, financial or technical advice, and the final selection, interpretation, opinions and conclusions presented here remain my own.
Comments
Post a Comment