How to find your first freelance client when you've only ever been employed

There's a version of "how to find your first freelance client" that assumes you've been thinking like a freelancer for years — that you've been nurturing leads, developing a brand, positioning your expertise in public ways. That version starts with a strategic foundation that most employed tech workers haven't built and weren't planning to build, because they were busy being employed.

This piece is for the other version. The one where you've spent seven years as a senior engineer or engineering manager or product person at a series of companies, your professional network is entirely composed of former colleagues, and the instinct you have when you need work is to update your CV, not write a pitch. That version is considerably more common and considerably less well-served by the standard freelancing advice.

What you actually have that you don't think you have

The standard freelancing advice tells you to build a portfolio, develop a niche, and market yourself to inbound leads through content creation. This is reasonable advice for people building a freelance practice as a long-term structure over years. It is nearly useless advice for someone who needs their first client within the next few months, has never sold anything, and doesn't have eighteen months to build an audience.

What you actually have, if you've been employed in tech for any meaningful period, is a network of people who have direct personal experience of your work. They've seen how you think under pressure. They've seen what you deliver. They know the quality of your output in a way that no portfolio piece and no LinkedIn recommendation can replicate. This is not a consolation prize for not having a marketing strategy. It is a more valuable starting position than most freelancing guides acknowledge, because the hardest part of the client problem — trust — is already present. What's missing is the connection between that trust and a commercial transaction.

The first conceptual shift required is from "building a client base" (which sounds like a long-term project with a marketing funnel) to "having a specific conversation with people who already know my work" (which is immediately actionable and considerably less abstract). You're not going to the market. You're talking to people you already know. That's not a lesser version of the real thing. For a first client, it's the most direct path available.

How to reframe employer relationships as potential clients

The resistance here is often framed as awkwardness — it feels strange to pitch to people you've worked alongside as an employee. But what's actually happening, when you think about it clearly, is not that different from what happens when any trusted professional proposes a different working arrangement. The relationship already has professional credibility in it. What you're doing is proposing a different structure for how that credibility gets exchanged commercially.

Start with the most obvious category: companies you've worked for that are still doing the kind of work you do. If you spent three years at a scale-up building data infrastructure and you're now going freelance as a data engineering consultant, the scale-up has direct knowledge of your capability and may have ongoing or intermittent needs for exactly that capability without the overhead of a full-time hire. Startups spinning up new functions, teams covering for parental leave, organisations with a one-time technical problem that doesn't justify headcount — these are real and frequent needs, and your former employer knows exactly whether your skills match better than any cold prospect ever will.

The second category is colleagues who have moved. Tech workers move frequently. The engineering manager who was two levels above you at your last company is now VP of Engineering somewhere else. The PM you worked closely with is at a different company building a new product. These people know your work, have professional credibility with their current organisation, and are — if you're direct with them — in a position to refer you for work or commission work directly if the need exists. They're not doing you a favour by doing this. They're accessing capability they trust, which is exactly what their current employer wants them to do.

The third category is people who were adjacent to your employers — at companies that competed, partnered, or worked alongside yours. Your professional credibility in a given domain is visible to more people than just your direct employers, and the signal of your employment history at recognisable companies transfers to organisations that never employed you directly but are in a position to value what you know.

How to price when you have no freelance track record

Pricing is where first-time freelancers consistently undervalue themselves, for reasons that are psychologically understandable and financially damaging. The absence of a freelance track record feels like a reason to discount. It isn't. Your track record is your employment history and the quality of work you produced there. The fact that you haven't previously invoiced someone for it doesn't reduce its market value.

A usable starting point: take your employed annual salary, divide by the number of days you'd typically work in a year (around 220), and multiply by two. This gives you a day rate that begins to reflect the real overhead of working independently — the unpaid gaps between engagements, the self-employment costs, the holiday and sick pay you're no longer receiving, the pension contribution nobody is making for you automatically, the accountant you'll need, the professional insurance some clients will require. The multiplication isn't profit padding. It's the cost of being independent that your salary used to absorb invisibly.

The instinct to price below that number is strong and nearly universal among first-time freelancers. The logic goes: I haven't done this before, I should price conservatively until I've proven the model. The problem with this logic is that underpricing creates its own complications. Clients who engage at a low rate form expectations around it. Repricing later requires having the conversation your low original price was designed to avoid, with the additional awkwardness of doing it against an established precedent. And the financial pressure of underpriced work, during a period when you're also managing the other anxieties of the transition, is worse than the discomfort of holding a number you believe is fair.

