Loading...
Answers
MenuWould you pay a mobile app designer with a percentage of profits in the future if you don't have the cash to pay upfront?
I don't have much cash to work with and I am working on developing a mobile app. However, I want to find a good designer to work with. I don't want to give them equity but I do want to pay people for their work. Would you recommend promising (in writing) a profit percentage? If so, how much would this be?
Answers
Hi,
Yes, this is something that is fairly common.
Calculation: in order to calculate the % you should give, you need to understand how much is due to the designer for all their work, and how much your projected profits will be in the first 6 months/year. Then, you offer a % which should give the designer a little bit more than the value of their work during that 6 or 12 month period.
It is important that you define in the agreement/email, what the amount is - meaning that when the designer gets that amount, you stop giving them a % of profits.
I would also add a section in the agreement that states that should you decide to do so, you can pay them off the entire amount and stop making the monthly payments.
Lastly, make sure it is clear that they are only getting a % of the profits (not the income) and that they don't have any voting/decision rights.
Good luck
I've successfully helped over 350 entrepreneurs, startups and businesses, and I would be happy to help you. After scheduling a call, please send me some background information so that I can prepare in advance - thus giving you maximum value for your money. Take a look at the great reviews I’ve received: https://clarity.fm/assafben-david
This is what we like to call a revenue share. If I believe in the person, along with h the product and// or service while having the time to invest, I have been known to participate in the past. It's essential to understand this endeavor is a gamble and long term investment that may not make a single red cent. If this happens that is the calculation of risk we decided to take. If it doesn't work out as business plan suggest we can't have hard feelings later. It is high risk for a potenttial tich reward. That said as we are all well aware, most businesses fail in the first five years. Please proceed with extreme caution, at your own risk. I am not a fear monger , simply protecting the interest of all involved. Transplant , Crystal clear expectations are beyond crucial to protect your bottom line , in business we don't have any friends. Often this is a great way to loose a friend. This is my opinion , with obvious brutal honesty. Others may have the answer you wish to read. I have played this tape forward and in this arena would have to say thank you but no thank you I would not be willing to participate
You can certainly come to a profit sharing agreement and there is some good feedback from other experts listed here about how to structure that to protect yourself. However, most technology startups and mobile apps need to be reinvesting their profits back into the company, so even though money may start to come in, it doesn't mean you want to spend it on paying back the designer you worked with. When I started my company, I gave a designer 1% stock to design my logo, business cards and the four main pages of my website. This was a great deal for me and would have been an incredible deal for them if we sold for a big amount in the end. But most importantly, it didn't use up any of my precious cash in the early stages of my business.
You may not have a lot of money coming in for awhile. I would try not to spend any of it at all if you can find someone willing to work for equity instead.
In my humble opinion and experience, this is a bad idea. If you don't have cash and can't raise it either, then you should be willing to give equity. Otherwise, your proposal may end up self-selecting a poor quality developer. The reason being is you're asking the dev to take on too much risk in return for very little reward, and the offer/demand curve is against you (there's lots of other entrepreneurs willing to pay cash and/or give equity for a good developer). I run a small software development firm (see www.chimi.co), we build mobile apps (among many other things), and we'd not accept this. We have, however, in very few occasions (e.g.: known entrepreneur we've worked with in the past, and upon satisfactory due diligence from our side, etc) exchanged a discount on services in exchange for (vested) equity.
The main issue isn't whether this is a good idea, it's whether you can find a designer who would be interested. I have a business finding app developers for entrepreneurs and small businesses, so I can tell you from experience that most designers and developers don't want equity or a percentage of profits; they want cash. And that's understandable. They have an extremely valuable skill, and they'd rather have cash than a slice of equity that might be valuable or might be worth nothing. There are so many risks in involved with apps that most pro designers or developers wouldn't take that kind of risk. In this case the deal is even worse since it's a percentage instead of equity.
This kind of value disconnect with entrepreneurs is common. The problem is that you see your app as an exciting, sure thing. And that's only right; as a startup owner you should be excited and motivated about your big idea. But for a designer, it's not their big idea, it's their job. And so they want to be paid like with any other job. The only time I tend to see this kind of arrangement is when the entrepreneur has a friend that they're going to work with. Even then though you see equity more than profit percentages. I'm not saying that finding a designer who's willing to accept a percentage can't happen, I'm just saying it's not that likely unless you have a history of startup success and an impressive resume.
This may not be what you want to hear, but it's the situation that you have to deal with. So what do you do? There are a few things. First, keep your app plans as simple as possible with very few features. That means a simpler and cheaper design. Also, consider whether you actually need a pro designer. It's not necessarily a given that you do. Obviously you need some sort of design for your app, but depending on how complex it is you may not need a separate designer, you may be able to just do some mockups of your own. In fact, if you're planning on making revisions to your app post-launch, you'll end up having to revise the design anyway to accommodate the changes. Of course, if you're a commercial business that needs an app as a sales tool, then you might need a designer to make sure that your design has some polish to it. Overall, I'd say the key thing for most apps is picking the developer, not the designer. Of course, I can't give firm advice since I have no idea what the app is or what you're trying to do.
I consult on app planning and developer hiring, so feel free to reach out if you'd like some more individualized advice.
After 40 years managing designers, I have a diferent point of view.
First class designers are not gamblers. I do not know any reliable designer that will accept a risk condition and sustain the drive to commit himself aoo%.
Do not make such an error. Invest in design and your start up will give your expected future profit.
If you want to discuss my view, do not hesitate to call me.
My site www;marcarbranding.com
If you can find a developer who would accept your proposal, it is a good deal for you. Most developers worth their salt will not agree to something like it unless you have some unfair advantage.
If a developer is free they can develop on their own ideas and keep 100% of the profits and equity. However, you might be able to find new developers or students who are looking for experience with a model like this.
Related Questions
-
Whats are some ways to beta test an iOS app?
Apple will allow a developer to register 100 UDID devices per 12 month cycle to test via TestFlight or HockeyApp. Having started with TestFlight, I would really encourage you NOT to use it, and go directly to HockeyApp. HockeyApp is a much better product. There is also enterprise distribution which allows you far more UDID's but whether you qualify for enterprise distribution is difficult to say. As part of your testing, I'd encourage to explicitly ask your testers to only register one device. One of the things we experienced was some testers registering 3 devices but only used one, essentially wasting those UDID's where we could have given to other testers. Who you invite to be a tester should be selective as well. I think you should have no more than 10 non-user users. These people should be people who have either built successful mobile apps or who are just such huge consumers of similar mobile apps to what you're building, that they can give you great product feedback even though they aren't your user. Specifically, they can help point out non obvious UI problems and better ways to implement particular features. The rest of your users should be highly qualified as actually wanting what you're building. If they can't articulate why they should be the first to use what you're building, they are likely the wrong tester. The more you can do to make them "beg" to be a tester, the higher the sign that the feedback you're getting from them can be considered "high-signal." In a limited beta test, you're really looking to understand the biggest UX pain-points. For example, are people not registering and providing you the additional permissions you are requiring? Are they not completing an action that could trigger virality? How far are they getting in their first user session? How much time are they spending per user session? Obviously, you'll be doing your fair share of bug squashing, but the core of it is around improving the core flows to minimize friction as much as possible. Lastly, keep in mind that even with highly motivated users, their attention spans and patience for early builds is limited, so make sure that each of your builds really make significant improvements. Happy to talk through any of this and more about mobile app testing.TW
-
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.SG
-
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.comKM
-
If I am planning to launch a mobile app, do I need to register as a company before the launch?
I developed and published mobile apps as an individual for several years, and only formed a corporation later as things grew and it made sense. As far as Apple's App Store and Google Play are concerned, you can register as an individual developer without having a corporation. I'd be happy to help further over a call if you have any additional questions. Best of luck with your mobile app!AM
-
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. MihaiMP
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.