Hey IH ๐
Two weeks ago I shipped an AI Appointment Setter for small businesses โ solo therapists, trainers, coaches, consultants โ anyone who loses clients to missed calls and back-and-forth booking emails.
How it works:
No forms. No phone tag. Just a conversation that ends in a booked appointment.
Tech stack:
It's multi-tenant โ each business gets their own branded booking page and dashboard.
I got my uncle, a property consultant, to actually use it with real clients for two weeks instead of just demoing it to myself. That turned out to be the most valuable thing I did โ he found two real UX bugs I never would have caught alone (markdown formatting showing as raw asterisks, and the chat input not auto-focusing). Fixed both based on his actual usage, not assumptions.
Here's what he said after using it:
"Normally for property enquiries, clients have to call or message back and forth just to coordinate timing โ but with this, they directly talk to the AI and book the appointment themselves. The best part is that appointments automatically show up in Google Calendar, so I don't have to worry about tracking things manually anymore. It saved time and made the booking process feel more professional."
Built the entire thing using Claude Code โ from spec to live deployment to iterating on real user bugs, all in focused sessions.
Live demo: https://vedantix-appointment-setter.vercel.app/book/aivedantix
I'm a solo founder running this under VEDANTIX AI, currently offering done-for-you setup for small businesses. Starting at $399.
Would love feedback from this community โ especially on positioning and whether the conversational booking approach feels genuinely better than a Calendly-style form, or just different.
Interesting.
I'd be careful that the lesson doesn't become obvious too quickly.
Early validation can sometimes answer a question while quietly creating a different one underneath it.
That's what stood out to me here.