How it works
Start with the journey your business needs.
Define what customers buy or book, how providers deliver it and what your team needs to operate.
1. Define the marketplace.
Bring the catalog, the service locations, the required options and the rules that shape a booking.
Products, service visits and programs have different requirements. The demonstration should reflect your actual operating model.
2. Scope the configuration.
Separate the existing brand, catalog and service settings from any additional engineering work.
3. Review the customer and operational views.
Inspect the relevant customer journey and the information available to providers and marketplace operators. The examples below are a separate local operational scenario.
4. Plan validation and delivery.
Agree the implementation scope, acceptance criteria and release responsibilities before launch.
Release timing follows the product, data and operational checks required for the agreed scenario.
Questions before a marketplace demo.
Which service models can we discuss?
Location-based appointments, scheduled at-home services, and programs with sessions. Branches, working times and coverage zones are configured per service.
Can we combine a product with installation?
The customer app screenshots show a product and its installation in one cart, including time selection. The illustrated journey stops before payment.
Are session packages demonstrated?
Recorded journeys demonstrate package purchase, credits and redemption, along with session capacity and provider-recorded attendance. This does not establish production readiness for recurring subscriptions or memberships.
Does a booking automatically dispatch a provider?
Provider assignment and zone matching are partly integrated and are not connected end to end to booking creation. ASAP dispatch and live tracking require engineering.
What can we configure, and what needs engineering?
Supported themes, content, terminology and per-service settings can be scoped as configuration. New layouts, modules and integrations may require engineering.
Is assisted booking released?
It is in testing, not released. The recordings show service discovery, time selection and an unpaid cart; they do not demonstrate a paid booking or a verified full booking journey.
Do all screenshots show one completed transaction?
No. The customer demonstration and operational scenario are separate runs. The provider and admin detail views show the same demo booking, with payment not recorded.
Your next step
Scope your marketplace, step by step.
Bring your first use case. We’ll discuss the product fit, configuration and checks required before release.
Request a demo