>From reading the answers here - it appears there are 2 different cases. 1) if the customer just wants assurance they have the code if you go belly-up, or 2) if the customer wants the code for their internal use.
>
>If 1), I like the idea of putting the code in 'escrow' or whatever you call it for them. Might be an option you give to all your customers. Should you charge? I don't know.

Charges would be if they get the source code. I mean as long as we're there no charge. But if something happens to the company then they would have to pay.

>
>If 2), they split from you and have their own code base. You charge them for work on the application as an outside consultant. I think it would be impossible to incorporate changes you make on your version into theirs.
>
>-w-
>
>
>>A client asked us to have access to the source code of our app they are using.
>>
>>The thing is that this app is made for a vertical market. So there is no way that they'll get the source code right away.
>>
>>What would be the best thing to do for everyone is to make the source code available in case something happens to the company and that they end-up with nothing.
>>
>>That's the situation they want to avoid.
>>
>>Should they have to pay a premium because right now they pay for a fair amount considering that the app is also sold to other businesses. If they get the source code then it's another thing because then the amount they paid (license) would'nt seem to be enough to get all the source code.
>>
>>Now what do you think would be the best deal for everyone?
>>
>>What should be considered in that kind of deal?
>>
>>What kind of clauses?