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.
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
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)
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
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
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
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
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
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