News for hackers. Stuff that matters.
Re:To become a software consultant, avoid letting clients pa... by tptacek on Tuesday October 16, 2018 @11:34AM (#18230181)
This notion of the distinction between contractors and consultants as a career status strikes me as similar to the distinction we make between developer and manager. And then, this is useful advice if what you want to do is manage, and code less.

I've been consulting professionally since 2005, and I think I've gotten pretty good at it? And my take on this is, graduating from "IC" to "manager" in the eyes of your client is presumably one way to ratchet up your status. But there are others, and I think they can be more lucrative.

Two straightforward alternative approaches to leveling up a consulting business that you've started by freelancing IC-type work:

1. Scale it out. Take on more work, find trusted people to subcontract it out to, eventually bring on a partner, standardize and methodologize what you do, get to the point where you can train other people to do it, start hiring people. You will probably find that when you get to the point of hiring consultants to work for you, your business accelerates naturally --- one of the most overlooked and important value components of most consulting businesses is on-demand availability, which is expands as your roster does.

2. Specialize. Start looking for commonalities between the projects that you do. Build tooling for them. Maybe publish some open source stuff. Build a specialty practice around that. You can do this repeatedly, for different areas; eventually, you'll do it for business verticals. In both kinds of cases you'll find that you become attractive to different kinds of companies when you change from generic to specific.

In neither case do you stop coding, or reposition yourself from the kind of company that writes code to the kind of company that tells other people how to write code.

We agree about hourly billing, though!

Re:To become a software consultant, avoid letting clients pa... by vram22 on Tuesday October 16, 2018 @01:27PM (#18231267)
>2. Specialize. Start looking for commonalities between the projects that you do. Build tooling for them. Maybe publish some open source stuff. Build a specialty practice around that. You can do this repeatedly, for different areas; eventually, you'll do it for business verticals.

A former manager of mine, who had some consulting background, once told me that the big management consulting firms like McKinsey do something like this. They compile tons of detailed case studies from former engagements (that's what consulting gigs are called in that field) and then reuse the hell out of them for new gigs, thereby saving a lot of their staff's working time on those. Also probably surprise the clients (who may not know about this practice) by being able to come up with results sooner due to this.

Re:To become a software consultant, avoid letting clients pa... by 121789 on Tuesday October 16, 2018 @03:05PM (#18232196)
Haha, I was a consultant and you paint a very idealistic picture of the situation. It usually went something like this in my experience:

1. Partner hears client is interested in a certain type of engagement

2. Partner promises that their firm has extensive expertise in the area

3. Partner commits to writing a proposal for the potential project

4. Lower level staff scramble to talk to other consultants in their firm (same industry) and dig through old case studies to figure out if #2 is actually true

5. Staff hurriedly compiles a proposal deck from a mish-mash of slides from other projects that are mildly relevant

6. Multiple iterative feedback loops where the partner gives vague suggestions on improvements and staff makes the changes

7. Send finalized proposal to design/production team

If you win the proposal, you use some lead time before the project to build an approach using past projects. In rare cases there would be a firm-sponsored template or framework (often when there is associated whitepapers or other marketing materials), but in general the situation was a more reactive "I do not have time to start this from scratch, so what can I gather from past projects?" and less of a proactive "let's build a template to reuse for new projects"

Re:To become a software consultant, avoid letting clients pa... by vram22 on Tuesday October 16, 2018 @03:59PM (#18232709)
>Haha, I was a consultant and you paint a very idealistic picture of the situation. It usually went something like this in my experience:

1. I did not claim to "paint" the full picture. 2. I did not paint the picture. Was saying what my ex-manager said to me. 3. The plural of anecdote is not data.

Interesting to hear of your experience, though.

Regardless of your experience, systematically collecting and analyzing data on prior projects, with a view to applying the learning to future ones, is useful, for any discipline, not just management consulting or software engineering. That's part of how progress in any field happens.

Re:To become a software consultant, avoid letting clients pa... by vram22 on Tuesday October 16, 2018 @04:01PM (#18232723)
Also, I'm well aware of the "golmaal" (Hindi slang term) that goes on in any field. Hey, it's common knowledge. But that does not invalidate work of the good actors in the field.
Re:To become a software consultant, avoid letting clients pa... by vram22 on Wednesday October 17, 2018 @10:24AM (#18239349)
Sorry, I didn't explain what golmaal means in English, also may have used the wrong word. I meant something like skullduggery, but golmaal means chaos or confusion (according to Quora, at least).
Re:To become a software consultant, avoid letting clients pa... by vxNsr on Tuesday October 16, 2018 @03:50PM (#18232604)
I think it comes to the same thing, as I start to try and get ventures off the ground I'm finding that there's nothing like experience to improve your chances of success. Put another way: 90% of success is being successful.
Re:To become a software consultant, avoid letting clients pa... by 01100011 on Tuesday October 16, 2018 @12:29PM (#18230688)
I think the biggest failures at the software consulting houses I've worked at have come from not building adequate tooling and not establishing a framework for knowledge/skills transfer. A close runner up would be failures related to trying to build actual products. The problem with consulting though is scalability. You can make a product and recoup your NRE with the first x units, and then most of what you sell beyond that is pure profit which can roll in while you sleep. Scaling a consulting business is tough. You just have to increase billable hours and that is a lot tougher than it sounds(especially in the current market).

I made a lot of money in consulting over the years, but at the middle of my career I find myself looking for a product company to call home. Consulting can be great... or it can be terrible. My friend is now charging $165/hr for his solo corp... but sometimes the invoices never get paid and you have to swallow a loss(I'm owed over $14k currently and will probably never see it).

Re:To become a software consultant, avoid letting clients pa... by tptacek on Tuesday October 16, 2018 @02:26PM (#18231866)
$165/hr is not particularly high (in addition to the fact: don't bill hourly). A $3200 day is not unusually high.

Product development is in some ways more gratifying than consulting. But consulting has its own rewards, too.

Re:To become a software consultant, avoid letting clients pa... by 01100011 on Tuesday October 16, 2018 @08:15PM (#18234438)
Sure, you could charge a lot more depending on your role and resume. My friend is getting $165/hr doing Sr. Software work, writing code for satellites. It's a steady 40ish hour/week role, so I think that, compared to salaried senior devs in the area(i.e. not silicon valley or NYC), he's doing quite well.

For comparison, I know a local engineering staffing/design services firm that charges $200/hr for principal engineer time. You're getting more out of that sort of company though.

Re:To become a software consultant, avoid letting clients pa... by mrhappyunhappy on Wednesday October 17, 2018 @03:22AM (#18236878)
Seems backwards, your friend should be the one making 200+
Re:To become a software consultant, avoid letting clients pa... by 01100011 on Wednesday October 17, 2018 @05:17PM (#18243897)
Why? He doesn't have to pay a sales team, marketing department, IT guy, etc. He also doesn't have a building full of engineers who he can query if he runs into something he can't handle. I would never pay an individual, regardless of whether or not they're a corp, more than I'd pay a company which provides engineering talent.
Re:To become a software consultant, avoid letting clients pa... by tptacek on Wednesday October 17, 2018 @08:13PM (#18244954)
Not that the specific number is worth litigating, but worth mentioning: a sales team, marketing department, IT guy, and all that are part of the competing consultants cost basis, and not so much the value they offer clients. Unless you're selling gypsum, for the most part, nobody is buying based on your cost basis. You're either doing something worth $X, or you're not.
Re:To become a software consultant, avoid letting clients pa... by 01100011 on Wednesday October 17, 2018 @11:01PM (#18245600)
Not going to litigate the number but I will say that sales teams often do add value. They provide a human point of contact to escalate issues and manage customer expectations. They also may act as a single point of contact for flexible staffing needs - i.e. if they need a second body to meet a schedule, they don't have to hit the open market but can simply buy more engineering talent.

That said, I've often felt like the sales team doesn't provide much value. It depends on the company.

I will say though that companies are generally more comfortable paying a higher rate to another company vs. one guy working out of his house. There is a greater expectation of responsibility. Also, many companies will not even deal with you as an individual corporation unless certain rules are met. One rule might be that no more than, say, 30% of your income can come from the company looking to hire you. They want to see a diverse revenue stream and a well established business.

Re:To become a software consultant, avoid letting clients pa... by toyg on Tuesday October 16, 2018 @02:57PM (#18232139)
I’ve just started out in a niche that I thought richer than average, and I charge less than a third of that.

Where have you seen people charging that much?

Re:To become a software consultant, avoid letting clients pa... by mrhappyunhappy on Wednesday October 17, 2018 @02:33AM (#18236638)
$3200 per day? Where do I find those people... This is Dev consulting?
Re:To become a software consultant, avoid letting clients pa... by 01100011 on Wednesday October 17, 2018 @05:18PM (#18243903)
Yeah, I call bullshit. Unless you're one of the top 1% of engineers in the valley or in FinTech you're not getting near that.
Re:To become a software consultant, avoid letting clients pa... by tptacek on Wednesday October 17, 2018 @08:13PM (#18244957)
Yeah, you're wrong about this, and I'm not just talking about my own field.
Re:To become a software consultant, avoid letting clients pa... by 01100011 on Wednesday October 17, 2018 @11:02PM (#18245608)
That's fine, but I'm not buying it without evidence. I don't expect you to bend over backwards trying to convince a stranger on the internet so I think we're done discussing it.
Re:To become a software consultant, avoid letting clients pa... by tptacek on Friday October 19, 2018 @11:43PM (#18261650)
Well, for starters, that number is less than my bill rate was at NCC.