Finding your first clients

The first freelance project almost never arrives through a form on a website. It arrives through somebody who already knows what you are like to work with — an old colleague, a person you helped in a community thread, a friend of a friend who overheard that you build things. That is uncomfortable if you were hoping for a marketing funnel, but it is good news: it means the work starts long before anybody is paying you.

So make yourself findable in the places where that recognition happens. Write down what you fixed and how, in public, in plain language. A short post about a rendering bug you chased for two days is worth more than a page of adjectives about your process, because it lets a stranger imagine you inside their problem. Three of my first five projects came from posts I nearly did not publish.

Be specific about what you do. “Full-stack developer available for projects” is invisible; “I rebuild slow product dashboards so they load in under a second” is a sentence somebody can forward to their manager. Narrowing feels like closing doors, but in practice it is the only way to be the obvious choice for anyone at all. You can widen later, once the referrals are steady.

Price the first project so you can afford to do it properly. Underpricing does not win goodwill — it buys you a rushed job, a tired week and a portfolio piece you are not proud of. Quote a number that lets you sleep, write down what is included, and say plainly what is not. Clients rarely argue with clarity; they argue with surprises.

Then treat the first project as the marketing for the second. Most of the reasons people come back have nothing to do with code.

What actually earns the second project

Answer quickly, even when the answer is “I will look at this tomorrow morning”. The single most common compliment freelancers get is not about architecture; it is that somebody replied. Silence is the thing clients remember, and it is free to fix.

Show progress before it is finished. A short screen recording halfway through the week costs you ten minutes and removes the low background anxiety that comes with paying somebody you cannot see working. It also catches misunderstandings while they are still cheap to correct.

Write the boring documents. A one-page scope, a short weekly note, a handover file explaining how to deploy — none of it is billable in an obvious way, and all of it is the reason a client describes you as easy to work with. That description is what gets repeated to other people.

Finish properly. Remove the dead code, leave the repository in a state somebody else can pick up, and send a final note that says what was delivered and what you would look at next. The last impression is the one that gets quoted in a referral six months later.

And keep the door open without being needy. A short message when you ship something relevant, or when you notice their product changed, is enough. Most of my repeat work came from a two-line note sent at exactly the moment somebody was about to start looking for help — and had not got around to it yet.