The practical approach: name a number you believe is right, state it plainly, and give the client space to respond before you start negotiating against yourself. The instinct to fill the silence that follows a price quote with justifications and qualifications and alternative options is the thing that costs you the most. The number does not need defending until they push back on it. If they do push back, there's usually room to negotiate scope, payment terms, or timeline before reducing the rate itself.

What to say in the first outreach message

The terror of the outreach message comes from imagining it as a sales pitch — from thinking you need to convince someone of something, which requires deploying a kind of persuasion you've never had to use in a professional context before. The frame is wrong, and the terror comes from the frame.

When you're talking to someone who already knows your work, the outreach message is not a sales pitch. It's a change-of-status notification and a question. Something like this:

"I'm going freelance in [month]. I'll be doing [specific type of work] — similar to what I was doing at [company]. I wanted to reach out to people in my network who might have use for that kind of work, or who might know someone who does. Is there anything on your radar that might be a fit, or anyone you'd suggest I talk to?"

This works for several reasons. It's not asking for anything that feels like a favour. It's giving them information — you're now available — that is genuinely useful to them if they have a need. It provides them with an easy out (a referral rather than direct engagement) that removes the pressure of being the decision-maker. And it's short enough that it doesn't feel like a burden to receive or respond to.

What you're not doing: explaining your entire positioning strategy, listing all your services, attaching a rate card, or making the message so long that the recipient has to work out how to respond. The goal of the first message is a reply. The reply can go wherever it needs to go. The conversion happens in the conversation, not in the outreach message, and trying to front-load everything into the first contact usually prevents the reply from arriving at all.

How to handle the fear of rejection when you've never sold anything

The fear of sending these messages is disproportionate to what actually happens when you send them. This is close to universal among people who've been employed their entire career and are doing this for the first time, and understanding why the fear is disproportionate is more useful than trying to suppress it.

The fear isn't really about rejection — it's about what rejection means when selling is new. In employment, your competence was continuously validated by the structure. You passed the interview. You got the role. Your performance reviews confirmed you were meeting the bar. The system provided external proof of your capability on a regular cycle. In freelancing, every potential engagement starts from nothing, and the initial silence before a response carries personal weight in a way that a job application rejection usually doesn't — because this time, you asked. You put yourself forward as the thing being evaluated. That feels different from responding to an opening.

The reality of the first round of outreach is considerably less dramatic than the anticipation. Most people don't have work for you right now, will tell you so warmly, and will often suggest someone who might. A smaller number will say they might have something in the next quarter and want to stay in touch. A smaller number again will have something now. The "no" you're afraid of mostly doesn't arrive as a "no" — it arrives as timing ("not right now, but keep me posted"), or as a referral ("you should speak to X at Y"), or simply as silence, which means what silence always means: they're busy and it's not a current priority for them.

None of these are the crushing rejection the fear imagines. All of them are things you can work with. And the process of making the asks, receiving whatever comes back, and continuing to make more asks builds something that matters more than the first client: a working relationship with the discomfort of the ask that makes every subsequent ask easier. You don't learn this by reading about it. You learn it by doing it a few times and noticing that the world didn't end.

What the first engagement actually gives you

The first client is not just revenue. It's evidence — proof that the model works, that people will pay for your work outside the structure of employment, that the thing you've been afraid of is survivable. This is disproportionately valuable relative to its financial contribution, which is why getting the first one matters more than getting it at the optimal rate or on the best possible terms. A small engagement at a slightly low rate, delivering clearly to someone whose opinion you care about, is worth more than waiting six months for the perfect opportunity at the ideal price.

First engagements are also where you learn the things that can't be read in advance: what a client conversation feels like when you're setting the agenda rather than responding to one. What it actually feels like to invoice someone for a number you named. What the gap between project completion and payment involves in practice. What working without the structure of a team has that you didn't expect — and what it's missing that you didn't anticipate.

These are all learnable. None of them are as difficult as the first outreach message felt before you sent it. The freelancing life that comes after has its own complications and its own rewards, but almost all of them are downstream of the decision to make the first ask. That's the step that's actually paralysing. Everything after it, including the ones that go wrong, is something you can navigate.

The honest account of going freelance from burnout covers the first six months in detail — including the underpricing mistake and the isolation that hits harder than people expect. The PM to independent consultant piece has the detailed financial picture of the first 90 days that most accounts skip. And if you're still working out whether freelancing is the right move at all rather than just the available one, the five-question framework is a useful diagnostic before you start the outreach.