CRM AND LOYALTY IN
SAAS DASHBOARD

Building a Retention Flywheel Inside an Operational Restaurant Solution

CRM and Loyalty SaaS Dashboard — Laptop and mobile mockup of the loyalty platform

Project Summary

Zak is an end-to-end SaaS platform for restaurants, focused primarily on operational efficiency. Payments, inventory, fiscal management, and administrative workflows were already well established. The challenge was not operational — it was strategic.

Small and mid-sized restaurants lacked structured customer databases, had no visibility into retention, and relied heavily on organic foot traffic. The platform helped them operate better, but it did not actively support growth. The opportunity was clear: transform Zak from an operational tool into a growth platform by building a configurable, automated credit-based loyalty system deeply integrated into restaurant operations.

Project Details

Role

Product Designer

Duration

4 months (May — August)

Platform

Web Dashboard & White-label Mobile

Industry

Restaurant SaaS / FoodTech

Tools

Figma Miro FigJam

The Challenge

Strong operations, but no growth engine

Zak was already strong as an operational, end-to-end restaurant SaaS, but it wasn't driving growth. Small and mid-sized restaurants lacked a structured customer base, couldn't track retention, and relied heavily on organic traffic. The core challenge was to add retention and relationship-building capabilities without increasing operational complexity or disrupting the most sensitive moment in the product: the payment flow.

Proposed Solution

A native retention engine, fully integrated

Zak introduced a native CRM and loyalty "retention engine" built as an integrated system: an automated campaign engine with four lifecycle-based templates, a centralized dashboard for configuring financial rules and activating promotions self-serve, and a white-label customer experience accessed via QR code (no app required). The loyalty benefits were tightly integrated into checkout with clear identification, credit application, and final value confirmation, while dashboards surfaced key metrics to prove value and make retention measurable for restaurant owners.

My Role

As Product Designer, I operated beyond interface design — shaping the strategic architecture and business logic that powered the entire retention engine.

01

Campaign Engine Architecture

Structured the logic behind the four lifecycle-based campaign models and their convergence parameters.

02

Payment Integration Flows

Modeled the critical payment integration ensuring loyalty was embedded into the product's core.

03

Financial Logic Simplification

Simplified complex financial concepts into scalable abstractions accessible to non-technical restaurant owners.

04

MVP Prioritization & Prototyping

Defined scope alongside PO and Tech Lead, delivered high-fidelity prototypes ready for development.

Design Methodology

A structured, hypothesis-driven approach that balanced business strategy with user-centered design.

01

Discovery & Research

Market analysis on loyalty in food service. Competitive benchmarking (Starbucks, Panera, Chipotle). Stakeholder interviews with restaurant owners and consumer behavior studies.

02

Definition & Strategy

Product thesis and hypothesis framing. Campaign engine architecture modeling. User persona mapping (owner + consumer) and MVP scope prioritization with PO & Tech Lead.

03

Ideation & Design

Collaborative workshops with cross-functional teams. Low-fidelity wireframing, flow mapping, high-fidelity prototyping in Figma, and critical payment integration flow design.

04

Validation & Launch

Prototype review with development team. Pilot launch in 3 restaurants in São Paulo. KPI tracking, adoption metrics analysis, and iteration planning for future releases.

Project Roadmap

A 4-month sprint from May to August — structured to deliver measurable impact first, sophistication later.

M

May

Discovery

  • Market research & benchmarking
  • Stakeholder interviews
  • Product thesis definition
  • Ideation workshops
J

June

Definition & Design

  • Campaign engine architecture
  • User flow mapping
  • Wireframing & prototyping
  • Payment integration design
J

July

Hi-fi & Handoff

  • High-fidelity prototypes
  • White-label app design
  • Developer handoff
  • QA & design review
A

August

Pilot & Validation

  • Pilot in 3 São Paulo restaurants
  • Adoption metrics tracking
  • Iteration planning
  • Future roadmap definition

Ideation Workshops

Collaborative sessions that shaped the product direction and aligned stakeholders on the retention strategy.

