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.
I don't see anything in the OP asking for an extended semantic debate about the meaning of the word "consultant" or any problem any consultant has that could be solved by it.
Comments
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
Yeah but it gives people a warm and fuzzy. Just like companies hiring “senior software engineers with at least three years of experience”.
Writing software is an act of labor, not getting information or advice.
That definition just proves his point. Or am I missing something?
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.
I don't see anything in the OP asking for an extended semantic debate about the meaning of the word "consultant" or any problem any consultant has that could be solved by it.