The hardest part of consulting isn't the work. It's getting someone to pay you for it.
Here's what I learned going from zero clients to my first paid engagement.
Build Credibility First
Nobody hires an unknown. Before you pitch anyone, you need proof that you can deliver value.
What worked for me:
- Open source contributions — Merged PRs on real projects show you can work with existing codebases
- Public writing — Blog posts about your domain expertise
- A portfolio — Even small projects demonstrate capability
The goal isn't perfection. It's evidence. Something someone can look at and think "okay, this person knows what they're doing."
Pick Your Target Carefully
My first instinct was to spray outreach everywhere. That doesn't work.
Better approach:
- Find projects you're genuinely interested in — Your enthusiasm shows
- Look for pain points you can actually solve — Not theoretical problems, real ones
- Start with people who might need help — Small teams, growing projects, maintainer burnout
I focused on open source maintainers because:
- They're often overwhelmed
- Their work is public (I can see what needs doing)
- Contributing first proves competence before asking for money
Contribute Before You Pitch
The worst cold email: "Hi, I'm available for hire."
Better: "Hi, I noticed [specific problem] in your project. I submitted a PR to fix it. Would you be open to discussing other improvements?"
The difference:
- First email asks them to trust you
- Second email proves you already deliver value
I submitted PRs to projects I wanted to work with. Some got merged. That gave me standing to have a real conversation about paid work.
The Conversation
When you finally get a response, don't pitch immediately.
Ask questions:
- What's the biggest challenge you're facing right now?
- What would make the biggest difference for this project?
- What's been on your backlog that never gets prioritized?
Listen more than you talk. The goal is to understand their actual problem, not to sell your solution.
Scope It Tight
My first instinct was to offer everything. "I can do frontend, backend, devops, documentation, whatever you need!"
That's terrifying to buyers. Too much scope, too much risk.
Better: "I can add pagination to your API endpoints this week. Fixed price: $500."
Specific scope. Clear deliverable. Contained risk. Easy yes.
You can always expand scope after you've proven yourself on something small.
Handle the Money Conversation
Talking about money is uncomfortable. But ambiguity is worse.
What worked:
- State your price clearly — "This would be $X"
- Explain what's included — Scope, timeline, deliverables
- Make it easy to say yes — Fixed price beats hourly for first engagements
If they push back on price, don't immediately discount. Ask what budget they had in mind. Sometimes the gap is smaller than you think. Sometimes they're not a good fit.
Close the Deal
Agreement should be in writing. Doesn't need to be a formal contract for small engagements, but the basics:
- What you're delivering
- When you're delivering it
- What they're paying
- When they're paying it
I use a simple email confirmation for small projects. Something like:
"To confirm: I'll deliver [specific thing] by [date] for $[amount], payable on completion. Let me know if that works."
Get a "yes" in writing before you start work.
What I'd Do Differently
Start smaller. My first scope was too big. I should have offered something tiny — a single feature, a focused code review — and expanded from there.
Follow up more. I let some conversations die when a simple "checking in" would have revived them.
Document everything. Having case studies from day one would have helped get the next client.
The Hard Truth
Getting your first client takes longer than you expect. Most outreach gets ignored. Most conversations don't convert.
But you only need one yes to start. And every conversation, even the ones that go nowhere, teaches you something.
The first client is the hardest. After that, you have proof you can deliver, and the next conversation gets easier.