Validating an idea before building it: an AI that remembers your return windows, warranties and price drops from a receipt
Context: I run VORNEAUX, mostly known for premium audio + a music/sound identity. This is a new, separate product idea I'm validating before committing engineering time to it.
The observation: every purchase has a timeline attached — a return window, a warranty, sometimes a price drop right after you bought it. None of that is tracked by any tool people actually use. It lives in a receipt that gets forgotten the moment you leave the store.
The idea: Ownership OS. Upload a receipt, AI extracts the purchase, and you get back three things automatically — days left to return it, how long you're covered under warranty, and whether the price has moved since you bought it.
What I've built so far: a landing page that acts as a functional demo of the concept (since there's no usable app yet), a waitlist with email capture, and basic FAQ/trust copy addressing the obvious question — "why would I upload my receipts to a startup?"
What I'm trying to validate before writing a line of backend code beyond the waitlist:
- Is "forgetting return windows / warranties / price drops" a problem people recognize themselves in, or is it a "meh, I'd survive" problem?
- Would people actually hand over receipt data for this, or is the privacy friction too high?
- Is "ownership intelligence" a category that means anything, or does it need to be repositioned as something more familiar?
Landing page + waitlist here if you want to see how it's positioned: https://vorneaux.com/ownership-os
Genuinely want the "this won't work because X" feedback as much as the positive kind — that's the point of this stage.
The receipt upload idea is interesting, especially because the useful part isn't really storing the receipt — it's what happens after the purchase.
The return window, warranty, and price movement are all things I'd normally forget to check. Curious which of those three you expect people to care about most.
Good question — honestly still figuring that out, that's part of why the waitlist exists.
My guess going in is warranty, just because it's the one with the highest "silent cost" — you don't even think about it until something breaks 14 months in and you're not sure if you're still covered. Return windows I think people already half-track mentally because the deadline is short and top of mind right after the purchase. Price drops are the one I'm least sure about — could be a nice-to-have, could turn out to be the thing people check most obsessively. No real signal yet either way.
If you don't mind me asking back: of the three, which would actually get you to open an app/check something, versus which would you just shrug at if you missed it?
I’d probably check price drops more proactively, while warranty is something I’d only think about when I need it. This is an interesting one to follow as you get more signal — if you’re open to continuing the conversation, what’s the best email to reach you at?
Quick addition since I didn't want to make the post longer than it already was:
The trickiest design decision so far has been how much to show on the landing page without having a working app behind it yet. I ended up simulating the actual flow (receipt → AI extraction → return/warranty/price data) directly on the page, because just describing it in words wasn't landing — people need to see the "so what" immediately.
The other thing I keep going back and forth on: how upfront to be about privacy before anyone even asks. Right now the FAQ addresses it, but I'm wondering if it needs to be closer to the CTA instead of buried lower on the page. Curious if that's the kind of thing that would make you hesitate before signing up, or if I'm overthinking it.
Also happy to share actual numbers (visits, signup rate, drop-off) once there's enough traffic to make them meaningful — figured that might be useful for anyone else validating a similar kind of idea.