The Tandem guide

A little clarity
goes a long way.

Understand the demo, shape your availability, and see exactly what happens when someone finds a time.

One conversation, a clear path.

Tandem is a fictional scheduling product built around a familiar human problem: finding a moment without a long thread of messages. The local demo lets you explore the complete path from available hours to a reviewable request.

  1. Open Availability and choose the host’s weekdays, hours, and buffer.
  2. Open the booking demo and select a conversation length, date, and time zone.
  3. Choose a time, add your details, and prepare a request draft.
  4. Review the exact local time or download a tentative calendar file.
Try the experience →

Boundaries make the invitation better.

The demo offers weekday availability in UTC. The default is Monday through Friday, 09:00–17:00, with a 15-minute buffer after each meeting. You can disable a day or choose different whole-hour start and end times.

Lunch from 12:00 to 13:00 UTC stays reserved. A meeting and its buffer must fit entirely before lunch or after it, and before the end of the working day. Start times are offered on half-hour intervals. Slots less than one hour in the future are unavailable.

Example: with a 17:00 end time, a 30-minute conversation and a 15-minute buffer, 16:00 is available. A 16:30 start would end its buffer at 17:15, so it is not offered.

If every weekday is disabled, the booking page correctly shows no available dates. You can return to Availability to reopen a day or reset the defaults.

The same instant, wherever you are.

The booking calendar’s date grid follows the host’s UTC date. The time buttons translate each available instant into London, New York, Los Angeles, Mumbai, Tokyo, or UTC, using your browser’s standard time-zone database.

Changing time zones changes the displayed clock time, not the underlying meeting instant. The review always includes the full local date and time-zone abbreviation. In a far-ahead or far-behind zone, the local date can differ from the host date shown in the calendar.

Daylight-saving differences are handled through named time zones rather than a fixed hour offset. This avoids treating London or New York as if they kept the same UTC offset throughout the year.

A draft you can review.

Preparing a request reveals a summary with your name, email, selected time, duration, and optional context. It does not reserve the slot, contact Maya, or create a video meeting. The host is a fictional demonstration profile.

The downloadable calendar file contains a generic tentative conversation, its UTC start and end times, and a reminder that it is a local demo. It includes no attendee email addresses, organizer identity, or automatic invitation instruction.

You can edit the details or choose another time before saving anything. Opening or importing the calendar file is your choice and is separate from using this webpage.

Simple, local, and explicit.

Weekly availability is stored in session storage so it follows you between pages in the same browser tab. Your name, email, and conversation notes remain in the current page and are cleared by a reload. There is no sign-in, analytics integration, or external calendar connection in this concept.

If your browser blocks session storage, the settings page reports that it cannot save. The booking page can still use default availability. No form data is submitted to a remote service.

This is an interactive product demonstration, not an operating scheduling service. No actual invitations, bookings, or messages are sent.

More connection.
Less coordination.

Explore a calmer way to find time together.

Find a time in the demo ↗