Who can see what
Set viewing and action access by employee role, assigned location and work area.
Security & customization
Keep each organisation’s data separate and each employee’s access clear.
Teachers, front desk, finance and managers see and change information according to their role and location.
Discuss requirementsPublic website & demo
Organisation A system
Organisation B system
The website demo never touches a customer’s real business data.
The website and public demo only use public information and sample records. Each paying customer’s business information stays in its own operating environment.
Four important protections for everyday work.
Separate data for each organisation
Each organisation’s customers, classes and financial information stay in its own business system.
Avoid duplicate attendance and payments
A slow network or repeated click will not create the same business record twice.
Keep every important change
See who changed important information and when.
Keep receiving product updates while preserving the way your organisation works.
Start with standard processes, then adjust booking rules, staff access and reports. Add dedicated features only when they are genuinely needed.
Everyday management features
Lead management, scheduling, attendance, class credits, payments and reports keep improving.
CustomersSchedulingAttendanceClass cardsPaymentsReports
Adjustments for your organisation
Set booking, leave, make-up classes, staff roles and fields to suit your service.
Class typesBooking rulesPage accessStaff rolesCustom fields
Organisation-specific needs
Plan dedicated processes, reports, system connections and old-data migration when genuinely necessary.
Dedicated processBusiness reportSystem connectionData migrationRole-specific page
Confirm custom work before it goes live.
The advisor agrees the problem, proposed approach and acceptance criteria with the people who will use it. Your team tests the result before release.
- 1
Agree the need
Confirm who uses it, how the work is done and what a successful result looks like.
- 2
Configure or build
Adjust the product within the agreed scope and prepare it for testing.
- 3
Test it together
Ask the people who will use it to complete the important process and note any changes.
- 4
Launch after approval
Release only after both sides approve the result, with ongoing support available.
Start with the users, process and expected result.
Tell us who will use it, how the work is done today, where errors happen and what a good result looks like.