Nathan Miller identifies five signs your product actually works but your execution doesn't. A ROAS above 1.5 with low order value means test your pricing. Early unprofitable sales need patience for Facebook's algorithm to improve. A weak website lacking trust signals kills profitability even with sales. Spend at least $100 to get real data before quitting.
5 signs that the product you're testing actually has potential but you're the problem. Number 1 is you have a good ROAS, like you have above a 1.5 ROAS, but your AOV is low. Simply, simply just need to A/B test pricing a bit more. You need a value stack, create a better offer to increase your AOV, add upsells, yada yada yada. Number 2 is that you're close to break even just from KLRIPs. KLRIPs really should just be for validation. You should be able to understand how to double down. How to see the data from Kayla Ripp, see what's working, and actually turn that into winning concept by basically swiping other brands, changing out their messaging and their mechanism for yours. Number 3 is that you're actually getting a few sales on day 1, but it's not profitable, and for some reason you want to cut it. Facebook takes time to find your audience, and a lot of times day 2 will be better. Number 4, you've gotten some sales, but your site looks like absolute doo-doo water. I don't think site matters so, so much in the beginning, but it definitely matters a little bit. So changing your site could actually make something profitable, like actually having good risk reversal, social proof, all that stuff, and then making it congruent as well to the ads you're running in terms of copy and what you're saying on it. Number 5, you've spent less than $100 on the product. If you haven't even given it $100 in ad spend, you don't have enough data to even make a decision yet. You need to have more conviction, more intention behind your product tests, and actually think that it will work so that you're willing to actually give it a shot.
