84 karma · joined August 4, 2013
Besides, amazon.com has amazon fresh for the grocery delivery service needs. Why cut into their own business?
Identifies business challenges and offers a custom-tailored solution that will generate more money than it costs. Then that said developer will effectively pitch their prospective customer from that angle.
A business, if convinced you're correct and capable, will be happy to pay $500,000 to a developer who will develop software that will make them or save them $1,000,000 in the next year.
I've been thinking of a few non-profit startup ideas to combat this widespread corruption problem, but its nothing I'd want to discuss publicly in case I actually pull the trigger on it and desired to remain anonymous. I think you're thinking down the right highway of thought though.
My only question remaining is how you guys handle shareholder liability since there's no corporate veil for partnerships. Is there some sort of general liability policy requirements, or is that kind of up to the people running the partnership?
I'm 99.9% sure the law would consider this equity compensation in exchange for labor performed, since this is being positioned as "getting a share" of the company. The only difference between standard "sweat equity in exchange for labor" agreements and this is that there are "coins" that represent a certain percentage of ownership instead of a standard contractual agreement bearing stock certificates.
That opens up a whole can of worms in terms of questions:
- Can the project owner further dilute the "coins" of the project, by increasing the total coin count? (Can prior work be diluted, thus lowering earning for prior work?)
- What kind of financial reporting requirements to companies have that work through assembly? Sarbanes oxley compliance? How do you know that they're reporting accurate earnings and not short-changing developers?
- Are these just "amorphous projects with a DBA" aka an informal partnership or are they all required to be corporations or LLC's?
- How about implicit liability?
If someone were to do an amount of work equal to 10-20% of a company's ownership equity, and the company did something illegal, wouldn't the developer have implicit ownership since he was profit sharing with the company? Would this open the developer to potential liability? (disclaimer: not an attorney, and it's been a while since I looked at related laws, but I remember reading some surprising case law that implied this a while back.)
- Possibly most importantly: How does this work with the SEC and IRS regulatory landscape?
How is this viewed by the SEC? The SEC requires that any exchange of securities be subjected to extreme regulations (you must take your company public to sell shares to public investors). When I raised money for my angel round, I had to seek SEC Rule 506(d) exemption just to provide shares to my initial investor base and to sweat equity to myself and my founder.
Most SEC exemption types carry additional reporting requirements for companies that have "non-qualifed" stockholders. This means monthly financial reporting that is SOX compliant by a CPA among other things IIRC. For the record, "qualified investors" have a net worth of $1mm+ or access to internal information that allows them to make knowledgeable investing (or in this case, investment of the developer's labor). These developers won't qualify simply by developing software for the company, as they need to have access to executive-level information.
In addition, SEC exemptions need to be filed by the actual companies in question. Those exemptions have a window of time during which they're valid. Different exemptions have different maximum non-qualified investor counts before the company must go public. That may mean that there's a maximum amount of different developers that can develop and receive sweat equity on a project before it reaches a ceiling, depending on interpretation of the law.
Finally, how does this affect the developer's taxable income? If he were to receive these equity shares (whether called "coins" or not), the IRS is going to deem these coins as having some sort of a value, just like stocks do. There's a lot of case law here, and typically it's going to work out to be (company valuation / ownership percentage = effective income amount). The IRS doesn't simply have you pay on dividends received from your equity, it has you pay the value of the equity as income as well, so how about with these coins? The IRS will see this as an asset received for labor, so how will this affect the taxable income of the developer? Do you require the companies on assembly to post a credible, running, monthly valuation by a 3rd party investment bank for taxation purposes? How do you handle the possibility of phantom taxation?
I apologize if this seems negative, I think the idea is (potentially) pretty sweet. I just hope you and your founding team talked with some good attorneys before building out this business. As a startup CEO myself, there's a lot of basic regulatory issues that I see with it which would have prevented it from passing the initial "idea vetting" process.
Or maybe this "Jeffrey" is full of bs and has no real information, which would explain why he's trying to get money from the public. Obvious troll seems obvious.
I think it was detrimental.
A phone with comparable specs to the Moto G could have achieved their real goal that you mentioned, with the effect of spreading sales opportunities to millions more people. Those millions more in phone sales would have caused many, many more added transactions to the Amazon machine, as I assume they intend with the Amazon Fire Phone.
With my body at least, it seems that the difference between 2 lbs per week and 3-4 lbs per week is huge in terms of how much muscle is kept during the fat loss process.
If you're already hugely overweight than of course it doesn't matter and fast weight loss should be expected.
However, it's normal to spend a lot of money on CAPEX and make higher profits on the services after the financing for capital expenditures used to expand the services has paid off. The only people who might find this less than obvious are probably solely from the lean internet business space, and haven't had any real experience in manufacturing or other capital-heavy businesses.
But startups producing social media products, or consumer applications that are freemium or passively monetized will not benefit with sales. They need marketing via PR, social media, or viral mechanisms baked in early on into the app.
Let's not overgeneralize.
"Make common user tasks as friction-less as possible."
Now, when a common user behavior is to use the main menu to switch between many different places in the app, then yes, hiding that menu from the user introduces an additional step. That creates additional friction. A permanent menu would be a good idea in that case.
But, if the most common use case involves a user mostly navigating from a main page (like a timeline or feed), then hiding the menu becomes less of a big deal. They will "organically" navigate through content from the timeline. Therefore allowing more space for the main element (the timeline) makes sense and increases the quality of the user experience.
As a plus, removing items from the screen helps make the action that you'd prefer the user to perform more obvious. That increase conversions in a context when you want the user to do certain things.
Lets focus on good UI/X design, which is often case dependent. No need to evangelize one particular approach and condemn another as being worthless (especially when you have weak reference studies).
I recognize that there's complex case-law here that differentiates between those varying shades of grey, but that's just my (unpopular) opinion.
I'm interested if the tuberculosis actually "killed" the melanoma or if it caused an unusually aggressive autoimmune response that happened to knock out the melanoma. I'd like to see if there's a case study available on that treatment method.
I just drafted a stock purchase agreement for my business partner and I on our new startup and one of the basic boilerplate additions to the stock purchase / vesting agreement is a spousal agreement to the terms of the purchase.
The communal property law only relates during a divorce were the shares are split up between the couple by the courts. Any decently written stock purchase agreement has a first right of refusal for the company to purchase back those shares in the event of an involuntary transfer.