I launched an app and learned that distribution starts with a sharper problem
I’m a factory worker in Italy, and I built and launched an Android personal-finance app in my spare time.
I originally thought the hardest part would be building the product. In reality, the hardest part has been explaining the problem clearly enough for the right people to care.
The app came from a personal frustration: I wanted to understand how much money was really available after accounting for recurring expenses, installment payments, savings goals, and upcoming commitments. A bank balance alone never gave me that complete picture, so I built a tool that combines those elements in one place.
A month after launch, most installs still come from people I already know. External distribution has been very weak. I tried a few launch communities, social posts, and local press outreach, but I learned that simply listing features — expenses, budgets, accounts, savings, installments, offline privacy — does not create a clear reason to care.
My current lesson is that a product can have many useful features but still need one understandable entry point. I’m now testing broader positioning around “understanding your real available money”, rather than presenting the app as just another budget tracker or installment manager.
For founders who found their first audience: did you start with the complete product, or did you lead with one specific problem and expand the message later?
I’d especially value examples of how you discovered the wording that made people immediately recognize their own problem.
The web-calculator-before-install idea is worth pushing on, because it solves two problems at once, not just the "ask for less commitment" one. Right now you don't know whether "real available money" resonates as a message or whether it resonates once someone experiences the calculation. A standalone version of the one number — no signup, no install, just "here's what you can actually spend until payday" — lets you test the language and the mechanism separately. If people react to the calculator but don't install, that tells you the number itself is the value and the app needs to be the natural next step from it. If they don't even engage with the calculator, the language still isn't landing, and you've learned that for free before spending more on distribution.
Worth trying that as the actual "narrow door" test before finding the exact worker language — the calculator becomes the thing you post in those payday-stress conversations, not a description of the app.
Thank you — this makes the “narrow door” much more concrete.
I had been treating a web calculator mainly as a lower-commitment way to introduce the app, but you are right: it can test two separate things — whether people care about the message, and whether experiencing the calculation creates enough value to make the full app the natural next step.
I’m going to build a small standalone calculator with no signup and no install required, focused on current money, planned income, bills, installments and known upcoming expenses before the next income date. The result will show the remaining spending margin and an optional daily estimate.
That gives me a much clearer experiment than continuing to post a feature list.
Thank you.
installments being a first class thing is very european, most us finance apps barely model them. that might be ur narrow audience right there
That’s a really useful observation — thank you.
I had been treating installments as one feature among many, but for a lot of people they are the reason their bank balance becomes misleading in the first place.
Nexmy already models installment plans with due dates, monthly impact and payment history, then includes them in the broader picture of planned commitments and projected balances. I may have been underestimating how strong that entry point is, especially for an Italian and European audience.
I’m going to test a more focused message around: “see what your installments leave you to spend after bills and planned expenses,” rather than leading with a generic personal-finance feature list.
Thanks — this gives me a much clearer angle to test.
installments being a first class thing is very european, most us finance apps barely model them. that might be ur narrow audience right there
installments being a first class thing is very european, most us finance apps barely model them. that might be ur narrow audience right there
Congratulations on launching your app! Doing this in your spare time while working in a factory is a massive achievement.
Your shift from listing features to focusing on "understanding your real available money" is exactly the right move. People do not buy budget trackers; they buy the peace of mind of knowing they can pay their bills.
Since you are targeting workers juggling bills, try looking for forums or threads where people talk about payday stress or managing tight monthly budgets. Instead of pitching the app, share a simple calculation tip: how to subtract fixed costs to find your "real daily budget." Mention your app only at the end.
How do you currently calculate "real available money" in the app? Sharing that specific formula in a short post could be highly valuable for early users.
Thank you — this gives me a much clearer next step.
In Nexmy, the idea is essentially: current available money + expected income, minus the expenses, installments, recurring bills and savings amounts already planned before the next relevant date. The result is the remaining spending margin based on what the person has actually entered.
I like your suggestion because it shifts the message from “use my app” to “here is a useful way to think about your money.” A short calculation tip could also help me learn whether the problem resonates before asking anyone to install anything.
I’m going to look for conversations about tight monthly budgets and recurring-payment stress, then lead with the calculation rather than a feature list.
Thank you.
The gap between 'bank balance' and 'what I can actually spend' is real and well-understood pain. The challenge with finance apps is that the problem is specific but the audience is everyone, which makes it almost impossible to stand out.
The question worth asking: which type of person experiences this exact version of the problem most acutely? Factory workers with installment payments and fixed schedules have a cash flow problem that looks different from freelancers or students. Starting with one tight slice and talking their language will outperform broad 'personal finance' positioning every time. Distribution starts with a narrow door, not a wide one.
This is a very helpful way to frame it.
I think you’re right: I’ve been describing Nexmy as a broad personal-finance app because it includes expenses, budgets, savings, accounts and installments. But the problem that made me build it was much narrower: I’m a factory worker with a fixed monthly income, recurring bills and installment payments, and I needed to know what I could actually spend after accounting for everything already committed.
I’m going to test a more focused starting point around workers with fixed pay and recurring commitments, instead of trying to speak to everyone at once.
The difficult part will be finding the exact language they use for this problem rather than imposing my own wording. Would you start with one specific occupation, or with a broader group such as workers with fixed monthly income and installment payments?
The language problem is real but solvable. The fastest way I've found: don't ask users how they describe the problem, just watch how they describe it unprompted. Reddit posts, app store reviews for adjacent apps, the exact words people type into search. Those phrases convert because they're already inside someone's head. 'Workers with fixed pay and recurring commitments' is your internal frame. The user phrase might be something like 'I know my salary and still can't save' or 'my bills eat my paycheck before I can plan.' Test those.
That’s a very practical distinction — thank you.
I can see that “workers with fixed pay and recurring commitments” is useful as my internal target, but it is not necessarily how someone would describe their own frustration.
I’m going to collect unprompted wording from Reddit discussions, reviews of adjacent finance apps, and search suggestions before changing the message again. The examples you gave already feel much more human than the language I have been using.
I had been trying to invent the right positioning first; observing the language already in people’s heads makes much more sense.
“Real available money” becomes sharper when tied to a moment: “How much can I safely spend until payday after every bill and installment?” I would start with workers juggling recurring payments, use their exact language from interviews, and offer a simple web calculation before asking for an Android install. Lead with the one number they want, then let budgeting, savings, and privacy become reasons to stay.
Thank you — this is very helpful.
I think you’re right that “real available money” is too abstract on its own. The actual moment I built Nexmy for was exactly that: looking at my balance and still not knowing what I could safely spend after bills, installments and recurring costs.
I also like the idea of offering a simple web calculation first instead of asking people to install an Android app immediately. That could help validate whether people care about the one number before I lead with the broader feature set.
I’ll start paying closer attention to the exact language people use around this problem.
Thanks again.