Statement of Work

Technical Audit, Discovery & Replatforming Strategy

Midas Labs × ClubSpeed February 26, 2026 Version 1.0 ← View Pitch Deck
About

Midas Labs

Midas Labs is a forward-deployed AI engineering entity — a new category of product studio purpose-built for the AI era. We were architected from the ground up around AI-native delivery: AI systems do the heavy lifting, and a small cadre of senior engineers provide the judgment, context, and decision-making that AI alone cannot.

We act as a technical co-founder for venture builders and startups, and as a high-velocity engineering partner for established firms. We step in to accelerate timelines, eliminate technical debt, and resolve critical development logjams — delivering outcomes that traditional teams cannot match on cost, speed, or quality.

What "Forward-Deployed AI Entity" Means in Practice

Traditional consultancies sell headcount. They staff projects with layers of junior engineers supervised by a senior lead, and they bill by the hour. The economics reward slow delivery. Midas inverts this model entirely.

We deploy AI systems as the primary workforce — autonomous agents that analyze codebases, profile databases, generate documentation, review code for vulnerabilities, map schemas, and draft architecture specifications. Our senior engineers direct the AI systems, validate outputs, make architectural judgments, and own the decisions.

  • Codebase Ingestion at Machine Speed — AI systems simultaneously ingest, map, and document ClubSpeed's .NET codebase, Resova's Laravel stack, and the CPO's prototype — weeks of work completed in days
  • Schema Profiling at Scale — AI-driven analysis profiles all 1,500+ Resova tenant databases for schema drift, anomalies, and normalization patterns. No human team can inspect 1,500 databases in 3 weeks.
  • Exhaustive Code Review, Not Sampling — AI systems review the entire codebase — every module, every API endpoint, every stored procedure — identifying vulnerabilities, anti-patterns, dead code, and test coverage gaps
  • Architecture Exploration at Breadth — AI design assistants rapidly prototype multiple architecture options, stress-test each against edge cases, and generate ADRs
  • Documentation as a Byproduct — technical audit reports, migration plans, and architecture specifications generated as natural output of the AI analysis pipeline

The result: ClubSpeed receives the depth and breadth of output that would traditionally require an 8–10 person team over 6–8 weeks — delivered by a three-person senior team in 3 weeks, at a fraction of the cost. This is a structurally different operating model.

Project Context

Understanding the challenge

ClubSpeed is the world's leading venue management software for family entertainment centers, serving go-karting tracks (with hardware timing device integration), trampoline parks, and multi-attraction complexes. Concurrently, ClubSpeed operates Resova, an activity booking platform for smaller venues.

ClubSpeed

Legacy .NET / C#

Built circa 2007 with incremental updates. SQL Server with complex bi-directional on-premise ↔ AWS sync. Significant operational complexity.

Resova

Angular + Laravel

MySQL with 1,500+ per-tenant databases on shared schema. Severe architectural fragmentation blocks platform-wide rollouts.

The Competitive Imperative

$34.4B FEC Market 2025
$93.5B Projected 2035
10.5% CAGR
$50M ROLLER's 2025 Raise

ClubSpeed's strategic objective is to replatform and merge both products into a single, unified system. This transition must be completely seamless — requiring "zero-downtime" automated migration. Speed is not optional — it is the primary competitive differentiator.

Project Scope

Technical Audit & Discovery

Evaluate both architectures end-to-end, normalize data structures, assess the in-progress prototype, and produce a detailed, actionable replatforming strategy.

1

System & Environment Evaluation

Week 1
  • Gain administrative access to AWS environments, GitHub repos, CI/CD pipelines, and on-premise sync infrastructure
  • Audit existing data models (SQL Server for ClubSpeed; MySQL for Resova) — referential integrity, schema differences, data volumes, tenant structures
  • Document all external integrations, third-party dependencies, and hardware interfaces (timing systems, POS, payment gateways)
  • Catalog existing API surfaces — endpoint coverage, authentication, and versioning
  • Review infrastructure topology: hosting costs, scaling behavior, monitoring/alerting, and disaster recovery
[Question] Can you provide a rough estimate of total data volume across both platforms? This significantly impacts migration timeline estimates.
[Question] Are there active compliance requirements (PCI-DSS, GDPR, SOC 2, etc.) that the new platform must satisfy from day one?
2

Data Normalization & Migration Strategy

