After 8 months of nights and weekends, two Apple rejections, and more debugging than I want to admit β CoinCoach is officially live on the App Store today.
https://apps.apple.com/us/app/coincoach-ai-money-coach/id6770703206
I want to share the journey while it's fresh β the why, the build, the rejection saga, and what I'm scared of going forward. Hopefully useful for anyone else in the trenches.
I moved to the US when I was 16. My mom worked seven days a week to support us β and still does. She has always managed paycheck to paycheck with more discipline than most people I know.
But the bigger money questions β retirement, buying a home, whether she could ever afford to stop working β never had answers. Those answers exist for people who can afford financial advisors. We couldn't.
She tried Mint. Spreadsheets. The ones that link to your bank and bury you in charts. They told her nothing she didn't already know. The feature lists clearly weren't designed for someone with her financial life.
So I decided to build the thing she actually needed: not another dashboard, but something closer to a knowledgeable friend who happens to understand money β available at 11pm when the worry hits.
A personal finance app built around an AI coach. You track expenses, set goals (table stakes). But the core is this: you can ask the AI anything about YOUR money, and it answers using your actual data.
"Can I afford a $400 trip this month?"
"Where is my money actually going?"
"Should I build my emergency fund or pay down this card first?"
Plain language. Specific to your numbers. No judgement. No "consult a professional" deflection on questions a thoughtful friend would just answer.
The thing I'm proudest of isn't technical β it's that my mom can use it without me on the phone walking her through it.
Shipping beats native perfection. Choosing Capacitor over learning Swift is controversial, especially for a finance app. But I had a working PWA months before I had an iOS build. Real users beat hypothetical elegance.
The AI was the easy part. The trust was hard. Making an LLM answer finance questions is straightforward. Making it feel safe, honest, and non-judgmental β and ensuring it NEVER pretends to be a licensed advisor β took most of my prompt-engineering time. I hardcoded the safety guardrails server-side so they can't be bypassed.
Privacy as a feature, not a checkbox. CoinCoach never connects to your bank. You enter expenses manually or snap a receipt. I lose the "automatic" convenience, but I never touch anyone's bank credentials, and that tradeoff felt non-negotiable for the people I'm building for.
Apple rejected me twice before approving. Sharing the specifics in case it helps someone:
Rejection 1 (Guideline 2.1(b), 3.1.2(c), 1.5):
Rejection 2 (Guideline 2.1(b) again):
The fix that finally worked: Sign out of personal Apple ID from App Store on the test iPhone (NOT iCloud level, just App Store), use a fresh sandbox tester account, record a complete fresh purchase flow on physical device starting from the Home Screen. Took about 4 hours total.
Lessons for anyone hitting these:
I'm sharing this at $0 revenue on purpose. I'd rather document the real journey than show up later with a polished "here's how I made $10k" story that hides the uncertainty.
Distribution. I knew shipping would be hard. I underestimated how hard "getting people to find it" would be. I have a small Reddit account (12 karma, lol), a Twitter/X profile with zero follower, and a landing page that's converted maybe 2 waitlist signups. I'm posting on Indie Hackers because this community has been quietly essential β countless late-night searches landed on IH posts from people who'd hit the same walls I did.
I don't have a network. I don't have an audience. I don't have a "marketing budget." I have a real product, an honest story, and the next year of nights and weekends. If you have any advice on early traction for B2C iOS apps, I'm all ears.
If you want to try it (iPhone only for now): https://apps.apple.com/us/app/coincoach-ai-money-coach/id6770703206]
The landing page: https://coincoach.app/
If the story resonates and you know someone who'd benefit β a freelancer juggling 1099 income, a parent who never got financial advice, anyone who deserves a money coach but can't afford one β please share. That's who I built this for.
And honestly: even if you never download it, feedback from this community matters more than downloads. What would make you trust an AI with your finances? What would make you NOT? Those questions keep me up at night and I'd rather hear it from you now than learn it the hard way.
Thanks for reading. Now I'm going to go refresh my App Store Connect dashboard a hundred more times.
The grind is part of the deal. What nobody tells you is that it gets quieter before it gets louder. How are you holding up?
8 months of nights and weekends and you ship for your mom first. That's a better product brief than most funded startups write. The Apple rejection details are genuinely useful β the 'attach subscriptions to version separately' one trips up almost everyone their first time through App Store review.
On distribution with no audience: the IH post is the right call. The fastest thing that worked for me early on was finding the communities where my users were already in pain and just helping, not promoting. Your story about the 11pm money worry is exactly the kind of thing that lands on r/personalfinance or r/Frugal. Not a pitch. Just honest context about why you built it. A handful of genuine comments in the right threads are worth more than weeks of Twitter posting. What does your beta user feedback look like so far?
"Better product brief than most funded startups" β that's generous. Thank you! Building for one specific person I know deeply has been the constant when everything else felt uncertain. The fact that other commenters in this thread keep gesturing at the same thing makes me trust it more.
The Reddit strategy is now officially the most-repeated advice in this entire thread β you're the fourth commenter pointing at the same play, and each one added specificity. The framing you just added is the sharpest: bring my STORY into existing threads, not a pitch. "I built this because my mom had 11pm money worries" lands differently than "check out my app."
On beta user feedback: honestly minimal. A handful of beta testers used the app over the last few months β feedback was mostly mechanical ("this button is unclear", "this flow felt confusing") and led to UX fixes. The product-level questions β does the AI Coach actually deliver value, would users pay, what's the right tier limit β I don't have data on yet. My mom is the most active "user" I have, and her feedback has been "I trust this more than the other apps I tried" but I obviously can't generalize from her alone.
Launching is partly about ending the hypothesis phase and entering the observation phase. Going to spend the next 30 days watching what real downloaders actually do (or don't do) before adjusting anything major.
Thank you for your time and feedback. I really appreciate it
β Thuy
The 30-day observation plan is exactly right. Watch what real users actually do before adjusting anything. The gap between what beta testers said and what real users do is always the interesting part. Good luck with it. Rooting for you on this one.
Every indie hacker hits the wall. The ones who make it work are the ones who adjust, not quit. What's your next move?
I got bounced twice on my own iOS thing β a tiny memo app β and both times it was Guideline 4.2 "minimum functionality," not an actual bug. What finally cleared review was boring: a sharper screenshot set and one line in the review notes saying exactly who it's for. Reviewers seem to reject the pitch as much as the binary.
The "built it for my mom" part is the real moat, honestly. Most finance apps are made for a generic "user" who doesn't exist; building for one person you understand deeply is what makes the first 50 strangers feel seen too. How are you planning to reach more people like her β through her, or somewhere she'd never think to look?
The Guideline 4.2 angle is interesting and not something I'd considered. My rejections were both 2.1(b) β subscription mechanics, not the pitch β but you're right that the reviewer is evaluating the COMMUNICATION around the product, not just the code. Sharper review notes that name the user explicitly might've saved me a cycle.
The "moat" framing is generous but I think you're onto something I hadn't articulated. Yesterday a commenter pushed me to "narrow my segment" β which felt right intellectually but I couldn't figure out how to act on it. Your reframe lands harder: I already picked the segment. She's my mom. The work isn't choosing a segment, it's communicating that I chose one. That's a more actionable problem.
Your question is the one I genuinely haven't worked out. I think the honest answer is some of both, but probably weighted differently than I'd assumed:
β "Through her" works for the parts of CoinCoach that hit the immigrant-family experience β there are real communities (Vietnamese, Chinese, Indian diaspora finance discussions on Reddit and Facebook groups) where the story would resonate. But she's not on those platforms, so I'd need to find them myself.
β "Where she'd never think to look" is the more interesting answer. The actual buyer for CoinCoach might not be the immigrant mom β it might be her adult daughter or son who downloads it FOR her, or recommends it. That's a different distribution game entirely. Adult children of immigrant parents are on the same Reddit threads where everyone keeps telling me to comment.
So: same Reddit strategy I've been hearing all day, but with sharper targeting β looking for "I want to help my parents with money but they don't trust finance apps" energy specifically, not just generic personal finance threads.
Genuine question back: when you were figuring out distribution for your memo app, did you find it harder to identify your audience or to actually reach them? I'm finding the "where do they exist" question more answerable than the "what do I say when I find them" question.
Thank you for your time and sharing your inputs
β Thuy
The Apple rejection saga is painfully relatable β the "subscriptions attached vs just created" distinction is exactly the kind of undocumented gotcha that burns everyone at least once. Thanks for writing it up so specifically, that'll save people hours.
On your distribution question: your "built it for my mom" framing is genuinely compelling and your best asset right now. The next move is getting that story in front of r/personalfinance, r/financialindependence, or r/frugal β not as a launch post, but as a comment or story in threads where people are already complaining about the apps they use. Your target users are there, describing exactly the problem you solved.
The "no bank connection, manual entry" angle is also a real differentiator with that crowd β a lot of r/personalfinance users are specifically suspicious of apps that touch bank credentials. Lead with that in your Reddit presence, not just in the App Store description. Good luck with Day 1.
Thank you LifePilot for that β the Apple writeup was partly catharsis, partly hoping it'd save the next founder some hours. I'm so glad it landed.
The Reddit strategy is officially settled in this thread β you're the third commenter today pointing at the same thing, and each one made it more specific. The earlier commenters said "answer questions where people ask them" and "YNAB price complaints + 'don't want to link my bank' threads." You named three exact subreddits and framed it as comments-in-existing-threads, not launch posts. I'm going to start a daily habit there.
The "no bank connection as a differentiator specifically with the personal finance crowd" insight is the one I hadn't fully internalized. I built manual entry as a privacy tradeoff (better for my mom) but I haven't been positioning it as a value prop for the r/personalfinance subset that's already suspicious of Plaid-backed apps. That's a sharper angle than how I've been talking about it. Going to think about how to lead with that more in the Reddit voice specifically.
Thanks for the time and the specificity β both of those make a real difference.
β Thuy
Congrats on shipping. I build a personal finance app too (Money Me, web first, manual entry, no bank linking) so a lot of this is familiar. The manual entry tradeoff you describe was the same call I made, and users bring it up as a reason they stay, so I don't think you lose as much as it feels like. On distribution for B2C finance: the YNAB price complaint threads and the "I don't want to link my bank" threads on Reddit are where my best signups come from. People literally describe the product they want, you just have to already be in the thread when they do. Slow, but it compounds. Directories did almost nothing for me. And one thing from the Android side: when you eventually go to Google Play, their closed testing gate needs 12 testers across 14 days before you can release. Plan for it earlier than I did.
Congrats on your app Money Me and I hope it does well. The retention validation actually matters to me a lot: I had a hypothesis that manual entry would FILTER for engagement (people who'll do the work also stay) but I had zero data. Knowing your users actually cite it as a reason they stick around is the signal I needed.
The Reddit distribution play is the most actionable thing I've heard. YNAB price complaints and "I don't want to link my bank" threads are exactly where people describe the product I built in their own words. Going to start a daily habit there.
Directories noted β saving myself from that rabbit hole. And huge thank you for the Google Play closed testing heads up. I had no idea about the 12 testers / 14 days gate. I'm iOS-only for now but Android is on the roadmap, and "plan for it earlier than I did" is exactly the kind of warning that's worth its weight.
Genuine question: when you find one of those YNAB/bank-linking threads, do you reply with a direct mention of Money Me, or do you answer their question substantively first and just have your link in your bio/profile so they discover you? I'm trying to figure out what threads the right line is between helpful and self-promotional.
Thanks for taking the time
β Thuy
respect for pushing through the rejections. for mobile apps, the first impression often does more work than founders expect - i ran into that enough that i built appkit for it. happy to share if useful.
the hard part after launch is usually the first impression loop, not the build itself. for mobile apps i keep seeing screenshots do more work than founders expect, which is why i built appkit. happy to share if useful.
respect for pushing through the rejections. for mobile apps, the screenshots and first impression often do more work than founders expect - i ran into that enough times that i built appkit for it. happy to share if useful.
Thanks π You're not wrong about screenshots β you're actually the third commenter on this thread to flag the same thing (others pointed at positioning and "answering who is this for" specifically). I'm clearly missing something in the first impression.
Going to sit with the broader positioning question first before doing a screenshot redesign β feels like the screenshot is downstream of figuring out who I'm actually talking to. But appreciate you raising it. I'll keep appkit in mind if I get to the stage where the right framing is locked in and I just need the production help.
β Thuy
Every indie hacker hits the wall. The ones who make it work are the ones who adjust, not quit. What's your next move?
Thanks π The adjust-not-quit framing is the right one for where I am.
Next moves, honestly:
The "wall" piece is real β quiet Day 1 was already humbling. But you're right that the answer is calibration, not exit.
β Thuy
Built it for my mom β that framing is exactly what makes the "knowledgeable friend, not another dashboard" call ring true; Mint-style charts mostly tell people what they already know. I went through the Apple rejection wringer on my own little iOS side project (a Captio-style memo app): bounced twice, once on a guideline I'd plain misread, and the resubmit anxiety was honestly worse than the original build.
What calmed me down was treating each rejection as one concrete checklist item instead of a verdict on the whole app. And choosing Capacitor over native to actually ship, rather than chase Swift purity, is the same trade I'd make again. Now that you're live, are you leaning on RevenueCat's trial conversion to find your first payers, or holding the paywall back until the AI coach has clearly proven its value to someone like your mom?
The "checklist item, not verdict" framing is exactly right β and exactly what I lost sight of during the second rejection. The first one I handled fine. The second one (the IAP-not-found-in-binary one) felt like a deeper "your app doesn't actually work" verdict instead of "your screen recording showed Restore Purchases instead of a fresh purchase." Hours of catastrophizing before I sat down and reread what they actually wrote. Stealing your framing for next time. Thank you!
Solidarity on the resubmit anxiety being worse than the original build β that hit. I had infrastructure that worked, content that was approved, and still felt sick every time I clicked Update Review. Solo founder thing maybe, or just the asymmetry of caring more about the app than Apple ever will.
Your paywall question is the one I've been wrestling with and don't have a confident answer to. Right now I'm doing the standard thing: free tier with 25 AI Coach messages/month, paywall triggered when they hit feature limits or try receipt scanning. RevenueCat is handling trial conversion. But your framing has me reconsidering β for an AI finance coach specifically, the trust barrier is so high that "let users prove to themselves it works before asking for money" might actually be the right call. The risk is I just trained users to expect free forever.
What did you end up doing with your memo app β early paywall or later paywall? And did the data tell you you'd made the right call, or did it take time?
I really appreciate you sharing your rejection experience. It helps to know the anxiety wasn't just me.
β Thuy
Congrats on shipping. I build in the same space (manual entry personal finance, no bank linking) so a lot of this landed. The no-bank-linking call is right for this audience. It filters for people who actually want to engage with their money rather than glance at a dashboard, and they stick around longer. On the trust question: what would stop me handing finances to an AI isn't accuracy, it's not knowing where the data goes. You already run the AI calls server side with guardrails - say that on the landing page in one plain sentence. On distribution with no audience: the questions your coach answers are the exact questions people type into Reddit and Google every day. Can I afford X, emergency fund or credit card first. Write honest answers where people already ask them. Slow, but it compounds and costs nothing. Good luck with the marathon.
Hi Markbnet. Thank you for reading my story and sharing your inputs. This is the most useful comment I've gotten β and it's from someone in the trenches, which makes it land harder.
The retention point hadn't crystallized for me until you said it that way: "manual entry filters for people who actually want to engage." That's a much better way to frame the no-bank-linking decision than I've been articulating it. If you're open to sharing β what's retention look like for you compared to bank-linked apps?
On the trust positioning: you're completely right. I have all the right technical infrastructure (server-side AI calls, no PII sent, hardcoded safety prompts) and it's nowhere on the landing page. That's a fix I can ship this week β one plain sentence in the hero or right under the founder story. Going to think about the exact wording and would actually love your gut reaction if you have one. "Your data stays yours: AI runs on our servers with hardcoded safety, we never sell anything, delete anytime" β too long, but in that direction.
The distribution insight is the one I needed most. "Write honest answers where people already ask them" β that maps perfectly to the AI Coach's actual use cases. The questions are exact: can I afford X, emergency fund vs credit card, savings rate at my income. I have the answers in the app already. I just haven't written them where humans search. Going to start a habit of one thoughtful Reddit comment per day in /r/personalfinance and adjacent subs, answering real questions with real reasoning. Slow as you said, but I have time and not money.
Genuinely β thank you so much. This comment was worth the launch.
β Thuy
great story. make the first screenshot answer who it is for and why it matters today.
Oh, this is sharp. You're right β my first screenshot is the AI Insights, which shows WHAT it does but not WHO it's for. Two IH commenters now have pointed at this same gap (aryan_sinh flagged that I'm diluting across too many user segments). I'm noticing a pattern.
Sitting with what the right first-screenshot positioning would be. The closest framing I have is something like "Built for people who never had a financial advisor" β which is true to my mom's story and the "no bank connection, no judgement" positioning, but I haven't translated that into a screenshot yet.
Genuine question: when you've seen App Store listings nail this, what made the difference? Was it the text overlay, the actual screenshot behind it, or the emotional cue? Curious what catches your eye specifically. Thank you so much for the feedback.
β Thuy
This is a strong story, but Iβd be careful not to let the story carry all the distribution weight.
The sharpest angle is probably not βAI finance app.β That category sounds crowded and risky.
The stronger frame is closer to:
βa private money coach for people who never had access to financial advice.β
That fits the mom story, the no-bank-connection choice, and the no-judgment AI positioning much better.
For early traction, Iβd avoid broad B2C app marketing first. Iβd pick one emotionally specific user segment: freelancers with uneven income, immigrant parents managing paycheck-to-paycheck, or people scared to look at their spending.
Each one needs different trust language.
The real test is not βcan people find CoinCoach?β It is: can one specific group trust it enough to enter their first few expenses and ask one real money question?
Happy to put a tighter version in writing if useful. Iβd map the first user segment, trust positioning, App Store/landing page angle, and a simple 7-day plan to get the first serious users.
Thank you so much for taking the time and providing your inputs. This is the kind of comment I needed today.
You're right that "AI finance app" is a crowded category β I've been wrestling with that exact framing. The "private money coach for people who never had access to financial advice" angle feels closer to what this actually is. I'll definitely consider this.
The user segmentation point lands harder. I built this for my mom specifically (immigrant, paycheck-to-paycheck, never had a financial advisor) but you're correct that I haven't done the work of really designing the landing page and onboarding around ONE specific group's trust language. Right now it's diluted across freelancers, immigrant parents, anyone-overwhelmed-by-money. That probably makes it weaker for all of them.
Genuine question back at you: how did you choose YOUR first user segment for whatever you've shipped? The "guess the segment from your office chair" risk is real β I'm worried about picking wrong and over-investing in the wrong audience before I have actual user data to tell me which segment is responding.
I'm planning to watch the first 1-2 weeks of who actually signs up and downloads (especially anyone who reaches out unprompted) before making any positioning pivots. Curious if that matches your experience or if you'd push earlier.
Appreciate you sharing all of this β the question about "can one specific group trust it enough to enter their first few expenses and ask one real money question" is the right framing. That's the test.
β Thuy
Thatβs a real question, and I wouldnβt answer it by just waiting for random signups to decide the segment.
For CoinCoach, the first segment should probably be chosen by trust intensity, not market size: who has the strongest reason to enter real money details and ask an uncomfortable question?
Drop your email and Iβll send over a tighter version. Itβll be easier to make useful in writing than turning this into a full segmentation teardown here.
I appreciate the framing β "trust intensity, not market size" is a useful sharpening of the question. That's a more rigorous test than "who's the biggest segment."
I'd actually love to see your thinking on this play out in this thread if you're up for it β it'd be useful for other IH founders reading along who are wrestling with the same positioning question. (Selfishly: I learn more when I can see the reasoning, not just the conclusions.)
The "who has the strongest reason to enter real money details and ask an uncomfortable question" framing is one I'm sitting with. My instinct says it's probably immigrant families managing paycheck-to-paycheck (the audience I built this for, where financial advice is most withheld and most needed). Curious if you'd push that or against it. Thanks!
β Thuy
I get why youβd want the reasoning public.
The reason Iβm hesitant is that the useful part here is not one quick opinion. Itβs actually mapping the segment choice against trust language, onboarding, and the first user test. If I compress that into a thread reply, it becomes too shallow to be useful.
The short version is: I would not choose the first segment from random early signups alone.
If you want the proper version, I can write it up as a focused CoinCoach segmentation note: which first user segment Iβd test, why, what trust angle Iβd use, and what signal would prove the segment is worth pursuing.