You are in a pull-request thread, an architecture chat or a conference hallway, and someone asks which tool you would pick for the pipeline. You have an opinion. You also have a history: a former employer, a free licence, a friend who runs the product team. Here are eight short sentences you can say, in plain words, before you give the opinion. Each one tells your listener what is in it for you, so they can weigh your advice the way it deserves to be weighed. Pick the ones that fit your situation and keep them handy.
1. “I work there right now.”
The simplest and the strongest. If you are on the vendor’s payroll, say so before you say anything else. Colleagues will hear the rest as advocacy, which is fine, because advocacy is useful when it knows it is advocacy. A speaker who opens this way tends to get sharper questions and more honest pushback.
2. “I used to work there.”
Former employers matter more than people expect. You know the product’s quirks, you may keep friends on the inside, and your opinion may be a little stale or a little rosy. A sentence like “I left a while ago, so some of this may have changed” keeps you honest on both counts.
3. “They gave me access for free.”
Free seats, credits and trial accounts shape impressions even when you try to stay fair. If the tool came to you at no cost, say so. Your listener can then ask whether you would have paid for it yourself, which is a fair question worth answering out loud.
4. “I get paid if you sign up.”
Referral and affiliate arrangements are common in tooling, learning and hosting. Name them in the same breath as the recommendation. The phrase “there is a referral payment on my link” costs a few seconds and removes any doubt about why the link is there.
5. “I own a piece of it.”
Shares, options, advisory stakes and profit-sharing deals all belong here. These are the ties people are most reluctant to mention, and the ones listeners most want to hear about. If you hold equity, say it before the pitch, not after the question.
6. “A friend built this.”
Friendship is a tie too. It does not make your view invalid; it means you have extra goodwill toward the project. “A friend of mine maintains this, so I am rooting for it” is an honest preface that most teams will happily accept.
7. “I teach a course that covers it.”
Trainers and writers have a built-in reason to promote the tools they teach. If you earn from workshops that use a product, mention it when you recommend that product. Our own notes on what to learn when starting out with AIOps show the kind of subject where a trainer’s pick deserves a short note about the trainer’s own interests.
8. “This post came out of a paid campaign.”
Writing for the public is a different setting from talking in a meeting, but the principle carries over. Some publishers take sponsored work arranged through marketplaces, for instance CollabGigs, a website laying out a marketplace where companies fund promotional campaigns and independent bloggers or video makers publish them. If your tooling post came from a deal like that, put the fact in the opening lines in your own words, so no reader has to guess.
Where to put these sentences
Order matters more than polish. Say the sentence before you give the recommendation, because people form an impression in the first few seconds and then read everything else through it. On the page, aim for the opening paragraph or the line right above the section in question. In a meeting, it means before slide one. In a chat thread, it means in the same message as your pick, not three replies later after somebody asks.
One more reason to put it first: a late disclosure reads like damage control. The identical sentence delivered upfront reads like candour. The words are the same, but the timing changes what the listener hears.
Mixing and matching
Real situations are rarely tidy, and that is fine. You might have a former employer, a free licence and a referral link all at once. Do not try to compress them into one clever clause. List them plainly: “I used to work there, I have a free licence, and I earn a referral credit.” Three short facts are easier to digest than one carefully balanced hedge.
A quick example from machine learning operations
Suppose you are advising a team on how to set up model deployment, and you point to a particular platform. A line such as “I earn from workshops that use this platform” lets the team treat your advice as one input among several. It fits neatly beside material like why operations discipline matters for machine learning projects, where choices about tooling tend to stick for years and deserve a careful hearing.
Sorting out the reactions
- Most listeners say thanks. They appreciate the information and move on to the real discussion.
- A few ask follow-ups. That is helpful, since it gives you room to explain how you formed your view.
- Very few walk away. And those who do were probably going to wonder about your motives later anyway.
Make it a reflex
The easiest way to keep this up is to turn it into a reflex, the way you reach for a seatbelt. Before any recommendation, run a one-second check: do I gain anything from this? If yes, pick the matching sentence from the list above and say it. Give it a month and the list becomes unnecessary, and the people around you will quietly learn that your recommendations arrive with the full story attached.