Week 1–2
  • Analyze Resova's schema and tenant isolation model at the schema level to identify patterns, anomalies, and normalization opportunities
  • Audit legacy ClubSpeed data model — domain entities, relationships, undocumented business logic in stored procedures/triggers
  • Design a unified data model consolidating both platforms into a single multi-tenant database with row-level tenant isolation
  • Architect "single-click" automated migration — data transformation pipelines, validation checkpoints, rollback procedures, phased cutover
  • Identify data quality risks: orphaned records, duplicates, schema drift, and manual reconciliation needs
[Question] Do any Resova tenants have custom schema modifications beyond the shared schema?
[Question] Is there customer overlap between ClubSpeed and Resova? How should conflicting records be reconciled?
3

In-Progress Prototype Review

Week 2
  • Thorough audit of the CPO's prototype — all completed modules, APIs, data models, and front-end components
  • Evaluate code quality, test coverage, API-first design adherence, and production-readiness
  • Identify gaps: missing modules, unhandled edge cases, scalability concerns, security vulnerabilities
  • Deliver clear salvageability assessment: carry forward, rework, or rebuild
[Question] What technology stack was used for the prototype? Is there existing documentation or architecture diagrams?
[Question] How many developers contributed to the prototype, and is the CPO the sole author of technical design decisions?
4

Target Architecture Definition

Week 2–3
  • Backend: API-first design with modern framework (recommendation from audit findings)
  • Database: Centralized multi-tenant with row-level isolation — migrating 1,500+ per-tenant databases is a major re-architecture effort
  • Front-end: Framework recommendation based on audit findings, team capabilities, and product requirements
  • Infrastructure: Cloud-native AWS deployment — containerization, CI/CD automation, environment parity
  • Cross-cutting requirements: multi-language, multi-currency, hardware integration, real-time sync
  • Architecture Decision Records (ADRs) and preliminary security architecture
[Question] What is the expected growth trajectory? (Venues per quarter, geographic expansion.) Affects scalability requirements.
[Question] Preference for microservices vs. modular monolith? Both have trade-offs at this scale.
5

Feature Parity & Customer Experience Mapping

Week 2–3
  • Comprehensive feature parity matrix — every capability across both platforms: carry forward, redesign, deprecate
  • Map all customer-facing touchpoints: booking flows, admin dashboards, reporting, notifications, widgets
  • Identify consolidation opportunities — where the unified platform delivers more than either legacy system
  • Assess white-label and branding requirements (venue-level customization, branded booking pages)
[Question] Are there features in either platform currently unused or slated for deprecation?
[Question] Do venues rely on custom reports or exports that must be replicated exactly?
6

Testing, Observability & Quality Strategy

Week 3
  • Define testing strategy: unit tests, integration tests, E2E regression suites, performance/load benchmarks
  • Establish baseline performance metrics from existing platforms as acceptance criteria
  • Design observability architecture: structured logging, distributed tracing, alerting, dashboarding
  • Recommend canary deployment and feature flagging strategy for gradual tenant migration
[Question] Are there existing monitoring tools (Datadog, CloudWatch, New Relic) that should carry forward, or is this greenfield?
7

Customer Communication & Change Management

Week 3
  • Customer communication strategy — what tenants need to know, when, and how to minimize support volume
  • Migration cohort segmentation — low-risk early adopters validate the process first
  • Internal knowledge transfer plan — ClubSpeed's team owns the new platform post-launch
  • Support escalation framework: roles, SLA expectations, rollback decision criteria
[Question] Does ClubSpeed have an existing customer success/support team for migration communications?
[Question] Are there contractual SLAs (uptime guarantees, data residency) that constrain migration execution?
8

Risk Assessment & Execution Roadmap

Week 3
  • Identify and rank top technical, operational, and business risks
  • Phased execution roadmap with milestones, team structure, and go/no-go decision points
  • Success metrics and acceptance criteria for the build phase
  • Parallel-run strategy: how long legacy systems remain operational during cutover
  • Cost-of-delay analysis — quantifying the ongoing cost of maintaining two legacy platforms
Outputs

Nine comprehensive deliverables

01

Technical Audit Report

Comprehensive assessment of both legacy platforms — architecture diagrams, data model documentation, integration inventory, and infrastructure review.

02

Prototype Assessment

Detailed evaluation of the CPO's build — code quality, salvageability, gaps, and production-readiness with clear keep/rework/replace recommendations.

03

Unified Data Model & Migration Plan

Normalized target data model and step-by-step "single-click" migration strategy with transformation logic, validation gates, rollback procedures, and phased cutover.

