YUPPI

YUPPI

Yuppi homepage

Yuppi turns chaotic dining discounts into a single, elegant QR-first experience.

Diners save tangible cash, restaurants earn reliable traffic, and Yuppi captures value through subscriptions, tiny payment spreads, and soon, data insights.

The tech stack is modular for fast experiments, the budget discipline keeps burn predictable, and early metrics show sticky user love.

Key threats are POS instability and promo fatigue, both already hedged.

Next up: group payments and external SDKs to expand transaction volume without proportional marketing spend.

Yuppi: Discovery and Deals
Dia 2025-07-16 2.png

Yuppi: End-to-End Case Study

1. Product Vision & Market Gap
Dining out should feel rewarding, not random. Yuppi was born to blend discovery with automatic perks, giving Turkey’s food lovers a single discover-deal first app that:

  • Surfaces nearby restaurants matched to taste, budget, and mood,

  • Applies the right discount the moment the QR on the table is scanned,

  • Tracks loyalty across independent venues that cannot afford their own tech stack.

2. Dual-Sided Value Proposition

For diners:

  • Curated restaurant suggestions that feel serendipitous yet data-driven, cash savings that routinely beat the 100 TL monthly subscription fee, and a live ledger of perks that feels almost game-like.


For restaurants:

  • Weekday footfall during slack hours, zero upfront hardware cost, granular spend analytics they could never afford to build in-house, and commissions only on real revenue, not on theoretical bookings.

3. Business Model

  • Revenue Streams: B2C subscription (100 TL), payment commission (2.2 %), data insights SaaS tier (planned).

  • Cost Structure: PSP fees (~0.8 %), referral cashback pool (0-12 % based on campaign), small support team.

  • Unit Economics: Contribution margin positive by the third customer month; CAC recouped in 2.4 months.

4. Technical Architecture

  1. Mobile App (React Native, Expo) – Feature toggles allow A/B tests without re-deploy.

  2. Payments Layer – Craftgate API for card vaulting; Lidio evaluated for split-payment. QR token maps bill, auto-applies discount, pushes split: Yuppi fee → Yuppi escrow, net → merchant.

  3. Segmentation Engine – Snowflake + dbt generates cohorts nightly; OneSignal hooks trigger push/email.

  4. Admin Panel – Next.js, TypeScript

5. UX Principles

  • 3-tap flow: scan QR, slide slider, pay instantly. Target checkout <15 s.

  • Self-optimising feed: swipe-through cards ranked by recent cravings survey (Typeform onboarding) and dwell-time signals.

  • Fun: every screen should create fun and resemble it at least.

6. Executive Takeaways

  1. Holistic win-win: Yuppi aligns diner savings with restaurant margin, avoiding the usual race to the bottom.

  2. Fast-but-frugal delivery: 6 % budget variance, shipping QR rails in 8 weeks.

  3. Data as moat: nightly cohort refresh powers personalised feeds and dynamic pricing tests.

  4. Known downside: success hinges on POS stability and discount fatigue—both are in the mitigation plan.

  5. Next big bet: frictionless group payments and external SDKs to multiply transaction volume without proportional acquisition spend.

Next

ByFood