3 ms·

My experience with shorter versus longer jobs, in the tech industry, consulting a few years back: - 30-60 minute consultations, I need to charge $600/hour mini

by blagie 4y ago

My experience with shorter versus longer jobs, in the tech industry, consulting a few years back: - 30-60 minute consultations, I need to charge $600/hour minimum to make ends meet - 1-2 week gigs, I need to charge $300/hour minimum to make ends meet - 6-36 month gigs, I need to charge $100/hour minimum to make ends meet Making ends meet means covering mortgage, health care, etc., not having a decent lifestyle. There is overhead to: - Finding clients - Billing - Cancellations - Marketing - Commuting - Networking - Contracts / legal Etc. All of that overhead goes down with longer jobs. I don't feel that "longer jobs" are the root culprit here. If I were to guess, the root problem is that anyone can do carpentry (poorly). That sets low expectations on prices. That keeps better tradespeople out, since you can make so much more in any of the other trades.

ricardobayes 4y ago
Any tips on how to get into software consultancy?
- blagie 4y ago
  This will sound flippant, but know people. You don't need to know them well. Former bosses, workers, etc. are fine. In a tight job market, many will be looking for people. Random recruiters are fine too. If someone's calling you up to recruit, you can let them know you're not open to employment, but glad to consult. Many companies will be open to both. Indeed, consultants are cheaper on taxes and benefits, and easier to let go, so there are a lot of wins for the company. . The bigger question is whether you should consult. Why do you want to get into it?
- jlevers 4y ago
  disclaimer: i've only been doing this for a couple years...but it's gone pretty well. i've written this more like a story than direct advice, because i think all the twists and turns are relevant. i went straight from college (dropout) into the consulting world right before COVID hit. i gave myself a year to get the consulting business going, and if that didn't work, i was planning to get a "real job." i started off by leveraging my existing contacts in the software world: mostly a couple internships that I'd had (one before my year of college, one after). the first few months, i was only working for those two places while i tried to figure out how to expand. i started a blog [0] at this point -- it was mostly nontechnical content, but helped me demonstrate that i'm a sane person and a reasonably good communicator. i started replying to the "Who wants to be hired?" threads here on HN and got my first couple (small) independent contracts there. then a family friend who runs a high-volume used book business needed his whole inventory/order management system redone from scratch, and i was a) cheaper and b) a known quantity, so he hired me. you can interpret this as me getting lucky, and in some sense it is, but i strongly believe that luck favors the prepared. i certainly wouldn't have gotten that gig if i hadn't been prepping for it, hard. this is when i started to raise my rates. (you've probably seen this repeated endlessly on HN, but it bears repeating: raise your rates. raise your rates. and then raise them again. to match $XX/hr as a FTE, you need to charge at least 2*$XX/hr as a consultant. ideally a lot more.) i spent tons of time reading HN and twitter, and responding to anyone who was doing something i found interesting. i went into these interactions with no expectation of getting work out of it -- i just wanted to meet people who were working on cool things. a few of those interactions did turn into work, and one person i met is now one of my best IRL friends. crazy. at some point, i had to learn about a new amazon service (the Selling Partner API) for that bookstore project, and discovered just how badly documented and tested it was. after a couple months (!!) figuring out how to use it properly, i wrote a few blog posts about it, and people started hiring me from my blog (and now, my OSS SP API library [1]). between that, and a few of those people i talked about meeting via HN/twitter/etc, i've kept busy for the past 18 months. i actually just hired my first part-time employee, which is exciting :) i think the three biggest things that have made me a modestly successful consultant are: 1. focusing on people over everything else. if you're a consultant, you're a salesperson, and in my experience just being genuinely interested in other people is the easiest and most effective form of sales. 2. writing online. it's cliched, but it works. you don't need that many people to see what you've written for it to be worth it -- i've never gotten more than 150 views in a day on my blog, and usually it's way less than that, but that's been enough to have plenty of work. 3. raising my prices ;) i make a lot less money than i might by working for FAANG/etc, but i have total time and location freedom, i don't work a ton, and i really enjoy running my own show. ymmv, and good luck :) [0] https://jesseevers.com https://jesseevers.com [1] https://github.com/jlevers/selling-partner-api https://github.com/jlevers/selling-partner-api
