Live data from Hacker News

Ask HN: How did you land your first projects as a solo engineer/consultant?

news.ycombinator.com

21–30 of 165 posts

Re: Ask HN: How did you land your first projects as a solo engineer/consultant?

#21
*All* my work as a solo consultant/contractor was from former colleagues who needed "trusted pair of hands" to deal with a project, or former colleagues introducing me to new people.

People hire you because they want something done with zero hassle. It is a risk to go with someone you don't know or haven't had someone vouch for.

Re: Ask HN: How did you land your first projects as a solo engineer/consultant?

#22
As a consultant I got my first project through a former colleague who referred me to the organization looking for a consultant.

It's not easy to find consultations out of the blue, I have gotten one by apply to a public call looking for a consultant that I am in the being interviewed process now, but referrals are far more easier.

Re: Ask HN: How did you land your first projects as a solo engineer/consultant?

#23

*All* my work as a solo consultant/contractor was from former colleagues who needed "trusted pair of hands" to deal with a project, or former colleagues introducing me to new people. People hire you because they want something done with zero hassle. It is a risk to go with someone you don't know or haven't had someone vouch for.

[deleted]

Re: Ask HN: How did you land your first projects as a solo engineer/consultant?

#24
Absolutely easiest way is to find some consultant work sales agency that takes a commission when they manage to sell you somewhere. At least where I live there are multiple options, just list yourself (or your company) there.

Also you don't have to do the sales work yourself and they find suitable customers for you etc, it's totally worth the price especially if you are just starting

Re: Ask HN: How did you land your first projects as a solo engineer/consultant?

#25
Working as a feeelance consultant means you have to do marketing AND sales. (and backend paperwork as well). You need to be able to float through stretches of no work, and you need to be able to deal with clients who won't pay you.

Your product is yourself, so you start with brand building. What are your differentiators? (human) Networking is the most common way to market your services, but some write books, speak at conferences, have a substack, and blog too.

Setting rates and closing sales is another challenge. There are whole schools of materials to help with this.

Lastly remember you are trading your time for money. Your time includes the marketing, sales, and finance/taxes/billing. You may need liability insurance as well. With all that said your time is finite and not scalable - even if you charge top dollar there is a ceiling on how much you can make. Don't expect to get rich in this line of work by itself. (Side note: "ownership" - real estate, stocks, intellectual property, etc - are the scalable wealth builders)

I went down this route for a while, but ultimately decided I would rather just do the technical work and leave the rest to others.

Re: Ask HN: How did you land your first projects as a solo engineer/consultant?

#27
post #18

General consultancy is an extremely crowded space. As a startup CEO, I get at least 3 emails per week from software agencies and consultants. On top of that, they're usually located in India/Ukraine and the rates they offer are very low, so I assume it's very difficult to compete. My advice would be to differentiate yourself: - Become an expert in 1 thing, and one thing only: either start an open source project, or b…

Becoming an expert in one thing also narrows down the potential suitable work tremendously. Also these days nobody wants to pay the expert prices since.. Claude can so the expert stuff with a non-expert (at least in their mind)

This is a strong assertion that's directionally wrong. No matter the economy's state or any AI progress, experts are always searched for.

Re: Ask HN: How did you land your first projects as a solo engineer/consultant?

#28
Identify who your buyer is. It’s probably not a technical person (and thus HN isn’t a great place to advertise).

Talk to operational people if you are interested in finding operational pain. Tech teams will tell you they are working on it and don’t need help, or at best want to hire an IC. (If that’s what you want then just approach it as a job search)

For the same reason, hours are a bad unit of time and a bad giveaway. You want to be able to offer a free diagnostic or something - nobody’s waiting with operational pain and a plan to fix it that they want to start paying for. You need to help with the plan and show them what they need.

Just my $0.02 of course, circumstances may vary

Re: Ask HN: How did you land your first projects as a solo engineer/consultant?

#29
It's bedtime in Melbourne, but I write what would be fair to call a well-known tech blog, and very publicly started a consultancy about 1.5 years ago. Pretty much in the same niche you're in. We made enough money to pay two people full -time wages in the first year and I've cracked $1K per hour on some engagements (not many, and each one was Happy to have a chat if you drop me an email.

Re: Ask HN: How did you land your first projects as a solo engineer/consultant?

#30

General consultancy is an extremely crowded space. As a startup CEO, I get at least 3 emails per week from software agencies and consultants. On top of that, they're usually located in India/Ukraine and the rates they offer are very low, so I assume it's very difficult to compete. My advice would be to differentiate yourself: - Become an expert in 1 thing, and one thing only: either start an open source project, or b…

>>I get at least 3 emails per week from software agencies and consultants. On top of that, they're usually located in India/Ukraine and the rates they offer are very low, so I assume it's very difficult to compete.

One place hired me thinking I could fix some software they farmed out to India. I was not aware of that when they hired me. Afterwards they said they wanted it fixed in two weeks and fired me when I told them it wasn't possible. The software was in a language I'd never used on hardware I never programmed for.

They hired someone locally who was something of an expert in the area who claimed he could fix it in a month. It took him six months to fix the problems.

Lesson of hiring cheap overseas.

Post reply on HN