>
There is some truth in terrys suggestion about positioning yourself as a solution provider and why should a client care what tool you use.
>
This reminds me of when VFP was included as part of Visual Studio. I recall the strategy then was to bill yourself as a "Visual Studio" Developer as opposed to being a VFP developer.
It did not work for two reasons:
1 - The VB folks continued to refer to themselves as VB developers and
2 - The custom software customers were not totally stupid to not ask the
logical follow up question - "Which tools in Visual Studio do you use?"
No question that developers should bill themselves as solution providers. That however - does not mean that at some point in the conversation - the tool is irrelevant.
If somebody thinks there is cross-elasticity in demand between VFP and other tools - he/she does not understand the true landscape of things.
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only