04

Feature Parity Matrix

Complete mapping of all capabilities across both platforms — categorized into carry-forward, redesign, consolidate, and deprecate.

05

Target Architecture Specification

Technology stack recommendations, ADRs, infrastructure topology, security model, observability design, and cross-cutting concern strategies.

06

Testing & Quality Strategy

Testing standards, performance benchmarks, observability architecture, and canary deployment / feature-flag rollout plan.

07

Change Management Plan

Migration cohort segmentation, communication templates, support escalation framework, knowledge transfer plan, and training recommendations.

08

Risk Register & Execution Roadmap

Prioritized risk assessment, phased execution plan, team structure, milestone definitions, cost-of-delay analysis, and estimated build timeline.

09

Build Phase SOW

Detailed breakdown of resources, timeline, and cost for the fully unified platform — ready for immediate approval and kickoff.

Timeline & Resources

Three weeks, end to end

Presuming that necessary system access, repository access, and stakeholder availability are provided promptly at kickoff.

Week Focus Key Activities
Week 1 System Evaluation & Data Deep-Dive Environment access, codebase review, data model audit, integration mapping, AI-accelerated schema profiling
Week 2 Prototype Review & Migration Design CPO build assessment (AI-assisted), unified data model, migration strategy, feature parity matrix
Week 3 Architecture, Quality & Roadmap Target architecture, testing/observability strategy, customer comms plan, risk assessment, Build SOW

Team Composition

Three senior humans backed by AI systems as the primary analytical and production workforce. No junior roles — AI replaces the labor layer entirely. Every human exists to make decisions, not to write boilerplate.

  • Technical Product Manager (Lead) — single point of contact. Owns execution, stakeholder communication, deliverable production, and the Build SOW. Directs AI systems for documentation, competitive analysis, and roadmap modeling. Full-time.
  • Senior Solutions Architect — owns codebase analysis, data model design, target architecture, and migration strategy across both legacy platforms and the prototype. Directs AI systems for code review, schema profiling, and architecture exploration. Full-time.
  • Senior Cloud & Infrastructure Engineer — infrastructure audit, deployment topology, CI/CD assessment, observability architecture, and cost modeling. Directs AI systems for infrastructure scanning and config analysis. Part-time (Weeks 1 & 3).
  • AI Systems (Autonomous) — codebase ingestion and mapping, schema profiling across 1,500+ databases, exhaustive code review, vulnerability scanning, documentation drafting, architecture option generation. Operates continuously under engineer direction.
[Assumption] We assume 2–3 hours per week of stakeholder availability from the ClubSpeed side (CPO + technical contact) for Q&A sessions and access provisioning. Delays in access may extend the timeline.
Investment

Budget & invoicing

This engagement is billed as a fixed-cost project. The fee covers all human labor, AI system usage, internal review cycles, and up to two rounds of revisions on all 9 deliverables. For context: a traditional consultancy would staff this scope with 5–8 people over 6–8 weeks at a cost of $75,000–$120,000+. Midas delivers the same scope in 3 weeks at less than half the cost.

$34,500 CAD — Fixed Cost (+ GST/HST)
Milestone Amount Trigger
Project Kickoff $11,500 CAD (33%) Upon signed SOW and confirmed environment access
Mid-Engagement $11,500 CAD (33%) Delivery of draft Technical Audit, Prototype Assessment, and Feature Parity Matrix
Final Delivery $11,500 CAD (34%) Delivery and acceptance of all remaining deliverables

All invoices in Canadian Dollars (CAD). GST/HST added as applicable. Net 15 days.

Build Phase Rate Card

The following rates apply to the anticipated Build Phase. Every role is a senior decision-maker backed by AI systems — no junior tiers. Rates reflect the combined output of the human engineer plus the AI systems they direct.

Role Rate (CAD) What You're Getting
Technical Product Manager $200/hr Strategic direction, stakeholder management, AI-driven roadmap and documentation output
Senior Solutions Architect $175/hr Architecture decisions, data modeling, AI-driven codebase analysis and code review at scale
Senior Cloud & Infrastructure Engineer $140/hr Infrastructure design, DevOps strategy, AI-driven config scanning and cost modeling
Senior Software Engineer $120/hr Production engineering, feature development, AI-driven code generation and testing

How to compare: A traditional consultancy would staff with 1 senior architect ($175–$250/hr), 2–3 mid-level devs ($100–$150/hr each), and 1–2 juniors ($60–$90/hr each) — totaling $500–$800+/hr in blended team cost. Midas delivers equivalent output through a single senior engineer directing AI systems.

