A neo-banking platform for businesses in India
#MVP • #Micro-Interactions • #Dark-UI • #Built-in-a-month
Note: This isn't a case study but more of a design overview. The project hasn't yet reached at a state to become a case study. We're yet to reach our product-market fit. And from a design perspective, we know tons of things that don't work or we haven't validated enough.
Since the other two projects from Razorpay focus more on the UX aspects, I thought I'll use this one to demonstrate my/our visual design heavy work.
Before We Begin, My Role and Responsibilities
- Led the product’s design and managed designers that worked on its multiple phases.
- Extensively hands-on for the first release. Conceptualised the product architecture and design language.
- Coordinated with teams, organised sync ups and brought everyone to the same platform to keep pace.
- Worked with the product team to define the product construct, came up with solutions and prioritise features.
- Worked with the tech team to come up with solutions that that would work in the constraints we had.
RazorpayX is a neo-bank for businesses in India.
Dealing with banks is painful and their products aren't built for what the new-age businesses and startups need.
Users and Use-Cases
Eventually, we want to build a platform that serves businesses of all shapes and sizes. The use-cases that we're focusing on right now:
- API Banking
Businesses that want to automate their money-flow. RazorpayX APIs are designed for developers.
- One-stop Replacement for Current Bank Account
By partnering with banks, we want to be the one-stop for businesses to manage all of their bank account and their entire money flow.
- MVP and Early access release
In January 2019, with the early access release, we aimed to solve API-based payouts (payments going out, a subset of use-case 1). Right now we have the product being actively used by a significant number of businesses for the same.
- Consequent releases and feature additions
Since then we've added a bunch of features to further facilitate the use-cases but we aren't done with the features to fully solve use case 2.
How we built the MVP in a Month...