Freelancers sell judgment. A client hires a DevOps freelancer partly for the contract hours and partly for the opinion: which pipeline tool, which cloud region, which monitoring product. That opinion carries more weight when the client knows the freelancer’s interests, and less when it does not. Because a freelancer has no employer handbook to lean on, the habit of naming your own stake has to be personal and portable. Here are eight situations where a short, plain sentence about what you gain should come before the recommendation.
Eight ties worth stating out loud
1. A referral fee
If a tool vendor or a marketplace pays you when a client signs up through your link, say so as you make the suggestion. The reasoning is simple: the client should know that your recommendation has a price tag attached on your side, however small. Stating it takes one line, and it settles the question before it is asked.
2. A free or discounted licence
Vendors often hand freelancers trial seats, upgraded tiers or conference passes. These are normal courtesies in a small industry. Mention them when you praise the product, because gratitude and judgment blur easily, and the client cannot see where one ends.
3. Paid teaching or content about the tool
Freelancers frequently run workshops, record courses or write sponsored tutorials. If your income includes teaching a product, you have a reason to see it favourably. Name the product and the nature of the work, such as “I am paid to deliver a training session on this”.
4. A past employer
Time spent on the payroll of a product’s maker shapes both your knowledge and your loyalty. It also gives you real insight that clients value. Say “I used to work there” and let the client use that as context rather than a surprise.
5. A current client who uses or sells the product
Suppose you advise two companies and one of them sells the platform you are recommending to the other. That overlap deserves a plain mention, even if confidentiality limits the details. “One of my other clients is connected to this vendor” is enough to let the listener weigh the point.
6. An ownership stake
Even a small shareholding or advisory equity in a startup changes your incentives. Be specific that you hold a stake, without exaggerating or minimising it.
7. A friend or family link
Recommending a subcontractor, a designer or a monitoring tool built by a friend is perfectly reasonable. The client simply deserves to hear about the friendship as part of the introduction.
8. A habit you want to keep
The eighth item is less a tie than a reason: you simply prefer a tool because you already know it well, and switching would cost you billable time. That is an honest interest too. A sentence such as “this is what I know best, so it is what I reach for” helps the client separate your comfort from the best technical fit.
Why the evidence points toward saying it early
The argument for early disclosure does not need statistics. It rests on how decisions get made. A client weighing a recommendation is doing a quiet calculation: how much should I trust this person on this point? Information about your interests feeds that calculation directly. If the client learns it later, the calculation was run on incomplete data, and any decision built on it can be reopened. If the client learns it first, the decision stands on firmer ground and your reputation is protected.
There is also a practical effect on repeat work. Clients who have heard your ties up front tend to bring you the next question, because they know how you behave when your interests are involved. Freelance work lives on that kind of reputation.
A format you can copy
Keep the sentence structure simple: who, what, and how it might affect you. “I earn a referral fee if you subscribe through this link, so check the pricing page for yourself too.” Nothing there demands a lawyer’s polish. It just needs to be said before the suggestion, not tucked at the end.
If you are still building a client base, an earlier article about growing a support circle and meeting mentors when you work solo is a useful companion, since the people in your network are also the people to whom you will be recommending things.
A look at the wider publishing world
Freelancers are not alone in this. Independent bloggers and video makers, including many who share DevOps content, take sponsored work too. CollabGigs presents itself as a site where brands pay for sponsored-content campaigns and independent publishers run them through their own blogs, videos and social accounts. Anyone who endorses things in public, whatever the format, faces the same small decision about saying what they stand to gain, and that includes you on your next proposal.
A small first step for this week
Do not try to audit your whole business in one afternoon. Open your last three proposals, circle every recommendation you made, and next to each one ask whether you gained anything from it. You will probably find that most were clean and one or two deserved a sentence. That quick review is enough to build the habit, and it costs less than an hour.
Wrapping up the list
None of these eight ties disqualifies you from recommending a tool. They simply give the person listening what they need to weigh your advice. Pick the two or three that apply most often to your own work and write a template sentence for each, stored where you draft proposals. Next time a client asks “what would you use?”, the honest answer can arrive with its context attached, and the conversation that follows will be a better one.
For more on dealing with newcomers’ questions, you might also like a beginner’s set of questions and answers about starting out as a DevOps freelancer.