Building ExpenseSpy solo, no funding — launching June 17 on iOS & Android
Hey IH 👋
I've been lurking and commenting here for a bit, figured it's time to share what I'm building.
ExpenseSpy: snap a photo of a receipt, AI extracts the merchant, date, amount, and line items, and you export to Excel, CSV, or PDF in one tap. Multi-currency, built for one-person workflows.
A bit of honesty on the "why": I'm not someone drowning in receipts myself. But I kept watching freelancers, frequent travelers, and small business owners fight the same boring problem — manual entry, lost receipts, currency mess. Most expense tools are built for 50-person finance teams. I wanted something light enough for a single person.
The stack: Flutter (iOS + Android), OpenAI Vision for extraction, RevenueCat for subscriptions, Firebase backend. Bootstrapped, solo, first product.
Launching June 17. Right now I'm in the messy pre-launch stretch — Product Hunt scheduled, store listings in review, and a lot of second-guessing.
Two things I'd genuinely love input on:
- For those who've launched solo — what's the one pre-launch thing you wish you'd done differently?
- Freemium model (10 receipts/month free, then $4.99/mo). Too generous? Not enough?
If you want to follow along or get notified at launch: expensespy.com
Happy to answer anything about the build. Thanks for having me. 🙏
Congrats on the upcoming launch! As a fellow full-stack dev who is currently building a personal finance web app (just rolled out v2.0 of my project, TrackMentHub), I totally resonate with your "why". Most tools out there are bloated and built for 50-person finance teams, not for individuals.
To answer your question about the Freemium model: 10 receipts/month feels like a very sweet spot for a solo user. It’s enough for them to test the OpenAI Vision accuracy (which is the real "aha!" moment of your app), but low enough that any active freelancer or traveler will hit the wall by week two and consider the $4.99/mo premium.
One pre-launch advice since you are in the messy stretch: don't overthink the store approval delays or small bugs. Focus heavily on shouting about it on Twitter/X, Reddit, and LinkedIn right now to build a small checklist of people for your Product Hunt launch day.
Your stack (Flutter + Firebase) sounds super solid for a quick solo execution. Wishing you the best of luck for June 17th, I'll definitely follow along! 🚀
Really relatable problem, especially for freelancers and solo users. I’m also building small utility tools and can relate to the pre-launch overthinking part. One thing that helped me before launch was getting even a small group of real users early and watching where they get stuck, it gave more clarity than internal testing.
Freemium model sounds reasonable. The only question is whether 10 receipts/month is enough to show value without feeling too limited. Curious how you’re planning your first user acquisition , niche first or broad launch?
The positioning insight you already have is strong. 'Built for 50-person teams, but you're one person' is a real pain point. One thing I'd test at launch: target freelancers who just got their first international client. Currency pain hits hardest there, and they're actively looking for lightweight tools at exactly that moment.
This is a great wedge — "just landed their first international client" is so much sharper than "freelancers" in general. That's the exact moment currency tracking goes from "nice to have" to "I need this now." I hadn't framed the timing that precisely. Did you find that first-international-client moment shows up anywhere specific (certain communities, marketplaces, subreddits), or is it more about catching them through general freelance channels?
The freemium question is interesting but I'd reframe it slightly, 10 receipts/month is probably enough to feel useful, but not enough to create a habit. The risk is users hit the limit before the app becomes part of their routine.
From what I've seen with solo-user tools, the stickier moment isn't the capture, it's the first time they actually export something and it saves them real time. If you can make that happen within the free tier, the conversion case makes itself.
Good luck on the 17th. Solo launches are brutal and you're asking the right questions.
This is a really sharp point, and it's making me rethink the limit. You're right that the "aha" isn't the scan — it's the first export that saves real time. If someone hits the cap before they ever export, they churn without seeing the value.
Two things I'm now considering: either bump the free tier so the first export is basically guaranteed, or make sure the onboarding pushes them to export early (sample data, a nudge after the 3rd receipt). The habit has to form before the wall.
Really appreciate this — and the kind words. The 17th is going to be a ride.
The thing I'd be careful with is that receipt capture is rarely the reason someone pays.
A lot of products in this category can extract receipts. The harder question is what specific situation makes a solo user decide their current workflow is no longer acceptable.
That feels more important than the exact free limit or launch checklist.
I'd be cautious about treating this as a pricing decision before you're sure you're solving the right buying moment.
This is exactly the problem I built around, so I'm glad you pushed on it.
You're right that extraction alone doesn't make anyone pay. The buying moment I kept seeing: people who travel a lot rack up expenses across a trip, then weeks later finance or accounting comes back asking for a breakdown — and they're stuck digging through a pile of receipts trying to reconstruct it.
That's what the Projects feature is for. You group receipts by trip or project, so at any point you can see total spend for that trip and pull it back up instantly. And each receipt/expense carries a status — submitted to accounting, reimbursed, etc. — so the back-and-forth control gets a lot easier.
So the wedge isn't "scan a receipt," it's "when someone asks you to account for a trip three weeks later, you're not panicking." Does that line up with what you meant by the right buying moment — or do you see a sharper one?
Possibly.
The reason I'm hesitant to answer that directly in-thread is that the useful part isn't the observation itself. It's making the actual call.
That's the kind of decision that can change the positioning, paywall, and what users think they're buying, so I try not to make it casually in public.
If you'd like the tighter version, drop your email and I'll send it over properly.
Appreciate you offering the sharper version — and I get why you'd keep the actual call out of a public thread. Rather than emails, want to continue over IH DM? Happy to share more context on what I'm seeing on my end, and I'd genuinely value your read on it. Either way, this thread already gave me more than I expected.
Sure, happy to continue in IH DM.
Send me a note with a bit more context and I'll take a look.
Tried to DM but it looks like my account's too new to message yet 😅 No worries — you've already given me genuinely useful angles here in the thread. I'm going to work through the actual call myself before the 17th, since it's so tied to the product vision. Really appreciate you taking the time, and good luck with your work.
That makes sense.
The reason I kept stopping short is that once you get close to the actual call, a small positioning decision can end up shaping months of product and marketing work.
Given you've got the 17th in mind, I'd be more interested in whether the decision becomes clearer as you look at real users than whether the current wording gets sharper.
Curious where you land.