If you are a developer trying to build a consulting pipeline, the conventional sales advice is almost entirely useless. Cold calling, email sequences, pushy LinkedIn messages. None of it sits right and most of it does not work anyway. After 17 years as a developer and consultant, having worked across Dynamics 365 implementations, SaaS products and everything in between, here is what actually keeps the pipeline full.
The good news is that developers have a genuine advantage in consulting that most salespeople do not. When you actually know your subject, people come to you. The trick is making sure enough of the right people know you exist and understand what you do.
Stop trying to sell and start trying to be useful
Every piece of work I have ever landed came from one of three places: a previous client, someone a previous client recommended me to, or someone who had read something I wrote or heard me talk about a topic. Not one piece of serious work has come from sending unsolicited messages to strangers.
This is not unique to me. Every consultant I know who is genuinely busy has the same story. The pipeline is built from reputation, not outreach. The question is how you build that reputation before you have an established track record to lean on.
The fastest way to build a reputation is to demonstrate what you know
Writing is undervalued by most developers as a business development tool. I am not talking about tweeting opinions or posting vague LinkedIn updates about hustle culture. I mean actually writing about what you know in a way that shows genuine depth and experience.
If you specialise in something, whether that is Dynamics 365 implementation, .NET architecture, or building SaaS products on a tight budget, write about it honestly. What mistakes do clients consistently make? What does good actually look like? Where does conventional wisdom get it wrong? The posts that get shared and remembered are the ones where someone says "yes, finally someone who gets it."
This blog exists partly for that reason. It is not just a way of ranking for keywords. It is a way of showing people how I think and how I work before they ever pick up the phone. By the time someone contacts me, they already have a reasonable sense of whether I am the right kind of person for their problem.
Get specific about what you actually do
The generalist developer who can do anything for anyone is the hardest sell in consulting. Not because generalists cannot deliver value, but because a business with a specific problem finds it very hard to work out whether a generalist is the right person for that specific problem.
When I present myself in a consulting context, I am not "a software developer". I am a developer with 17 years experience who specialises in Dynamics 365 implementation, SaaS product development and technology strategy for growing businesses. Those are specific things a specific buyer might need. A vague description does not create that same connection.
You do not have to niche so tightly that you turn away half the work. But you should be able to describe what you are best at in a sentence, and it should be specific enough that someone with that exact problem immediately thinks "that could be the person I need."
Your network is more valuable than you think, but only if you maintain it
Most developers have a reasonable network from previous jobs, clients and collaborations. Most of them do not maintain that network in any deliberate way. They are not doing anything wrong. Staying in touch with former colleagues and clients does not come naturally to a lot of technical people, myself included in the early days.
The approach I use is simple. If I do good work for someone, I stay in light contact. Not pestering them. Just staying on their radar. If I write something relevant to their industry, I might share it with them. If I see something useful to their business, I send it over. You are not selling. You are just reminding people you exist and showing you are paying attention to the world they are operating in.
When they or someone they know has a problem that matches what you do, you are the person they think of. That is the whole game, really. It sounds simple because it is, but most people do not do it consistently.
LinkedIn is not a sales channel but it is a useful reputation tool
I am not going to tell you to post every day and build your personal brand. That way lies a lot of effort for questionable return and most of it is just noise. But LinkedIn does serve a purpose as a place where potential clients can check that you are who you say you are and see some evidence of how you think.
A decent profile. A handful of genuinely useful posts over the course of a year. Engaging with content in your specialist area in a way that shows you actually know what you are talking about. That is enough. If you get it right you will occasionally get inbound enquiries from it. More often it will simply reduce the friction when someone you have been referred to checks you out before they get in touch.
Make it easy for people to refer you
Referrals are the backbone of a healthy consulting pipeline, but referrals do not happen automatically even when people genuinely want to help you. The person who wants to recommend you has to be able to remember clearly what you do and feel confident that you can handle the specific thing they are referring you to.
Tell the people in your network what you are looking for. Not in a desperate way, but directly and clearly. "I am looking for Dynamics 365 implementation work with mid-market businesses" is far more useful to a potential referrer than "if you know anyone who needs a developer, let me know." The second one requires your contact to do all the matching work themselves. The first one means they can immediately think about who they know who fits.
This feels uncomfortable for a lot of developers because it sounds like you are asking for something. You are. That is fine. People who rate working with you want to help. Give them something specific to help with.
What genuinely does not work
Cold email sequences. Automated LinkedIn connection requests with a pitch in the follow up. Paying for leads from aggregator sites. None of these build a sustainable consulting business for a developer. They might generate occasional work but they are a terrible return on the time and money they cost, and they attract clients who are shopping purely on price because they had no recommendation to anchor their trust to.
The client who comes via a referral from someone they respect is a better client in almost every way. They trust you before they have met you. They are not shopping around in the same way. They are more willing to pay a fair rate and less likely to question every decision you make. Building a pipeline of those clients takes longer but the business you end up with is significantly better.
The longer game
If you are just starting out in consulting, none of this is quick. The first year is genuinely hard. You are doing good work, building relationships, writing occasionally, staying in touch with your network. Not a great deal is happening visibly. It can feel like nothing is working.
By year three, if you have done it right, you should have more work than you can take on. By year five you should be turning work away and becoming more selective about what you take. I am speaking from experience. That is roughly how it went for me, and I have seen the same pattern with other developers who have made the transition to consulting.
If you want to think more broadly about building something around your technical skills, I wrote about that in why developers should start a business. The principles overlap more than you might expect. And if you want to see how I have positioned my own practice, the services page gives you a clear picture of how I describe what I do and who I do it for.
Consulting is sales. It just does not look like the version of sales that makes developers uncomfortable. It looks like being genuinely good at what you do, talking about it honestly, maintaining relationships with people who have seen your work, and making it as easy as possible for the right work to find its way to you. That is a version of business development that most developers can actually do.