Brainstorming Sessions

Open ideation sessions exploring reward models, campaign types, and integration touchpoints. The team evaluated points-per-dollar, stamp-based, and cashback/credit approaches before converging on the credit model.

Stakeholder Alignment

Cross-functional workshops with product, engineering, and business teams to define the four lifecycle-based campaign models: Welcome Bonus, Birthday, Referral, and Reactivation — ensuring strategic alignment with growth objectives.

Feature Prioritization

Eight feature proposals were evaluated using an impact-vs-effort matrix, prioritizing customer frequency, program participation, and operational automation. The MVP scope was defined to deliver measurable impact first, sophistication later.

The key workshop insight was that all campaigns should converge around two core parameters: benefit value and expiration period. This abstraction reduced technical complexity, created mental consistency for users, and ensured future scalability.

Product Thesis

Before designing any interface, we structured a business hypothesis: if we enable restaurants to build their own customer database, increase purchase frequency, incentivize referrals, and reactivate inactive customers — then we increase retention, average ticket size, and the perceived value of Zak itself.

5%

increase in retention can drive up to 95% profit growth

67%

more spending from loyal customers vs. new ones

63%

of consumers aged 18–44 increase spending due to loyalty programs

System Architecture

The solution was designed across three interconnected layers, each working independently while generating compounding value when connected.

LAYER 1 Web Dashboard Restaurant owner CRM & configuration Settings Campaigns Customers Reports API & Webhooks LAYER 2 Campaign & Loyalty Engine Backend logic: cashback, credits & automation Cashback % Expiration Reactivation Referral QR Code & Web App LAYER 3 White-label Customer App Consumer-facing mobile: wallet, referral & rewards Registration Wallet Referral Rewards Data flows bidirectionally across all layers

Three Interconnected Layers

Web Dashboard

The restaurant owner's control center. Configures cashback rules, manages automated campaigns (Welcome, Birthday, Referral, Reactivation), monitors customer data, and tracks key revenue metrics.

Campaign & Loyalty Engine

The backend brain. Processes cashback percentages, credit expiration rules, inactivity reactivation thresholds, and referral rewards. Automates campaign triggers and connects dashboard decisions to customer-facing outputs.

White-label Customer App

The consumer touchpoint. Accessed via QR code — no download needed. Handles registration, displays the digital wallet with real-time balance, enables share-and-earn referrals, and delivers reward notifications.

Each layer was designed to function independently — a restaurant can use only the dashboard, only the customer app, or the full stack. But the compounding effect happens when all three connect.

Personas & User Flows

Three distinct personas interact with the loyalty ecosystem — each with unique goals, frustrations, and journeys through the platform.

Carlos Oliveira

Restaurant Owner · 42 · São Paulo

Business Owner Low Tech Time-constrained

150

Covers/day

22%

Return rate

Bio & Context

Runs a mid-sized restaurant in Vila Madalena. Arrives early for supplier deliveries, manages the floor during peak hours, briefly reviews POS dashboard at end of day. Has 15 minutes max for anything marketing-related.

Goals

  • Increase customer return rate above 35%
  • Build a customer database from scratch
  • Automate reactivation campaigns

Frustrations

  • No visibility into who his customers are
  • Complex loyalty tools require dedicated staff
  • Previous marketing showed no measurable ROI

Behaviors & Habits

  • Checks WhatsApp more than email
  • Relies on POS reports for business decisions
  • Trusts peer recommendations from restaurant associations

User Flow — Restaurant Owner Dashboard

1

Onboarding Call

Success team walks through setup

2

QR Code Deploy

Place QR codes on tables & receipts

3

First Campaign

Launch welcome cashback offer

4

Data Accumulation

Customer profiles build over time

5

Reactivation Push

Target dormant customers

6

Retention Growth

Monitor metrics & optimize

Emotional Arc

Curious

Anxious

Hopeful

Engaged

Confident

Empowered

Key Touchpoints

  • Onboarding call with customer success team
  • Dashboard daily snapshot via WhatsApp
  • Monthly performance review email
  • QR code printed materials at restaurant

Pain Points & Opportunities

  • Setup must take <15 min or he'll abandon
  • Needs visual proof of ROI within first month
  • Opportunity: auto-generated weekly reports
  • Opportunity: one-click campaign templates

MVP Strategy Under Constraints

Built under tight time constraints with a lean team — prioritizing a minimum viable retention engine.

Initial MVP Scope

Configurable Cashback

Restaurant owners set their own percentages and limits

Four Automated Campaigns

Welcome, Birthday, Referral, and Reactivation

Payment Integration

Loyalty embedded into the core POS flow

Core Reporting

Essential metrics for measuring program impact

Future Iterations

Advanced Segmentation

Customer clustering by behavior, spend, and frequency

Automation Layers

Smart triggers based on purchase patterns

Personalized Marketing Campaigns

Targeted messaging based on consumer data

Social Media Integration

Direct sharing and engagement tracking

Dashboard: Configuration & Management

The dashboard centralizes financial logic and campaign management for restaurant owners with limited time and marketing maturity.

Loyalty Dashboard — Full configuration and management overview showing the loyalty program settings panel

Fig. 2 — Dashboard overview: Loyalty program configuration panel with cashback settings, expiration rules, and QR code access

Structural Settings

General Settings Screen

This screen centralizes the program's financial logic: cashback percentage, maximum discount per purchase, credit expiration rules, inactivity reactivation threshold, and direct access to the customer QR code.

The design decision was to consolidate financial complexity into a single clear control point. Reducing cognitive load was critical for the primary users — restaurant owners and managers.

General Settings screen showing cashback configuration and program rules

Fig. 3 — General Settings: Cashback %, max discount, expiration rules, and QR code

Automated Campaigns screen showing four campaign types

Fig. 4 — Automated Campaigns: Welcome, Birthday, Referral, and Reactivation modules

Campaign Activation

Automated Campaigns Screen

Each campaign is presented as an independent module within a unified logic. The card structure clearly communicates campaign purpose, status, and primary action.

Limiting the system to four structured campaign types reduces complexity while guiding restaurants toward lifecycle thinking instead of isolated promotions.

Metrics & Validation

Customers & Reports Screen

Key metrics are positioned at the top of the dashboard: registered customers, total purchases, total discounts granted, average ticket size, and total revenue generated.

This positioning reframes the module as a strategic management tool, not just an operational feature. Retention becomes measurable.

Customers and Reports screen with key metrics dashboard

Fig. 5 — Customers & Reports: CRM table with registered customers, purchases, and revenue data

Integration with the Critical Payment Flow

The payment moment is the most sensitive operational touchpoint. If the loyalty system is not seamlessly integrated here, it becomes irrelevant.

Payment Activate balance usage (discount) Customer registered? Yes Discount applied No Registration button (show welcome value) Activation modal (terms acceptance) registered Close payment Payment start Loyalty (balance) Registration flow Success / End Yes (registered) No (not registered) Alternative / dashed path Decision point

Fig. 6 — Payment flow: CPF identification, credit application, and discount confirmation before checkout

Three Critical Decisions

01

Identification Before Confirmation

Customer CPF identification happens before confirming the final amount, maximizing capture and preventing missed database opportunities.

02

Credit Before Payment Method

The discount is applied before selecting debit, cash, voucher, or credit card — avoiding financial conflicts and operational friction.

03

Explicit Final Value Confirmation

The system clearly displays the updated total before completion, reducing operational risk and increasing trust.

Customer Journey & White-Label Experience

The program integrates naturally into real restaurant behavior — no app download required. The QR code bridges physical and digital experiences without installation friction.

Arrival / Table Checks Menu Places Order Looks at Table Information QR Code Loyalty Accesses Web App Register / Fill Form Staff approach Consumes Asks for the Bill Pays Leaves

Fig. 7 — End-to-end customer journey: Arrival → Menu → Order → QR Code → Register → Consume → Pay → Leave

Key Design Decisions

01

No App Download Required

The program integrates via QR code at the table, bridging physical and digital without installation friction. Customers engage instantly.

02

Immediate Reward on Registration

Welcome credit appears instantly upon sign-up, triggering perceived gain and significantly increasing return probability.

03

Journey Enhancement, Not Interruption

The loyalty experience flows naturally within the dining journey — from arrival through payment — rather than creating friction or requiring extra steps.

04

Staff-Assisted Fallback

If the customer doesn't scan the QR code, the staff approach at bill time ensures no opportunity is missed for registration and engagement.

Registration success confirmation screen

Registration Confirmation

Registration success confirms account creation instantly.

Welcome credit screen

Welcome Credit

Welcome credit appears immediately, reinforcing instant value.

Digital wallet mobile screen

Digital Wallet

Balance always visible. Transaction history builds transparency and trust.

Referral flow screen

Referral Flow

Share and Copy Link turn customers into acquisition channels.

Fig. 8–11 — White-label customer experience: Registration, welcome credit, digital wallet, and referral flow

Design System

Style Guide

The visual foundation powering the Loyalty Program experience — colors, type, components, and layout tokens.

palette

Color Palette

Primary — Pink

900
#831843
800
#9D174D
700
#BE185D
600
#DB2777
500
#EC4899
400
#F472B6
300
#F9A8D4
200
#FBCFE8
100
#FCE7F3
50
#FDF2F8

Neutrals

900
#18181B
800
#27272A
700
#3F3F46
600
#52525B
500
#71717A
400
#A1A1AA
300
#D4D4D8
200
#E4E4E7
100
#F4F4F5
50
#FAFAFA

Semantic

Success
#16A34A
Warning
#EAB308
Error
#DC2626
Info
#2563EB
text_fields

Typography — Web Desktop

Display DM Sans · Bold · 56px
H1 Heading DM Sans · Bold · 40px
H2 Heading DM Sans · Bold · 32px
H3 Heading DM Sans · Bold · 24px
H4 Heading DM Sans · Semi · 20px
Subtitle-lg DM Sans · Semi · 18px
Subtitle DM Sans · Semi · 16px
Body DM Sans · Regular · 16px
Body-sm DM Sans · Regular · 14px
Caption DM Sans · Medium · 13px
Description DM Sans · Regular · 12px
Description-sm DM Sans · Medium · 11px
smart_button

Buttons

Primary

Secondary

Tertiary

Ghost

Link

Default Hover Pressed Disabled

Sizes

text_format

Text Inputs

Default

Placeholder

Focused

Typing...

Filled

João Silva

Disabled

Placeholder

Error

Invalid input

This field is required

With Icon

search Search...
arrow_drop_down_circle

Dropdowns

Default

Select option expand_more

Focused / Open

Select option expand_more
Option A
Option B
Option C

Filled

Option A expand_more

Disabled

Select option expand_more

Error

Select option expand_more

Please select an option

apps

App Icons

Filled

loyalty
loyalty
loyalty
loyalty

Outlined

loyalty
loyalty
loyalty
loyalty

Duotone

loyalty
loyalty
loyalty
loyalty
grid_on

Grid & Spacing

4px

Base Unit

8px

Element Gap

24px

Component Padding

32px

Section Gap

Impact & Results

The pilot launched in three restaurants in São Paulo — two small and one mid-sized.

Key Outcome

50%+

of frequent customers joined

the loyalty program

3

pilot restaurants

in São Paulo

Growth
Partner

Perception shift

from operational tool to growth platform

Clear Value Proposition

Restaurants immediately understood and adopted the credit-based loyalty model.

Low-Friction Onboarding

QR-code driven registration required no app download, maximizing customer capture.

Strong Credit Model Adoption

The cashback/credit approach resonated with both restaurant owners and consumers.

Thank You

This was not the launch of a feature. It was the introduction of a new strategic growth layer inside the product — transforming Zak from an operational management tool into a growth partner for restaurants.