Booking HandbookSearch
Guides by topic

Build, buy or extend

Choose the lowest-complexity route that meets the requirements and has an acceptable ownership and maintenance burden.

Browse this topic in Guides
Two adult operators map an old paper calendar and record cards into a configured system, test fictional records, compare both views with a checklist, and keep the previous process available during cutover.
Map, test, compare, and keep a way back.A safe migration proves services, people, customer records, future bookings, and changes with invented test data before the live process moves.

Open a detailed guide

Choose the task that matches what you need to decide or fix now.

Before you compare software

Start with these five checks

  1. Material unmet requirement
  2. Simpler configuration/integration route
  3. Ownership and recovery owner
  4. Data and migration plan
  5. Acceptance tests and stop rule

Four connected areas

Use these four areas to see which part of the booking setup needs attention.

Custom requirements and qualification

Define roles, objects, states, rules, integrations, migration, reporting, acceptance tests, budget, scope, and the simpler alternatives.

Is the gap material enough to justify custom ownership?

Permissions, roles, privacy and security

Map customer, provider, receptionist, manager, and admin actions plus authentication, audit, retention, deletion, and sensitive workflows.

Who may see or change each booking state?

Automation, API and extensions

Specify APIs, webhooks, events, queues, retries, idempotency, limits, secrets, logs, recovery, and extension maintenance.

What happens after an automated step fails twice?

Maintenance, data ownership and reliability

Plan exports, identifiers, portability, backups, restore tests, monitoring, upgrades, rollback, incidents, ownership, and end of life.

Who is responsible at 2 a.m. when booking stops?