Core operations
Starter
GHS 2,990 yearly option available
Single-location teams that need booking, catalog clarity, and day-to-day operations.
Core operations
- Core booking
- Calendar
- Inbox
- Customer records
Capacity
- 1 active staff seat
- 1 location
Pricing
This page uses the current repo-backed billing catalog and shared plan presentation logic. It keeps pricing authoritative while still feeling premium and customer-readable.
Pricing overview
Current catalog
Authoritative values sourced from the repo
Billing cycle
Starter, Pro, and Enterprise with monthly and annual variants.
Starter
GHS 299
/ month
Pro
GHS 899
/ month
Enterprise
GHS 2,499
/ month
Plan cards
This structure avoids the common pricing-page mistake of dropping visitors straight into a dense comparison table.
Core operations
GHS 2,990 yearly option available
Single-location teams that need booking, catalog clarity, and day-to-day operations.
Core operations
Capacity
Growth and automation
GHS 8,990 yearly option available
Growing teams that want campaigns, loyalty, tickets, automation, and deeper customer context.
Core operations
Capacity
Growth, automation, and revenue
Scale and support
GHS 24,990 yearly option available
Multi-location or scale-heavy operators that need capacity, premium controls, and priority support posture.
Core operations
Capacity
Growth, automation, and revenue
Support posture
Plan comparison
The comparison stays readable by separating it from the top-level sales moment.
| Capability | Starter | Pro | Enterprise |
|---|---|---|---|
| Seats included | 1 | 5 | Unlimited |
| Locations included | 1 | 2 | Unlimited |
| Public booking portal | |||
| Catalog and FAQs | |||
| In-chat payments | |||
| Campaigns | |||
| Loyalty | |||
| Support tickets | |||
| Customer memory | |||
| Advanced automation | |||
| Group and multi-service bookings | |||
| Support posture | Standard | Standard | Priority support |
Pricing FAQ
These answers stay close to the real operational decisions behind public pricing.
Yes. The numbers shown are aligned to the repo-backed current billing catalog and shared plan presentation logic.
The repo includes both monthly and annual variants for the current catalog, so the storefront presents both and keeps them centralized in one source file.
Yes. Pricing is centralized in the storefront data layer, so later changes are one-file updates rather than page-by-page edits.
Close the pricing route
The pricing page should narrow uncertainty, not replace the rest of the product story. Use the contact route for the next conversion step.