Currently testing in Washington, it identifies surge pricing areas and locations that could experience surges in future due to sporting events etc. Looks pretty early stage, but good concept!
@riaface
Hi, Ria. Been so busy I almost missed your post. Yes, we're early stage and fine-tuning it with extensive Driver-Partner feedback. Thanks for sharing it and your support!
Is it possible that by getting more drivers to potential surge locations, you'll lower the % of the surge pricing for users? I see a potential win-win.
@daniloebs,
Thanks! You’re right on the money; I think it’s a win-win, as well. After reviewing the data, I’ve found several more areas ripe for improvement (and folks much smarter than I will probably find even more!). As I mentioned, my immediate need was to give myself and other Driver-Partners the information we needed to make better day-to-day decisions. This, of course, involved surge pricing, patterns, etc. After releasing several iterations of the service, the demand from other Driver-Partners has been insatiable and I’ve been working with them to continue the feedback loop (I haven’t even been able to continue driving!). I’d definitely like to explore more in this direction - hopefully I can obtain more resources to assist in this effort (I’m on AngelList - hint, hint). :)
@rrhoover Thanks, Ryan! Some of the surge fluctuations captured are too small to matter to the Driver-Partners (i.e. 30 seconds) but the ones which last longer than several minutes do come in handy for: establishing patterns and laying the groundwork for additional (predictive) analytics. I put a screenshot of some monitoring I did last night on @WhereMySurgeApp. Before this the Driver-Partner community had nothing to gauge surge frequency, length, etc. - this is the foundation which is improving with leaps-and-bounds from the tremendous feedback I've received from everyone!
Pivot
WhereMySurgeApp!
WhereMySurgeApp!
Product Hunt
WhereMySurgeApp!