> 2 ... tell the customer that you might consider converting it to delphi
and
> that you would like the input of one of the customers end users of the
> product to see if there are any minor features that could be tailored to
the
> customers requirements during the port. When you have the customers
> representative at your mercy, impress him/her with your product. Evaluate
> any changes they might require. Write a report with the *help* of the
> representative  Then send a leter to the boss indicating the price of the
> original product, the cost of adding the extra features using VB, the cost
> of porting the original product from VB to delphi and the cost of adding
the
> new features in delphi. Don't forget to add a copy of the report. If,
after
> this, he still wants it in delphi, tell him you have other commitments and
> that it will be several months before you can start the port..

I would double-negate the proposal, a pricing for delphi but a significant
discount if it is on VB.  Try swaying the customer to VB by offering
incentive.

But I would say it is on Delphi if it is on VB.  Without trust, you can
charge penny but there is no deal.  So treasure it.

Cheers, Ling SM

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu