13
24 Comments

12 weeks, $0 marketing, both app stores: BiteSpend launch recap. Inflation Antidote

Six weeks ago BiteSpend had 12 closed-beta testers. On May 24 it went live on Google Play in 177 countries. On May 25 it went live on the App Store. Solo founder, no funding, AI coding agents instead of a team.

I want to share the build, the numbers, and the three things that surprised me.

What BiteSpend is

Between stagflation, shrinkflation, and personalized pricing, the average consumer is stuck tracking grocery spend by the ever-growing Total dollar amount on the receipt. Every line-item insight goes in the trash the moment that receipt does. I want to bring that visibility back, so people can at least see how prices move between trips and between stores. That visibility can help consumers with savings, tracking habits, and setting realistic goals.

You snap any grocery or restaurant receipt with your phone. The AI reads every line item in about five seconds. Over time it builds a personal price map across every store you shop at, so you know which one is quietly charging you more for the things you actually buy.

The hook is the gap between "what your bank app thinks you spent on food" and "what your receipt actually shows." Bank apps see merchant plus total. They see "$87 at TARGET." They cannot see that $32 of it was paper towels, $14 was a birthday card, and only $41 was actual food. That gap is what BiteSpend closes.

The numbers

- Launch date Google Play: 2026-05-24 (BiteSpend 1.0.91)

- Launch date App Store: 2026-05-25

- Geographic reach at launch: 177 countries on Google Play

- Stack cost (LLM inference): $0.0026 per receipt scan, verified by structured prod log

- Backend infrastructure cost: Manus Cloud Run, well under $50/mo at current scale

- Paid acquisition spend so far: $0

- Time from initial commit to GA on both stores: ~12 weeks of part-time evenings and weekends

The stack, for the curious

Mobile app: React Native + Expo Router + Zustand + tRPC client

Backend: Express + tRPC + Drizzle ORM, hosted on Manus Cloud Run

LLM: Gemini 2.5 Flash via Manus Forge (NOT Haiku, NOT GPT, deliberately Flash for the speed + cost combination)

Database: MySQL, Manus-hosted

Storage: Cloudflare R2

Landing site: Static HTML, Vercel auto-deploys on git push

Auth: Google OAuth + PKCE via expo-auth-session

Two LLM-related decisions I would defend in a knife fight:

1. Gemini Flash, not Claude Haiku, not GPT. I tested all three. Flash wins on the specific job of receipt OCR plus structured extraction by a meaningful margin on accuracy AND a 2-3x margin on cost. At $0.0026 per scan the unit economics is favorable for everyone.

2. Skip Tesseract entirely. I started with Tesseract.js for OCR plus an LLM step for line-item extraction. It was a disaster. Tesseract dropped 13 of 33 items on a single Trader Joe's receipt, a 40% failure rate. Removed the entire OCR layer, sent the image straight to Gemini Flash with detail: "high", and the same receipt now returns 30 of 33 line items. The lesson is that 2024-era multimodal models are good enough that the old "OCR pre-pass" pattern is obsolete for this use case.

Three things that surprised me

1. The category problem is structural, not a UX problem.

Every budgeting tool I tried (Mint, YNAB, Rocket Money, Copilot) has the same core failure: they pull from bank feeds, and bank feeds only contain merchant plus total. The category called "Groceries" in your bank app is a guess based on the merchant code. Target sells groceries, so your $87 at Target gets labeled "Groceries." Cat food and birthday cards included.

I assumed I would build a better budgeting UI. I built a different data source instead. Receipts are the only place the line items exist in a way an app can read.

2. Cross-store price intelligence is the actual moat.

The initial feature was "see your spending broken down." The retention feature turned out to be "see the same item across different stores." Once a user has scanned at two stores, they immediately want to know which one was cheaper for the items they actually buy. Costco wins on bulk paper goods. Sprouts wins on produce. Trader Joe's wins on snacks. There is no single cheapest store. There is only cheapest per item, per basket, per household.

Every user makes the next user's price map slightly better.

3. The build pipeline broke in surprising places.

EAS-built AABs failed the Google Play signature check. Took three days to figure out and one Slack conversation to fix (Manus Publish builds correctly, EAS does not, this is non-obvious). The iOS submission process has a silent-failure mode in App Store Connect where the build picker just stays empty if there is a version-number collision. Sentry's source map upload broke EAS iOS builds and the fix is a single env var. None of these are documented anywhere I could find them by Googling.

