Waypilot
A multi-tenant operating system for driving schools—combining branded websites, school administration, instructor tools, learner self-service, payments, finance and platform operations.
Change the view. Keep the context.
An instructor records a lesson. The office sees a completed session. The learner sees progress. Three interfaces, one underlying event.
Try it: record the sample lesson, then switch to the school or learner view. This illustrates one part of a much larger multi-tenant platform. Simplified model. No client data. No production actions.Waypilot
A business, connected.
Explore how the product works with illustrative data.
The problem behind the brief
A driving school is a capacity, scheduling, teaching and payments business operating through several distinct roles. Generic CRMs solve the contact list; generic calendars solve the time slot. Neither manages the complete operating model, and neither becomes a repeatable product for many schools.
Waypilot productises the domain as a configurable platform. Each school can have a branded website and isolated operating environment; staff run leads, learners, instructors, communications and money; instructors manage teaching and finance; learners self-serve; platform operators provision tenants, domains, packages and capabilities.
The design decision
A complete operation, without one overwhelming interface.
Waypilot separates the platform operator’s work from the daily work of a driving school. Within a school, an office administrator, instructor and learner need different actions and levels of access. We designed these as connected experiences around shared records, rather than repeating the same dashboard for every role.
The trade-off to examine
Separate workspaces reduce the number of decisions each person faces, but make shared state and permission boundaries more important. The useful test is whether a lesson recorded by an instructor reaches the right school and learner views without exposing another school's records. A role switch in the demo explains the interaction; it is not evidence of a production security test.
In the working example above, record a lesson and switch roles. Look at what changes for each person and what stays consistent. It demonstrates the design decision with sample data; it is not a customer account or a measurement of business results.
Design and development by Voodoo AI. Explore the interaction above and the actual public website below.
Under the surface
Not a dashboard. A configurable business platform.
Waypilot has to work at two levels at once: the platform that brings schools online and the tenant product each school uses every day. Under that sit acquisition, teaching, scheduling, payments, reporting and self-service journeys.
Platform operations
Tenant lifecycle, domains, packages, capabilities, provisioning, subscriptions, audits and controlled support access.
Waypilot team · Provisioning / Packages / GovernanceBranded acquisition
A configurable public website gives each school an acquisition layer connected directly to its operation.
Prospective learners · Website / Content and SEO / Lead captureSchool workspace
Leads, learners, instructors, diaries, communication, payments, content and reporting in one school-specific system.
Office and management · CRM / Multi-instructor diary / ReportingInstructor cockpit
Lessons, pupils, progress and utilisation sit alongside income, expenses, vehicles and tax workflows.
Driving instructors · Teaching / Utilisation / Finance and MTDLearner portal
A secure self-service view of upcoming lessons, progress, payments, documents and account security.
Active learners · Lessons / Progress / PaymentsShared infrastructure
Tenant isolation, authentication, audit, storage, communications and payment services keep the platform dependable.
Every tenant · Data isolation / Security / IntegrationsHow the work moves
Each hand-off has a next step.
- 01Choose
A school selects the operating package and capabilities that match its model.
- 02Provision
Tenant data, domain, website and operational services are created as one controlled run.
- 03Configure
Brand, locations, instructors, services, pricing, availability and content shape the school instance.
- 04Operate
Leads, lessons, teaching records, communications and self-service run through connected role-based tools.
- 05Transact
Invoices, card and direct-debit payments, payouts, income and expenses follow the operational record.
- 06Scale
Capabilities, subscriptions, reporting, support and governance evolve without rebuilding the tenant.
What we built
A live vertical-SaaS foundation with separate platform and tenant data layers, role-specific workspaces and an end-to-end route from new customer provisioning to the daily running of a school.
Provisioning is handled as a queued operation. Separate platform and tenant data layers let the team manage schools, domains, packages and capabilities while each school works in its own environment.
