Appointment-Booking MVP: Scope, Cost, and Timeline

This worked example scopes a responsive booking product for customers, service providers, and an operations team managing availability, appointments, payments, reminders, and cancellations.

It is an illustrative planning range, not a quote. Reviewed 10 August 2026.

Must have

The complete appointment promise

  • Customer, provider, and administrator accounts with appropriate access.
  • Provider profiles, services, duration, price, location, working hours, breaks, and blocked time.
  • Availability search, timezone-aware slot selection, booking confirmation, rescheduling, and cancellation.
  • Card payment or deposit, refund state, customer receipt, and provider payout record where required.
  • Email/SMS reminders, provider schedule view, admin booking search, and support intervention.

Should have

Controls that prevent calendar chaos

  • Configurable cancellation windows, no-show state, buffer time, notice period, and booking horizon.
  • Calendar export or one carefully selected calendar integration.
  • Accessible booking flow, privacy controls, audit trail for schedule changes, and delivery monitoring.
  • Basic reporting for utilization, cancellations, no-shows, revenue, and reminder delivery.

Post-MVP

Scope to earn after the core flow works

  • Native apps, offline provider schedules, waitlists, memberships, packages, and gift cards.
  • Resource pools, group bookings, recurring appointments, multi-location optimization, and marketplace discovery.
  • Automated pricing, recommendation, advanced CRM campaigns, and broad third-party integration catalogs.

Visible assumptions

How this example reaches its range

  • This reproduces the booking calculator's starting selection with Rescheduling and cancellation moved from Could to Should so the estimate covers the reviewed scope.
  • Base feature effort: 48 optimistic, 92 most-likely, and 164 pessimistic person-days; PERT expected effort is about 96.7 person-days.
  • Public web, authenticated web, and an admin portal; three primary roles; standard design; small launch scale; one language; and one tenant.
  • Product management, design, QA, and DevOps/release coverage add 40%. Three platform surfaces add 28%, the third role adds 4%, and the selected accessibility allowance adds 8%.
  • Blended rate: €650 per person-day. Productive team capacity: 12 person-days per week. Discovery and release buffers add 1.5 weeks.
  • The 15% contingency applies to all three estimate bands. The combined factor is 2.315, producing about 111.1 optimistic, 223.8 expected, and 379.6 cautious person-days.

Using these assumptions produces an indicative cost range of approximately €72,000–€247,000 and an elapsed range of about 11–33 weeks.

Delivery phases

A practical implementation sequence

  1. Resolve service duration, capacity, timezone, cancellation, payment, reminder, and support policies.
  2. Build identity, provider/service setup, schedule rules, and admin foundations.
  3. Deliver slot search, booking, payments, notifications, provider operations, changes, and refunds.
  4. Test concurrency, daylight-saving transitions, accessibility, payment failure, reminder delivery, and operational recovery.

Main risks

Questions discovery must resolve

  • What exactly reserves a slot, and how are simultaneous booking attempts resolved?
  • Which timezone owns availability, reminders, rescheduling cutoffs, and reporting?
  • When are deposits or full payments captured, refunded, forfeited, or paid out?
  • Which calendar is authoritative, and how should conflicts or integration delays recover?

Try the scenario

Replace this example's assumptions with your booking model.

Reproduce this booking estimate Read the estimation methodology Compare export options