Building a consumer app in 90 days sounds reckless. But with the right constraints — clear scope, a disciplined team, and a go-to-market plan built in parallel with the product — it's not only possible, it's often better than spending 9 months on something no one asked for.
This is the story of a FinTech app we took from zero to 10,000 downloads in its first quarter.
The Brief
The client had a validated idea: a personal finance tracking app designed specifically for Indian freelancers and gig workers — a segment traditionally underserved by banking apps that assume a steady salary income.
They needed the product designed, built, and launched on both iOS and Android. They had a 90-day window before a competitor they knew about was likely to launch something similar. Speed was the strategy.
Week 1–2: Product Definition, Not Feature Speculation
Before we opened Figma, we spent two weeks on product definition. Not an extensive discovery process — just three focused questions:
- What is the single most important thing the app needs to do on day one?
- What does success look like in week 12 (not year 3)?
- What can we cut without compromising the core promise?
The answers shaped every subsequent decision. The core promise was: "Know exactly how much you can spend this month." Everything else was secondary or deferred.
Week 2–5: Design with Constraints
We designed in Figma with the following constraint: every screen had to be usable one-handed, on a mid-range Android phone, in under 5 seconds. This forced clarity — no complex navigation, no modal-heavy flows, no features that required explanation.
The design system was minimal by choice. Three primary colors. One font. Consistent spacing tokens. When you're building fast and building to a budget, a simple design system is a feature, not a limitation.
The best feature we almost didn't build: a single-screen monthly summary that answered "am I doing well this month?" with a color (green/amber/red) before the user even needed to tap. It became the feature users mentioned most in App Store reviews.
Week 4–10: Development in React Native
We chose React Native for one reason: a single codebase for iOS and Android halves development time at this scale. Performance is near-native for data-heavy apps. The ecosystem is mature enough to find libraries for everything we needed — open banking APIs, biometric auth, push notifications.
We ran two-week sprints with a standing rule: no new features enter a sprint once it starts. Scope creep on a 90-day timeline is a project killer.
Week 8–12: Launch & Growth
We submitted to both app stores in week 11 — iOS App Store review took 3 days, Google Play took 2. We launched on a Thursday (statistically, the best day for app launches — lower competition for featured slots).
The go-to-market strategy was content-first: we'd spent weeks 6–10 building an audience of Indian freelancers through a newsletter and Twitter community. The launch email went to 4,200 subscribers. The App Store and Play Store reviews started within hours.
The Results
10,000 downloads in the first quarter. A 4.7-star rating from 340+ reviews. And a D7 retention rate of 62% — meaning 62% of users who downloaded the app were still using it 7 days later. Industry average for FinTech apps is around 35%.
The 62% retention was the number we were most proud of. Downloads are a vanity metric. Retention means the product actually works.