>> Just curious as to what bullet points *technically speaking* you might address (and certainly any other points you might raise to help sell your solution to the client).<<
Your experience with a vertical is probably stronger than mine, so take this for what it is. I would only discuss technology below the hood if the customer asks and understands it. My experience is the glazed-eye syndrome unless you are working with an IT person. Just yesterday I was trying to explain an index problem to a customer without using the word node. I would focus on the functional merits, the extensibility, the superior tech support, and the ability for the users to use today's standard reporting techniques to create ad-hoc reports. (provided these advantages exist) Depending on the level of technical expertise I might discuss backend databases, and the Web advantage from a usability point of view, not deep technical. Backups without being offline, offsite storage, remote server support, uptime, etc. I think most customers rarely care about Microsoft's support of any language, or the J2EE lifecycle (is there one?) with a vertical app. Just like most of users don't ask what language their word processor or spreadsheet are written in. I think they would care more about the MB Software Solutions support and lifecycle (do you have one published?). Rick White Light Computing, Inc. www.whitelightcomputing.com www.swfox.net www.rickschummer.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
