Scheduling for people who guard their time

The booking link that defends your calendar.

Halfhour gives invitees a page that only ever shows the right slots — your buffers, caps, and deep-work hours already subtracted before anyone picks a time.

Zero “does Tuesday work?” emailsCalendar sync is read-onlyTimezones handled, DST included
The scheduling tax

Seven emails to book thirty minutes.

Every meeting you host gets negotiated twice — once for the time, once against your own day.

  • The reply-all roulette

    “Does Tuesday work?” → “Mornings are bad” → “Next week?” — seven messages, four days, one thirty-minute call.

  • The meeting that landed on deep work

    You said yes to be polite, and the only two focus hours of the day went with it. The calendar never fought back.

  • The 9pm timezone math

    “3pm your time or mine?” — and one of you does daylight-saving arithmetic at the kitchen table. Someone still joins an hour early.

  • The no-show that cost an hour

    Prepared, dialed in, waiting. No reminder went out, so the slot died — and the buffer you didn't take died with it.

The signature idea

A day, defended.

Rules run before slots render. Invitees see a generous page; you keep a day with seams.

09:00

Deep work — guarded

Never bookable, never negotiated. The page simply doesn't offer it.

10:00

First bookable slot

Your earliest “yes.” Nothing before it, no exceptions to explain.

12:30

Lunch — guarded

An hour that doesn't appear on anyone's grid but yours.

14:00

Booked: intro call

Thirty minutes, confirmed to both calendars — and fifteen minutes of buffer stitched on after.

16:30

Last slot of the day

A four-a-day cap means the fourth booking closes the doors politely.

17:00

Hard stop

The page says “no times left today” — you never have to.

Product

One link. Your rules underneath.

Everything an invitee touches is generous; everything behind it is guarded.

A booking page per offer

Intro calls, paid working sessions, Friday office hours — each with its own length, price, notice window, and page.

Rules & buffers

Nothing before 10:00, fifteen minutes after every call, four a day, lunch untouchable.

Read-only calendar sync

Reads Google and Outlook to subtract conflicts; writes only its own confirmed events.

Reminders that end no-shows

24-hour and 1-hour nudges to both sides. Last month that meant two no-shows in sixty-one bookings.

Paid sessions

Put a price on the page and collect it at booking through your Stripe account.

One link, this week

What a defended week reads like.

18Sessions bookedof a 24-hour cap
0Scheduling emails sentthat's the product
15 minBuffer after every callnever skipped
2/61No-shows last monthreminders work
How it works

Set the rules once. Send the link forever.

The setup is an evening; the payoff is every meeting after it.

  1. 01

    Write your rules

    Connect your calendars read-only, then set the guardrails: earliest slot, buffers, daily cap, guarded blocks, notice windows.

  2. 02

    Make a page per offer

    A free intro call, a paid working session, office hours — each gets its own link, length, and price.

  3. 03

    Let the page say no for you

    Invitees pick from what's honestly available in their own timezone. Confirmations, reminders, and reschedules run themselves.

From defended calendars

The day has seams again.

I put the working-session price on the booking page and the tire-kicker calls just stopped. What's left on my calendar looks like my actual priorities.
RARenske AldervanFractional CMO
The buffer rule alone was worth it. I used to sprint between calls with my mic still muted — now every meeting ends with fifteen minutes that belong to me.
WOWale OkusanyaPrincipal, Okusanya Advisory
Pricing

Cheaper than the email thread.

Free for your first booking page. Paid plans add the rules that do the defending.

Link

$0/mo

One page, unlimited bookings.

  • 1 event type
  • Read-only calendar sync
  • Invitee-timezone slots
  • Email confirmations
Popular

Solo

$12/mo

The defended calendar.

  • Unlimited event types
  • Buffers, caps & guarded blocks
  • 24h + 1h reminders
  • Paid sessions via your Stripe

Team

$39/mo

One page for the whole bench.

  • 5 seats
  • Round-robin and collective events
  • Shared event types
  • A team booking page
Fair questions

Asked by everyone who's been double-booked before.

How does it prevent double-booking?

Halfhour reads every calendar you connect — read-only — and subtracts conflicts before a single slot renders. If something lands on your calendar between page-load and booking, the confirmation re-checks and offers the next honest slot instead of a clash.

What about timezones and daylight saving?

Invitees always see slots in their own timezone, detected and switchable. DST shifts are computed per-date, so a 14:00 in March stays a 14:00 in April — for both of you. Nobody does kitchen-table arithmetic.

What do invitees actually see?

Open slots and nothing else. Never your events, never titles, never how full the day is. A guarded morning and a booked morning look identical from the outside — that's the point.

Does it replace my calendar?

No — it defends it. Your calendar stays the source of truth; Halfhour writes confirmed bookings into it and reads everything else to keep the page honest.

What happens to no-shows?

Both sides get a 24-hour and a 1-hour reminder, and paid sessions can require payment at booking — the strongest no-show cure there is. Reschedule links are in every email, so a conflict becomes a new slot, not an empty one.

Can I leave with my data?

Yes. Export every booking to CSV whenever you like, and your link keeps redirecting for 30 days after you cancel so nothing in the wild goes dead mid-transition.

Send one link. Keep your morning.

Set the rules tonight — by tomorrow, the page is doing the negotiating.

Free for one event type · No card required