Hey Indie Hackers!
My name is Aaron and I recently launched Capsule: AI Expense Tracker to the App Store. This is my first launched product and I want to share the story while it's still fresh.
The Problem I Was Solving:
I'm a solo developer and I kept running into the same frustrating cycle — receipts stuffed in pockets, miles never logged, and that annual tax-time panic trying to reconstruct months of expenses from memory. Every existing solution felt bloated, expensive, or built for teams of 500, not someone like me. I travel for work quite often, so you can imagine how fast I could stack up receipts and expenses.
So I built what I actually wanted.
What Capsule Does:
Snap a photo of any receipt and Claude AI reads it instantly; merchant, date, total, category, and every line item; all organized automatically. No manual entry. No spreadsheets. Just open, snap, done.
On top of receipt scanning:
The Tech Stack:
React Native + Expo, Claude API, Supabase, RevenueCat, Google Maps SDK.
The Business Model
I priced it deliberately low because the goal was to actually solve the problem for as many people as possible, not build a paywall. I wanted users to actually experience something better than the enterprise-level expensing workflow that they already dislike, and frankly, dread.
Now, for the most important part...
What I learned building this:
Claude AI is genuinely remarkable for receipt parsing. Watching it read a crumpled, faded receipt in 2 seconds and extract every field correctly never gets old. Building the app was the easiest part for me; I have a technical background and grew up with the internet, so that wasn't the hard part. The hard part came after the app was built and working. The difficult part was trying to figure out how I was going to notify the world that this even existed. What was I going to do, walk down the streets with a sign, go to every website blog I can think of and start writing blurbs? Am I going to pay for $100's, even $1000's of dollars in ads on multiple platforms? It all seemed improbable and honestly it was a little bit anxiety inducing...
So, a little about me, I have an engineering background... What do I know about marketing? (I had to laugh a little bit, because the answer is absolutely nothing). So, as I was nearing completion of my app, I spent more time reading literature about marketing, watching lectures about driving organic growth, and consulting with anyone I had ever known about "What do you think I should do?"
One booked that actually helped me that I will namedrop here is called "Launch" by Jeff Walker. His read was very insightful, but other than that, I didn't ever find THE answer. And I think that is because there is not necessarily a right or wrong way to do this, there is only the way you choose and how you execute on it.
I spent days, weeks, multiple months thinking of my plan and I didn't only decide until the day of the launch... And that was to try a mixture of everything until I find that one outperforms the others and slowly knock those off the list. Not ideal, I know, but in my position, it makes the most sense to me analytically until I really resonate with a particular method.
If anyone has recommendations, I am absolutely all ears. I have found a couple amazing nuggets on Indie Hackers in the growth groups. But I will tell you something, all in all, I have enjoyed the experience in all of this. I set a goal, challenged myself, and I learned more than I thought I could have along the way, and ultimately, the knowledge is the reward.
As we stand today, I am on Day 2 of my launch, and I have achieved my first organic customer. (My first customer ever was my Mom, Haha thanks Mom!)
Revenue: $20 — Day 2. Let's see where this goes!
I'd love honest feedback from this community specific to marketing tactics; And if you're a freelancer or small business owner, what's your current expense tracking solution? What is the biggest criticism for any of the technology you already have in your workflow?
App Store link here for anyone that wants to check it out - Maybe we can collaborate or work on something together one day!
Thanks, Indie Hackers!
Nice milestone. One organic customer teaches more than a hundred guesses. I'd double down on where that person came from before adding new channels.
Yeah, I am certainly directing focus there for right now. I will keep you updated on how this turns out!
The receipts-stuffed-in-pockets thing is so relatable, I think every freelancer feels that tax-season panic. one thing that helped me with a first app was a short screen recording of the actual "snap a receipt, done" moment, it lands way harder than screenshots because people can see how fast it is. how are you planning to get the first batch of downloads?
First batch of downloads have been purely word of mouth and cold reaching out to my network. In my current field I have a lot of individuals that feel the same pain as mee, so I have been utilizing that. But I am now trying to segue into outside my network, but similar industries. I think I will then take my campaign online into the social networks
But yes, many responses have been about the demo of the product. Which I am almost done with, and I will make sure that is visible to anyone who can find the app. The next step, as mentioned before, is pushing it to people in and outside of my network with that exact focus.
Thanks for the comment Doremon!
This resonated with me because I'm also building my first product as a solo founder. The biggest surprise wasn't building it, it was realizing that creating something people genuinely need is only half the journey. Helping the right people discover it is a completely different skill.
I also appreciate that you kept your pricing focused on accessibility rather than maximizing revenue from day one. It takes courage to ship, listen, and improve instead of waiting for perfection.
Congratulations on your first organic customer. I hope it's the first of many.
Thank you! I appreciate the kind words.
Day two with one organic customer is still further than most solo builders get before distribution burns them out. The subreddit angle makes sense given the timing, tax season creates urgency freelancers don't usually feel. Have you run the numbers yet on what a heavy user actually costs you per scan, given the unlimited plan?
Yes, it actually costs me less than a penny per scan. So, an unlimited user would have to scan an unreal amount of receipts to make it even show up in the costs section. I would have to be generating quite a lot of traffic for it to be even recognizable on a ledger.
Good to know, sounds like the unit economics hold up fine even at heavy usage. Have you thought about someone trying to abuse the unlimited plan on purpose, scanning junk repeatedly, or is that not really a realistic risk given the volume it'd take to matter?
Yeah, this is a thought, and I do have a risk setting set aside which will be implemented at the right time, when it comes. However, to your pointed question, it would take a lot of volume, thousands of uploads on a monthly basis. Even then, the price is minimal.
Now, that doesn't mean it is impossible; just improbable. I am sure there is a way to spam it. But with the level of security I have implemented, I have flags in place for identifying an unreasonable number of duplications or exact timestamps for large data dumps, which would trigger a hold. Not a foolproof system, but something that would alert me so I can manually tend to it.
nice work
Your "mix of everything, then cut" plan is more right than you think, but give each channel a real number before you kill it, something like four weeks and a signup target, or you'll quit winners early. The bigger flag is pricing: $2.99 against a tax-pain problem reads as a toy to the exact buyer who dreads receipts most, and freelancers would pay $10 a month for this without blinking. Test the price before you test another channel.
Hmm.. I see what you're saying. The idea of the price itself may pose a bit of a subconscious 'gimmick' rather than something that is actually worth purchasing to solve your problem.
This is an interesting point. How do you recommend one price test? I am not certain how I would take advantage of this leverage, other than the research of 'What are other people charging?' or just trying to scalp something close to them but just under.
Any recommendations you have I will surely do the research and gather information. Thanks for the comment!
Congrats on the launch — especially shipping solo, that’s already a big milestone.
The product itself sounds genuinely useful, especially the “snap → auto-fill → done” flow. Expense tracking is one of those things people tolerate but rarely like, so there’s real room there if the UX feels fast enough.
On marketing, I think your instinct to test multiple channels is fair at this stage — just try not to stay in “spray and pray” for too long, or it gets expensive in time more than money.
Curious what your first organic user came from — that’ll probably be your clearest signal early on.
My first organic customer was actually word of mouth, and they are a contractor that had the same problem as me, but they were just able to bill the monthly fee back to their client.
And you're right, this immediately got me thinking about how can I focus an angle like this, where the price doesn't actually 'matter' as much as someone who may be paying out of pocket with this.
As for spray and pray, I definitely do not want to spend more than 30-60 days in this method. I am hoping to get at least a little bit of traction to where I can maybe create more focused content in a couple channels and then maybe mix in some social media ads. That seems like the common play, but ultimately, if done effiectively, it could be a good one.
Let me know if you have any other thoughts or what your experiences might have been! I am eager to learn!
Congrats on Day 2! Reddit comments in relevant subreddits (r/personalfinance, r/freelance) where your tool solves a real problem works well. Product Hunt: first 2 hours matter most. Good luck!
Thank you!
Yeah, I think I dropped the ball on product hunt. Didn't do enough there to gain any traction to be honest. But yes, I will start trying to post on Reddit as well.
I want to avoid too much self promotion, but I see some posts on there that follow that path. Do you have any experience with an effective approach without being pushy or something that seems like spam?
The trick that worked for me is to flip the ratio: for every 1 post about your own thing, leave 8-10 genuinely helpful comments where you mention nothing of your own. Communities can smell "I'm only here to promote" instantly, and that's exactly what gets flagged as spam.
A few specifics:
Honestly distribution is the hardest part for all of us. Consistency beats any single viral moment. Good luck with Capsule!
Thanks, Arafat. I have been up and down, and busy in general. But you're right about consistency.
I will continue the journey. I certainly appreciate the feedback too for navigating reddit. I will be sure to help the communities first and foremost!
Your built-in feedback system is the real marketing asset here. Ask your first 50 users what they'd actually type into App Store search, because at $2.99 as a solo dev that search box is basically your whole channel. Congrats on shipping.
Yes, I really need to lean into this and I have generated a decent chunk of feedback, but maybe I can do something to direct users there, or show them this tool in their onboarding.
Showing them that it contains already populated information may prompt them to engage more, which, would absolutely be a positive impact. I like this approach.
Thank you for your thoughts!
Happy to support!
One channel you didn't mention that's worth real time before you spend a dollar on ads: App Store search itself. Someone typing "receipt scanner" or "mileage tracker" is the highest-intent user you'll ever get, and most first-time devs leave the title, subtitle, and keyword field half-empty. "Capsule" tells the store nothing — your subtitle and keywords are where you win the "expense" / "receipt" / "mileage" searches. And the first two screenshots do more work than the other eight; make them show the snap-a-receipt payoff, not a feature list. ASO compounds quietly while you're figuring out the noisier channels. Happy to go deeper on the keyword field if it's useful.
I have tried to optimize my ASO as best as possible, I have named the app 'Capsule: AI Expense Tracker' to try and cover some of the additional 'findable words' too. As for screenshots, I definitely have the feature there, though it isn't the receipt capture itself, it is the elegant dashboard. But, maybe I should change that so users can see exactly what it does for them. Not just what it looks like after the fact.
How do you recommend I continue to support ASO? I find there is only limited space for the relevant wording. My current intent is to try and generate enough traffic word of mouth to try to get moved up the list in the app store a bit via feedback and ratings. But I know it doesn't always work like that.
Let me know if you have any further suggestions, I will definitely do a little more research regarding this topic.
Congrats on the first organic customer — day 2 with a stranger paying is a real signal, not luck. I work in an adjacent space (I build order-to-accounting sync tooling for Shopify merchants, so I stare at receipts and expense workflows all day) and one thing I learned the hard way about distribution: cold social barely moved anything for me, but being findable at the exact moment of pain worked. For your product that moment is probably "scanned receipt won't import into X" or "mileage log for taxes" type searches — a couple of genuinely useful posts targeting those exact phrases can quietly outperform weeks of feed posting. Curious about one thing: are you seeing users who already have an accountant/bookkeeper, or mostly people doing their own taxes? The two groups pay for very different things in my experience — the first group pays for clean exports, the second for peace of mind.
Thank you! And thank you for sharing your experience, this is a great comment too. I typically am seeing customers that already have an accountant and/or bookkeeper. And that's because this tool helps you organize what you may give to them, or if you do it yourself, you could absolutely use this tool to do so. But you are right, someone is not looking for capsule to make their taxes easier, it's just to make their lives less painful while they spend all of their time entering in all of the tax information.
The clean exports, tracking of spends, 'snap it and forget it' gives them comfort in knowing where to find a receipt come that time of the year, not necessarily that it will do the work for them. But, for example, for someone who travels for work, now you have a clean export to send to your company to bill for the expense. a couple captures, a clean summary, ready for upload and submission.
So, all in all, to answer your question, there are avenues for people who want to use it for tax time surely, but it would be more beneficial to hand these exports and their receipts to a bookkeeper themselves. I personally use it more for expense reporting than for taxes. But, for a business case, I snap receipts because I know where I can come back and find them.
Hopefully this made sense and answered your question. I appreciate the question, it drove me to a couple thoughts.
Solo founder iOS launch is brutal. The Brief Network took 30 days to ship 8 newsletters from zero — same principle: ship first, optimize later. What's the one thing you'd ship differently if you did it again?
Hmm great question. If I shipped again, the one thing that I would do differently is certainly try to get the word out at least 30 days before I launched. Trying to generate some buzz rather than a cold, hard launch might have been the way to go.
An honorable mention might have been trying to gather users to test the app from random communities, not just people I knew. I think this would have been a great way to learn honest feedback, not that friends and family aren't honest, but they tend to be more delicate.
This is a good question, and will surely be implemented into my next project.
Ship first, optimize later. If I shipped again, the one thing I'd change is getting the zero-overlap validation done before touching Beehiiv — we spent a week re-checking after draft, which was inefficient. But shipping in 30 days > optimizing in 90. The momentum unlocks everything else.
Yes, I agree whole-heartedly with this.
Congratulations on the launch! I really enjoyed reading your story, especially your point that building the app was the easy part and distribution became the real challenge. I think that's something almost every indie founder eventually discovers.
One question I'm curious about: now that you've started getting real users, have you noticed one type of customer getting significantly more value from Capsule than others? It seems like focusing on a very specific niche (e.g. consultants, freelancers, or people who travel frequently for work) could make your messaging much stronger than trying to appeal to everyone. Have you seen any early signals pointing in that direction?
Thank you, Richard! Definitely one of my most exciting projects.
But to answer your question, I don't have enough data to particularly see one way or the other who is benefiting the most from it. Currently, I have individuals who do contractor work that are using it that bill the monthly costs back to their client, mostly in the construction industry. I also have a couple people who do book keeping, and this helps their process.
These are the only data points that align with what you're saying, to specifically push towards specific groups. But, as I grow (hopefully) I will be able to identify the most active and impacted communities.
The receipt capture moment is your strongest angle. Most expense trackers assume people will remember to log things later, but you've cut that friction entirely. That's why the demo works - it solves the actual moment of pain, not an imaginary ideal version of someone's workflow. Your comment about needing to show up gradually is smart too. Freelancers don't think about your product until tax season stresses them, so building that mindshare now (blogs, Reddit communities) pays off in Q1.
I agree with this, and I appreciate your thoughts. Saving someone time and effort, and getting the immediate result should certainly be the focus. The demo is a great idea; it can be quick and clean, showing the simplicity and the desired result. I will definitely look into the Reddit communities too, I am sure there are many on there that would be of interest in some of those communities come Q1. Thanks, Omri Ben!
The pricing flag in the comments is worth taking seriously before heavy users arrive. If the per-scan API cost is meaningful at scale, $2.99/month stops being sustainable at exactly the moment the product starts working. Better to find that ceiling now than after you've built an audience around a price you can't keep.
The observation that distribution confidence is its own ongoing problem resonates. Most founders treat it as a one-time launch task when it's actually the thing that has to keep running in the background every single week regardless of what else is happening.
Yes, I definitely have an eye on the pricing flag and the API costs. With the current setup, it would take hundreds of customers and thousands of receipts a month to make a meaningful impact to create costs against the revenue. At Capule's current stage, this is not a concern. But it doesn't mean it will never be one!
As for the distribution confidence, are you referencing the confusion and overwhelming experience of marketing efforts? Just want to make sure I am understanding the comment. Because, yes, I think I knew that it would be an ongoing effort and not a one-time activity. I think it was the thought of 'How do I get this off the ground?', and not as much 'How do I keep this in the air?', if that makes sense.
The comments here have given me my first few strategies to try, the Demo being the most important. But I truly appreciate everyone's comments and feedback! Thank you.
What feels right here is that you went after the exact moment the data gets lost, not some prettier dashboard after the fact. Receipts in pockets and "I'll log it later" are basically the same failure mode as notes people mean to write and never do. That's a big part of why I built DictaFlow: capture the thing while it's still in front of you, before memory turns it into admin work. The demo clip matters, sure, but the real moat is that you took reconstruction out of the workflow.
You hit the nail on the head. Everyone likes to see a pretty dashboard and read the data there, but I wanted to focus on how 3 clicks (or taps in this case) can save you minutes, even hours of time depending on how often you have to repeat the process for your current workflows.
The demo has been mentioned a few times in this comment section and I am surely going to take everyone's advice and make that my next focus!
I will have to take a look at DictFlow, I like the idea of that as well. Do it now, or else you will never do it. Sounds like how I felt when I was staring at the screen deciding if I was going to release the app to the app store. Congratulations on your app as well, hopefully it is thriving!
Really helpful to read this. As a non-technical founder I keep going back and forth on how much to build vs validate first — how did you decide?
This is a great question, and I actually compiled 10s of builds before I finally decided that I was going to even submit it for app store review.
I built probably 80% of the application, including all the major components and some of the intermediate/nuanced items. I then tried to break it in every single possible way I could, corrected all those bugs, then holistically looked at what I had.
I wrote down the 5-10 most important things that needed to be implemented, 3-5 things I'd like to have, and then 3 things where I said 'This needs more attention.' I went through that list and again, made sure I couldn't break the app.
Once that was done, I had some testers take a look and try it out. After some positive (and harsh feedback). I made adjustments based on user feedback and then went to release. I knew that if I kept trying to make everything perfect, then I would never get it out to the world.
the honest good news: for this product your best marketing asset is a 15-second screen recording of snapping a crumpled receipt and watching Claude auto-fill merchant/date/total in 2 seconds. that "wait, it just did that?" moment sells itself. lead with that clip everywhere (Reels, TikTok, X), the demo convinces more than any copy you'd write.
on channels, don't spray. your buyer is already complaining in specific places: r/freelance, r/smallbusiness, r/digitalnomad (you travel, so do they), and r/tax gets loud Jan-April. show up as a freelancer who got tired of the receipt panic and built a thing, not as an ad. and tax season is your Super Bowl, so start the "freelancer receipt tracker / mileage log for taxes" ASO plus a couple of blog posts now so they're ranking by January.
one non-marketing flag since you priced deliberately low: $2.99/mo unlimited with a Claude call on every scan means a heavy user (200+ receipts a month) can cost you more in API than they pay after Apple's 30%. worth a fair-use ceiling or a usage-based Pro tier before you scale, or your best users quietly become your least profitable ones.
I appreciate the feedback on both sides of the coin, this is exactly what I was hoping for with the engagement in this community.
Another comment mentioned the demo/marketing tactic, and I totally agree. A 15-second short clip of the app being used is quite a beneficial selling point that I will utilize. All questions can be answered in a quick clip and 90% of the value add can be seen there, which is the biggest attention grabber I can offer at this point I think.
As for the non-marketing flag and the API usage, this is definitely something I have taken a look at, and will need to be addressed... However, I have crunched the numbers, and the reason I priced deliberately low is because the token inputs and outputs for 1 receipt cost very very little. So, as I scale, things will change, but given the volume now, the costs are so near obsolete that it currently isn't a concern.
But, you are absolutely right in the fact that it will need be monitored as progression and growth continue. I think a scaled in usage tier (a middle tier) will certainly become an reality.
I like that you realized building wasn't the bottleneck.
A lot of founders assume distribution starts after the product is finished. In reality, building confidence that the right people will discover it is its own product problem. Solving that often takes as much iteration as the software itself.
Building never felt like the hard part, in fact, it was the most fun. And I am sure others feel the same.
One thing I read much of was to create a waitlist, seemingly to help verify that people would even be interested in the product itself. However, I quickly realized that I didn't even have that understanding.
It still felt like the same idea to me, of needing money and a larger network to even make that worthwhile. So, ultimately I felt like I was in the same boat that I was already in.
My biggest takeway from this journey to identify or plan out how I should show the world what I built at an earlier stage, in a slow gradual path. It will surely be something I spend more time on in future endeavors.
I think that's exactly where the next strategic decision begins.
Your reply made me think there's one business decision sitting underneath that realization which becomes much more significant as future products build on it, but I don't think I can explain the reasoning properly in a thread without oversimplifying it.
If you're interested, what's the best email to reach you on?
Sure thing, feel free to email me at [email protected]. I appreciate the communication!
Thanks! I’ve just sent it over.
Looking forward to hearing your thoughts whenever you have a chance.