Bounded directory, planner, dashboard, and human-handoff capabilities form the current MVP starting set.
SmoozenExplore
Smoozen MVP scope
A modular wellness intelligence layer for B2B clients.
Smoozen helps a client offer better wellness discovery and planning without taking ownership of the client's identity, consent, booking, payment, safety, or final user records.
Scope interpretation
Current foundation is not future authorization.
Named integrations cannot start before their earliest-start dates and still need separate approval.
Payments, safety decisions, canonical bookings, identity, consent, and final records remain client-authoritative.
The starting set
Enough capability to be useful, bounded enough to be trusted.
The MVP foundation is deliberately small: assist discovery and planning, then return the decision to the client.
Wellness directory
Search and review approved providers, venues, services, prices, locations, and availability.
Foundation capabilityWellness planner
Turn bounded goals and preferences into advisory itineraries with transparent explanations.
Foundation capabilityClient dashboards
Give client administrators a tenant-scoped place to review plans, controls, usage, and approvals.
Foundation capabilityHuman handoff
Keep booking, payment, safety, consent, and final records in the client system of record.
Foundation capabilityNot part of the fast path
Some integrations stay deliberately deferred.
Dates below prevent work from starting early; they do not authorize work automatically.
WhatsApp and M-Pesa/payment implementation
Earliest start: after 2026-08-22. The date is a do-not-start-before gate, not an authorization.
PMS connectors, hotel credentials, live guest checkout, and OTA/travel APIs
Earliest start: after 2026-09-01. Each capability still requires separate approval and contract.
client.smoozen.com, or a server-to-server handoff. The initial fast path is synchronous REST; slow work uses jobs and signed callbacks.