4 ms·

Good question. The big difference is you own the products you build here, and charge a monthly fee for access (for up to X customers). It's a bit like kickstart

Good question. The big difference is you own the products you build here, and charge a monthly fee for access (for up to X customers). It's a bit like kickstarting a SaaS business. Versus with contracting/freelancing, you get paid 1x and the product is owned by the customer you work for.

epicide 9y ago
But who makes all of the minute feature decisions? E.g. one of the projects wants a bookkeeping service. That's a pretty vague description. Especially if they want to tie it into their other systems. If I get final say in what goes in, then it seems very likely they wouldn't be on board with this (especially not after going through a project). If they get final say, then this is just contract work. The other issue is liability. In the bookkeeping example again, who is liable in case of a data breach? If there is payroll info or client info in said service, who is responsible for compliance? They couldn't pay me $500,000 a month to get me to take on that kind of responsibility, much less $500. I know I'm harping on one example, but a lot of projects would have similar issues come up. I guess my point is that sometimes I don't actually want ownership of a project like that. > you get paid 1x That really depends on a lot of factors. From what I've seen on the site, it's more like the other way around is true.
epicide 9y ago
Another question for you: who determines when a project is done or that it has met the requirements for MVP? For example, say I pick up one of the projects and the subscriber picks me to work on it. Okay, great. I go and work on it and consider it done. As it turns out, there was a lot of miscommunication and they wanted something different. Do I still get paid? It seems like either way, there is a huge avenue for somebody to get screwed.

4 ms·

Good question. The big difference is you own the products you build here, and charge a monthly fee for access (for up to X customers). It's a bit like kickstart

by hackerews 9y ago

epicide 9y ago
But who makes all of the minute feature decisions? E.g. one of the projects wants a bookkeeping service. That's a pretty vague description. Especially if they want to tie it into their other systems. If I get final say in what goes in, then it seems very likely they wouldn't be on board with this (especially not after going through a project). If they get final say, then this is just contract work. The other issue is liability. In the bookkeeping example again, who is liable in case of a data breach? If there is payroll info or client info in said service, who is responsible for compliance? They couldn't pay me $500,000 a month to get me to take on that kind of responsibility, much less $500. I know I'm harping on one example, but a lot of projects would have similar issues come up. I guess my point is that sometimes I don't actually want ownership of a project like that. > you get paid 1x That really depends on a lot of factors. From what I've seen on the site, it's more like the other way around is true.
epicide 9y ago
Another question for you: who determines when a project is done or that it has met the requirements for MVP? For example, say I pick up one of the projects and the subscriber picks me to work on it. Okay, great. I go and work on it and consider it done. As it turns out, there was a lot of miscommunication and they wanted something different. Do I still get paid? It seems like either way, there is a huge avenue for somebody to get screwed.