6
15 Comments

I built an AI that books appointments for small businesses 24/7 — got my first real user and real feedback

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:

  • Client opens a chat-based booking page
  • AI collects their info, asks what they need, confirms duration
  • Checks real availability from the business owner's Google Calendar
  • Books the slot and sends confirmation emails to both sides

No forms. No phone tag. Just a conversation that ends in a booked appointment.

Tech stack:

  • Next.js 14 + Prisma + Neon Postgres
  • Claude API (Anthropic) as the conversational brain
  • Google Calendar API for real-time availability
  • Resend for email confirmations
  • Deployed on Vercel

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.

on June 20, 2026
  1. 1

    That first real user feedback is worth more than months of assumptions — what did they push back on or ask for that you didn't expect?

  2. 1

    Straight answer to your real question: conversational booking is not better than Calendly, it is better than the back-and-forth that happens before someone is ready to use a Calendly link. Different jobs. Calendly wins when the person already knows they want the 3pm slot. You win when they have three questions they need answered before they will book at all, which is exactly your uncle's property enquiries. So stop positioning against Calendly and start positioning against the phone tag, because that is the pain people actually feel. Two more things. Pick one vertical and own it. "Small businesses" is not a market, but "booking for property consultants" is, and you already have a real user and a real quote in that niche, so go get nine more just like him. And watch the $399 done-for-you number. That is setup revenue, it teaches you a ton, but the real business is the recurring per-tenant fee. Make sure every setup converts into something that bills again next month.

  3. 1

    One angle worth stress-testing: your chat widget depends on driving traffic to a booking page. But for property consultants, contractors, and healthcare providers, your core targets, the first touchpoint is usually a phone call. The "missed call" pain doesn't get solved if the lead never reaches the page.

    Have you thought about whether handling inbound calls (voice-to-booking) would close that distribution gap? Seems like the same appointment problem, just a different entry channel, and the business wouldn't have to retrain how their clients already reach them.

  4. 1

    That first real feedback is usually more valuable than the first broad traffic spike. I’d turn it into a tiny trust loop: what did the user believe before trying it, what did they fear, and what made them say yes? For Kinetic Override I found the same pattern around Android permissions/local data: the feature list mattered less until the page made 'local profiles, no account, no ads, no-root' obvious up front.

  5. 1

    thoughtful comment :)

  6. 1

    The instinct to get your uncle using it with real clients instead of just demoing it yourself is the right move. Most people skip that step and ship based on their own mental model of the user, then wonder why the bug reports don't show up until launch. Two real UX bugs from two weeks of actual usage is worth more than weeks of solo testing.

    On your actual question, conversational versus Calendly-style, I don't think it's universally better, I think it's better for a specific kind of business. Calendly works because the booker already knows exactly what they want, a 30 minute call, a specific service, pick a slot. The conversational approach earns its keep when the booker doesn't know that yet, like your uncle's property consulting example where the back and forth was never really about scheduling, it was about figuring out what the appointment even needed to cover. That's a meaningfully different job than what Calendly does.

    I'd lean into that distinction in your positioning rather than competing on "easier than Calendly," because for the simple case, Calendly already won and is free. Your edge is for businesses where the booking conversation requires some judgment, therapists, consultants, trainers asking qualifying questions, not just slot picking. I'd make that the headline instead of the chat interface itself, the AI conversation is the how, but the real value is probably "stop losing clients who don't know exactly what to ask for yet."

    $399 for done-for-you setup seems reasonable for that audience, those businesses tend to not want to configure anything themselves anyway.

  7. 1

    It's really good that you had someone in the family to do a first trial/demo.
    I wish I was so lucky. How do you get your first customers (or only testers) if you don't have a big social circle to pick from.
    I'm crrently running an invite based alpha mainly on IG reels content. I got my first 10 signups and real users running through the whole product, which is cool. But I'm really uncertain how to progress from here, just tweak my reels for more reach?

  8. 1

    The strongest part here is that you tested it with a real small business instead of only demoing it.

    For positioning, I’d make the pain more specific: missed calls, slow replies, and back-and-forth scheduling. “AI booking” sounds nice, but “stop losing appointments when you’re busy” feels more urgent.

  9. 1

    nice that you already have a real user. one wall hides in your target list.
    the moment a therapist uses this the what do you need intake becomes health info and that puts you under hipaa as a business associate.
    that means a signed agreement with every provider you serve and the same with anything downstream like your ai and email providers.
    a generic booking tool gets pulled in the second one therapist signs up. worth setting up before you chase the therapist crowd.

  10. 1

    The conversational angle feels strongest when you sell the outcome, not the AI: “turn missed calls into booked slots after hours.” I’d track where users abandon the chat, how often the bot asks a second clarifying question, and booked-slot rate versus a simple form.

  11. 1

    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.

    1. 1

      That's a fair flag. I think the question underneath might be whether
      this generalizes beyond one trusted relationship (my uncle) to a
      complete stranger with no prior trust in me. That's probably the real
      test I haven't run yet.

      1. 1

        That's actually the question I'd be most interested in.

        Not whether the result repeats.

        What exactly gets validated if it does.

        What's the best email to reach you on?

        1. 1

          You can reach me at [email protected] — happy to continue this
          there.

          1. 1

            Appreciate it.

            Just sent something over.

            Interesting question either way.

Trending on Indie Hackers
I built a tool directory that doesn't pretend every founder has the same needs User Avatar 62 comments Drop your landing page URL. I'll use Ferguson to tell you why visitors might be leaving User Avatar 49 comments AI helped me ship faster. Then I forgot what my product actually does. User Avatar 37 comments I Was Picking the Wrong SaaS Tools for Two Years. Here's the Mistake I Finally Figured Out. User Avatar 32 comments Most early-stage SaaS companies miss churn signals — here’s how to catch them early User Avatar 28 comments How I Run a 1.7M Product Search Engine at 66ms on a $0 Hosting Budget User Avatar 19 comments