Original Summary

We built a product with a lot of features. AI, search, location, QR codes, collections, offers, analytics, and more. On paper, it looked pretty impressive. Then we started talking to actual shopkeepers and asked a much simpler question: “Why would you actually use this?” That question changed how we looked at the whole product. We realized that a feature can be useful for the customer while creating a completely different problem for the business. For example, customers like being able to compare products and prices. But for a shopkeeper, publicly displaying prices can affect things like margins, negotiation, customer relationships, and competition. We also expected shopkeepers to upload products, photos, descriptions, collections, offers, etc. Then we stepped back and thought: Their job is to run a shop. Why are we asking them to become data-entry operators? That was probably the bigger lesson for us. Building an app and creating business value are two very different things. A shopkeeper saying: “Nice app.” doesn't mean: “I'll use it.” And even: “I'll use it.” doesn't necessarily mean: “I'll pay for it.” So we're changing the question we're asking ourselves. Instead of: “What feature should we build next?” We're asking: “Why would a shopkeeper open this tomorrow morning?” We don't have the answer completely figured out yet. But I think that's a much more useful question to work on. Curious to hear from other founders/builders: Have you ever built something that users liked in theory, but didn't actually have a reason to use regularly? What did you learn from it?   submitted by   /u/Imaginary-Gap8327 [link]   [comments]

  • 情报分类：工作与职业机会
  • 分类依据：内容涉及招聘、求职或职业发展
  • 信息来源：Reddit · SaaS
  • 发布时间：2026/9/18 14:14:58