Legal

Terms & Conditions

  • Confidentiality — All information shared during this engagement will be treated as strictly confidential. No disclosure to third parties without written consent.
  • Intellectual Property — All deliverables become the property of ClubSpeed upon full payment.
  • Change Requests — Material scope changes will be documented via written change order and may impact timeline and cost.
  • Cancellation — Either party may terminate with 5 business days' written notice. ClubSpeed will be invoiced for work completed to date.
Appendix

Open Questions for ClubSpeed

The following should be addressed prior to or during the kickoff meeting:

Systems & Data

  • What is the approximate total data volume across both platforms? (GB/TB)
  • Do any Resova tenants have custom schema modifications beyond the shared schema?
  • Is there overlap between ClubSpeed and Resova customer bases?
  • How critical is the current on-premise/cloud bi-directional sync? Plans to move fully cloud-hosted?
  • What are peak concurrent user counts and transaction volumes?

Prototype & Architecture

  • What technology stack was used for the CPO's prototype? Existing documentation?
  • How many developers contributed to the prototype?
  • Preference for microservices vs. modular monolith?

Product & Features

  • Are there features currently unused or slated for deprecation?
  • Do venues rely on custom reports/exports that must be replicated exactly?
  • What level of venue-level branding customization exists today?

Compliance, Contracts & Operations

  • Active compliance requirements (PCI-DSS, GDPR, SOC 2)?
  • Third-party vendor contracts or licensing constraints?
  • Contractual SLAs with current customers?
  • Existing monitoring or alerting tools?

People & Process

  • Expected venue onboarding rate and geographic expansion (12–24 months)?
  • Customer success/support team available for migration communications?
  • CPO and technical contact availability (2–3 hrs/week)?
  • Current size and composition of internal engineering team?

Competitive & Strategic

  • How does ClubSpeed currently win competitive deals against ROLLER and CenterEdge?
  • Any deals or customers lost to competitors in the past 12 months due to technology limitations?
Appendix

Competitive Landscape Analysis

The global FEC market is projected to grow from $34.4B (2025) to $93.5B (2035) at a 10.5% CAGR. Software vendors are rapidly consolidating around cloud-native, all-in-one platforms with AI-powered features, cashless/RFID integration, and open APIs.

ClubSpeed's Position

Widely recognized as the industry standard for go-kart and racing venues with a 4.9/5 rating on Capterra. Strengths: exceptional support, comprehensive all-in-one management, strong CRM/marketing. Vulnerabilities (from user reviews): steep learning curve, occasional bugs, integration lag — symptoms of the legacy architecture this effort aims to eliminate.

ROLLER

Top Threat

3,000+ venues, 30+ countries. $50M raise (Insight Partners + J.P. Morgan). $4B in annual transactions. 100M+ guest visits/year. Cloud-native with open API. Launched AI-powered ROLLER iQ. Acquired BookNow Software (Sep 2025). Claims 30% increase in average online revenue for switching venues.

CenterEdge

Medium

20+ years in FEC. Strong North American base. All-inclusive pricing, no hidden fees. 15-minute POS training claim. US-based 24/7 support. Deep operator relationships.

Parafait (Semnox)

Medium

RFID-integrated hardware: cashless payments, game card management, access control. Strong in arcade/game segment. Modern, purpose-built stack.

Connect&GO

Medium

RFID cashless payments, access control, loyalty. Open platform enabling existing POS/ticketing integrations. Growing in waterparks and large attractions.

Emerging players: Aluvii (cloud-native all-in-one), Party Center Software (event-driven FECs), LEAP360 (digital-first marketing), Smeetz (AI dynamic pricing). Several are cloud-native from inception.

Strategic Implications

Cloud-Native = Table Stakes

Every competitor is cloud-native. The on-prem/cloud sync is a competitive liability.

Open API is Non-Negotiable

ROLLER's API ecosystem drives switching cost and retention. Must be API-first with dev portal.

AI = New Battleground

ROLLER iQ launched late 2025. Architect for AI from day one, not as a bolt-on.

Hardware Moat

Timing device integration is a genuine, defensible differentiator. Must preserve and extend.

Multi-Venue HQ

Multi-location chains need centralized reporting, config, and pricing. Key buying criterion.

Speed = Survival

Every month of delay extends ROLLER's window to capture market share with $50M war chest.