Loading...
Answers
MenuWhat are the options for white labeling my mobile app?
How do I decide on a pricing strategy?
I have a CRM app (bootstrapped) in the app store for a certain vertical. Recently i got a request for white labeling my app for using it for his team. any advice on how i should charge him? how should my contract look like? and what are the different options of white labeling. any resources would be helpful
Answers


1. Talk to a lawyer who can write you a proper licensing agreement.
2. Charging should be around $10,000 per year or $50,000 one-off fee if you are scarce for money. It could also be $50,000 per year though, but this depends on how big of a budget you think the licensee has. Try to find that out indirectly in a call with them.
3. If someone can only pay you $5,000 per year or less, I wouldn't do it, since your rebranding, bugfixing costs are higher than the $5,000.


If you're bootstrapping, here's my advice (7-figure SaaS founder, bootstrapped):
I wouldn't spend too much time talking to lawyers, but rather just make a simple contract outlining all the things you want to be protected by. Lawyers can be expensive, and still not get the job done right - unless you outline all your terms (might aswell write one up then)
How much to charge him? Well, it's your business :-)
There's no magical number (like someone said $50k lol), but charging someone a hefty fine may be really hard as they can just invest that money and build it out themselves. Make it easy for them to make money, and you'll also make money


One thing you are going to have to contend with is customization requests. I've helped white label several applications now and while the licensing/pricing may be fairly straight forward to figure out, figuring out if or when to allow and then how to handle customization requests will be key (especially if you ever plan to move beyond just one single client.) there are a lot of options you need to think through in terms of individualized custom requests (front-end related such as design or look/feel as well as back-end new feature development requests.) There are some instances where you may want to allow for customization on any scale but charge a hefty price and others where you should absolutely avoid it altogether. so in addition to the pricing question and contract portion be sure to think ahead of how you'll handle one-off customization requests so you aren't caught off guard when they inevitably start rolling in.
Best of luck!


You should charge based on your monthly burn.
Related Questions
-
I've been working on an app concept for 6 months and built an MVP. Is it better to pay a development firm to build or hire a developer as a cofounder?
I have built two software companies by hiring out the development work. I sold one for a decent sum during the dot com era (circa 1999). I remain a shareholder in the other one. I currently work with amazing development company on behalf of one of my clients. Here are some things to consider. 1. Do you really want to give up equity? If not outsource. 2. How fast do you want to get to market? If sooner than later, outsource. 3. How capitalized are you? If undercapitalized, either outsource offshore (which runs about 20% of US rates), or bring on an equity development partner. I offer a free call to first time clients. Let's chat and I'll give you some great advice from three decades of experience. Just use this link to schedule the free call: https://clarity.fm/kevinmccarthy/FreeConsult Best regards, Kevin McCarthy Www.kevinmccarthy.com
-
What is the best technology for developing a new mobile app from scratch?
There are two sides to that question. One is the mobile app itself and the other is the backend. If I misunderstood in any way and you didn't mean "native" app I apologize in advance. On the backend, there is no clear cut answer to which is the "best". It depends solely on the developers you are able to get. We for example use Node.js , mongoDB, redis, elasticsearch and a couple of proprietary tools in the backend. But you have your pick of the litter now both on the backend api and the datastore with the myriad of options available and touted as the "best" currently on the market. Now on the app side again it solely depends on what you need your mobile app to do. Experiencing first-hand "develop once, run anywhere" I can say it's more like "develop once, debug everywhere" to quote a Java saying. We have tried Phonegap and Titanium Appcelerator and we have switched to native (ObjC and Java) after a couple of months of trying to go the hybrid route. The reasons behind the choice are as follows: - anything that breaks the pattern of how those frameworks NEED to operate is just a huge technical debt that keeps accruing a huge interest. - anything that uses css3 accelerated animations on Android is buggy at best and slow as hell at worst on any lower (< 4.1 I think) versions of Android I hope this gives you some insight. If you need/want to ask me anything feel free to contact me. Mihai
-
Any opinions on raising money on Indiegogo for an app?
Apps are difficult to fund on IndieGoGo as few are successful, and we rarely take them on as clients. Websites like http://appsfunder.com/ are made for that very reason, but again, difficult to build enough of a following willing to pay top dollar for an app that could very well be free, already existing in the marketplace. A site that is gaining more traction you may want to look into would be http://appsplit.com/. Again, Appsplit Is Crowdfunding For Apps specifically.
-
iOS App: Beta vs Launch Quietly?
I would suggest launching in a foreign app store only (ex: Canada). That will allow you to get more organic users to continue iterating without a big push. I got this idea from Matt Brezina (Founder of Sincerely, previously Xobni) https://clarity.fm/brezina - he's the man when it comes to testing & iterating mobile apps.
-
What is the generally agreed upon "good" DAU/MAU for mobile apps?
You are right that the range is wide. You need to figure what are good values to have for your category. Also, you can focus on the trend (is your DAU/MAU increasing vs decreasing after you make changes) even if benchmarking is tough. Unless your app is adding a huge number of users every day (which can skew DAU/MAU), you can trust the ratio as a good indication of how engaged your users are. For games, DAU/MAU of ~20-30% is considered to be pretty good. For social apps, like a messenger app, a successful one would have a DAU/MAU closer to 50%. In general most apps struggle to get to DAU/MAU of 20% or more. Make sure you have the right definition of who is an active user for your app, and get a good sense of what % of users are actually using your app every day. Happy to discuss what is a good benchmark for your specific app depending on what it does.