SAASPOCALYPSEverdict #BREWFINDER-F8C1
scanned 2026.04.28 · 02:46
subject of investigation
brewfinder.io
▸ nearby coffee shop discovery app
verdict: WEEKEND
buildability score
72
/100
tier · weekend
the blunt take
“Yelp but you only care about espresso and free WiFi — totally buildable, though the moat is as shallow as a cortado cup.”
The core loop is dead simple: geolocation → radius query → map pins → detail card. The "Alerts" tab suggests some kind of notification feature (new shops? deals?) which adds a smidge of complexity, but nothing that breaks the weekend budget. The real risk isn't the build — it's getting anyone to use it instead of just Googling "coffee near me".
cost breakdown.
their price ←→ your price
what they charge●
Assumed free tier
$0
/ mo
※ No pricing visible on homepage — pricing model unknown
annual:$0
what it costs you✦
01 · Vercel (hobby tier)$0.00
02 · Google Maps JS API + Places API (low-volume free tier)$0.00
03 · Supabase free tier (auth + PostGIS for geo queries)$0.00
04 · OneSignal push notifications (free tier)$0.00
05 · Domain renewal$17.00
TOTAL / mo17
▸ break-even:depends entirely on monetization model — if freemium with a $5/mo "power user" tier, ~20 subscribers covers infra
or, you know, use one of these.
if building feels spicy
option A
Google Maps (just Google it)
Ruthlessly honest: typing 'coffee shops near me' into Google does 90% of what this app does, for free, with reviews, photos, and hours.
option B
Yelp (free tier)
Already has every coffee shop, alerts, and a mobile app. The network effect is 20 years old.
option C
Osmapp.org (self-host + OpenStreetMap)
Open data, no API costs, hackable — if you want to build a niche map tool without Google's billing clock ticking.
what'll actually be hard.
est. total: 18 hours
▸ 2 hours geolocation + map setup · 4 hours coffee shop data layer (Places API) · 4 hours map UI + pins + detail cards · 4 hours alerts/push notifications · 2 hours auth + profile · 2 hours deploy & polish
easy
medium
hard
nightmare
01
easy
Geolocation permission flow
navigator.geolocation.getCurrentPosition() + a polite denial fallback. One afternoon.
02
easy
Map rendering + pins
Mapbox GL JS or Google Maps JS SDK. Drop pins from a Places API radius search. Standard tutorial territory.
03
medium
Coffee shop data freshness
Google Places API is fine but costs real money at scale. OpenStreetMap is free but patchy for indie cafés.
04
medium
Alerts feature
Push notifications for new nearby shops or deals requires a background job, a pub/sub layer, and user permission flows on both iOS and Android.
05
hard
Mobile-feel PWA or native app
The bottom nav (Map · Discover · Alerts · Profile) screams native mobile. Getting that snappy feel in a PWA takes real effort; a proper React Native build doubles the timeline.
06
hard
Differentiation from Google Maps
This is a product problem disguised as an engineering problem. Without a genuine niche (specialty coffee, laptop-friendly, quiet spots), you are a worse Google Maps.
recommended stack
Next.js 15 (PWA config)Supabase (auth + PostGIS radius queries)Google Places API or Overpass API (OSM)Mapbox GL JSOneSignal (push alerts)
ready to build?
We'll email you the build guide. You'll be done by Sunday.
▸ generated with love, by a heartless robotverdict v2.1 · saaspocalypse.dev