Product strategy, UX & custom software
Calendy: building an appointment product around the working day
We built Calendy to connect a client's booking journey with the team that has to deliver the appointment. The product brings service rules, staff availability, a working calendar, and client context into one operating model.
The product problem spans both sides of a booking
A client wants a suitable service and an honest appointment time. The business has to account for who can perform the service, how long it takes, when people work, and what is already booked. The public experience can be simple only when those relationships are explicit underneath it.
We treated the calendar as an operating view of that model. An appointment connects a business, a client, services, assigned staff, and time. Client history and activity notifications then help the team understand what changed and where to continue the work.
A complete journey, with clear responsibilities
- Step 1
Choose services
Service duration and eligible staff shape the request.
- Step 2
Find an available time
Working hours and existing commitments constrain the options.
- Step 3
Create the appointment
The booking is checked again before it becomes part of the schedule.
- Step 4
Manage the working day
Staff use the calendar, client context, and activity updates to act.
For multi-service appointments, the sequence and staff commitments matter as well as the overall start and finish. Availability is therefore a domain decision. The final booking must recheck the relevant rules because another request can arrive after a client first sees an available slot.
UX that supports the people doing the work
A usable calendar
The team can inspect appointments, adjust services and times, and assign staff in the context of the day. The interface makes the record and the next action accessible together.
Client continuity
Client records connect upcoming appointments with previous bookings. Staff can open an appointment from that context and continue managing it in the calendar.
Visible changes
In-app notifications keep recent booking activity accessible. Confirmation emails and calendar files close the client handoff; eligible bookings can also receive business-enabled email reminders.
See the calendar and client workflow
The public walkthrough shows the calendar, appointment editing, client history, and recent activity. It is a concrete view of the working interface.
Business boundaries inform the architecture
Each business operates in its own workspace. Owner and staff responsibilities shape access to records and actions. Those checks belong in the application behavior as well as the visible interface.
A typed web application and relational data model make the connections between services, staff, clients, and appointments explicit. The important engineering question is whether a valid action remains valid when it reaches the point of change.
External handoffs need their own model
Calendy uses Paddle for business-owner subscription billing and Resend for transactional email. Subscription events and email delivery serve different purposes, so the product handles them as separate responsibilities.
Owner subscription billing is separate from customer payment for an appointment. The same discipline applies when evaluating a new connection: define the business event, its authority, and the behavior when delivery is delayed or repeated.
What this product demonstrates
Calendy provides a working example of connecting product strategy, domain rules, UX, and implementation. Its evidence here is the implemented workflow and public walkthrough. Product usefulness still needs to be assessed through real adoption, unresolved work, and the support required in daily operation.
For a business choosing its next step, our build-versus-buy guide explains how to separate standard capability from the part of the workflow worth owning. Our integration planning guide explores the handoffs between systems.
Apply the same judgment to your product
Explore our custom software development and integration services, or bring us a real workflow to discuss.
Discuss your product