Skip to content
befday
Esc
navigateopen⌘Jpreview
On this page

Growth & the Two-Sided Flywheel

The go-to-market overview for befday — how a two-sided marketplace (consumers + merchants) grows without spending its way out of the chicken-and-egg problem. Frames the flywheel, the cold-start entry point, and which side to push first; the consumer and merchant acquisition docs hang off this.

Status: Accepted (direction); implementation deferred
Date: June 2026
Decision: Treat growth as a two-sided flywheel, not two independent budgets. befday is a marketplace — consumers come for merchant value, merchants come for consumer reach — so the two sides fund each other once the loop turns. This doc frames the flywheel, names the chicken-and-egg entry point, and decides which side to push first; the consumer and merchant docs detail each motion.

Direction, not a campaign plan

This is a decision doc about how growth works, not a marketing calendar or ad-budget plan. It reasons about the loops befday has already designed (referral, points, birthday, collectibles, insights) and how they become acquisition — not generic “post on social” tactics.


TL;DR

befday is a two-sided marketplace: each side is worthless without the other (chicken-and-egg). Growth = manually cranking the flywheel (seeded supply, founder-led merchant sales, demand backstops) until the designed loops (referral, points, birthday, collectibles) carry it. Lead with merchant supply per geography (the POS is useful standalone), then turn on consumer acquisition into a place that already has things to do. Acquisition spend follows density, not the reverse.


Context

Most of ideas/ covers what to build and why people stay (the retention stack). Almost none covers how anyone arrives. That’s the gap this fills.

befday is a two-sided marketplace:

  • Consumers (apps/native) want perks, points, birthday gifts, nearby deals, collectibles.
  • Merchants (pos + merchant) want footfall, repeat customers, and — later — embedded finance.

Each side is worthless without the other: a consumer with no nearby merchants churns; a merchant with no befday customers sees no value. This is the chicken-and-egg problem, the same one Cold-Start & Coverage tackles from the supply side. This doc is its demand-side companion — together they answer “how do we get to density in a new geography, and keep both sides arriving.”


The flywheel

        more merchants on befday


   more reasons for a consumer to install
   (nearby perks, points to spend, shops to catch)


        more consumers on befday


   more reason for a merchant to join
   ("your customers are already here")


        more merchants on befday   ──┐
                 ▲                    │
                 └────────────────────┘

The loop is self-reinforcing once it turns, but dead at zero — neither side moves the other until there’s a minimum of both. Early growth is about manually cranking the flywheel (paid/seeded supply, founder-led merchant sales, demand backstops) until it spins on its own, then letting the loops carry it.

The loops are already designed as features

befday doesn’t need to invent growth mechanics — most are already designed here, and a few are already built. Growth is mostly turning these on and pointing them outward. What exists in code today vs. what’s still a decision doc:

Built today (UI exists in apps/merchant + apps/native, mocked data):

Built feature Growth loop it powers Side it grows
Vouchers (merchant Vouchers → native claim/redeem) Merchant-funded perk → consumer reason to visit & redeem Consumer
Stamp cards Visit-again loyalty loop — progress toward a reward Consumer
Birthday-this-month signal (merchant Customers) Surfaces the birthday hook the full engine will automate Consumer

Planned (decision docs here, not yet built):

Planned feature Growth loop it would power Side it grows
Referral / points Two-sided viral loop — refer a friend, both earn points Consumer
Merchant Collectibles Shareable “I caught this shop” cards → social pull Consumer
Spend Insights Year-in-review / wrapped-style shareable summary Consumer
Birthday Engine “It’s my birthday, what do I get” → install trigger + word-of-mouth Consumer
Nearby Local discovery → “befday spots near me” pull Consumer
Cold-Start coverage requests “Notify me when a shop opens here” → merchant sales leads Merchant
Embedded finance “Cheaper insurance / working capital via your POS” → merchant hook Merchant

The single most important growth asset befday is designing is the referral + points loop — a proven two-sided viral mechanic paid in cheap on-brand points rather than cash. It’s not built yet, so it’s a Phase-2 priority, not a lever available today.


