Auto-invest

Stake  ⎯  2024

Project overview

Recurring Investments was one of the most consistently requested features at Stake. It allowed users to set up automated deposits into their account or schedule recurring purchases of a specific stock or ETF, reducing the need to manually fund and trade each time. For many users trying to build long-term habits, this was a meaningful gap in the product.

I led the end-to-end design across web and mobile, focusing on making automation feel transparent and controllable rather than abstract. Because this involved scheduled money movement, clarity was critical. Users needed to understand exactly what would happen, when it would happen, and how to edit or cancel at any time.

For Auto Invest, I led the end to end product design from early problem framing through to launch across app and web. What started as a high level request to add recurring investing required alignment across product, engineering, compliance, and growth, balancing user demand for automation with regulatory constraints and platform limitations. I reframed the initiative from a simple scheduling feature into a scalable recurring investment engine that integrated across funding, portfolio, and transaction journeys. Beyond designing the flows and system logic, I worked closely with engineers to ensure components and patterns could support future expansion, making the solution not just a feature release, but a foundation for long term growth.

  • Discovery
  • Problem Framing
  • Stakeholder Alignment
  • Systems Thinking
  • Journey Mapping
  • Interaction Design
  • Prototyping
  • Cross Platform Design
  • Engineering Collaboration
  • Delivery

This project was much bigger than it looks. Recurring didn’t live in one neat flow it cut across deposits, investments, active orders, portfolio tracking, and a bunch of existing states that were already embedded in the product. Because those journeys were already live and heavily used, we couldn’t just redesign them from scratch. We had to layer recurring behaviour into what was already there, and make it feel native rather than bolted on. The Figma file reflects the multiple entry points, edge cases, edits, skips and fail states all needing to connect back to real transaction logic. It was less about designing a new feature and more about carefully reshaping several existing systems so they could support automation without adding confusion.

Impact over the first 4 months

11,000

Recurring deposits

8,000

Recurring investments

9000000

Funded via auto-invest

Part of my role was translating our mobile app screens into considered web layouts. It wasn’t about scaling things up, it was about rethinking the experience for web. I adjusted navigation, hierarchy, spacing and interaction patterns so it felt native to the platform while still aligned to the system. I made sure components, assets and specs were structured and ready for engineering, with states and edge cases clearly defined. I also created the end to end prototypes across both app and web, helping validate flows and communicate the experience clearly before it went into build.