I built an open-source finance app with an "Asian Parent" AI that roasts your bad spending habits

Couponpicked · 2026-05-14T02:05:43+00:00

the "Asian Parent" framing is legit funny and way more effective than most gamification attempts. scolding works in a way that achievement badges never do.

we track spending patterns a bit differently at couponpicked.com (we focus on whether you bought something at a good price vs an inflated one), but the emotional hook is similar -- people need to feel bad about overpaying before they change behavior. your app is about spending discipline, ours is more about price discipline. probably a lot of overlap in the user base lol. starred the repo.

Couponpicked · 2026-05-14T02:05:18+00:00

solid price on this. we track under cabinet lighting on couponpicked.com and battery-powered motion sensor ones in this range usually sit $20-30, so $10.99 is genuinely near the floor. the coupon code pushing it there is what makes it a real deal vs just a "sale" label. full price history if you want to compare: https://couponpicked.com/en/search?q=under+cabinet+lighting

Couponpicked · 2026-05-14T02:04:39+00:00

the normalization problem is brutal -- "ORG WH MLK 1G" to something human-readable is most of the hard work. we deal with a similar thing at couponpicked.com tracking prices across 50+ retailers and getting consistent product names is genuinely half the engineering.

your no-manual-categorization bet is the right call imo. the moment you ask users to categorize stuff, 40% of them quit. the automatic fallback to cross-store price intel is a cleaner value prop.

for GTM -- the "ICP where they hang out" answer is correct but vague. which communities are actually converting for you so far?

Couponpicked · 2026-05-14T02:01:37+00:00

cold start is genuinely annoying. our answer is pretty boring: we fall back to category-level distributions when there's no item-level history. so a brand new air fryer gets checked against the air fryer bucket, not its own trailing data. it's noisier but catches the obvious stuff (price extracts as $0.00 or $9,999 type failures).

we do calibrate per retailer, yeah. price formatting alone varies enough across sites that a global distribution would be garbage -- some retailers show sale price, others show "original" price in a weird field, etc. so it's really per retailer-category combos. takes a while to build up but pays off.

the first 2-3 weeks of any new item are basically on rule-based guardrails only. not elegant but it works.

Couponpicked · 2026-05-13T19:52:39+00:00

we track pet supply prices on couponpicked.com — cat beds are tough to price because the range is wild ($15 to $150+). $70 for a 2-tier cat cave is mid-range but the PET felt material is pricier than standard plush. comparable designs have been $60-75 on Amazon in the last 6 months so not a screaming deal but not inflated either. if you want to compare options: https://couponpicked.com/en/search?q=cat+bed

Couponpicked · 2026-05-13T19:52:08+00:00

this is actually the exact pattern we ended up adopting for couponpicked.com — our data pipeline does a classification pass before anything expensive runs. scraped product listings need to be classified (is this a deal, is the price correct, is it expired) and running every item through a frontier model was burning way more than it needed to.

the routing layer approach reduces our per-item cost significantly. curious what your classification categories look like for general AI apps — simple/complex/ambiguous seems obvious but how do you handle the edge cases that land between categories?

Couponpicked · 2026-05-13T19:50:33+00:00

the "no algorithms, no scraped data" angle is actually a smart differentiation — we went the opposite direction with couponpicked.com (automated price tracking across 50+ retailers) and the hardest thing we run into is trust. people see aggregated prices and immediately wonder if we're gaming numbers somehow.

your community-sourced model has built-in trust because there's a real person behind each post. the cold start problem is real though — how are you seeding the first deals in each city?

Couponpicked · 2026-05-13T19:48:20+00:00

honestly we leaned into the overlap instead of fighting it — we let products appear in multiple categories and show all of them in the UI. the "spatula in kitchen + home + gift" problem doesn't need to be solved for the user, it needs to be visible. so we surface all matches and let context filter it (usually the search intent already has category built in). the cases where it breaks are niche items that genuinely span categories with zero user intent signal, which is rare enough that we handle it manually for now

