Merchant Acquisition
How befday acquires merchants onto pos — leading with "the POS is useful standalone," then layering the befday network ("your customers are already here") and embedded finance as upsell hooks. The supply side of the two-sided flywheel; founder-led at first, then referral + coverage-lead-driven.
Status: Accepted (direction); implementation deferred
Date: June 2026
Decision: Acquire merchants by leading with standalone POS value (pos is useful before befday’s consumer network is dense), then layering the befday network pitch (“your customers are already here”) and, later, embedded finance (insurance / lending) as adoption + retention hooks. Merchant acquisition is the supply side of the flywheel and leads consumer growth per geography.
Supply leads, per geography
Per the flywheel doc, a geography goes merchant-dense first — because the POS is useful standalone, merchants can be acquired before there’s a consumer network to justify it. This is also what makes consumer acquisition viable (no empty-app churn).
TL;DR
A merchant adopts pos for three escalating reasons; the pitch changes by phase. Phase 1: the POS is useful standalone (orders, stamps, analytics, no extra hardware) — founder-led sales, no consumer density needed. Phase 2: the network pitch (“your customers are already here”) once density exists — scaled via coverage-request leads + merchant referral. Phase 3: embedded finance (cheaper insurance / working capital from POS history) as a sticky hook. Because Phase 1 stands alone, merchant acquisition isn’t blocked by chicken-and-egg — supply leads demand. Activation = POS usage, not sign-up.
Context
A merchant adopts pos for one of three escalating reasons; the pitch changes by phase as the network matures:
- The POS is useful by itself — orders, stamp cards, analytics, no extra hardware. True day one, zero consumer density required.
- The befday network brings customers — “your customers are already on befday; join and they’ll find you / earn points / catch your shop.” True once consumer density exists.
- Embedded finance — cheaper insurance and working capital unlocked by POS history. True later, and a strong reason to stay.
Because reason #1 stands alone, merchant acquisition isn’t blocked by chicken-and-egg. We can build supply ahead of demand — exactly the flywheel sequencing.
The pitch, by phase
Phase 1 — “The POS is useful anyway” (founder-led)
Before any consumer network, sell pos on its standalone merits:
- No extra hardware — runs on a phone/tablet the merchant already has (vs. traditional POS terminals).
- Stamps + loyalty built in — the stamp identification flow (phone as identity, no camera) gives merchants a loyalty program for free.
- Analytics — the merchant dashboard gives revenue/transaction insight a cash-drawer doesn’t.
This is a founder-led, high-touch sales motion: direct outreach, in-person onboarding, one geography at a time. It doesn’t scale — but it’s how you seed the first city’s density (matching the cold-start “seed before launch” rule).
Phase 2 — “Your customers are already here” (network pitch)
Once a geography has consumer density, the pitch upgrades:
- Footfall / discovery — “befday users near you will see your shop in nearby.”
- Repeat customers — “befday’s points, birthday perks, and collectibles bring people back to you.”
- Coverage leads — the coverage-request signal (“N users want befday here”) becomes a warm sales lead and proof of demand to close the merchant.
This phase introduces scalable, non-founder channels: coverage-lead outreach, merchant referrals, and the credibility of an existing local network.
Phase 3 — Embedded finance as a hook
Once merchants have transaction history, embedded insurance and lending become both a retention moat and an acquisition hook:
- “Use befday POS for a few months → unlock cheaper insurance / working-capital advances priced off your real sales.”
- A merchant can’t easily get this elsewhere (it’s their own POS data), so it’s sticky and differentiating.
- befday stays the distribution + data layer, never the insurer/lender.
Channels (by scalability)
| Channel | Phase | Scales? | Notes |
|---|---|---|---|
| Founder-led direct sales | 1 | No | Seeds the first city; high-touch, in-person onboarding |
| Coverage-request leads | 2 | Yes | Demand signal from consumers → warm, pre-qualified merchant leads |
| Merchant referral | 2 | Yes | A happy merchant refers a neighbor — POS works → trust spreads locally |
| Embedded-finance upsell hook | 3 | Yes | “Unlock cheaper insurance/capital” — adoption + retention |
| Local reps / partnerships | 2–3 | Partial | Market-dependent (associations, suppliers, payment partners) |
Coverage-request leads are the highest-leverage scalable channel — they close the flywheel: consumer demand directly generates merchant sales leads, and the lead arrives pre-qualified (“N people here already want you”).
Sequencing
Merchant acquisition runs ahead of consumer acquisition per geography:
| Phase | Motion | Outcome |
|---|---|---|
| Phase 1 | Founder-led sales on standalone POS value, one city | Seed density → clears the cold-start floor |
| Phase 2 | Coverage leads + merchant referral + network pitch | Scalable supply growth; consumer acquisition turns on |
| Phase 3 | Embedded finance hook | Retention moat + differentiated acquisition |
The hard transition is Phase 1 → 2: founder-led sales must become a repeatable, documented motion before it can hand off to leads/referrals/reps. That’s the central merchant-growth challenge.
What we are not doing
- Not gating the POS behind consumer density. The POS must deliver value standalone, or Phase-1 acquisition has nothing to sell.
- Not over-promising the network in Phase 1. Selling “tons of customers” before density exists burns trust — lead with standalone value, let network upside be upside.
- Not becoming the insurer/lender to win merchants — embedded finance stays a partner-distributed hook (12 / 13).
Data Model / API Impact (sketch)
Reuses merchant + coverage primitives; adds acquisition pipeline tracking.
| Need | Reuses / adds |
|---|---|
| Coverage-request → lead | coverage_requests from cold-start; add lead state |
| Merchant referral | Mirror the consumer referral pattern for merchant→merchant |
| Onboarding funnel state | New — track merchant from lead → onboarded → active (POS usage as activation signal) |
| Embedded-finance eligibility | From insurance / lending — POS history thresholds double as upsell triggers |
| “Customers want you here” proof | Aggregate coverage_requests per geohash → sales-facing demand number |
The activation signal is POS usage, not just sign-up — a merchant who processes orders is acquired; one who installed and never used it isn’t.
Consequences
| Type | Consequence |
|---|---|
| Pro | Standalone POS value means merchant acquisition is not blocked by chicken-and-egg — supply can lead demand. |
| Pro | Coverage-request leads close the flywheel — consumer demand generates pre-qualified merchant leads at low cost. |
| Pro | Embedded finance is a differentiated, sticky hook competitors can’t replicate (it’s the merchant’s own POS data). |
| Pro | Merchant referral spreads locally on earned trust (the POS demonstrably works). |
| Con | Phase-1 founder-led sales doesn’t scale — the Phase-1→2 handoff (repeatable motion) is the hard, unsolved part. |
| Con | The network pitch is only honest once density exists — mis-timing it (Phase 1) burns trust. |
| Con | Embedded-finance hooks depend on partners + regulation (12/13) — can’t be promised until those land. |
Open Questions
- Phase-1→2 handoff: what does the repeatable, non-founder merchant sales motion look like, and what’s the trigger to switch?
- Activation definition: how many orders / what time window marks a merchant as “activated” vs just signed up?
- Merchant referral reward: what incentive (fee waiver, points, finance perk) makes a merchant refer a neighbor — and is it cash or in-kind?
- Coverage-lead workflow: the concrete pipeline from aggregated
coverage_requests→ sales contact → onboarded merchant (the open question carried from cold-start). - Pricing / take-rate: open direction remains freemium SaaS (free core POS, paid Growth/Pro tiers) plus Phase-3 embedded finance; the payments take-rate is zero — merchants use their own bank DuitNow QR, money goes bank-to-bank, and befday never sits in the money flow. The free core is what keeps this standalone-value pitch honest.
- Local partnerships: are merchant associations / suppliers / payment partners a viable Phase-2 channel in the target market?