Skip to content
All workCASE STUDY / PRODUCT DESIGN

Zidne CRM

A CRM for gyms that tells staff who needs attention, why, and what to do next.

Self-initiated concept

Type
Product Design · UX Case Study
Platform
Desktop web app, front-desk tablet ready
Market
Gyms and chains, Middle East
My role
Solo: research, product, UX and UI
Scope
9 modules · 5 patterns · AI layer
Tools
Figma · Notion · Photoshop · AI
Project
Self-initiated concept
Zidne CRM, slide 01: Cover: Zidne, a CRM for gyms that tells staff who needs attention, why, and what to do next

The case in 4 lines

01Problem
Gym software rarely lacks features. Daily work is slow and scattered, so staff keep Excel and WhatsApp open beside it. Gyms don't lose members at the door. They lose them between shifts.
02InsightP02
Staff don't want all the data. They want to know where to start, who needs them now, and what's next.
03Solution
From "a system that shows everything" to "a workspace that asks 3 questions": who needs your attention, why, and what's next?
04Principle
Every screen has to answer 4 questions: why is the staff member here? What do they see first? What do they decide? What do they do next? Otherwise it goes.
Zidne CRM, slide 02: One workspace for everyone behind the front deskZidne CRM, slide 03: The case in four linesZidne CRM, slide 04: Gyms don't lose members at the door. They lose them between shifts.

Research

products audited across 7 complaint areas
13.
ideas sorted with MoSCoW
38.
interviews with sales staff, one real working day each
2.
assumptions I refused to build on, because there was no evidence
10.

Evidence scaleEvery finding is tagged: strong / medium / weak

Strong
Medium
Weak
Zidne CRM, slide 06: 01 ResearchZidne CRM, slide 07: How the research was runZidne CRM, slide 08: The problem isn't missing features. It's slow, scattered execution.Zidne CRM, slide 10: Eight patterns that show up almost everywhereZidne CRM, slide 11: The issue isn't how many integrations. It's which one is true.Zidne CRM, slide 13: Four ways reports failZidne CRM, slide 15: Gyms run on events that expireZidne CRM, slide 17: What generic CRMs don't understand about gymsZidne CRM, slide 19: 13 products, 7 areas of complaintZidne CRM, slide 20: Where to match the market, and where to winZidne CRM, slide 21: Which Zidne ideas the evidence supportsZidne CRM, slide 22: Ten assumptions I refused to build on

The turning point

D1: From "a system that shows everything" to "a workspace that asks 3 questions"

  • Who needs your attention? Why? What's next?
  • Booking, attendance, InBody and mood are no longer modules inside the CRM; they became sources. The CRM's job is to collect the decision that comes out of them.

D2: Same member, 3 different screens (role-based)

  • Sales sees the right offers and the next step. Customer service sees complaints and history. The manager sees the numbers and the decisions.
  • This was one of the 10 assumptions I rejected: "one dashboard for everyone is better".

The design rule that tied it together

  1. Q1Why is the staff member here?
  2. Q2What do they see first?
  3. Q3What do they decide?
  4. Q4What do they do next?

Otherwise it goes.

Collect the decision, not the systems.
The interviews said: same data, two different jobs.
Zidne CRM, slide 23: 02 UsersZidne CRM, slide 24: Two people, one working day eachZidne CRM, slide 25: "Where do I start, who needs me now, and what's next?"Zidne CRM, slide 26: Mona opens LeadsZidne CRM, slide 27: Six findings, each with its evidenceZidne CRM, slide 29: What moved up, down, and what is still unprovenZidne CRM, slide 31: From a system that shows everything to a workspace that asks three questionsZidne CRM, slide 32: Collect the decision, not the systemsZidne CRM, slide 34: Every screen must answer four questions, or lose its placeZidne CRM, slide 35: Same member, three different screensZidne CRM, slide 36: The path every sale followsZidne CRM, slide 37: 03 DefineZidne CRM, slide 38: 38 ideas, sorted before a single screenZidne CRM, slide 39: Get them. Keep them. Serve them.Zidne CRM, slide 40: Five rules, fixed before any visual designZidne CRM, slide 41: Every "Create" looks the sameZidne CRM, slide 42: Every record opens the same wayZidne CRM, slide 44: Same bones, new skinZidne CRM, slide 46: 04 ProductZidne CRM, slide 47: Green acts. Violet thinks.

A day at the gym

07:00 · The problem today

A member's card was declined overnight, and nobody knew

With Zidne

A Critical alert with the reason and a suggested fix

Zidne CRM, slide 12: A card is declined before sunrise

10:30 · The problem today

An Instagram message left waiting all day

With Zidne

The lead shows up with its source, gets an owner in one tap, and AI suggests the offer

Zidne CRM, slide 09: An Instagram message waits all day

14:20 · The problem today

An issue nobody owns

With Zidne

Every case has an owner and a time, and Smart Assign suggests the best fit

Zidne CRM, slide 30: "Who owns this now?"

18:00 · The problem today

The 6 o'clock class is full again

With Zidne

All branches on one timeline

Zidne CRM, slide 18: The 6 pm class is full again

Monday · The problem today

"How are the leads doing?" and the answer arrives on Thursday

With Zidne

AI Analyze answers in a paragraph and a chart, and ends with an action

Zidne CRM, slide 14: "How are the leads doing?"

All day · The problem today

7 alerts in 7 places

With Zidne

One ordered follow-up list

Zidne CRM, slide 16: Seven alerts become one list

Call #30 · The problem today

A written report after every call

With Zidne

Outcome, mood, a summary and the next step

Zidne CRM, slide 28: The thirtieth call log of the day
Zidne CRM, slide 48: One screen, five layersZidne CRM, slide 49: DashboardZidne CRM, slide 50: Dashboard, detail screensZidne CRM, slide 51: LeadsZidne CRM, slide 52: Leads, detail screensZidne CRM, slide 53: MembersZidne CRM, slide 54: Members, detail screensZidne CRM, slide 55: Follow-upZidne CRM, slide 56: Follow-up, detail screensZidne CRM, slide 57: CommunicationZidne CRM, slide 59: Communication, detail screensZidne CRM, slide 60: OffersZidne CRM, slide 61: Offers, detail screensZidne CRM, slide 62: BookingZidne CRM, slide 63: Booking, detail screensZidne CRM, slide 64: Customer ServiceZidne CRM, slide 65: Customer Service, detail screensZidne CRM, slide 66: SegmentsZidne CRM, slide 67: Segments, detail screensZidne CRM, slide 73: Modules handing work to each other

AI that shows its work

D3: AI suggests, ranks and explains. The human decides.

  • Nothing sensitive happens automatically without a human.
  • AI never sits on a spinner: it shows its steps, the reply appears as it's being written, and it ends with buttons for the human to press.
Trust in AI comes from watching it think.
Zidne CRM, slide 68: 05 AI layerZidne CRM, slide 69: Rules taken straight from the researchZidne CRM, slide 71: AI Analyze reads the view and ends with an action; Smart Assign ranks the team

Where it stands

Proven

  • Logging calls by hand is a real burden
  • Staff need a daily priority list
  • Ownership and handovers are unclear
  • Sales revolves around follow-up
  • Role-based views beat a single dashboard

Still open

  • The best way to log calls
  • The final customer service workflow
  • The final Member 360
  • Details and permissions of the AI automation
  • The final KPIs for each screen

Next round: 30–40 interviews in 12–16 gyms.

Zidne CRM, slide 74: What is validated, and what is still openZidne CRM, slide 75: Now, next, later