New feature designe

Hi team

I’m Harsh, a product designer, and I recently worked on a concept called Ready Fund — an emergency fund experience designed for payments/neobanking apps.

The idea came from a personal pain point: I needed money for a small emergency, but my savings were locked in a recurring deposit. The problem wasn’t a lack of money — it was access. That led me to explore a simple question:

How might a product like Jupiter help users build an accessible emergency reserve, not just long-term savings?

The concept includes:
• Auto-Add to build reserves passively
• Instant add/withdraw with no lock-ins
• A Safety Limit that helps users stay prepared

I thought Jupiter’s product philosophy made it a particularly relevant place for this idea, and I’d love to share the case study for feedback if you’d be open to it.

Best,
Harsh Tiwari

Where will it be stored

  1. FD with auto break
  2. Liquid funds
  3. Some apps have do this feature where we can store it in liquid funds

The key trade-off I found was between returns vs instant accessibility.

• FD auto-break still carries mental friction and penalties
• Liquid funds improve returns but aren’t always truly instant and add investment complexity

For Ready Fund, I’ve intentionally prioritized instant access over returns, by defaulting to a wallet/savings balance layer — because in emergency situations, speed and certainty matter more than yield.

1 Like

So where will the funds be stored, wallet or savings bank