Drivers, race teams, model-launch and corporate-event prospects, prospective villa owners and press each have different qualification, paperwork and routing needs. Audience-routed entry points and pipelines (Charter, Member Portal) split intake into five distinct paths the office can run from one tool.
Sessions across multiple track configurations generate booking, marshalling, payment and incident-reporting workflows that need a single shared system to scale. The Member Portal and Race Control modules consolidate those workflows; the Phase 0 audit catalogues which existing tools they replace and which they integrate with.
A booking confirmation that reads like a Ryanair email, or a lap report delivered as a generic PDF attachment, sits awkwardly next to the physical experience Sol delivers on the asphalt. The platform sets explicit performance, accessibility and visual-quality budgets for every member-facing surface (booking confirmation, lap report, owner app, partner microsite) and tracks them per release.
A circuit, a clubhouse and a villa development can each be built by a competitor with capital. A five-tier driving programme validated against Sol's own lap-data archive (accumulated session by session from Phase II forward), plus the instructor-fleet model the Academy proposes and a member-bound owner application, are harder to replicate. The platform is where the defensible part of the business sits.
Each pillar solves a real operational problem on its own. Together, they share a single member record: a booking, a session, a lease, a Brand Event and a Charter enquiry all read from and write to the same data layer.
A public website with five audience-routed entry points (drivers, teams, brands, owners and press), each with its own qualification path and call to action. Built mobile-first to load on a paddock 4G connection, and editable by Sol's team without developer involvement.
A private, branded application that holds the member's entire relationship with the resort: session booking across every track configuration, guest invitations, payments, membership management and lap-report download.
A five-tier driving programme, from first time on track to advanced track driver, with theory modules, instructor-led on-track sessions, and tier validation against captured lap data. Existing race-licence holders enter at upper tiers with credit for prior experience.
Per-session timing and telemetry captured, stored under Sol's account, and exposed to the member through the Portal lap report and to the public through opt-in leaderboards. Lap data exports to the file formats race engineers use today.
A white-label event surface for the activities Sol's website already advertises: model launches and demonstrations, exclusive corporate events and brand presentations. The Studio packages microsite, registration, waivers, asset rights and incident response into a contract a partner's procurement and legal teams can approve.
Three connected products. A villa-selection surface (interactive villa picker, 3D tour, deposit reservation). Trackside garages for members without a villa (secure car storage, app-managed access, car prepared before arrival). The Owner App once a member has bought (concierge, garage scheduling, owner-tier track booking, maintenance log).
A shared operational view across marshal posts, race control and management, running across the full mix of activities Sol already hosts: member sessions, club racing events, brand-event days and race-team test programmes. Each flag, off-track, contact and recovery is logged with timestamp, post number, session ID and operator. The audit trail is exportable and tied back to the lap data from the same session.
The founding cohort is recorded by entry date, visible to the office, never to each other unless a member opts in. Subsequent enquiries split by audience (driver, team, brand, owner, press) with capacity-aware wait-list logic when any category is full.
Each module reads and writes to a shared data layer using open formats. A booking made in the Portal becomes a session in Telemetry, a milestone in the Academy and a load on Race Control without a staff member copying a reference between tools. Any single module can be replaced without breaking the rest.
Writes session data to Telemetry and milestone records to the Academy. Race Control draws current session state from the same booking record.
Consumes lap data from Telemetry for tier validation, and session records from the Portal for milestone tracking.
Powers lap reports in the Portal, milestones in the Academy, and paddock screens during member sessions and brand events.
Reuses Portal infrastructure for guest registration and waivers; draws on the Sol instructor roster when partners book hot-lap experiences; exposes telemetry in NDA mode for embargoed launches.
Connects to Portal booking with owner privileges, garage scheduling, and concierge through Operations.
Receives session data from the Portal in Phase II. Feeds incident timestamps back into Telemetry once that pillar lands in Phase III. Operates standalone in the meantime.
Off-the-shelf booking engines, CRM platforms and event tools each handle a slice of the problem. None handle a circuit, a Charter cohort and a villa community sharing one member record.
Circuits that started with three different tools for booking, timing and CRM spend years trying to get them to talk to each other before they can build a single view of a member. Sol has not fragmented yet. Phase 0 designs the architecture before that happens.
Drivers, teams, brands, owners and press route to separate pipelines with audience-specific qualification, paperwork and follow-up. Generic CRMs collapse them into one funnel and lose the routing distinction.
Performance, accessibility and visual quality of every member-facing surface (booking confirmation, lap report, partner microsite) measured per release against Sol's existing surfaces. Standards declared in Phase 0 and tracked in CI, not declared in the meeting and forgotten after go-live.
From Phase II forward, Sol owns the per-member lap-data archive and the Academy tier records. The Academy's instructor-fleet design (once Phase 0 sets the procurement and partnership model) adds a comparable telemetry library. A competitor can build a circuit; the archive that accumulates session by session inside Sol cannot be replicated by buying capacity.
Membership, event days, brand activations, villa sales, trackside garages and Academy tiers all settle to the same member record. Cross-sell becomes a query against the record rather than a workflow stitched across tools.
Each of the five phases delivers production-ready modules. Sol gets value at the end of Phase I and at the end of every phase after, without a release window that requires a calendar freeze.
Each phase delivers production-ready modules. Phase I lands a public site and Charter pipeline; each subsequent phase adds modules without disrupting what shipped before, and without a release window that requires a calendar freeze.
Public website with audience-routed entry points, plus a Charter pipeline that captures every enquiry by audience.
Member Portal with bookings, payments and digital waivers, plus Race Control with marshal incident logging. The email + spreadsheet workflow retires the day Phase II ships.
Near-real-time timing integrated with the transponder system Sol's audit selects, plus a neutral telemetry layer that ingests the timing and data hardware members already use. The Academy validates tier progression against the captured lap data.
Model launches, corporate events, prototype-testing programmes, villa reservations and trackside-garage enquiries move into the platform. White-label microsites with NDA mode, GDPR processor agreements, and asset rights signed work-for-hire on the partner's paper.
Once members and brands are running on the platform, the villa community moves into software: concierge requests, garage scheduling and opt-in owner directory, all bound by the owners' covenant drafted in Phase IV and registered against each villa at sale.
Beyond the modules themselves: how decisions get made, what ships before go-live, and where bespoke code is reserved for what defines Sol versus what gets licensed because it already exists.
Proven, audited vendors at the boring layers: timing, payments, waivers, content, email. The operation tells the platform what it needs; the audit names the choices. Bespoke code is reserved for what defines Sol, never for what already exists and can be licensed for less.
Marshal-device pool sized to the roster with a spare-replacement SLA. Device class set in the Phase 0 audit. Marshal training delivered in Portuguese before Phase II ships. Every digital flow paired with a documented analog fallback (radio and paper) for the first 90 days post-go-live. Dual-run with current tools across cutover, never less than 30 days side-by-side. Named platform engineer on-call within ten minutes through every event-day window (pit lane open through two hours after the last session), with backup escalation tier for concurrent incidents. None of it discovered after.
Phase 0 is an audit of every tool currently running Sol, scoped together with Sol's leadership before the Phase I scope is fixed, including (but not limited to) gate, calendar, accounting, marshalling and timing categories. Vendor choices follow Sol's audit, not a deck. What stays, what migrates, what retires: decided with evidence, not assumption.
The full scope above (seven modules, five phases, three operating principles) is what this proposal covers.