Which side first?

In a two-sided marketplace you usually can’t grow both sides evenly — you constrain one and over-invest in the other until the loop turns. The decision:

Lead with merchant supply, per geography; let consumer demand follow the loops.

Reasoning:

  • Consumers churn instantly on emptiness — install + “nothing near you, no perks” = gone (the failure Cold-Start defends against). Demand is cheap to acquire but expensive to retain without supply.
  • Merchants tolerate a slower ramp — a merchant on pos gets value from the POS itself (orders, stamps, analytics) before befday’s consumer network is dense. Supply can be acquired before the demand exists, because the POS is useful standalone.
  • So: make a geography merchant-dense first (founder-led sales + POS-is-useful-anyway pitch), then turn on consumer acquisition.

This mirrors the Cold-Start “don’t launch below a density floor” rule — growth and cold-start are the same decision viewed from acquisition vs. UX.

The exception: demand backstops

“Merchant first” doesn’t mean “zero consumers until dense.” Some consumer acquisition runs in parallel to generate the coverage-request demand signal that feeds merchant sales (people asking “bring befday to my area”). Early consumers are partly an acquisition tool for merchants, not just customers.


How the two motions connect

The consumer and merchant docs aren’t independent — each side’s growth feeds the other:

From consumer side → merchant side From merchant side → consumer side
Coverage requests (“bring befday here”) → merchant sales leads Each new merchant = new nearby perk / shop to catch → install reason
“Your customers are already on befday” → merchant pitch credibility Merchant-funded points/perks → consumer reason to spend
Consumer density → makes embedded finance data valuable Merchant promotes befday in-store → free consumer acquisition

The in-store moment is the cheapest acquisition channel on either side: a customer already paying at a pos counter is one QR-scan away from installing native (see collectibles catch flow). Merchant-led consumer acquisition is nearly free and high-intent.


Phasing

Growth tracks the same phases as the rest of the platform:

Phase Supply (merchant) Demand (consumer)
Phase 1 Founder-led sales; POS-is-useful pitch; seed 1 city Light — enough to generate coverage-request demand signal
Phase 2 Referral-from-merchants; coverage-lead outreach Turn on referral + shareable surfaces in dense areas
Phase 3 Embedded finance as a retention + upsell hook Full loop — birthday/nearby/collectibles drive organic pull

Don’t run Phase-3 consumer acquisition into a Phase-1 geography — it’s the cold-start churn trap. Acquisition spend follows density, not the other way around.


Consequences

Type Consequence
Pro Frames growth as loops designed into the product (a few already built, most planned), not a separate spend — the cheapest possible CAC once they ship.
Pro “Merchant-first per geography” aligns growth with cold-start discipline — one decision, two lenses.
Pro The in-store QR moment makes merchant-led consumer acquisition nearly free and high-intent.
Pro Two-sided framing prevents the classic mistake of buying demand into empty supply (or vice versa).
Con Merchant-first is slower to show consumer top-line — patience required; the loop is back-loaded.
Con Requires discipline to not over-spend on consumer acquisition before supply justifies it.
Con Founder-led merchant sales don’t scale — needs a repeatable motion before Phase 2 (the merchant doc problem).

Open Questions

  • Geography unit for growth: city, postcode cluster, or radius — same unit as cold-start launch gating, or different for acquisition?
  • Demand-backstop spend: how much early consumer acquisition is justified purely as a merchant-lead-generation tool before supply exists?
  • Channel mix: which channels matter for a Malaysian SMB-merchant + everyday-consumer market (WhatsApp, TikTok, in-store, local sales reps)? — detailed per side in 15/16.
  • Flywheel “it’s turning” signal: what metric tells us a geography has graduated from manual cranking to self-sustaining (organic install ratio, referral share of installs)?
  • Cross-side attribution: when a merchant-promoted QR drives an install that later refers others, how is that attributed across the two motions?

Was this page helpful?