SolutionsCraftersWe help build the future
Back to Work
Client engagement4.919 reviewsGoogle

Case study · Ruby Pedicure

Specialist care up front, admin that runs itself

Ruby Pedicure runs on a platform built for the way a medical footcare practice actually works: booking, signed medical intake, loyalty, vouchers and Dutch VAT invoicing in one place. The practice treats clients; the platform handles the paperwork.

SolutionsCrafters designed, built and operates the Ruby Pedicure platform: a bespoke build for a practice with specialist requirements.

rubypedicure.nl
The Ruby Pedicure homepage in English: a purple navigation bar, the headline "Healthy feet, personal care", booking and WhatsApp buttons, and a photo of the pedicurist in her treatment room.
01

Context

Ruby Pedicure is a footcare practice in Zwolle. Clients arrive with callus, corns, cracked heels, fungal nails or an ingrown toenail, often after months of discomfort, and many keep coming back for years. It's a personal practice with an excellent local name, built on unhurried, careful treatment. Every hour spent on forms and invoices is an hour not spent on feet.

02

Challenge

Medical footcare carries real responsibility. Before a first treatment, the practice needs a clear picture of blood thinners, reduced sensation in the feet, rheumatism, allergies and medication, and that picture has to stay current, not sit in a folder from two years ago. Around it sits everything else: gift vouchers, prepaid packages, loyalty cards, reminders and invoices that have to satisfy Dutch tax rules. Done by hand, that admin quietly eats the working day.

03 · Approach

Approach

SolutionsCrafters works along two routes: a ready-made platform for a standard salon, and a bespoke build when a practice needs more than that. Ruby Pedicure is a medical practice, so we built for the medical case. Intake became a versioned record, not a form: every submission is a signed snapshot of the exact questions asked that day, and the system flags on its own when a client's answers are too old to treat on. Booking was designed around it, so a first appointment cannot slip through on an incomplete intake. Everything commercial, from vouchers and packages to stamps, invoices and reminders, settles itself daily, so nothing rests on someone remembering.

System delivered

  • Medical-grade digital intake (anamnese) with a drawn signature, versioned question snapshots, and a flag when a record is out of date
  • A booking journey with real-time availability and intake gating before a first treatment
  • Gift vouchers with partial redemption, and prepaid treatment packages that reconcile themselves daily
  • Digital loyalty stamp cards with expiring stamps
  • Gap-free sequential VAT invoicing, with PDF invoices emailed automatically and aligned to the Dutch KOR scheme
  • Automated lifecycle messaging: appointment reminders, rebooking nudges, released-slot notices and win-back
  • A bilingual NL/EN site with localised URLs, plus an owner console for agenda, customers, analytics and marketing

What runs on its own, every day

  • Appointment reminders
  • Rebooking nudges
  • Released-slot notices
  • Win-back messages
  • Prepaid package reconciliation

Compliant Dutch invoices are generated and emailed automatically, in one gap-free sequence.

04 · What changed

What changed

  1. 01Every treatment starts from a current, signed medical record, not a form someone hopes is still accurate
  2. 02Bookings, vouchers, packages, loyalty and invoicing sit in one place, under the practice's own brand
  3. 03Routine client contact, from reminders to rebooking and follow-up, happens without anyone chasing it
  4. 04Invoicing meets Dutch VAT rules automatically, with no manual numbering and no gaps
  5. 05The reputation the practice has for calm, personal care is matched by how tightly it runs behind the scenes

Related services

Technology

Next.js 15Neon PostgresMollie paymentsAuth.js
Visit the public site

Have a project in mind?

Let’s define the next useful version of your product

Tell us what the product must do, who it serves, and where the current process breaks. Those three answers are enough to start.