Meetroid - Internal appointment Scheduling and payments, built into waldroid.com
An internal appointment-booking platform built for a company's sales and client-facing teams: Calendly-style availability, payment collection, and two-way sync with Outlook and Google Workspace, with each booking link generated automatically.

The challenge
Booking a call with Waldroid meant switching between a third-party scheduler, a separate payment link and a string of emails to confirm the time. The scheduler carried its own branding, which we could barely change, and it charged a monthly fee for every seat. Every person we added cost us more, and clients had to leave our site partway through booking.
The approach
- Replaced three tools with one flow. Booking, payment and confirmation happen on waldroid.com, in our own branding, with no hand-off and no per-seat fee.
- Made availability a single source of truth. Booking links started out with their own hours. I moved to one schedule per person: every link follows it or narrows it, and none can offer an hour outside it. A day can hold several windows, because that’s how people work across two countries.
- Made busy time belong to the person, not the link. Connected Google and Microsoft calendars and every held booking block the hour across all of someone’s links, so double-booking can’t happen.
- Showed every time in the reader’s own timezone. With hosts in Liverpool and guests in Lagos, nobody should have to convert a time. The server only deals in exact moments in time, and every screen converts them for whoever is reading.
- Designed payments for both markets. UK clients pay by card through Stripe. Clients in Nigeria pay by Naira bank transfer, the way they already pay, and upload proof that holds the slot until it’s approved. Either way, the guest can always see where their booking stands.
- Removed doubt after booking. Every booking gets a manage page to reschedule or cancel, the join link, and the host’s photo, name and title, so guests know who they’re meeting and what happens next.
- Prepared the host before the call. Each link can ask a few questions up front, and required answers are checked before the booking goes through.
- Protected guests’ privacy. A taken slot simply disappears from the public page. It never reveals whose booking it is.
- Grew it from a booking page into a team tool. I added staff accounts, calendars and links for each person, and self-service password resets, at no extra cost per person.
The outcome
A booking flow clients can trust from the first click to the calendar invite, in Waldroid’s own branding and in their own currency and timezone.
- Replaced the third-party scheduler and its per-seat subscription. Adding a team member now costs nothing.
- Double-booking is impossible by design, across every link and connected calendar.
- Card bookings confirm instantly. Naira bookings confirm with one click in the admin instead of an email thread.
- Shipped in about three months as roughly 20 incremental releases, growing from a single booking page into a scheduling tool for the whole team.
- [Real usage: bookings taken, share of paid bookings completed. These can be pulled from the live database.]
Meetroid now has its own booking directory at waldroid.com/book, with a page for each link.
Next step
The remaining gaps are in the time between booking and the call. Guests often book days ahead and nothing reminds them. So the next work is:
- Automatic reminders by email 24 hours and 1 hour before the call, with the join link and the manage link.
- No-show and completion tracking in the calendar, to measure the effect of reminders.