~/demos/booking

Booking Widget.

A self-serve booking flow that picks the slot, takes the deposit, and sends the confirmation — without a single back-and-forth email.

reacttypescriptdate mathformsruns locally

// the problem

When the inbox is the calendar.

For most service businesses, booking starts as a polite back-and-forth and ends with a missed follow-up.

~/the-problem.sh

$ grep -c "does Tuesday work?" inbox

14 emails to schedule one appointment.

Two double-bookings a month, three no-shows, zero deposits collected.

You're answering "what time slots do you have?" at 9pm on a Sunday.

// the solution — try it

A booking flow your customers actually finish.

Pick a service, pick a date, pick a time, leave a deposit. Four steps, no email tag.

~/booking.applive

1// pick a service

2// pick a date

Apr 2026

selected todayclosed: Sun · Mon

3// pick a time

All times in CST. Crossed-out slots are already booked.

4// your details

name *email *anything we should know?

// demo only · no card is charged · nothing is sent

// in production

What this becomes when it's real.

►~/in-production.mdavg setup: 3–5 weeks

✓01 / sync

Connected to your real calendar

Reads availability from Google Calendar, Outlook, or Apple. Customers can only book slots when you're actually free.

✓02 / collect

Real deposits, real receipts

Stripe or Square in the back. Deposits are held against the appointment, applied to the final invoice, or refunded automatically on cancellation.

✓03 / remind

No-shows drop

Reminder emails 24 hours out, SMS reminders 2 hours out. One-click reschedule link in every email so calls don't happen at midnight.

✓04 / followup

After the appointment

Auto-trigger a thank-you email, a review request, or a follow-up booking link. Fits inside whatever workflow you already run.

→ This demo runs entirely in your browser. No card is charged, nothing is sent.

// like what you see?

Need something like this?

I build booking and scheduling tools wired to your real calendar and payment processor.

When the inbox is the calendar.

For most service businesses, booking starts as a polite back-and-forth and ends with a missed follow-up.

~/the-problem.sh

$ grep -c "does Tuesday work?" inbox

14 emails to schedule one appointment.

Two double-bookings a month, three no-shows, zero deposits collected.

You're answering "what time slots do you have?" at 9pm on a Sunday.

A booking flow your customers actually finish.

Pick a service, pick a date, pick a time, leave a deposit. Four steps, no email tag.

~/booking.applive

1// pick a service

2// pick a date

Apr 2026

selected todayclosed: Sun · Mon

3// pick a time

All times in CST. Crossed-out slots are already booked.

4// your details

name *email *anything we should know?

// demo only · no card is charged · nothing is sent

What this becomes when it's real.

►~/in-production.mdavg setup: 3–5 weeks

✓01 / sync

Connected to your real calendar

Reads availability from Google Calendar, Outlook, or Apple. Customers can only book slots when you're actually free.

✓02 / collect

Real deposits, real receipts

Stripe or Square in the back. Deposits are held against the appointment, applied to the final invoice, or refunded automatically on cancellation.

✓03 / remind

No-shows drop

Reminder emails 24 hours out, SMS reminders 2 hours out. One-click reschedule link in every email so calls don't happen at midnight.

✓04 / followup

After the appointment

Auto-trigger a thank-you email, a review request, or a follow-up booking link. Fits inside whatever workflow you already run.

→ This demo runs entirely in your browser. No card is charged, nothing is sent.