<aside> 💡
Pre-validation product idea designed as a conceptual excercise.
</aside>
Amazon wishlist UX — for the entire internet. Any merchant, no address exposed.
| The Problem | The Solution | Why Now |
|---|---|---|
| Gifters want to surprise. Recipients want privacy. No product delivers both across all merchants. Amazon gives privacy but one merchant only. Universal wishlists support any merchant but expose the address. | A checkout proxy: gifter pays the platform, platform places the order, recipient address never exposed. Any merchant, any item, day one — no partnerships required to launch. | Creator economy normalised wishlists beyond events (Throne, Wishtender). BaaS & virtual card infrastructure now accessible. AI makes flexible order placement feasible. Privacy awareness at all-time high post-GDPR. |
| Step | What Happens |
|---|---|
| 1. Recipient adds item | Any URL, any merchant |
| 2. Gifter pays platform | Item price + service fee |
| 3. Platform places order | Via disposable virtual card |
| 4. Ships to recipient | Address never shared |
| 5. Confirmations sent | Gifter + recipient notified |
The quadrant nobody occupies: any merchant + privacy.
| Limited merchants | Any merchant | |
|---|---|---|
| Privacy preserved | Throne, Amazon Wishlist | ✦ This product |
| No privacy | Generic registries | Wishlist.com, Giftful |
| Segment | Why They Need This |
|---|---|
| Casual users | Friends & family gifts without sharing home address |
| Creators | Fan gifting at scale — currently stuck on limited platforms |
| Mutual aid communities | Safety-critical: can't expose address; ethics prevent Amazon use |
| Charities / orgs | Supporter gifting without operational overhead |
On mutual aid: These networks (disability communities, LGBTQ+ support, crisis groups) are trapped on Amazon specifically because of address privacy. They're highly motivated to switch, actively advocate within their networks, and validate the core product thesis more clearly than any other segment.