Skip to content
befday
Esc
navigateopen⌘Jpreview
On this page

Ideas

Forward-looking product decisions for befday — the "why" behind features not yet built. These are direction documents, not shipped behaviour.

Forward-looking decision records for befday. The rest of these docs describe what the apps do today; this section captures what we intend to build and why — trade-offs, alternatives considered, and data-model/API sketches.

Direction, not reality

These are idea / decision docs. A feature here does not mean it exists in the apps. Where an idea relates to something already built (e.g. Twin Birthday, Nearby Alerts), it links to the live docs and notes the difference.

Identity & stamps

Decision Summary
Stamp Identification Flow Phone is the identity anchor (POS, no camera); purchase stamps + welcome stamp; phone verified via WhatsApp OTP (Meta direct)
Platform Stamps & Referral Superseded by 04 — platform “befday card” + referral loop (completion-card mechanic replaced by points currency)

Inbox & CRM

Decision Summary
Inbox Customer Capture Saving a phone on an inbox conversation auto-creates a phone-keyed store_customer (no phone, no customer); phone is the only anchor, giving free dedup against POS + app; unverified until OTP

Points currency

Decision Summary
befday Points Currency Setel/Mesra-style spendable points: earned per spend (+referrals), redeemed via reward catalog or merchant-funded credit/discount
Cross-Merchant Points Funding Who funds cross-merchant redemption: launch constrained Model 1 (earning-merchant-only + caps), architect for Model 2 (earner pre-funds pool), reserve Model 3 (befday float)

Native retention

Decision Summary
Native Retention Stack (Overview) Umbrella framing: four return-drivers (money/memory/habit/identity), how the other ideas map to them, compounding, sequencing, shared push layer
Consumer Receipt Management Free receipt wallet in apps/native (scan via LLM vision + manual entry); merchant-funded, never charge consumers
Birthday Engine Flagship on-brand retention hook: merchants offer birthday perks, native shows a birthday calendar + push; reuses voucher/points rails, idempotent per (user, perk, year)
Nearby & “What Can I Use Now” Everyday high-frequency hook: nearby merchants ranked by actionability (points/perks/stamps/birthday), list + map; mostly reads, minimal new schema
Spend Insights & Tiers Low-cost data-leverage surfaces: monthly/annual spend insights (activates receipts) + Bronze→Gold tiers derived from lifetime points
Cold-Start & Coverage Strategy Shared risk across nearby/birthday/insights: seeding, platform-funded fallbacks (esp. birthday), density-aware UX, graceful empty states that feed merchant sales
Merchant Collectibles (“Catch the shop”) Gotcha-style collectible index where the “creatures” are befday merchants: scan the shop’s QR to catch, photo cut-out becomes a merchant card with merchant-set rarity; QR-only identification, no geolocation, no CV cost

Merchant monetization

Decision Summary
Merchant Embedded Insurance Offer business insurance / takaful inside the POS, using transaction history as an underwriting asset; befday is the embedded distribution + data layer (via insurtech), never the insurer; phase 2/3
Merchant Embedded Lending / Cash Advance Working-capital advances repaid as a % of daily POS sales, underwritten from transaction history; befday is the distribution + data + repayment rail (via fintech enabler), never the lender; phase 3, after insurance

Growth & go-to-market

Decision Summary
Growth & the Two-Sided Flywheel How a two-sided marketplace grows without buying demand into empty supply: frame the flywheel, lead with merchant supply per geography, let consumer loops follow; the demand-side companion to cold-start
Consumer Growth Acquire consumers via loops already in the product — referral + points, shareable collectibles, year-in-review, birthday hook, and the near-free in-store QR moment — not generic paid ads
Merchant Acquisition Lead with standalone POS value (useful before density), then the “your customers are already here” network pitch, then embedded finance as a sticky hook; founder-led → coverage-lead + referral driven

Was this page helpful?