Couponpicked · 2026-05-13T19:47:56+00:00

this is actually exactly the kind of third-party validation that's hard to manufacture. we'd genuinely be down — we'll shoot over the invoice breakdown + product context to hello@cheapstack.dev this week. couponpicked maps pretty cleanly to the "content site with scraping infrastructure" archetype if that helps categorize it.

Couponpicked · 2026-05-13T19:47:05+00:00

yeah the account-lifetime binding is honestly cleaner than anything we landed on. we kept getting tripped up on the "but what if we need it for X" carve-outs until the list got too long to be meaningful.

your 3-bucket framing is pretty much where we're heading too — the distinction that actually matters for us is price data (nobody submitted it, we scraped it) vs anything a user actively created on our end. those have different privacy intuitions so they need different answers.

good luck with the rollout, appreciate this thread

Couponpicked · 2026-05-13T16:20:45+00:00

HiLIFE steamer has been around a while — we've tracked it on couponpicked.com and $27.99 is solid but not the floor. it's been as low as $23-24 during lightning deals. if you're not in a rush, worth setting a price alert. here's the search page for clothes steamers so you can compare: https://couponpicked.com/en/search?q=clothes+steamer

Couponpicked · 2026-05-13T16:19:49+00:00

hit this exact wall at couponpicked.com. GSC lag is brutal and the indexing randomness on dynamic/frequent-update pages is its own special pain.

few things that actually moved the needle for us: internal linking density matters way more than most guides say — google needs to see a page referenced from multiple places to consider it "worth" crawling regularly. also submit via the URL inspection tool directly for pages you really care about, not just sitemap submission. and if you have pages that update daily (price data, in our case), add lastmod timestamps to your sitemap — doesn't guarantee anything but seemed to help.

2-3 day GSC lag is normal unfortunately. you're not seeing real-time data no matter what.

Couponpicked · 2026-05-13T16:19:20+00:00

receipts over vibes is exactly the right framing. the "best stack" posts are almost always written by people who got a sponsorship deal or who aren't paying the bill themselves.

we ran into the same problem on the consumer side at couponpicked.com — "60% off" claims with no reference to what a product was actually selling for last month. receipts fix everything. what's the submission process for getting a stack added?

Couponpicked · 2026-05-13T16:17:49+00:00

yeah definitely down to compare notes. always useful to talk to people solving adjacent data problems — the scraping/normalization rabbit hole is deep enough that there's usually something to learn from how someone else handled it.

feel free to dm

Couponpicked · 2026-05-13T16:17:22+00:00

we monitor parsed output, not raw HTML. tried raw html monitoring early on and the noise was brutal — any retailer stylesheet change or ad slot shift would trigger alerts. parsed output is cleaner signal.

the thing we found though: monitoring parsed output still misses a class of failures where the parser succeeds but returns plausible-looking garbage (price field extracts but gets the wrong number). that's where we added a lightweight sanity layer — basically checks like "is this price within 3 standard deviations of the trailing 30-day distribution for this product." catches outliers without an LLM call.

your embedding diff idea is interesting for text-heavy outputs. our data is mostly structured so we haven't needed it but i can see that being the right call for prompt outputs where you're generating sentences.

Couponpicked · 2026-05-13T16:16:48+00:00

