4 ms·

When you are first starting out white-label offers can be enticing to say the least. I have not heard of any companies doing them recently though. Most of the t

When you are first starting out white-label offers can be enticing to say the least. I have not heard of any companies doing them recently though. Most of the time, white label is common in the hosting/web-based service (i.e. email/project management/support companies). Like ecommando said, don't get sucked into it though, unless you can control every aspect of the deal, code, database, etc... As the white-label grows they will expect the world from you in terms of support/updates/code modifications/etc... They will take away from your time to support your own customers. I would offer a hybrid solution at most where you allow them to change the logo and remove references to your company, but you continue to host and control the code. To answer your question on why they wouldn't pay/use, well it is all about marketing. They want to be able to offer something different from their competitors and make it look like they are the ones behind it. As for pricing, NEVER, NEVER take a lump sum payment. Always work something from a revenue-share or monthly fee arrangement. You could even do an annual contract with built-in price increase each year based on percentages of their sales/revenue. If your product is that good that other companies are approaching you to white-label the solution, the best advice I can give you is to review your marketing/sales strategy. Why can't you sell direct to their market? Why risk losing revenue and allowing them to make money off your product?

ecommando 16y ago
Jeff is right on target. THE biggest issue I have with it is that one app never fits. There are ALWAYS an endless number of feature requests, and the license usually never takes these into consideration. Make sure that if you plan on doing it, and making changes, then you (a) charge for time, enough to make it painful ($150/hr or more), (b) are charging for time and that they don't own the code, and (c) limit the number of requests per day/week/month/year, etc, and (d) have the right to terminate the app, hosting, licensing, and support at will, and the only recourse they have is to buy it for a minimum amount decided by you. If they REALLY want it, they'll be willing to make concessions. If you go this route, you need to be willing to lose control of the app, and be blocked from the industry for up to three years. It will happen. Chances are they've looked for the app, even tried to have it written, and now they've found it for license, and a guy that's willing to keep it up. All that stands between them and the app is negotiations. We're not painting a pleasant picture, but we're holding back. It's worse than it appears.
- fezzl 16y ago
  We definitely don't want to lose control of our app, nor do we want to be locked into any particular partner. Thanks for bringing up the potential pitfalls.

ecommando 16y ago

Jeff is right on target. THE biggest issue I have with it is that one app never fits. There are ALWAYS an endless number of feature requests, and the license usually never takes these into consideration. Make sure that if you plan on doing it, and making changes, then you (a) charge for time, enough to make it painful ($150/hr or more), (b) are charging for time and that they don't own the code, and (c) limit the number of requests per day/week/month/year, etc, and (d) have the right to terminate the app, hosting, licensing, and support at will, and the only recourse they have is to buy it for a minimum amount decided by you. If they REALLY want it, they'll be willing to make concessions. If you go this route, you need to be willing to lose control of the app, and be blocked from the industry for up to three years. It will happen. Chances are they've looked for the app, even tried to have it written, and now they've found it for license, and a guy that's willing to keep it up. All that stands between them and the app is negotiations. We're not painting a pleasant picture, but we're holding back. It's worse than it appears.

fezzl 16y ago
We definitely don't want to lose control of our app, nor do we want to be locked into any particular partner. Thanks for bringing up the potential pitfalls.