u/ReasonableBox5301

I build Monni, an iPhone app for the moment before a purchase: after the bills due before your next payday and a cushion, what is actually safe to spend?

For people who left YNAB because the plan became too much work, would the first screen be more useful if it showed:

• the safe-to-spend amount
• the next bill and payday it is based on
• a tap to inspect the rest of the math

Or is there something missing that would make a short-horizon answer misleading? I am looking for the failure case, not compliments.

Try Monni on iPhone

I build Monni, a small manual money check-in, and I am trying to separate three different trust problems.

A consumer can have privacy commitments and a polished bank-connection story, yet still not trust a number if the cash, upcoming bills, and cushion behind it are hidden.

For a consumer money product, which failure kills trust first?

- no credible external security proof

- a secure product with an opaque calculation

- setup feels like work before it earns value

What would a credible minimum trust package look like?

I build Monni.

This is for the moment a balance looks spendable but upcoming bills and the cash you want to keep have already claimed part of it.

Start manually with cash, a bill, and a cushion. Monni shows the inputs behind what is left so you can check or change the number.

iPhone: https://apps.apple.com/app/apple-store/id6778174904?pt=103192850&ct=rd-bills-jul26&mt=8 Android or web: https://monni.io/?utm_source=reddit&utm_medium=community&utm_campaign=reddit_bills_first_jul26

If you use a money app, does starting without a bank connection make that first check-in more or less useful?

I build Monni. I wanted a money check-in that did not hand someone a magic “safe to spend” number and hide the reasons.

The first version starts with cash, upcoming bills, and a cushion, then keeps those inputs beside what is left. It is deliberately a short manual check-in, not a full category budget.

The part I am still testing: is seeing why the number moved enough to make someone come back next week, or does it still feel like personal-finance homework? I would value the blunt version.

I build Monni, a manual-first money check-in. This is product research, not a recommendation.

Mint gave people a lot of history but not always a clear next step. If an app gave you one number after upcoming bills and a cushion, what would it have to show to earn your trust?

• the exact bills and dates included
• why the number changed since last week
• a manual option before bank connection

Which of those matters most, and what is the fastest way an app loses your trust?

I build Monni and am separating download, signup, first answer, and a return check-in. A bills-first number can look useful in the first session without changing any decision. For a manual-first money app, would you call activation the first completed bills-and-cushion check, the first correction, or the second weekly visit? I am looking for a practical definition, not a growth hack.

I build Monni, a bills-first money check-in. I am trying to keep the weekly review short enough to return to without hiding the math behind one magic number. When a productivity app sticks, what earns the second open: a crisp next action, an obvious correction path, a visible summary, or something else? I want the blunt version, not downloads.

I build Monni, a manual-first money app. It is deliberately narrow: cash, upcoming bills, a cushion, then a clear answer about what is left.

The tradeoff is that a result before enough context can feel like a black box, while a full setup before any result makes the app feel like homework.

For products that produce a score, forecast, or recommendation: does your first run lead with the answer and reveal the math, or collect the inputs first? What makes one order feel earned rather than manipulative?

No link - I am looking for the design answer, not downloads or ratings.

I build Monni, a manual-first budgeting app. No link here - I want the design answer.

Budget name: Monni Budget style: manual, bills-first money management. You enter cash, upcoming bills, and a cushion rather than starting with a full category system. Similarity to YNAB: it overlaps on making upcoming obligations visible, but it is not an envelope-budget replacement; the first goal is an explainable after-bills number.

When you move away from YNAB or another envelope tool, which manual entry actually makes the number feel trustworthy: upcoming bills, a cash cushion, payday timing, something else?

What is the first setup step that crosses the line from useful context to homework?

I build Monni, a manual-first iPhone and web money app.

The first App Store screen currently has a plain outcome: what feels safe after bills. The alternative leads with cash, next bills, and a cushion so people can see how that number was reached.

