Stock SIP (Recurring Buy)
Stock SIP (Systematic Investment Plan) is a way to automate stock investments at regular intervals.
TIMELINE
Apr 2024 to Sep 2025
CONTRIBUTORS
Satvik Bansal - Product Manager
Riken Patel - Research
Nayna Yadav - Visual Design
AUM
₹450Cr+
(as of Sept 2025)
SIP BOOK
₹50Cr+
(as of Sept 2025)
Users
1.12M+
NIFTYBEES
10 qty
•
Every Friday
6
Mar
HDFC Bank
₹5,000
•
Monthly on 17th
17
Mar
Amount
Quantity
Background
In India, SIPs are widely used for mutual funds and follow the principle of dollar-cost averaging, investing a fixed amount at set intervals, regardless of the stock price.
It was one of our most requested features and also one of the more complex ones to implement. Given that complexity, our priority was to design an experience that made investing through Stock SIP feel simple and approachable for the end user.
We approached the design with three guiding principles in mind: communicate with clarity, prioritise simplicity, and give users control.
Placing an SIP order
An important consideration while designing the SIP creation screen was the range of choices available to users, whether to invest by amount or quantity, and whether to set a weekly or monthly frequency.
To reduce the chances of failed orders, users could also automate payments using autopay, ensuring their account is funded before each SIP cycle.
The goal was to make the experience as simple as possible. We aimed for this through smart defaults and a step-by-step flow that introduced customization options gradually.
Managing SIP
Once an SIP is created, users may want to edit, skip, or cancel it based on changing market conditions.
This aligned closely with our principle of giving users maximum control over their investments.
Since stocks are inherently volatile, it was important to make these actions easily accessible, so users could respond quickly to market shifts.
Messaging
Since SIPs are created at one point in time but executed later, there’s a gap that can lead to uncertainty. The experience has many moving parts and edge cases that require clear, ongoing communication.
To ensure users always know what’s happening with their orders, I developed a flexible messaging framework that allowed the team to surface contextual updates whenever needed.
Stock SIP (Recurring Buy)
Stock SIP (Systematic Investment Plan) is a way to automate stock investments at regular intervals.
TIMELINE
Apr 2024 to Sep 2025
CONTRIBUTORS
Satvik Bansal - Product Manager
Riken Patel - Research
Nayna Yadav - Visual Design
AUM
₹450Cr+
(as of Sept 2025)
SIP BOOK
₹50Cr+
(as of Sept 2025)
Users
1.12M+
Background
In India, SIPs are widely used for mutual funds and follow the principle of dollar-cost averaging, investing a fixed amount at set intervals, regardless of the stock price.
It was one of our most requested features and also one of the more complex ones to implement. Given that complexity, our priority was to design an experience that made investing through Stock SIP feel simple and approachable for the end user.
We approached the design with three guiding principles in mind: communicate with clarity, prioritise simplicity, and give users control.
Placing an SIP order
An important consideration while designing the SIP creation screen was the range of choices available to users, whether to invest by amount or quantity, and whether to set a weekly or monthly frequency.
To reduce the chances of failed orders, users could also automate payments using autopay, ensuring their account is funded before each SIP cycle.
The goal was to make the experience as simple as possible. We aimed for this through smart defaults and a step-by-step flow that introduced customization options gradually.
Managing SIP
Once an SIP is created, users may want to edit, skip, or cancel it based on changing market conditions.
This aligned closely with our principle of giving users maximum control over their investments.
Since stocks are inherently volatile, it was important to make these actions easily accessible, so users could respond quickly to market shifts.
Messaging
Since SIPs are created at one point in time but executed later, there’s a gap that can lead to uncertainty. The experience has many moving parts and edge cases that require clear, ongoing communication.
To ensure users always know what’s happening with their orders, I developed a flexible messaging framework that allowed the team to surface contextual updates whenever needed.