Original Summary

I built SeatSwiper. You tell it the restaurant, the date, the party size and the window you would accept, and it watches Resy, SevenRooms and OpenTable until something appears, then books it on your own account in your own name. The problem it solves is boring and specific. Hard restaurants do not sell out, they release. A table appears thirty days ahead at ten in the morning, or it appears at nine at night because somebody cancelled, and both of those are moments you were not looking. Nothing is being resold here and no queue is being jumped, it is just attention applied continuously instead of in bursts. Two things I got wrong early, in case they are useful. The first was thinking the interesting part was speed. It is not. Most tables that get booked this way come from cancellations, not from the release hour, and a cancellation can land at any point across a month. Watching for four weeks beats being fast for four seconds. The second was pricing it like a subscription. Nobody wants a monthly bill for something they use twice a year, and I did not want to be paid for months where I found nothing. First booking is free, then five dollars when it actually books a table. Happy to answer anything about the watching side of it, which is where all the real engineering went.   submitted by   /u/carval [link]   [comments]

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/17 22:38:02