>>I'm afraid I agree with you. Too many red flags all around. If their current apps meet and exceed their customers' business needs and are still competitive, then there should not be an "ASAP" requirement for a re-write in .net. It's possible the customer is bright enough to consider future enhancements not supported by their current tool set and a dwindling developer resource though and is pushing for that reason alone. That still doesn't make an "ASAP" requirement. Not enough information was provided as to why the customer is behind this. It's also concerning that one customer is a major make or break for this business. Additionally, it's concerning that a business would retain a large portion of their workforce who may be considered "weak in their field." I wonder if this is a family run business or perhaps stuck back in the good old boys days...

Agreed. IMHO Neil has it right, but if he pushes too hard he'll make himself unpopular with people who are happy with the current simple answers... including the manager who made the decision and the developers who apparently don't want to take on anything too complex.

Perhaps the best option would be to sell the development company to the single customer, formalizing the reality of their relationship. Then the customer can invest as it pleases in what it wants to see happen and Neil's desire to review options may get more interest.

>>Haven't seen you around much lately -- have you been buried in the snow? :o)

Funnier than you think! I'm in the Midwest, not buried but we got an inch yesterday. ;-)