Making rev share & partnerships work between marketers and developerss
- Thread starter Scattered
- Start date
It's never that black and white though. When you have hundreds or thousands of people using your software, each with their own ideas / needs, many of who love giving feedback, you have to say no sometimes. Don't get me wrong, feedback is amazing, and is what turns a good software product into a great one, without question.
However, you can't just add every feature requested, or else you end up with a bloated piece of junk with a huge learning curve that nobody wants to use. You have to find that fine line between functionality and user-friendliness.
Of course you can't make everyone happy and you have to prioritize what you're able to do, but I was really referring to wayn3s comment.
deleted, didn't feel like getting funky on wf today, i have other shit to do. you can leave those quotes up
Too bad. I read that post too, and it kicked ass. You should have left it.
You can find good programmers at $15/hr and up. Great programmers at $25/hr and up.
You cannot find good marketers that value their time anywhere near $25/hr. There is a reason for this.
You cannot find good marketers that value their time anywhere near $25/hr. There is a reason for this.
I'd love to see some code from your "great" developer at $25/hour.
A software developer is the same spectrum as say an architect. There's architects struggling to pay the $300/month rent, and there's architects raking in millions, designing the latest skyscraper or tourist resort. That same spectrum applies to software development.
* If your developer doesn't make most of his money from developing, then he's probably not the right guy for the developer job.
* If your developer doesn't have any of his past projects in production, then he's probably not the right guy for your developer job.
* If your developer has more time on open source contributions than commercial products in the last 3 months, he's probably not the right guy for the developer job.
* If your developer misses a deadline and doesn't contact you within 24 hours, he is not the right guy for the developer job.
* If your developer drinks or does drugs a lot, he is probably not the right guy for your developer job. Sober people always produce better code. ALWAYS.
* If your developer doesn't have any of his past projects in production, then he's probably not the right guy for your developer job.
* If your developer has more time on open source contributions than commercial products in the last 3 months, he's probably not the right guy for the developer job.
* If your developer misses a deadline and doesn't contact you within 24 hours, he is not the right guy for the developer job.
* If your developer drinks or does drugs a lot, he is probably not the right guy for your developer job. Sober people always produce better code. ALWAYS.
Its hard to not say I love you, especially on a gay webmaster forum
thanks for your quality responses guerilla
thanks for your quality responses guerilla
Soooo...
If I am all this, why should I partner with an asshole marketer who thinks he us the best thing since sliced bread and programmers are shit?
::emp::
Cant you answer that question yourself? You obviously shouldnt. I dont get this obsession with marketing anyway. There are about a million marketing degrees a year world wide. marketing is easy. it doesnt do shit. the only reason people on this forum have a hard time being a "marketer" is because theyre really trying to be conmen. a more correct name for affiliate marketing would be affiliate hitting the sweet spot breaking enough laws to make a quick buck but not getting caught.
if you have a solid product, just put it on reddit. will take care of itself for the most part. or put it on pinterest. whichever platform it is that your target audience frequences. wont make you millions but who around here really makes millions? thats a pipedream which will never come true. the only person right now who really makes that much money is danke, and hes not a even the part of marketer youre trying to be. he owns the products.
the point i was originally trying to make was that a developer rarely has the capital to invest any of the funds the thread starter was talking about. for that reason only, he doesnt deserve a majority share in the company. does he need someone equally inept to partner with who claims to be a marketer? in my opinion, thats just magnificent failure waiting to happen.
affiliate marketers arent marketers. marketers are the hobos who lurk around at highly frequented public places asking stupid questions. affiliate marketers arent entrepreneurs. theyve got nothing proprietary. their biggest fear is the offer going down, and if that happens, they dont even get noticed. networks dont have technology in place that triggers some kind of signal that affiliate marketers could use to automatically suspend their campaigns. thats how highly the networks think of their marketers. theyre breadcrumbs. affiliate marketers have some vague sense of demographics. but thats not difficult to acquire information. i was a member of imgrind for a month or two, and these are probably somewhere at least reasonably high on the affiliate marketing foodchain, and what it comes down to acquiring that sophisticated affiliate marketing intelligence that only a seasoned veteran has is "oh yea you just need to test that. in general, x is slightly better than y, but just use a couple hundred bucks to acquire the data". any hobo with a couple hundred bucks can do that.
it probably serves a couple guys well, but do yourself a favor and quit calling yourself marketers. or entrepreneurs. or running a business. youre ruthless scam "artists" with no conscience. if thats the life you wanna live, i dont have a problem with that. but you should be aware of that. for your own sake. :xomunch:
The only reason you would wanna do equity-share is if you don't have money of your own to pay your programmers salary. If that's the case, then I would suggest splitting the profit 70/30 until the programmer's salary is paid in full, and then do a 50/50 split moving forward. Or even you 70, and programmers 30, depending on how much money your business is bringing in after the launch.
Whatever your decision is, you must have control. Unless of course, you're just scamming him to work for free.
Whatever your decision is, you must have control. Unless of course, you're just scamming him to work for free.
So after slamming developers, this is your big advice? Put it on reddit or pinterest? Fuck me...
If I was still contracting, you're one of those clients I would fire within 48 hours. Just refund the deposit, and tell you you're better off looking elsewhere.
You obviously have no clue what you're talking about, and have never headed up any large development projects. Because if you had, you'd be singing a different tune.
This is just my thought on it from some experience I've had ...
It wasn't with developers persay, but more with partners. Joint ventures.
Total worth of the project was under 50k, so I can't say I've worked on 'huge development projects' or anything of the sort.
But I always find people work better when they're properly compensated.
I strive to make the compensation equal.
50/50 split ... regardless of how much work each party has to put in.
Mainly because if you're partnering with someone, you're bringing completely different skill sets to the table.
And I feel by making a 50/50 split, you both start to focus on making the PIE bigger instead of your piece (this works if there's more people as well ofc).
That's not to say that's some sort of golden rule or something.
But I really find the best and most fruitiful relationships I've had on any joint venture projects, were an even split.
Even when I was doing 95% of the work, I was happy to give my partner his 50% cut ... why?
Because I knew without him there would be 0% of work to do. Since it was his skillset which made it possible in the first place.
It's something along the lines of inter-dependance instead of in-dependance.
But like I said before ... I never headed any huge development projects ... I'm just talking about motivating people to not just do the work, but keep on doing it and working with you to make the pie bigger.
I think part of the solution to that, is giving them equal ownership within the project, getting them past the personal problem of "whats in it for me" on the % level, and instead focusing on improving the project to generate more cash for themselves (and subsequently everyone else involved).
It wasn't with developers persay, but more with partners. Joint ventures.
Total worth of the project was under 50k, so I can't say I've worked on 'huge development projects' or anything of the sort.
But I always find people work better when they're properly compensated.
I strive to make the compensation equal.
50/50 split ... regardless of how much work each party has to put in.
Mainly because if you're partnering with someone, you're bringing completely different skill sets to the table.
And I feel by making a 50/50 split, you both start to focus on making the PIE bigger instead of your piece (this works if there's more people as well ofc).
That's not to say that's some sort of golden rule or something.
But I really find the best and most fruitiful relationships I've had on any joint venture projects, were an even split.
Even when I was doing 95% of the work, I was happy to give my partner his 50% cut ... why?
Because I knew without him there would be 0% of work to do. Since it was his skillset which made it possible in the first place.
It's something along the lines of inter-dependance instead of in-dependance.
But like I said before ... I never headed any huge development projects ... I'm just talking about motivating people to not just do the work, but keep on doing it and working with you to make the pie bigger.
I think part of the solution to that, is giving them equal ownership within the project, getting them past the personal problem of "whats in it for me" on the % level, and instead focusing on improving the project to generate more cash for themselves (and subsequently everyone else involved).