> give them a TW course with everything exposed, I essentially give them > a template that they could run with or farm out to another > consultant. So they could use me - only once. I'd stand a big risk > of losing downstream development with that scenario.
Is the rationale for using closed source "to force customers to stay"? Open source profit is not made by restricting access to the source... it's made by adding distinct and unique value to the deliverables (such as superior design, custom features, robust error handling, high- quality documentation, and responsive support services). It seems to me that if your customer is likely to dump you after the initial delivery just because the source is open, then you haven't made the 'value proposition' of your consulting services clear to them... or they are just cheap and have weak business ethics. In any case, the solution may be to focus on social engineering instead of software engineering, in order develop a more cooperative business relationship with your clients (or find better clients), rather than taking an adversarial stance by reverting to a 'old school' closed-source model to force your clients to behave as you want them to. -e --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/TiddlyWiki?hl=en -~----------~----~----~----~------~----~------~--~---
