Hi WWJSBSNL, First of all, don't put your email addresses directly in a public post! You WILL regret it later. Second what you ask is really a what makes all the difference. How to sell the "add-on" module? Everybody (well most here in the forum) can make a great custom add-on module. Most developers I know have one or two "drawer-projects" or semi-ready add-on's, they have made at some point. Often a solution made for a specific customer, but good enough (?) to be come a product. You don't even need to have it approved. Just use the custom objects numbers, then the customer just need to buy those specific objects numbers (and you just have to hope they have not used the same numbers already). They have to pay Microsoft for whatever objects they need. The price for your "add-on" (your code) is a matter only between you and your customers. What SBHATBNG refers to are the Certified for Microsoft Dynamics add-ons. Here Microsoft has a long list of things you have to do in order for them to "approve it" and assign you your own objects numbers etc. Getting this certificate is not easy, takes months of work and preparations. And that's before you even start selling it. So why would you get it certified? Personally I would always recommend any of my customers only to buy CMD add-on's, unless it comes with a lot of good references. Simply because I have seen so much *** (sorry to say it). "Solutions" which were not really solutions, but merely a set of custom changes turned into an add-on, and never upgraded after 1 or 2 NAV releases. But as Seiferte writes it also means have a "brand" people will remember. Who will remember a product by someone who calls himself WWJSBSNL? Not really something to remember. [;)] If you really have a "fantastic add-on" all customers need, then I'm sure you can do it.
↧