My concern is that outcome-first may earn more taps but look like a black box; inputs-first may earn trust but bury the payoff.

For a finance category page, which sequence would you test first? What would make the “safe after bills” idea credible enough to keep scrolling?

No link here; I am looking for the ASO decision, not downloads or ratings.

I build Monni, an iPhone and web money app. I am choosing between two screenshot orders:

• outcome first: safe to spend this week

• inputs first: cash, next bill, cushion, then the result

Which earns a tap without looking like a black box? I want a real first reaction, not a download or rating.

A small campaign can produce a few page views and zero signup, which is easy to overread. It might mean the community or creative is wrong, the product page does not earn a download, or the first session does not show the promised value.

When the sample is too small for a conversion-rate decision, what qualitative evidence changes your next step? Do you prioritize response quality, product-page behavior, first-session drop-off, or something else?

I build Monni, a weekly money check-in. People could agree that “safe to spend” sounded useful and still not try it.

The next question mattered more: “When would you reach for this instead of checking your bank balance?” The useful answers were not about more charts. They were about a repeat moment: before a weekend, after payday, or when a bill changed.

That changed the work from explaining a finance dashboard to earning one specific weekly habit. What question has helped you separate polite interest from a job someone will actually return for?

I build Monni, a weekly money check-in. One thing I learned from early feedback: people do not object to a simple number; they object to a number whose inputs feel hidden.

The product treats upcoming bills, card payments, and a cash cushion as the things that reduce spendable cash. What is the smallest “why this number” explanation that earns trust without becoming another budgeting dashboard?

Would you show one expandable equation, a short ordered list of the biggest deductions, or a change log from last week? I am after UX feedback here, not downloads.

I build Monni, a personal-finance app. One thing I keep hearing is that people want to understand the inputs before they connect an account, even when connection would be faster.

For those who have worked on consumer fintech: where is the threshold at which manual setup earns trust, versus simply creating abandonment? What must stay visible and editable once data sync begins?

I am not asking for downloads. I am trying to avoid treating connection as a substitute for explaining the model.

I’m trying to understand the exact moment a savings goal stops feeling protected.

Is it usually an unexpected bill, spending from one mixed account, forgetting what is already spoken for, or setting the target too aggressively?

I build a money app, so this is product research, not a recommendation. What warning would have helped before you dipped into savings?

People I’ve talked to often forgive setup friction. They do not forgive a money app showing one wrong number. A duplicated transfer, stale balance, or unexplained “safe to spend” result makes every later screen suspect.

For anyone shipping imported financial data: what error causes the fastest uninstall, and have you found a recovery flow people actually trust? I’m especially interested in support or retention evidence, not opinions.

I build Monni, a budgeting app. One pattern keeps showing up: setup feels useful, then one missed week turns into cleanup and people stop opening the app.

I’m testing a simpler weekly habit around one question: after upcoming bills and a cash cushion, what is actually safe to spend?

If you’ve kept any money app longer than a month, what brought you back:

• one clear number
• automatic imports
• reminders
• something else?

Blunt product feedback is more useful than compliments.

I posted here last week about changing Monni’s promise from a broad AI money tracker to one decision: what is safe to spend after upcoming bills. The feedback since then is consistent: people understand the outcome, but they do not automatically trust the number.

The questions are about proof: which bills were counted, how fresh the inputs are, what changed since last week, and how to correct a bad assumption. So the next experiment is not more features; it is showing the math before asking people to act.

For products that output a score, forecast, or recommendation, do you lead with the result or the evidence behind it?

I build Monni, and the arithmetic is not the hard part: cash available minus upcoming bills, card payments, and a cushion. The hard part is earning enough trust for someone to act on the result.

Would you need to see every input and its freshness, a clear correction path when the number is wrong, or a manual/local-only option before connecting accounts? What destroys trust fastest in a consumer finance product like this?

No download ask here. I am trying to understand where useful guidance becomes an overconfident claim.