iancmceachern 4y ago
Another experienced consultant/contractor here and this 100%. The time overhead is what kills you, spending hours to get an hour of payable work is different than spending hours to get 18 months of billable work. And spending hours of work just to not get the project is common. It's why actors have agents, if they had to market themselves they'd have no time for acting.

by blagie 4y ago

ricardobayes 4y ago

Any tips on how to get into software consultancy?

blagie 4y ago
This will sound flippant, but know people. You don't need to know them well. Former bosses, workers, etc. are fine. In a tight job market, many will be looking for people. Random recruiters are fine too. If someone's calling you up to recruit, you can let them know you're not open to employment, but glad to consult. Many companies will be open to both. Indeed, consultants are cheaper on taxes and benefits, and easier to let go, so there are a lot of wins for the company. . The bigger question is whether you should consult. Why do you want to get into it?
jlevers 4y ago
disclaimer: i've only been doing this for a couple years...but it's gone pretty well. i've written this more like a story than direct advice, because i think all the twists and turns are relevant. i went straight from college (dropout) into the consulting world right before COVID hit. i gave myself a year to get the consulting business going, and if that didn't work, i was planning to get a "real job." i started off by leveraging my existing contacts in the software world: mostly a couple internships that I'd had (one before my year of college, one after). the first few months, i was only working for those two places while i tried to figure out how to expand. i started a blog [0] at this point -- it was mostly nontechnical content, but helped me demonstrate that i'm a sane person and a reasonably good communicator. i started replying to the "Who wants to be hired?" threads here on HN and got my first couple (small) independent contracts there. then a family friend who runs a high-volume used book business needed his whole inventory/order management system redone from scratch, and i was a) cheaper and b) a known quantity, so he hired me. you can interpret this as me getting lucky, and in some sense it is, but i strongly believe that luck favors the prepared. i certainly wouldn't have gotten that gig if i hadn't been prepping for it, hard. this is when i started to raise my rates. (you've probably seen this repeated endlessly on HN, but it bears repeating: raise your rates. raise your rates. and then raise them again. to match $XX/hr as a FTE, you need to charge at least 2*$XX/hr as a consultant. ideally a lot more.) i spent tons of time reading HN and twitter, and responding to anyone who was doing something i found interesting. i went into these interactions with no expectation of getting work out of it -- i just wanted to meet people who were working on cool things. a few of those interactions did turn into work, and one person i met is now one of my best IRL friends. crazy. at some point, i had to learn about a new amazon service (the Selling Partner API) for that bookstore project, and discovered just how badly documented and tested it was. after a couple months (!!) figuring out how to use it properly, i wrote a few blog posts about it, and people started hiring me from my blog (and now, my OSS SP API library [1]). between that, and a few of those people i talked about meeting via HN/twitter/etc, i've kept busy for the past 18 months. i actually just hired my first part-time employee, which is exciting :) i think the three biggest things that have made me a modestly successful consultant are: 1. focusing on people over everything else. if you're a consultant, you're a salesperson, and in my experience just being genuinely interested in other people is the easiest and most effective form of sales. 2. writing online. it's cliched, but it works. you don't need that many people to see what you've written for it to be worth it -- i've never gotten more than 150 views in a day on my blog, and usually it's way less than that, but that's been enough to have plenty of work. 3. raising my prices ;) i make a lot less money than i might by working for FAANG/etc, but i have total time and location freedom, i don't work a ton, and i really enjoy running my own show. ymmv, and good luck :) [0] https://jesseevers.com https://jesseevers.com [1] https://github.com/jlevers/selling-partner-api https://github.com/jlevers/selling-partner-api

iancmceachern 4y ago

Another experienced consultant/contractor here and this 100%. The time overhead is what kills you, spending hours to get an hour of payable work is different than spending hours to get 18 months of billable work. And spending hours of work just to not get the project is common. It's why actors have agents, if they had to market themselves they'd have no time for acting.