| Guys, This is really clever. When I first looked at it I thought "I can already do this in my app or with Unbounce or ..." But then when I took a closer look at app it occurred to me that this is sooooo simple. Unbounce takes a learning curve and doing app-level routing testing can take some configuration. With that in mind, I see a couple of options: 1. Do A/B testing on the type of products you suggest, such as Google Docs that don't normally then themselves to such functionality. The issue I have with this approach is that I don't actually know of a situation where I would have done this. The times I'm A/B testing something (which isn't often), I'm highly invested in whatever I'm doing and the outcome. This is almost always whatever I'm building or selling, hence Unbounce or my own app. 2. Figure out a way to put var.to INTO an app or a situation that I care a lot about and would pay for the tool. IF you could figure out way to make it drop-dead simple for me to put it into my app and then provided killer analytics an services on top if it, then it might be something I'd pay for. Bottom line: I think you have a clever, interesting, easy-to-use tool that I like from an intellectually curious position. But it doesn't yet grip me emotionally with a "I've GOT to use this" position yet. Nice job, hope it helps! Kevin |