Switch language:

Lessons From Building Keppli Finance: From 0 to 700+ Users and 1700+ Downloads - 06/03/2026

Building a real financial product with real users is an experience no course can teach you. Here's what I learned taking Keppli Finance from 0 to 700+ users and 1700+ downloads on Play Store.

Website: kepplifinance.com

Building a real financial product, with real users, in a real market, is an experience no course can teach you. With Keppli Finance I learned more in months than in years of personal projects without users. Here’s what I took away.


The Number That Changes Everything: The First Real User

There’s an enormous difference between a project with zero users and one with one. That first user you don’t know, who didn’t give you direct feedback before downloading, who trusted a finance app with their data — that user forces you to be professional.

The first 10 users revealed bugs my tests never caught. Flows I considered “obvious” were completely confusing for someone without context. The onboarding I designed for myself didn’t work for anyone else.


Lesson 1: Personal Finance Is a Trust Problem, Not a Features Problem

The first thing I learned: users don’t look for the app with the most features. They look for the app they trust to handle their money.

That radically changes priorities:


Lesson 2: Offline-First Architecture Is Not Optional in Mobile Finance

In Latin America, connectivity is not constant. Designing assuming there’s always internet is designing to fail.

I implemented an offline-first strategy where:

1. User actions are saved locally (SQLite / AsyncStorage)
2. The UI responds immediately, without waiting for network
3. Sync with the backend happens when there's connection
4. Conflicts are resolved with deterministic merge logic

The result: the app feels fluid even with poor signal, and users in areas with intermittent connectivity became the most enthusiastic fans of the product.


Lesson 3: Onboarding Is Everything

70% of churn happens in the first 3 minutes. I learned this the hard way, analyzing drop-off points in the activation funnel.

I redesigned the onboarding three times:

  1. First version: full registration screen → users dropped off at the form.
  2. Second version: email + password registration, financial profile later → better, but “how much do you earn?” created friction.
  3. Third version: minimal registration (email only), first value action (log an expense) before asking for more data → Day 1 retention increased by 40%.

The rule: the user must receive value before giving information.


Lesson 4: The Metrics That Matter in a Personal Finance App

Not all metrics are equal. The ones that truly predicted Keppli’s growth:

I ignored download count as a success metric. 1700 downloads with 700 active users is a real retention of ~41% — which for an early-stage financial app is a solid number.


Lesson 5: Support Is Product

When a user writes to you with a problem, they’re not just looking for a solution. They’re evaluating whether they can continue trusting you. Every support response is a loyalty opportunity.

I implemented a support channel with responses in less than 24 hours. The impact on Play Store reviews was immediate: users who received support left 5-star reviews explicitly mentioning the attention.


What I Would Do Differently

  1. Ship faster with fewer features: I spent too much time polishing before validating with real users.
  2. Analytics from day one: the first weeks I flew blind because I had no event tracking. Costly.
  3. Monetization earlier: waiting too long to talk about money creates users who never expected to pay.

The Number That Matters Most to Me

It’s not the 1700 downloads. It’s not the 700 users. It’s the message I received from a user who said: “for the first time in my life I know where my money goes”. That’s the product working. Everything else is vanity.