What is next (v1.2 "Insights" release)

The current product is intentionally lean: scan, see your dashboard, see the price map. The next release adds an interpretation layer.

- Trends tab renamed to Insights. The framing matters.

- Per-receipt AI breakdown right after every scan (Free). Category mix, items you have bought before, items cheaper at another store you shop at.

- Ask BiteSpend chat panel (Pro). Conversational queries over your full spending history, across stores, over any timeframe. "What did I spend on eggs this quarter at each store?"

- Personal Food Inflation rate as a brand pillar. Your basket has its own inflation rate that is almost certainly different from the national CPI. We will publish it back to you.

The cost math here works because per-receipt analysis is bounded (one LLM call per scan, already in the cost model) and chat is gated to Pro tier where the revenue offsets it.

What I would love feedback on

If you build mobile apps, indie or otherwise, three things I would genuinely value input on:

1. Pricing. Pro is $4.99/mo or $39/yr. Family is $7.99/mo or $59/yr. Free is 15 scans/month plus the full Stores tab and Item Price History. Pro unlocks unlimited scans, longer history, and proactive alerts. Curious whether 15/month on Free is the right number to drive Pro conversion or whether something different would convert better.

2. Cross-platform IAP infra. I am using RevenueCat for both stores. Anyone running a smaller setup that is also working?

3. Reddit launch strategy. I am about to drop on r/SideProject. Beyond that I am eyeing r/indiehackers, r/personalfinance, and r/EntrepreneurRideAlong. Any I should not skip? Any that will tar-and-feather me for posting? I have had that happen once 😅

Links

BiteSpend on the App Store: https://apps.apple.com/us/app/bitespend/id6764653856

BiteSpend on Google Play: https://play.google.com/store/apps/details?id=com.bitespend.app

Landing site: https://bitespend.com

Blog post on the bank-app problem (good background reading): https://bitespend.com/blog/whats-in-your-target-receipt

Founder: Samir @ BiteSpend

Happy to AMA below. Will reply to every comment today.

EDIT 2026-06-02: Bumped Free tier from 5 → 15 scans/month based on excellent feedback in the comments below. The argument that 5/month gives no runway for habit formation before paywall is fair, and grocery behavior is weekly. Shipping the backend change today. Thanks to everyone who weighed in.