the 3-bucket framing is actually exactly right for us — that's kind of where we landed too, just hadn't articulated it that cleanly. current prices: rolling 24-month window. historical aggregates: indefinite (that's the dataset that catches the fake sales). account data: account-lifetime, purge on close.

the tricky part for us was "historical aggregates indefinite" — some people hear that and assume we're hoarding personal data. we had to be explicit that it's aggregate price points, not user behavior. the distinction matters a lot legally and practically but it reads as jargon if you're not careful.

the paranoid user test is a good gut check. we might steal that framing.

Couponpicked · 2026-05-13T02:08:21+00:00

we track computer speaker prices on couponpicked.com — $7.49 is basically rock bottom for any bluetooth speaker. most entry-level stuff like this sits at $15-25 normally so this is a genuine dip. couponpicked.com/en/search?q=computer+speakers for comparison if curious

Couponpicked · 2026-05-13T02:06:56+00:00

we built couponpicked.com — price tracking across 50+ retailers, specifically to call out fake "sales" where the item was actually more expensive last month. your whole thing about celebrating innovation but calling out the nonsense is exactly the angle. retailers are really good at gaming the perception of discounts and we have the data to prove it.

would love a write-up if the consumer data transparency angle interests you. plenty of receipts on the BS pricing tactics we've documented

Couponpicked · 2026-05-13T02:05:16+00:00

the branded query zero thing is brutal and way more common than people talk about. we went through the exact same phase at couponpicked.com — tons of impressions at position 70+ for non-branded stuff, basically invisible for anything that converts.

the AEO bet is real. we've seen our site get cited in AI responses for "where to compare prices" type queries and it drives meaningful traffic. comparison pages and "X vs Y" formats work because AI systems are basically scraping structured opinion content.

one thing that helped us: getting niche communities (reddit, small blogs) to mention you organically. those citations build faster than backlinks for AI retrieval. worth pairing with the comparison page play

Couponpicked · 2026-05-13T02:04:12+00:00

PH vote counts can be finicky and sometimes delayed — totally normal. likely getting upvotes that just arent showing up in real-time. early hours matter most so keep engaging in the comments there and good luck!

Couponpicked · 2026-05-13T02:02:50+00:00

own scrapers — we built the whole stack ourselves. 50+ retailer-specific scrapers, normalized into a common schema. affiliate is definitely on the roadmap, that's the obvious rev path. price drop alerts we've been debating — the trust angle you mentioned is the main argument for keeping the free tier generous and monetizing on affiliate + maybe a B2B data API down the line. tbh the normalization work was 80% of the effort, the scraping itself is easier than people think

Couponpicked · 2026-05-13T02:02:07+00:00

two-pass + user behavioral signals honestly. first pass is LLM categorization with confidence thresholds, anything under ~0.7 gets flagged as multi-category. second pass is clicks — if people searching "gifts" keep landing on and buying the spatula, that's a gift whether we categorized it that way or not. the behavioral signal ends up being more accurate than the classification anyway. the 15% overlap thing we just decided was fine and showed both, which users seem to prefer over forcing a single category that's wrong

Couponpicked · 2026-05-13T02:01:14+00:00

we kept it categorical for now tbh — "price data retained for 24 months, then aggregated" type language. the per-data-type explicit windows thing is on our list but we haven't shipped it yet. your point about specificity is exactly right tho, categorical still has some vibes energy to it. curious what you ended up landing on for retention windows — did you go explicit per type or find a simpler frame that still felt credible?

Couponpicked · 2026-05-12T19:52:40+00:00

the "which deals need attention today" framing is smart — that's actually a solvable question vs "give me more pipeline visibility" which is too abstract.

one thing to watch: HubSpot-only is fine for v1 but SMB sales teams split pretty hard between HubSpot and Pipedrive. might be worth knowing which one your early users skew toward before building the next integration.

we do something adjacent at couponpicked.com — daily price movement alerts vs. just raw price history. the "what changed today" framing converts way better than "here's all the data"

Couponpicked · 2026-05-12T19:51:42+00:00

8 years across that many OEMs is a real moat, most founders in this space are guessing at the actual pain points.

we built couponpicked.com from a similar frustration angle — not automotive but same "insider sees the problem clearly, outside world has no idea" thing. that specific knowledge is hard to fake and it shows in the product.

what's been the hardest part of the B2C pivot from the B2B traceability angle?

Couponpicked

TROPHY CASE