ReimeiTech
REIMEITECH.
← Web & Mobile
Booking & Scheduling Systems

Calendar logic that handles the real world.

Booking that survives timezones, double-bookings, buffers, recurring availability, and no-shows — with provider calendar sync, enforced policies, and payments, all in one system instead of three glued together.

Availability rules / timezones / calendar sync / policies / payments

The moment a date becomes an appointment.
Scroll
01The idea

Booking looks like a calendar widget — right up until the real world shows up.

Then come the timezones, the double-bookings, the buffer between appointments, the client who reschedules at midnight, the daylight-saving weekend, the provider who blocked Friday on their own calendar. Each is a small thing; together they're the reason a booking flow either quietly works for years or generates support tickets every week. We build the engine that gets every one of them right — so the calendar just works.

02The edge cases

The hard parts are the whole job.

Anyone can show a calendar. The value is in everything that has to be true before a slot is safe to offer.

  • 01

    Timezones & daylight saving

    Stored in UTC, shown to everyone in their own zone — even on the night the clocks change.

  • 02

    Double-bookings

    Slots locked at the moment of booking, so two people can't claim the last one at once.

  • 03

    Buffers & travel time

    Prep, clean-down, and travel between locations baked into what's actually offered.

  • 04

    Recurring availability

    Weekly, fortnightly, and custom patterns — with the exceptions that trip naive systems.

  • 05

    Multi-resource rules

    A booking that needs a room and a person and a piece of equipment, all free at once.

  • 06

    Cancellation & no-show

    Windows, late-cancel and no-show fees, enforced by the system, not an awkward chat.

03What we build

Every shape of "when can I come in?"

The category changes the matching and the fulfilment; the availability engine underneath is shared craft.

Appointments & services
01

Appointments & services

One-to-one bookings for salons, clinics, consultants, and trades.

Classes & events
02

Classes & events

Group sessions with capacity, waitlists, and per-attendee details.

Rentals & resources
03

Rentals & resources

Time-based hire with availability, deposits, and return windows.

Multi-location
04

Multi-location

Different staff, hours, prices, and policies per branch — one system.

Rooms & equipment
05

Rooms & equipment

Multi-resource booking where a room, a person, and kit must align.

Team & round-robin
06

Team & round-robin

Route bookings across a team by availability, skill, or fair rotation.

04The availability engine

One engine decides what's bookable.

Availability isn't a column in a table — it's the result of every rule applied together, in the right order, for the right resource. We build that engine as the core of the system, so a customer is only ever offered a slot that genuinely works.

  • Working hours per person & location
  • Buffers before and after
  • Minimum lead time
  • Maximum bookings per day
  • Blackout dates & holidays
  • Multi-resource availability
Availability rules
Calendar sync
05Calendar sync

Two-way sync with Google & Outlook.

Providers already live in their own calendar — so we meet them there. A two-way sync means their personal events block availability and their bookings appear alongside everything else, with nobody keeping two calendars in their head.

  • 01

    External events block availability

    A personal event on Google or Outlook removes that slot automatically.

  • 02

    Bookings appear on their calendar

    Each booking lands on the provider's calendar with details and a link.

  • 03

    Changes flow both ways

    Reschedules and cancellations stay in sync — no calendar drifts out of date.

06Reminders & policies

Fewer no-shows. Policies that enforce themselves.

No-shows are a tax on every service business, and "please remember your appointment" doesn't scale. We automate reminders and bake your policies into the system, so the rules apply consistently and quietly — every time, without a difficult conversation.

  • Email and SMS reminders at intervals you choose
  • One-tap confirm, cancel, or reschedule
  • Cancellation windows enforced automatically
  • Late-cancel and no-show fees applied on the record
  • Rescheduling that re-checks every availability rule
  • Waitlists that fill a freed slot automatically
Reminders and policies
Booking payments and pricing
07Payments & pricing

Booking and payment, one motion.

A booking that isn't paid for is a maybe. We connect Stripe so a slot can be secured with a deposit or full payment, and the awkward money — no-show fees, refunds, per-location prices — is handled by the system, not chased afterward.

  • Take payment or a deposit at booking
  • Per-location and per-service pricing
  • No-show and late-cancel fees charged automatically
  • Refunds and partial refunds within policy
  • Packages, memberships, and credits
  • Tax and currency handled per location
08The whole loop

Pick a service. See real availability. Book and pay.

A booking flow should feel like three quiet taps. All the difficulty lives behind it, where the customer never has to see it.

A booking system in use
09How we work

The book-and-pay loop first, the edge cases right after.

01

Map your rules

We capture every rule — hours, buffers, policies, resources — that decides what's bookable.

02

Design both flows

The customer's booking journey and the provider's day, each designed to feel effortless.

03

Build the engine

Availability, conflicts, timezones, and the book-and-pay loop, working end to end early.

04

Sync & automate

Two-way calendar sync, reminders, rescheduling, and policy enforcement layered in.

05

Launch & refine

We go live, watch real bookings, and harden the edge cases your business actually hits.

10Right when

The glue is starting to fail.

  • You're stitching together Calendly + Stripe + Sheets

    It works until it doesn't. We replace the fragile glue with one system that holds.

  • Bookings fail when timezones get involved

    The classic. We make a time mean the same instant for everyone, every season.

  • You need policies actually enforced

    Cancellation windows and no-show fees that apply by themselves, not by reminder.

Booking on a device
A scheduled calendar
11The stack

Built for time, done correctly.

App
Next.js/React/TypeScript/Tailwind CSS
Scheduling
Availability engine/RRULE recurrence/Luxon / UTC/Conflict locks
Calendar & comms
Google Calendar API/Microsoft Graph/Email/SMS
Money & data
Stripe/PostgreSQL/Redis/Webhooks
12Questions

The things teams ask us first.

Because the seams are where it breaks. Each tool is fine alone, but the glue between them is manual, fragile, and invisible until a double-booking, a missed payment, or a no-show slips through. A real booking system makes availability, payment, policies, and your calendar one coherent thing — so the edge cases are handled by logic, not by someone remembering to copy a row.

Let's make the calendar just work.

Tell us how your bookings work — the services, the resources, the policies, and the edge cases that keep breaking. We'll build a scheduling system that handles all of it, syncs to your calendars, and takes the payment.

ReimeiTech builds booking and scheduling systems that handle the real-world edge cases — multi-resource booking, recurring availability, timezones, conflict resolution, cancellation policies and no-show fees, two-way Google / Outlook calendar sync, reminders, rescheduling, and per-location pricing.