Live data from Hacker News

Ask HN: Resources/Steps for Becoming a Consultant?

news.ycombinator.com

31–40 of 116 posts

Re: Ask HN: Resources/Steps for Becoming a Consultant?

#31
Take a break, honestly. A lot of people seem to be of the opinion that if you don't work your life will start to implode around you.

I've just started my first consulting job via a friend I used to work with. I was 10 months unemployed, living in an exotic country, enjoying myself and building out my own projects. I only ended up taking the job because the pay was good.

Whilst I've been doing my own thing I've met a lot of 'digital nomads.' They all do interesting things and the stories of how they got there are all different. And if they don't like it anymore, they can stop at any time.

In short, there's other options than diving from a job that's burnt you out straight into a consulting gig.

Re: Ask HN: Resources/Steps for Becoming a Consultant?

#33
post #27

Earlier quoted context omitted.

Read every single article on daedtech.com related to software consulting (and maybe some that aren't) -- the amount of insight contained inside those articles for free is insane. 99% of the people who think they are doing consulting (me included) are not doing consulting. If you're getting paid to write software, you're not a consultant, you're a freelancer/service provider. Let those words shake you then read all th…

> If you're getting paid to write software, you're not a consultant, you're a freelancer/service provider. That's by definition: consult verb (used with object): to get information or advice from a person, book, etc. with special knowledge on a particular subject https://dictionary.cambridge.org/dictionary/english/consult

You're right that it's very obviously in the definition of the rowds and should be this simple to classify "software consultancy" by definition, but that's not what's out there in practice.

How people use (in this case misuse) the term leads to confusion and the linked article (and the other related ones) starts with this fact as the baseline (we're in agreement) and goes into how/why software shops are doing it wrong/mislabeling themselves, and how you can stop doing that. It seems to be exactly what OP is looking for.

Re: Ask HN: Resources/Steps for Becoming a Consultant?

#34
The hardest part for me was learning how to spot good clients from bad clients. Reading the "Win without pitching" manifesto"[1] transformed my business (I'm not affiliated in any way).

"Breaking the time barrier"[2] is also a good book I wish to have found earlier.

[1] https://www.winwithoutpitching.com/the-manifesto/

[2] https://www.freshbooks.com/fbstaticprod-uploads/public-websi...

Re: Ask HN: Resources/Steps for Becoming a Consultant?

#35

Depending on skills you can earn a magnificent hourly rate in comparison to full-time employment and have more freedom in the types of projects you pick. Location matters a lot though. Be ready to jump on a plane / train to discuss with potential clients. It takes a lot of grit especially if you build your own client base and wish to avoid middle-men who broker to the larger companies. For larger firms though you won…

I’m an independent consultant and am on the supplier list for a Fortune 10 company. If your client is a decision maker at the company and they value your service enough, then they will get you on the list.

Re: Ask HN: Resources/Steps for Becoming a Consultant?

#37
Sorry to say, it looks like you're approaching this backwards.

You shouldn't be looking for resources, steps, advice, pitfalls, experiences, or anything else.

You should be looking for a customer whose hair is on fire.

Then, and only then, should you be looking for whatever it takes to build them a fire extinguisher. Anything else is a waste of time.

Re: Ask HN: Resources/Steps for Becoming a Consultant?

#38

>In the pin factory, when learning comes first, we neither expect nor want the workers to improvise on any aspect of the product, except to produce it more efficiently. Sounds like a Dickensian nightmare to me. I would have thought some of the best placed people to suggest improvements are the people who build the pins, second only to people who use the pins every day. Stay classy HBR.

You wouldn't want them to be improvising while on the assembly line. You want their feedback, just not while they're supposed to be making pins.

If they're in a position where they need to be improvising in order to make pins correctly or efficiently, that's a bad sign.

Post reply on HN