Platform Owner Flow
The platform owner runs BookFlow as a SaaS product. This layer sells plans, creates vendor workspaces, runs the sandbox subscription checkout, lists businesses in the directory, and gives customers a central dashboard.
Platform Pages
| Page | Link | Purpose |
|---|---|---|
| Home | Platform home | Explains BookFlow and routes visitors to plans, directory, login, or signup. |
| Plans | Plans | Shows subscription choices. A selected plan can prefill signup. |
| Directory | Directory | Public marketplace where customers can discover vendors and professionals. |
| Signup | Signup | Creates the vendor owner, business profile, first location, subscription, and tenant subdomain. |
| Login | Login | Shared login for platform, vendor, staff, and customer accounts. |
Subscription Flow
Signup Checkout And Tenant Creation
Signup now proves the full commercial path. The owner account, business profile, first location, subscription transaction, checkout reference, and tenant workspace are created together, then the buyer finishes the sandbox billing step.
| Step | What BookFlow creates | Visible proof |
|---|---|---|
| Plan selection | Plan id and billing cadence are carried into signup. | Plan page and prefilled signup context. |
| Business signup | Owner user, business profile, location, membership, and tenant subdomain. | Workspace-created success message and tenant URL. |
| Subscription checkout | A platform subscription transaction with a checkout reference. | Hosted sandbox checkout page under the current live host. |
| Checkout completion | Billing proof, transaction status, and activation state. | Vendor admin can open after the transaction is approved. |
| Customer layer | Central customer dashboard and wallet relationship remain available outside one tenant. | Customer dashboard, customer portal, and demo mailbox proof. |
Screenshots
Login Logic
Login is central. The same login page can send a user to different places based on role and membership.
| User | After login | Why |
|---|---|---|
| Vendor owner | Nimbus admin workspace | They have an active business membership and owner permissions. |
| Staff member | Allowed tenant admin pages | They have a business membership but fewer permissions than the owner. |
| Customer | Customer portal | They need bookings, payment, receipt, review, and rebooking actions. |
Customer Dashboard And Demo Mailbox
The platform also owns customer-facing proof that is not tied to a vendor admin page. The customer dashboard summarizes next actions, the portal holds wallet/payment/support history, and the demo mailbox records customer-visible events such as wallet top-ups, payment receipts, support handoffs, and admin wallet adjustments.
Customer dashboard
Shows upcoming bookings, wallet status, payment actions, and linked businesses after login.
Customer portal
Lets a customer pay, top up wallet balance, rebook, review, manage support, and view receipts.
Demo mailbox
Lists generated proof messages so buyers can verify lifecycle events without real email delivery.
How Platform Connects To Tenant
When signup creates a business with subdomain nimbus, tenant routes become available under /t/nimbus. The same app now knows which business is active and loads that business's services, staff, pages, bookings, settings, and colors.
Directory Marketplace Proof
The directory is the marketplace proof surface. It shows real tenant listings, services, staff/trust signals, reviews, and booking links from the seeded data, so a buyer can verify BookFlow is not only an admin panel. After signup, the new tenant can appear in the same discovery path when its profile and public settings are ready.
Detailed Screen Reference
For every plan card, directory filter, signup field, and login field, open Platform Screen Reference.