Live data from Hacker News

Ask HN: How to Become a Consultant?

news.ycombinator.com

11–20 of 66 posts

Re: Ask HN: How to Become a Consultant?

#11
I have been doing this successfully for the last 8 years (and in the later years earning significantly more than I could as an employee in Europe) so hopefully my advice can help you.

You need to figure out if you just want to be an individual consultant or hire other staff. If you're looking to build out a business with employees it will be much more challenging as you will need to be a full time sales person, always making sure you have enough work in the pipeline to make sure they get paid, rule 1 is that staff always get paid before you.

I would suggest you find like minded individuals and partner up with them, that way when one of you has a bad week or you need a holiday the other/others can pick up the slack.

Seeing as you have so much experience you should be able to lean on previous employers / colleagues to get contracts, this is how we started out. Once you have a few projects under your belt and a decent website you will need to see if you're getting enough work by word of mouth from previous projects or if you need to invest in marketing. If you stay as a small team it will be much easier to do well via word of mouth if your quality of work is good. At the end of the day it's all about your network and driving quality projects into your business.

I would strongly discourage you from only bringing projects to the POC/MVP state. This is what we did initially but you need a far higher throughput of projects and you're in danger of leaving clients high and dry if they want the idea built out further.

That's how we got started anyway, best of luck with your venture!

Re: Ask HN: How to Become a Consultant?

#12
post #9

0) First step: read Jerry Weinberg "The Secret of Consulting" 1) Understand that Consultants solve problems when asked for against money. 2) People need to start asking you to solve their problems. So first step is to tell people that you have the potential to solve their problems. So I recommend to start giving talks on (virtual) meetups, start publishing in some way (articles, blogs, podcasts, newsletter, video) ei…

If someone wonders how to create massive value for a client in 1h, this is the way I do it https://medium.com/@franz.enzenhofer/the-systematic-1h-clien...

Re: Ask HN: How to Become a Consultant?

#13
> What I want to keep doing is getting projects from 0 to POC/MVP state

If you can reliably find this kind of work, then go for it. But what I've seen as a consultant is that everyone likes to do that part, but what clients usually want to contract for, and what makes money is the steady, often boring, implementation part.

Targeting the MVP work you are often competing with others who will heavily discount the initial work hoping to get the lucrative implementation. What makes it harder is the uncertainty involved, there is a high bar to being trusted enough contract for something that had not been defined yet.

In the management consulting world which I am more familiar with, the distinction is between "strategy" work - the focus of well reputed (in some circles) firms with very strong networks like McKinsey, and implementation or "transformation" type work from IBM or a Big 4. The dream is to be McKinsey and come in and demonstrate a brilliant plan that others are stuck implementing, but the reality is that that kind of work is tough to sell.

Re: Ask HN: How to Become a Consultant?

#14
I spent the last 4 years consulting, and I just last month deliberately wrapped up with my last two clients, because I know if I keep just stringing along on slow lingering projects with them I'll never get serious about finding a new fulltime job.

The people who tell you that this is as much about sales/marketing/relationships than any actual technical topic are so so right. When I started out I didn't deny that, I just didn't realize that its not an abstract concept you need to be open to, its a full third of your manhours you need to grind. You need to be contributing to open source, writing blogs, doing videos, helping out in community slacks, going to conferences, attending meetups, giving presentations/talks, etc constantly.

And thats just the background stuff. With your clients you need to relentlessly be the one who follows up, asks for work, ask for introductions, invites people to things, etc.

Then comes the "relationships" part of the work-dynamic, which is overwhelmingly one-sided (like most vendor relationships). You need to be the one who repeats yourself endlessly without getting frustrated, who doesn't take being ignored and schedule-bumped personally. Who politely handles not getting paid as an administrative kerfluffle not a rude form of apathy driven wage theft. You need to have dozens of conversations with people over and over about wether or not you are worth it to spend the money on for this project. Usually your direct contact will be kind enough to express shame over it, but its still an inevitable part of the multi-layer-management/budget-approval process.

Re: Ask HN: How to Become a Consultant?

#15
I’m a software engineering looking to work on a project of mine. I’m looking to learn from others’ software engineering experience. I am interested in learning from you. I would be happy getting on calls and paying per hour. Let’s discuss?

Side note: How do I find consultants for: React, React-Native, Node.js servers, Chat client-servers, and architecting/planning solutions?

Can there ever be a legal issue with me getting some knowledge from others and applying it in my work?

Re: Ask HN: How to Become a Consultant?

#17
post #10
post #3

Earlier quoted context omitted.

It is funny that you ask this, as I've just began [this][1] learning path on AWS. Having the knowledge is only half the story though. I'm not good at sales / finding business partners. I'm good at solving their problems. [1]: https://aws.amazon.com/partners/training/path-tech-pro/

Have you thought about working for a tech consulting firm? It probably won't pay as much as freelance, but you won't have to deal with sales and bookkeeping. Or: the other day there was this article here on HN about an agency for developers. I can't find it right now, I think the title was "The cost of the developer" or something like that, original article on The New Yorker, iirc.

https://www.newyorker.com/magazine/2014/11/24/programmers-pr...

Re: Ask HN: How to Become a Consultant?

#18
I submitted a link[0] of a Twitter thread to HN[1] explaining how we do it.

I often see this question pop up, either in the form of someone wanting to freelance, or someone asking about how to deal with clients. That thread has a few pointers and could be useful.

PS: For context, I live in Algiers, Algeria but we have a presence in Paris, France. All of our clients are in Europe. We make bespoke machine learning products for enterprise at different degrees of maturity (from "I want in on the AI stuff" to "we have an in house data science team but we need help" all the way to "we are an R&D arm, specialized in artificial intelligence, of a major group and I co-invented something you used to get here, how can you help us innovate faster?").

[0]: https://twitter.com/jugurthahadjar/status/131066829330549965...

[1]: https://news.ycombinator.com/item?id=24809257

Re: Ask HN: How to Become a Consultant?

#20
If you don't want to go through the added risk and uncertainty of trying to create and run your own business, you can get the parts of the job you seem to enjoy by looking for positions as a "Professional Services Engineer", which is usually a weighted blend of consulting, engineering, and sales (in that order). Professional Services Engineers also tend to be better compensated than their internal product engineering counterparts because the PS Engineers are closer to the revenue stream (their $$$ time is billable to the customer, and thus they're a revenue generator for the company), so it's often easier to justify and negotiate for higher comp. You also get to rapidly grow your network of people in industry, and if you're strategic about your relationships and on-site engagements, you can often establish rapport with executive level folks as well.

If I look back over my career, the single greatest accelerant along the arc from programmer to co-founder & CEO was my time spent learning, working, and networking as a PS engineer.

Post reply on HN