We are converging :) I guess it is just a matter of terms, I would have never called what you just described as a "software consultancy" since you mentioned bu

We are converging :) I guess it is just a matter of terms, I would have never called what you just described as a "software consultancy" since you mentioned building, developing, code reviewing and such terms a lot of times. By talking to you I understand that the meaning I give to the word "consultancy" is not as universal as I have thought. For me consultants never dive into anything "practical", they limit themselves to aspects of the software that stay all around the actual development. From my point of view you I would call you an experienced freelance developer, or a development agency (congrats on growing BTW, going from 0 to 1 employee is a big step). Mind that developing is not simply coding, so IMHO you are still a developer even if you "stay involved enough in the development of the rest that I can ensure what the team delivers is what the organization actually needs". You happen to advice your customers about stuff not strictly related to the actual development process, and that would be a consultancy, but it doesn't sound from all your comments that this is your main focus so from my strictly personal point of view I wouldn't call you a consultant. Developer: code, output, stuff that works and implements some business logic. Consultant: advices, indications, expectations... and then it is up to someone else to make it work. (and they don't care if ever, how, when, why, who) Anyway don't take it personally, and by the way I didn't mean to be disrespectful towards you. Maybe my first comment was a little harsh, so I'm sorry if you felt it as an attack on your person or your professionalism :D