Picture an IT lead at a Dutch logistics company with a migration to plan. A partner has given her two names for the architect role. Before she emails either of them, she opens both LinkedIn profiles.
One says "Senior consultant at [firm]" and lists a job title from 2019. The other says who he helps, with what, and links to a short write-up of a database cutover. She doesn't know yet which one is better. But she knows which one she can explain to her CFO.
That quiet reference check is the reason personal branding for IT consultants matters. It happens before the first call, and nobody tells you it took place.
What buyers have already decided before they call
Buyers arrive with opinions. In the 6sense 2025 B2B Buyer Experience Study, which surveyed 945 B2B buyers in Belgium, France, Germany, the Netherlands and Sweden, the winning vendor was already on the buyer's Day One shortlist 92.4% of the time. Buyers typically first contacted a seller about 58% of the way through their journey.
Two caveats. It's a vendor study, and it covers B2B buyers in general, not IT buyers specifically. We haven't found a Belgian or Dutch study on how IT buyers vet individual consultants, so we won't pretend one exists.
What it does suggest is that what a buyer sees before the call matters. Referrals, certifications and technical proof matter too, and a profile doesn't replace them. But a clear profile and a few concrete posts make you easier to put on the list, and easier to say yes to once you're on it.
Why technical people avoid it, and why the reasons are fair
If you're an architect or engineering lead and you don't post, you probably have one of three reasons.
Nobody told you what's safe to say. Your client's name, their stack and their incident history aren't yours to share. Staying quiet feels like the responsible default.
It feels like marketing. Much of what you see on LinkedIn is "thrilled to announce" and a stock photo. You'd rather not add to it.
You bill 40 hours a week. Writing comes after the work, and the work never ends.
These are fair. Rick Zwart, co-founder of Dutch custom software firm Triniti Solutions, described where he and co-founder Danny Zwart started: "We were great at helping other businesses go digital. But our own online visibility? That was a blank page." Later he said of working with Willow: "We're not marketers, but Willow made it feel doable. We got help where we needed it and learned the rest step by step."
We cover the company-level version of these blockers in our post on social media coaching for ICT companies. This post is about you as an individual, and what to do next.
What a technical personal brand actually is
Strip away the word "brand" and what's left is credibility made visible. Someone who has never worked with you can see how you think before they spend an hour on a call with you.
It has three parts:
- A profile that says who you help and with what. Specific enough that the right buyer recognises themselves.
- Two or three topics you're known for. Pillars, for example cloud migrations for mid-sized companies, security basics for non-security teams, or data quality. A content calendar isn't needed. If you need help choosing, what should I post on social media walks through it.
- Proof of how you think. A decision explained, a mistake owned, a trade-off made visible.
An influencer chases reach. The engineer people trust is known by a small, relevant audience for a narrow set of problems. That's the one you want to be.
LinkedIn's VP Global Editorial, Laura Lorenzetti, said at Paris Creator Week on 4 November 2026: "Nobody really wants to hear from a brand page anymore. They want to hear from people they trust." For a technical buyer, that person can be you.
And a small audience of the right buyers is enough. Our analysis of 374 LinkedIn company pages found that a page with 800 consistent, relevant followers often beats one with 5,000 followers that posts once a month. That's company-page data, so read it as a pattern to borrow. Our post on the executive creator makes the same case for B2B: a few trusted voices can beat a big following.
Fix your LinkedIn profile first
This is the quick win. You can do it tonight, and it matters more than any post.
The headline. LinkedIn gives you 220 characters. A bare job title uses a fraction of them. Say who you help and with what.
- Weak: "Senior IT Consultant at [firm]"
- Strong: "I help mid-sized Belgian companies move off on-prem Exchange and Active Directory without a weekend of downtime. Microsoft 365 and Entra ID architect."
The strong one is an illustration we made up. What matters is that a buyer who reads it knows within five seconds whether you're relevant.
The About section. Write four or five short paragraphs for a technical buyer, not a recruiter. Start with the problem you solve. Then say how you work, in plain language. End with what to message you about.
The Featured section. This is where proof lives. Pin the things a buyer would otherwise ask for: certifications, a conference talk, a write-up of a project (anonymised), a short post you're proud of.
Then look at your profile as a logged-out visitor would. If your top three lines don't tell them what you do, rewrite them.
What engineers can post, with the client left out
Share what you learned. Announcements can wait.
Five post types that work for engineers:
- The problem and what you tried first. The dead end is the interesting part.
- The mistake you wouldn't repeat. A migration step you'd do in a different order now.
- A decision explained. Build or buy, cloud or on-prem, and why you landed where you did.
- A before and after in plain numbers. Restore time, ticket volume, build duration. Round it if you need to.
- A tool or approach you stopped using. And what replaced it.
Every one of these can be written without naming a client. That's the rule worth making explicit.
A client-safe check before you post:
- No client name unless you have written permission.
- No configs, version numbers or architecture details that would help an attacker map a client's environment.
- Describe the situation, not the company. "A 60-person Dutch distributor" is fine. Their logo isn't.
- Check with your contract and your own security or legal contact. They have the final say. Nothing here is legal advice.
There's a reason to take this seriously beyond manners. The Dutch Cyberbeveiligingswet has applied since 15 August 2026, and the Netherlands Enterprise Agency (RVO) writes that non-regulated suppliers can also be indirectly affected by its requirements. Your clients' security duties can reach you. Belgium has its own NIS2 law of April 2024: the dates and details are in our post for ICT companies.
A rhythm for someone who bills 40 hours a week
Don't aim for daily. Aim for something you'll still be doing in six months.
- One post every week or two. If that's too much, start with one a month. A steady small rhythm beats a burst followed by silence: in Willow's analysis of 43,738 posts, company pages that posted in most weeks got about three times the impressions of pages that posted in only some weeks.
- Write when a project closes. Fifteen minutes while it's fresh. That's an editorial suggestion from us, not a researched number, but you still remember what went wrong.
- Edit a draft. A rough draft that's 80% there takes far less effort than a blank box.
- Work from a short list. Keep a note of five topics tied to your two or three pillars, so you never start from "what do I say?".
If drafting is the bottleneck, that's where Willow fits. Willow Create drafts posts from a profile of your business: your services, audience, tone and point of view. A dedicated coach reviews drafts on request and checks quality regularly, you approve every post, and you can add custom instructions to fine-tune future posts. Coaching helps with the decisions around it. It keeps the rhythm going, and what's safe to say stays your call.
One more decision is personal profile or company page. Both have a job, and we explain the difference in company page vs personal profile.
How a firm owner can get the whole team doing this
If you run the firm or lead a practice and you're reading this for your engineers, a few things help.
- Start with one or two willing people. Mandating it can backfire. Pick the people who already explain things well in meetings.
- Write the safe-to-share rule down. One page: what's fine, what needs permission, who to ask. Engineers often hold back because they can't tell where the line is.
- Go first. If the founder posts a lesson and nobody on the team sees a downside, the second and third person follow.
- Give them the time. Fifteen minutes after a project closes should count as work, not as something they do on top of billable hours.
Customers who started small look like this. At Testersuite, colleagues John, Frank and Alexander contribute posts from their own profiles, and the company keeps up at least two posts a week. At Itineris, an IT consulting firm, 9 engaged employees were ready to start posting from their own profiles.
Where to start this week
Three things, in this order:
- Rewrite your headline. Who you help, with what. Ten minutes.
- Pick two topics. The two problems you'd be happy to be asked about at a dinner.
- Draft one post from your last closed project. No client name, no configs. What you tried, what worked, what you'd change. Send it to your security or legal contact if you're unsure, then publish.
That's it. No calendar, no persona, no influencer routine.
If you want help keeping this going, take a look at social media for IT and software companies.