LiveMy own project2025
Hiring platform
A marketplace where hiring and freelance work run on the same four steps.
Next.js · React · TypeScript · PostgreSQL · Prisma · Neon
Read the full storyBack to work
SaaS platform
Smart booking platform
An answer at any hour, from the centre's own prices
Booking for beauty centres: WhatsApp at the front, a full system behind it.
- Beauty and wellness
- Live
- My own project
At a glance
- What it is
- Messages arrive at all hours. The platform answers for the centre, in the client's language, and turns questions into bookings.
- Who it is for
- Beauty and wellness
- Status
- Live
- What I owned
- Everything technical
The situation
Beauty centres run on WhatsApp and a paper diary. Messages arrive at all hours, the owner's hands are busy with a client, and the reply waits. A customer who gets no quick answer books somewhere else. And nobody knows how many appointments were lost that way, because a message that was never answered leaves no trace.
I built this platform as my own product. It runs on a monthly subscription for the centres that use it.
What was actually wrong
The question the platform is built on: how does the centre reply in the same minute without saying something wrong? A fast reply on its own is easy. An automatic answer that quotes a wrong price, or offers a service the centre does not provide, is worse than silence. Clients write in different languages, so a system that understands one and fails at another is not enough. And a conversation by itself is not the goal: it has to end as a booking the centre holds, not a promise in a chat.
What we were building inside
- The first reply cannot wait for the owner. It has to go out while the client is still on their phone.
- A wrong price sent in the centre's name is not a small mistake in this business. Answers come only from what the centre entered.
- The client writes in whatever language they use, and the reply comes back in that language.
- The centre owns its records: clients, conversations and bookings live in its database, not in somebody's phone.
- Owners of small businesses do not set up software themselves, so I install and configure the platform for each centre myself.
How I approached it
WhatsApp is only the door. The client writes where they always write, downloads nothing, opens no account. But what receives the message is not a phone. It is the centre's platform: its services and prices, its staff, its appointment book, and the record of every client, every conversation and every booking.
The assistant that replies is bound to what the centre entered. It takes prices from the centre's own list, free times from its own schedule, and it answers in the client's own language. What the centre has not entered, the system does not answer at all, because an invented answer in the shop's name costs more than an unanswered question.
And I set the platform up for each centre myself: I enter the services and prices with the owner, set up the schedule, and hand over a dashboard that runs it all. Owners of small service businesses do not onboard themselves, and a product that pretends they do dies quietly.
What it does
Booking for beauty centres: WhatsApp at the front, a full system behind it.
A reply at any hour
The client writes in the evening, on a holiday, or while the centre is full, and an answer comes back at once. No message hangs until the owner's hands are free.
In the client's own language
The client writes in Arabic, French or another language, and the system understands and answers in the same one. The language of the reply is not a setting fixed once. It follows each conversation.
Answers from the centre's data alone
Every price, service and time the assistant gives is taken from what the centre entered in its dashboard. What is not in the centre's data, it does not answer.
The conversation ends in a booking
A question about an appointment does not stop at the answer. The booking is written into the centre's schedule with the client, the service and the time, and the owner sees it on the dashboard.
The centre runs itself
Services, prices, staff and the appointment book all live in a dashboard the centre manages. Changing a price or adding a service needs no call to me, and the assistant answers with the new data at once.
A record that belongs to the centre
Every client, conversation and booking is kept in the centre's database. The message that used to vanish in a phone is now a record the centre can return to at any time.
The decisions
Every one of these had a real alternative and a real cost. Both are written down.
- 01The call
An app the client downloads, or a reply where they already write?
What I chose
WhatsApp is the door. Nothing to download, no account to open.
Why
Every new app is a wall in front of a busy person who only wants an appointment. The client already has WhatsApp and already messages the centre on it. The real product is not the chat window. It is the system behind it.
What I gave up
The door belongs to another company. WhatsApp's rules, limits and changes are outside my hands, and the platform has to move when they move.
- 02The call
Does the assistant answer freely, or only from the centre's data?
What I chose
From the centre's data alone. What is not entered gets no answer.
Why
In this business a wrong price does not stay on a screen. The client brings it to the centre's front door. One mistake like that destroys the centre's trust in the whole platform, and trust is the only thing the platform sells.
What I gave up
It answers less. Every service and price has to be entered before the assistant knows it, and many questions get no automatic answer until that entry is complete.
- 03The call
One language for everybody, or each client's own?
What I chose
Each client's own. The reply returns in the language the question was written in.
Why
Someone messaging a beauty centre writes the way they speak, and the system has no business forcing another language on them. The centre itself serves clients of more than one tongue, and a platform that understands one loses the rest.
What I gave up
No fixed script can cover it. Every rule in the assistant has to hold in every language that arrives, including ones nobody at the centre reads.
- 04The call
Self-service sign-up, or set up by hand for every centre?
What I chose
By hand. I set each centre up myself and enter its data with the owner.
Why
The owner of a beauty centre is busy running it and will not spend an evening configuring software. Products that assume otherwise in this market die quietly: a sign-up, an attempt, then silence. The platform works from day one because I make it work.
What I gave up
Growth is bound to my time. Every new centre costs a setup session, and none of that scales by itself.
How it moved through the stages
You tell me the idea
I started from how the centres actually work: WhatsApp for messages, a paper diary for appointments, and messages landing while the owner is busy. A lost appointment leaves no trace, so that became the thing the platform solves.
You see the real screens
I drew the product on one rule: WhatsApp is a door, and the platform stands behind it. The centre's data lives with the centre, answers come only from that data, and a conversation has to end in a written booking, not a promise.
You watch it being built
I built the dashboard where a centre manages its services, prices, staff and schedule, then the assistant that answers from that data alone, in the client's language, then the booking that closes the loop.
You launch, and I stay
It launched as a product on a monthly subscription. I install each centre myself and enter its data with the owner before the automatic replies begin.
What exists now
The platform runs today as my own product, on a monthly subscription, with paying centres using it. Each new centre I install myself, sitting with the owner until the services and prices are entered in full.
Revenue and growth belong to the client. I do not publish numbers I did not measure myself.
Built with
- Next.js
- TypeScript
- Prisma
- Neon
- Better Auth
- WhatsApp Business API
- Vercel AI SDK
- Cloudinary
- Upstash
- Inngest
- PostHog
Other work
In development
Smart travel guide
A travel guide that stays with the traveller and deals with providers directly.
Next.js · TypeScript · Prisma · Neon · Better Auth · Vercel AI SDK
Coming soon01 · You tell me the idea
At the same point this started from?
An idea, no technical co-founder, no obvious next step. That is the normal starting position.
Tell me about your idea