Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The people who care about these distinctions are mostly within those three groups. For the customers it's 'consulting'.


I disagree - no one is calling large scale gov contractors such as Northrop Grumman, GDIT, CGI, CACI, many more etc. consultants - yet a lot of the IT work they do overlaps with the consultancies.

“Contractors” has become the more common term over time.


That’s definitely not true. I’ve worked for companies on the consulting side for five years.

We have two types of Statements of Work (SOWs) we get signed by the client. The first type and the only type I would ever get involved with are project based. The client has a business need but not the technical expertise. I come in right after sales and work with the business to tease out their requirements, get their sign off. We do the work and leave the project once the requirements are met.

With this type of SOW, we (I) lead the project technically, the project management etc and once the work is handed off, we move on. It’s outcome based.

The second type of contract is where the client has the technically expertise. But not the manpower. They then sign a contract with us to get $X number of people for $y hours with the expertise they need. The client controls what gets done and when. They handle the project management. This is your typical staff augmentation.


Too later for an edit, but: The point of this whole scheme is trading OpEx for (on the books) CapEx.


Not at all. I buy these services in a large Fortune 500. Consulting is the least used model for us.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: