MindPalaceX · The Workshop
The Idea Wall →

On the Idea Wall · ▲ 0 votes

Clientbook — the spec

A permission-gated client portal for service businesses — starting with salons — where clients own their profiles, preferences, and service history, and businesses earn access to exactly what each client chooses to share. Clients book, give feedback, and build a visual record of their work; businesses get the context they need to deliver a consistent, personalized experience every visit. The platform also runs a two-way knowledge layer: businesses can teach clients (product tips, aftercare, technique education), and clients earn points for engaging and sharing feedback.

---

Decisions locked

QuestionAnswer
ShapeClient portal (web app)
Primary audiencesConsumers managing their own service relationships; business owners and their staff
Core loopClient maintains profile → attends appointment → leaves feedback → earns points; business reads permitted profile data → serves better → shares knowledge
v1 success metric10 active users per week at day 30

---

The core loop

  1. Client creates a profile — enters preferences, skin/nail notes, allergies, style goals, and uploads reference photos.
  2. Client grants permissions — chooses which businesses can see which profile sections.
  3. Business staff reviews permitted data before the appointment — preferences, tech notes, and photo history load on the booking detail view.
  4. Appointment happens — staff may add internal tech notes (visible to permitted staff only, never the client).
  5. Client receives a post-appointment feedback form — rates the experience, adds comments, and the visit logs to their service history.
  6. Client earns points — for completing feedback, engaging with business knowledge posts, or referring others; points redeem for perks set by each business.

---

v1 scope

Client Profile with Service History and Preferences
Stores name, contact info, service preferences, skin/nail notes, allergies, and a chronological service history. Lives on the client dashboard and is the single source of truth for every booking.

Tech Notes (Staff-Only)
A private notes field on each appointment record that only permitted staff can read or write. Surfaces on the booking detail view inside the business dashboard — never exposed to the client-facing UI.

Post-Appointment Feedback Form and Ratings
A short form triggered automatically after each appointment: star rating, open comment, and optional photo upload. Results aggregate on the business analytics view and attach to the client's history.

One-Click Rebooking with Preferred Tech or Service
A rebooking button on the client's appointment history that pre-fills their last service, preferred technician, and duration. Sends the request directly to the business calendar.

Client Photo Gallery of Past Work
A visual log of photos uploaded by the client or added by staff (with client permission) at each visit. Lives on the client profile and is browsable by both client and permitted business staff.

---

Deliberately later

  • Permission-based data sharing between client and business — the permission model is foundational but needs the core profile solid first; a misconfigured v1 permission layer is a trust liability.
  • Appointment reminders with preference summaries — valuable once booking volume exists to justify the SMS/email cost and template logic.
  • Service availability calendar synced to bookings — real-time calendar sync requires provider integrations (Google, Square, etc.) that deserve a focused build sprint, not a v1 afterthought.

---

Data model sketch

  • users — id, name, email, phone, role (client | staff | owner), points balance
  • businesses — id, owner user\_id, name, industry, reward rules
  • client_profiles — id, user\_id, preferences JSON, allergies, style notes, created\_at
  • permissions — id, client\_profile\_id, business\_id, granted\_sections JSON, granted\_at
  • appointments — id, client\_profile\_id, business\_id, staff\_user\_id, service, datetime, status
  • tech_notes — id, appointment\_id, staff\_user\_id, note\_body, created\_at
  • feedback — id, appointment\_id, rating, comment, created\_at
  • gallery_items — id, client\_profile\_id, appointment\_id, file\_url, uploaded\_by, visible\_to\_client bool

---

Screens

  • Client Dashboard — profile overview, upcoming appointments, points balance, and rebooking shortcuts
  • Profile Editor — preferences, notes, and permission controls organized by business
  • Photo Gallery — chronological grid of past-work photos, filterable by service
  • Business Dashboard — today's appointments, each with permitted client data and tech-note access
  • Appointment Detail (Staff) — full permitted profile, tech notes editor, and post-visit actions
  • Feedback Form — post-appointment rating, comment, and photo upload (client-facing, mobile-first)
  • Knowledge Feed — business-posted tips, aftercare guides, and education content with point rewards for engagement

---

How to use this document

  • Bring it into Mind Palace, where the guided platform and its AI coach pick up from exactly this document and build with you step by step.
  • Hand it to a developer as the complete v1 brief — scope, data model, and screens are all defined.
  • Keep it as the single source of truth while you build, so every feature decision traces back to one agreed baseline.

This is Noonie's. Build yours.

A spec like this is step 3 of Mind Palace's nine — the other six take a weekend: working software, a real offer, first customers.

Want to build this with Noonie?

Tell us who you are and we'll broker the introduction — their contact details stay private until they say yes.