posted to Icon for BiteSpend
BiteSpend
  1. 2

    the cross-store price intelligence being the retention feature rather than the spending breakdown is a really clean product insight. the spending breakdown is useful once. the price map across stores gets more valuable every time you scan. that's a very different retention curve than most budgeting apps have and it's worth being explicit about in your positioning because it's the thing that makes BiteSpend structurally different rather than just better

  2. 2

    I shipped a data-heavy consumer tool last month, and your line about bank feeds only seeing merchant + total is the real wedge here. Same problem, different stack.

    Also the Tesseract miss, 13 of 33 items, is exactly the kind of ugly detail people usually hide, so I liked seeing it. One boring thing I'd tighten early: once users upload receipts, the trust copy around where images go starts mattering fast. I tried Termly and iubenda first, then built around PrivacyForge for a simpler founder setup when privacy docs kept lagging product changes.

    The product angle feels strong because its not "budgeting", its "what did I actually buy and how are those prices moving."

    1. 1

      Glad we agree in principle. You can reach us at [email protected] - Feel free to share more about your data-heavy consumer tool. Skipping Tesseract is the kind of insight beta period helped. Have not tried termly or iubenda but will give it a whirl.

  3. 2

    $0 marketing in both app stores is the right early-stage move because store optimization (screenshots, keywords, first-week velocity) compounds without ad spend. The trap is staying there — at some point organic plateaus and you need either a referral loop or a press moment to crack the next plateau. Curious which one you're leaning toward for the next 12 weeks.

    1. 1

      Thank You for the comment and support. Honestly leaning towards a bit of both here. Slowly but surely :) To your point, I'm scared shitless of hitting that plateau.

  4. 2

    Dropping Tesseract and going straight to Gemini Flash is the kind of decision that sounds obvious after someone else figures it out. Also skip r/SideProject for launch, r/personalfinance people actually live this problem every grocery run.

    1. 1

      I don't disagree. sideProject feels like a village of founders pitching each other. any other subreddit you recommend? Do like personalfinance but have to do this without 'pitching' hard :)

  5. 2

    The dual-store launch in 12 weeks is impressive, especially with the per-scan cost already measured. One thing I’d keep tracking separately is install-page conversion by store, because Android and iOS users seem to react differently to permissions and screenshots. I’m building an Android-only utility (Kinetic Override), and the clearest screenshots + “what data stays local” wording have mattered more than I expected.

    1. 1

      Such a good insight. Don't app stores natively offer that type of insights? DM me constructive criticism on our screenshot as well as anything at [email protected]

  6. 2

    One of the sharpest launch posts I've seen. Strategic insight (category problem is data source, not UX) is exactly right.

    Pricing question (15 scans) isn't the lever. Conversion happens when users see what they'd see with Pro. Free tier should expose 1 month full history + Pro upsell visible inside each insight. Scan limit matters less than visibility hook.

    Geographic density is the harder moat. "Every user makes next user's price map better" requires critical mass per geography. Solo founder won't get density nationally. Pick one metro and go deep. "Most accurate for [Bay Area]" beats "177 countries."

    Reddit: r/SideProject and r/indiehackers safe. r/personalfinance brutal — frame as insight not launch. r/budget, r/Frugal, r/MealPrepSunday focused audience. Skip r/povertyfinance, r/Apps.

    "Personal Food Inflation rate" is huge PR angle. Worth pitching TechCrunch, Bloomberg money sections specifically.

    (Pressure-tested through HiveMind — myosin.xyz/hivemind, code HivemindIH123. AI strategy copilot for launch-window pressure-test.)

    1. 1

      Hivemind is busy today :) Appreciate the feedback nonetheless. I will say the localized accuracy for this data is a good area to consider with enough usage.

      1. 1

        Apologies for the Hivemind hiccup — DM me or email [email protected] and I'll get you direct access, beta capacity is uneven some days.

        Your reframe is sharper than mine. "Localized accuracy emerges from usage density" beats my "pick one metro" — you can let natural concentration produce localization without committing to a geographic choice.

        One thing worth extending: emergence only works if acquisition channels concentrate users geographically. Random global Reddit posts produce thin density everywhere. Concentrated channels (metro subreddits like r/sanfrancisco, local journalism, regional FB groups, Nextdoor) produce density faster. Acquisition channel choice determines whether emergence pattern fires.

        Same effort spread across 5 channels nationally = no localized accuracy. Same effort on 2 metros = real moat. The geographic call shows up at the channel layer, not the product layer.

  7. 2

    The Tesseract finding is genuinely useful — I've seen a lot of people still recommending the OCR pre-pass pattern and you've just demonstrated with actual data why it's obsolete for image-heavy tasks. Sending straight to a multimodal model and skipping the intermediate step entirely is the kind of thing that seems obvious in hindsight but takes someone actually testing it to prove.

    The cross-store price intelligence becoming the retention feature rather than the original spending breakdown is a really interesting example of users revealing what they actually value versus what you thought you were building. The moat that emerges from aggregated user data across stores is something you can't replicate — every scan makes the product more valuable for everyone else.

    On your pricing question — 5 free scans a month feels quite restrictive for habit formation. Most people shop weekly so that's barely one shop per week with no margin for error. I'd test 15-20 personally. You want users to build the habit of scanning before you ask them to pay, and 5 doesn't give enough runway to get hooked.

    On Reddit — r/personalfinance is your best bet by far, the community there actively wants tools like this. Just lead with the problem and the data rather than the product and you'll be fine.

    1. 1

      Appreciate you taking the time to comment. Agree on Tesseract. It seems like the easy option to start with until it's not. Hear you on the feedback on scan. I'm hearing something similar from other users as well. Thanks for the tip on r/personalfinance post.

  8. 2

    Strong launch recap. The most interesting part is that BiteSpend is not really competing with budgeting apps directly. It is creating a better personal data source first, then using that to explain food spend in a way bank apps cannot.

    On pricing, I would be careful with 5 free scans/month. It might be too low for the habit to form. Grocery behavior is weekly, so I’d test something closer to 10 to 15 scans/month or “first 30 days with higher scans” before tightening. The user probably needs to scan across 2 or 3 stores before the cross-store price map feels valuable enough to pay for.

    The strongest Pro hook is probably not unlimited scans. It is “personal food inflation + cheaper store alerts + ask questions across your real receipts.” That feels more emotionally tied to savings.

    For Reddit, I would avoid leading with “AI receipt app.” Personal finance subs may treat that like another app promo. The sharper angle is: “Bank apps cannot tell what you actually bought. Receipts can.” That is more discussion-worthy and less salesy.

    I’d probably start with founder/story-driven posts in r/SideProject and r/EntrepreneurRideAlong, then use more educational/problem-first posts for personal finance communities. The post should feel like a breakdown of what bank apps miss, not a product drop.

    1. 1

      Correct. Not 'just another budgeting app'. 10-15 seems like the sweet spot that we keep hearing. I'm learning that B2C does not like to hear 'AI anything' especially early on. Feedback noted. We aren't strictly budgeting app but to have some baseline our competitors in a similar space is Monarch or YNAB that is priced a bit steeper. What do you think about the pricing for pro tier itself?

      I love the last thing you said about 'breakdown of what bank apps miss, not a product drop'. If you have time, feel free to download the app. Appreciate this community.

      1. 1

        I’d be careful copying Monarch or YNAB too closely because BiteSpend is not selling the same promise.

        YNAB sells budgeting discipline. Monarch sells full financial visibility. BiteSpend feels more like food-spend intelligence: what you bought, where prices are moving, and what you could change next trip.

        So Pro pricing probably has to be tied to visible savings, not just “premium app access.”

        My gut: test a simple monthly tier first, but make the paid hook very concrete:

        cheaper store alerts, personal food inflation tracking, receipt search, and “ask questions across my groceries.”

        I would not lead Pro with unlimited scans. That sounds like usage. Lead with “save money on repeat groceries.”

        There’s a deeper pricing question here around whether you should use a 30-day higher-scan trial, a low monthly Pro tier, or a savings-based annual plan.

        Send me your email if you want. I can think through the Pro pricing, free scan limit, and Reddit launch angle privately in a more structured way.

        1. 1

          I say YNAB or Monarch to set a baseline for our research on pricing but 100% agree we are in slightly different category with our focus. The insights feature coming soon is what makes pro a lot more meaningful. hit me at [email protected] and would love to continue our conversation. Thanks in advance for your time on this!

          1. 2

            Just sent you a note.

            Kept it focused on the Pro pricing question, free scan limit, paid hook, and how to frame the Reddit launch without making BiteSpend sound like another AI finance app.

  9. 1

    The bank-feed point hits home. I build a finance app myself (Money Me) that skips bank feeds for the same reason - the merchant-code category guess is wrong often enough that people stop trusting the whole app. Your receipt angle fixes that for food in a way bank data never can.

    One question on the price map: what happens with the shopping people don't scan? Online grocery orders, cash markets, the partner who does half the trips. Curious whether partial coverage still gives useful store comparisons or whether the map needs most trips in it before it earns trust. The answer probably matters for how you pitch the Family tier too.

    Congrats on shipping both stores in 12 weeks solo.

  10. 1

    For those following , we are also on Product Hunt. Appreciate your support 🚀https://www.producthunt.com/products/bitespend

  11. 1

    Great recap, and the honest cost numbers are refreshing. On your pricing question, I would flip the variable. The number that matters is not 15 scans, it is how many scans it takes to reach the aha, and your own post answers it: the magic happens once a user has scanned at two different stores and sees where they are overpaying. So I would not cap the behavior that creates both your aha moment and your moat. Every scan at a new store makes the price map better and makes that user more likely to convert and stay, so a monthly scan cap risks throttling the exact action you want early users doing constantly. I would let scans run generously early and paywall depth instead: long history, the Ask BiteSpend chat, cross-store alerts, the personal inflation rate. Gate the insight, not the input. On Reddit, r/personalfinance will be the harshest on anything that smells like a launch, so go in as a helpful breakdown of the Target-receipt problem with the app as a footnote, not a pitch. What does your scan-to-second-store rate look like so far, because that is your real activation metric here, not signups.

  12. 1

    Hi! I'm developing a tool that automatically generates GA4 analytics reports for agencies and freelancers.
    I'm looking for two or three people willing to test it for free—I'll create two reports based on your data in exchange for honest feedback.
    If you manage clients and create analytics reports for them, please message me privately and we can discuss the matter.

  13. 1

    Spot on with the comparison. Most people assume one store is cheaper and never verify it because the data doesn't exist in one place. The moment you have enough scans to say "you specifically would save X buying produce at Sprouts but bulk goods at Costco" that's when this stops being a budgeting app and becomes something people tell their friends about.

    Curious whether you're seeing that "second store" moment as a measurable retention inflection point in your early data?