Right I work in both roles, I work as a consultant for the big wall street firms, where I do technical strategy consulting. This is where I look at a potential merger or acquisition and tell the decision makes that the technology strategy of the deal looks good or it does not. It is a paperwork job and I consider it to be true consulting. On the other hand I am hired by companies to build apps, many times they only have a rough idea of what they want. I call that freelancing, I am brought it to help them get to an app in all manners that they need, advise, code, data, server setup, etc. I see freelancing as the closest to generalist. Finally sometimes I get a call in which they will say we have all the specs, the system is designed and we just need someone that knows X to turn the design into a system. To me that is contracting and it is my least favorite out of the rolls I do.

Haha, I have often called myself a resultant because of the stigma. Over time I care less as I've gotten established and built a track record.

Still, sometimes I find myself saying "I solve business needs with technology." Means what it should to the people who will sign my cheques, and I don't care to explain what I do to anyone else.

Since a consultant isn't the first thing people might assume when they look at me, I think it's important to remember it just comes down to being likable, genuine, curious, responsible, and caring enough to follow through. Respect is my currency and assholes filter themselves out.

Actually, that's pretty much what consulting actually _is_. You dish out advice, they hand in the cash. You have to tailor your advice to them but they get to decide what to do in the end.