We're considering Mike Moyer's the Slicing Pie method to decide equity splits and profit interest for our new company. Anyone have experience with it?

With all respect to Dan, I'm not seeing anything like that. You said "pre-revenue." If it's pre-revenue and enterprise, you don't have anything proven yet. You would have to have an insanely interesting story with a group of founders and execs on board with ridiculous competitive advantage built in. I have seen a few of those companies. It's more like $3m-$5m pre. Now, post-revenue is different. I've seen enterprise plays with $500k-$1m revenue/yr, still very early (because in the enterprise space that's not a lot of customers yet), getting $8m-$15m post in an A-round. I do agree there's no "average." Finally, you will hit the Series A Crunch issue, which is that for every company like yours with "cutting edge tech" as-yet-unproven, there's 10 which also have cutting edge tech except they have customers, revenue, etc.. So in this case, it's not a matter of valuation, but a matter of getting funded at all!

It stands for allowing someone to continue doing or use something that is normally no longer permitted (due to changing regulations, internal rules etc.)

Cash money should be treated separately than sweat equity. There are practical reasons for this namely that sweat equity should always be granted in conjunction with a vesting agreement (standard in tech is 4 year but in other sectors, 3 is often the standard) but that cash money should not be subjected to vesting. Typically, if you're at the idea stage, the valuation of the actual cash going in (again for software) is anywhere between $300,000 and $1m (pre-money). If you're operating in any other type of industry, valuations would be much lower at the earliest stage. The best way to calculate sweat equity (in my experience) is to use this calculator as a guide: http://foundrs.com/. If you message me privately (via Clarity) with some more info on what the business is, I can tell you whether I would be helpful to you in a call.

There is quite a bit of information available online about eCommerce conversions rates. According to a ton of sources, average visitor-to-sale conversion rates vary from 1-3%. This does not mean the Furniture conversions will be the same. The bigger problem is that visitor-to-sale conversions are not a good data point to use to measure or tune your eCommerce business. All business have some unique friction factors that will affect your final conversion rate. It's very important to understand each of these factors and how to overcome them. The best way to measure and optimize is to take a conversion funnel approach. Once you have defined your funnel you can optimize each conversion rate to better the total effect. For example: Top of the funnel: - All web site visitors, 100,000 / month First conversion: View a product page, 50% of all visitors Second Conversion: Add to Cart, 10% of people who view products Final Conversion: Complete Checkout, 80% of people who put items in a cart In this example we see that only 10% of people who actually view products put them in to a cart, but 80% of those people purchase. If you can figure out why visitors are not adding items to their cart and fix the issue to increase the conversion rate, revenue should increase significantly because of the high checkout rate. You can use free tools like Google Analytics to give you a wealth of information about your site visitor and their behavior or there are some great paid tools as well.

10% of the total monthly sales churning on an absolute basis is near fatal. That means that within 5 months, you have 50% absolute churn per year, which reveals fundamental flaws with the service itself. Anything above small single digit churn is telling you and your team that customers are not seeing enough value in your product. I'd start by doing as many exit interviews as you can with those that have churned out, including, offers to reengage at a lower price-point while you fix the issues that matter to them. Happy to talk through this in more detail in a call.