Getting Your First Client With No Network

"I have no network" is almost always false.

Open your phone. Count the people you've worked with, studied with, interned alongside, shipped something for, or answered a technical question for. Most developers land somewhere near forty. Then count how many of those forty know, in one specific sentence, what you currently sell. For most people the answer is zero.

That gap is the entire problem. It isn't a marketing problem, it isn't a personal-brand problem, and it is definitely not solved by sending three hundred cold emails. Here are the channels I've actually used, ranked by how well they converted, best first.

1. People who already know you can ship

Nothing else is close enough to be on the same chart.

Former colleagues, founders you contracted for, the senior engineer who reviewed your PRs at an internship, the friend who is now employee number four somewhere. These people have already watched you finish something. They aren't evaluating your skill, they're checking your availability.

My first paid month as an independent came from exactly one message to a former colleague. Not a pitch. Just this shape:

Hey, I've gone independent as of March. I build AI products and mobile apps end to end, mostly Next.js, React Native and AWS. If you hear of anyone who needs that, I'd appreciate the forward. No rush, and happy to return the favour.

Three things make it work. It states the change, it says what you do in words a non-engineer can repeat, and it asks for a forward rather than a job. Nobody has a job to give you. Plenty of people have a forward.

I sent that to about twenty-five people over two weeks. Nine replied. Two turned into work inside six weeks, one of them a $6,000 project. That conversion rate does not exist anywhere else on this list.

2. Communities where your clients are, not where developers are

I spent my early evenings in developer Discords. Lovely people, zero buying intent. Developers are your peers, not your market.

The shift that mattered was being present where founders talk about their problems. Indie hacker forums, startup meetups in Hyderabad, coworking common rooms in Da Nang and Bangkok, small founder Slack groups. One of my current clients came from a conversation over bad coffee in a coworking kitchen, which is not a strategy you can put in a spreadsheet but is a reason to leave the apartment.

The rule: answer questions, don't advertise. Being visibly useful about a problem is a sales call that doesn't feel like one.

3. Writing in public

Slow, compounding, and worth starting before you need it.

Writing is the only channel where a stranger can evaluate your judgement rather than your logo collection. A post explaining why an AWS bill triples, or how you'd choose between two mobile frameworks, does what a portfolio thumbnail cannot: it shows the reasoning a client is actually hiring.

The honest caveat is timing. My writing has produced enquiries, but months after publishing and never on demand. Treat it as an asset you build during quiet weeks, not a lever you pull when the pipeline is empty.

4. Small open-source and technical contributions

A fix in a library your target clients use, a well-written issue, a working sample repo for an SDK with terrible docs.

Low volume, high quality, because anyone who finds you this way already knows you can read code you didn't write. I've had exactly one enquiry from this route. It was from a technical founder and it was the easiest sales conversation I've had, because there was nothing left to prove.

Don't do it as marketing. It reads as marketing and it doesn't work. Do it because you needed the fix anyway.

5. Job boards, Upwork, and the marketplaces

The honest case for them is narrower than the courses claim.

Marketplaces are bad at rates and good at proof. If you've never delivered for a stranger who found you online, a couple of platform projects give you reviews, a track record, and the experience of scoping for someone who owes you no goodwill.

What they won't give you is your rate. The bidding structure pushes prices toward whoever needs the money most, and that isn't you if you're doing this properly. I treated them as a training ground and left. If you're still there a year in, something upstream has gone wrong.

6. Cold outreach

Last, and I'll be blunt about the numbers, because the internet lies about this constantly.

In my first weeks I sent about sixty researched cold emails. Four replies. Two calls. Zero clients. That's not a disaster, it's just what cold email does when you have no reputation attached to your name.

It works at all only when it is specific. The difference is entirely in the first line:

Dead on arrival: "Hi, I'm a passionate full-stack developer with experience in React, Node, and AWS. I'd love to help you grow your business."

Gets a reply sometimes: "Your signup flow drops the user on a blank screen after email verification on mobile Safari. I recorded it, 40 seconds, link below. I build React Native and Next.js apps, and I fixed something similar for another travel product last year. Want me to send the two other things I noticed?"

The second is an observation, not an introduction. You did work before asking for work. That's the whole trick, and it's why cold outreach doesn't scale: doing it properly takes twenty minutes per prospect, which means fifteen good emails beat sixty generic ones.

What the ranking actually says

Look at the order. The top of this list is entirely people, and the bottom is entirely strangers. Every channel here is really the same channel at different temperatures, and your job in the first year is to move as much of your pipeline up the list as you can.

Which is also the honest answer to "how do I get my first client with no network." You don't build a network from scratch. You go tell the one you already have what you do, in a sentence they can forward, and then you make sure that when they do forward it, the thing they land on is worth the click.

I was terrified of the "where do clients come from" question before I left my job in March. The answer turned out to be embarrassingly boring. They came from people who had already seen me finish something, and the only real work was reminding them I existed.