Built at the intersection of two lives.

Sean Marshall has been two things for twenty years. A software engineer shipping real systems at companies that couldn't afford for those systems to leak, break, or guess. And a youth sports coach across the South — on fields, courts, and diamonds in Mississippi, Louisiana, and Texas — coaching basketball, soccer, football, baseball, tennis, whatever his kids picked up or his community needed a coach for.

Those two tracks ran in parallel for most of his career, but they kept intersecting in ways the sports-software market was not solving. Every platform he used as a coach either did not respect the data or did not respect the users. As an engineer who had shipped Electronic Medical Records systems — where HIPAA is not a suggestion — he knew what actually serious data handling looked like. The gap between how sports platforms treat family data and how platforms trusted with medical records treat medical data was not going to close itself.

So he built Recursive. A platform designed from the first commit around the kind of data protection he was used to seeing in regulated software, with a product model that treats families and members as customers — never as advertising inventory.

In computer science, recursion is a function that calls itself. Each step builds on the one before. The whole structure rests, ultimately, on a stable foundation.

That's also how sports clubs actually work. Every practice feeds a game. Every game feeds the season. Every season feeds your club's history. Today's captains were yesterday's rookies and will be tomorrow's alumni. The structure is self-referential by design — and it only holds if the foundation is trustworthy.

Recursive is built that way on purpose. An immutable event log where every game rests on the data below it. A permission system where every role inherits from the one above it, with the most specific rule winning. A schedule that carries practices, matches, and tournaments forward without forgetting what came before. And a data foundation — COPPA-aware, audit-logged, free of third-party trackers — sturdy enough for the whole club to stand on.

Recursive is also the name of our parent company, Recursive Creations. We build software that creates the conditions for more creation. For a sports club — at any age, at any level — that means a platform that doesn't just record this season; it makes the next one easier.

Sports grow by repetition and return. So does Recursive.

Most sports software is built by people who understand one side of this problem. Engineers who haven't coached underestimate the operational complexity of running a club. Coaches who aren't engineers can't ship software that meets a compliance bar. The intersection is a thin place — which is why the current market of sports platforms either feels clinical or feels insecure.

Recursive is the platform built by someone who has worked on both sides for two decades. It reads like a product designed by an engineer who has actually used the software at 7 a.m. on a Saturday, because it is.

The security posture — COPPA-aware consent workflows, granular RBAC + ABAC permissions, immutable event logs, external UUIDs, audit logging, SOC 2 in progress — comes directly from a career shipping EMR systems and working in cybersecurity. None of it is retrofit. It's the default.

The product shape — published pricing, no ad tracking, families ride free, teams ride free, the club is the customer — comes from watching twenty years of sports platforms monetize the wrong things.

This is the platform Sean wanted to exist when he was standing on a field trying to find his team's schedule on a platform he didn't trust. So he built it.