Finamie turns your voice into detailed financial insights, automatically. Log expenses hands-free, track your spending, and understand your money like never before.
Every expense tracker I'd used wanted me to type things in. Open the app, add a transaction, pick a category, type the amount, type a note. I'd do that for a week and then stop, and after that the data was too incomplete to be useful.
I started with just voice logging. Hold a button, say the amount and what it was for, and the app pulls out the amount, currency, category, and description on its own.
After that worked, the transactions still didn't mean much on their own, so I connected them to income and financial goals so the analytics reflect the person's actual situation instead of generic charts.
Later I added a way to create new analytics by describing what you want to track in a chat, instead of building it through settings screens.
One thing changed from the original plan: I added a way to record a transaction and see it analyzed before creating an account, since requiring signup first didn't match what I was trying to do.
Happy to answer questions about any of this.
Report
Love it Santiago! Having spent control is key and you're making it so easy! Love to see this kind of projects launching here and wish you all the best
@german_merlo1 Thank you so much! I really appreciate your input!
Report
the "type a note for a week then stop" problem is real and voice is the right fix for it. what I'm curious about is the correction flow, since parsing is never going to be 100%. if I say "thirty five for lunch" and it hears "thirty five fifty" and files it under the wrong category, how many taps does it take to fix that transaction after the fact? that gap between "voice capture is fast" and "fixing a misparse is annoying" is usually where habits like this quietly die a second time.
@galdayan Great question, honestly this is opening my eyes to a gap I hadn't really tackled head on. Right now correction is basically: tap the transaction, manually edit the amount or category, save. So it's the standard few taps to fix, not a "no, I meant X" one-tap flow. That's fine if you're already fluent with the app, but you're right that this is exactly the kind of friction that kills the habit a second time, especially when the whole pitch of voice is not having to think about the UI at all.
I really appreciate you naming this so precisely. "Voice capture is fast, but fixing a misparse is annoying" is a much sharper way to put the risk than how I'd been thinking about it. It's pushing me to treat the confirmation right after parsing as its own moment, like showing "heard: $35, Food, tap to fix" immediately after capture, instead of making people go hunt down the transaction later. I'm going to spend real time on this before pushing voice capture further. Thanks for calling it out, truly.
Replies
Finamie
Love it Santiago! Having spent control is key and you're making it so easy! Love to see this kind of projects launching here and wish you all the best
Finamie
@german_merlo1 Thank you so much! I really appreciate your input!
the "type a note for a week then stop" problem is real and voice is the right fix for it. what I'm curious about is the correction flow, since parsing is never going to be 100%. if I say "thirty five for lunch" and it hears "thirty five fifty" and files it under the wrong category, how many taps does it take to fix that transaction after the fact? that gap between "voice capture is fast" and "fixing a misparse is annoying" is usually where habits like this quietly die a second time.
Finamie
@galdayan Great question, honestly this is opening my eyes to a gap I hadn't really tackled head on. Right now correction is basically: tap the transaction, manually edit the amount or category, save. So it's the standard few taps to fix, not a "no, I meant X" one-tap flow. That's fine if you're already fluent with the app, but you're right that this is exactly the kind of friction that kills the habit a second time, especially when the whole pitch of voice is not having to think about the UI at all.
I really appreciate you naming this so precisely. "Voice capture is fast, but fixing a misparse is annoying" is a much sharper way to put the risk than how I'd been thinking about it. It's pushing me to treat the confirmation right after parsing as its own moment, like showing "heard: $35, Food, tap to fix" immediately after capture, instead of making people go hunt down the transaction later. I'm going to spend real time on this before pushing voice capture further. Thanks for calling it out, truly.