FR/ENRequest a quote
Industry · Sports & Events

Custom business platforms and toolsfor sports and events.

Staffing, field coordination, matchmaking, back-office: tools built for the day everything happens at once, yet remain useful between seasons.

Discuss your project View our work
SiteX
Leedeel
01 — Industry challenges

Everything hinges on the big day.

An industry defined by peaks, staffing to coordinate down to the hour, makeshift tools hitting their limits, and participant data that demands proper handling.

An industry defined by peaks

An event mobilizes in a few days what a regular business spreads over months. Tools must handle peak demand without degrading and remain useful between seasons.

Staffing to coordinate in real time

Recruiting, assigning, replacing, clocking in: coordinating staff happens by the hour, often from the field and via mobile.

Makeshift tools hitting their limits

Spreadsheets, no-code databases and messaging apps work fine at low volumes. Beyond a certain threshold, data duplicates, gets lost, and no one retains the full picture.

Personal data to handle seriously

Staff, temps, contractors: contact details, availability, administrative documents. This is personal data, with all the obligations that entails.

02 — What we build

Four projects, depending on what’s holding you back.

A matching platform to launch, a back-office to build, a no-code tool to leave behind, or repetitive tasks overwhelming your teams during peak season.

Matching platforms & marketplaces

Two-sided matching, onboarding for both parties, operator back-office, moderation. A platform that handles peak event loads.

MarketplaceTwo-sidedBack-office
Marketplace

Operational tools & back-office

Scheduling, assignments, time tracking, invoicing: the tool that replaces the shared spreadsheet and gives operations teams a unified view.

SchedulingField operationsBack-office
Business application

Exiting no-code & modernisation

Airtable, Bubble or in-house databases at their limit: gradual migration to a maintainable application, coexisting with the existing system until the switch.

MigrationNo downtime
Application modernisation

Operational workflow automation

Follow-ups with staff, schedule syncing, payroll exports, field notifications: the repetitive tasks that overwhelm teams during peak periods.

n8nNotificationsExports
Automations
03 — Proof

Tools that have weathered the season.

Two references in this field.

SiteXEvent staffing · Business tool
Airtable → Next.jsSupabaseProgressive migration

From Airtable to a bespoke application, with zero business disruption.

Gradual migration from an Airtable business tool to a Next.js and Supabase application, with the old system running in parallel until full switch-over. Twenty-four months of support, no operational downtime during the transition.

Read the SiteX case study
LeedeelEvents · Matchmaking platform

Marketplace connecting brands with athletes / clubs / sports federations

-60% time spent identifying relevant sports partners thanks to the search engine and matching system. -50% time spent on sponsorship campaign operational management via a centralised workspace. 100% of campaigns tracked in a single dashboard, with visibility on progress, deliverables, and performance.

Marketplace
Read the case study
04 — Our approach

Three principles that hold on the big day.

What we establish during scoping, and why the tools hold under peak load and survive the season.

Designed for peak, not for average

We size for the event peak, not daily activity: it’s the day when everything happens at once that determines if the tool holds.

Gradual migration

The old and the new coexist for as long as needed. We switch scope by scope, each validated in real conditions.

Your data and tool belong to you

Code delivered, data exportable, hosting transferable, documentation maintained. Interveners’ data stays in France, GDPR by design.

05 — Stack & method

A lean stack that handles peak load.

Proven, hirable technologies, a database sized for peak demand, and data hosted in France.

Front

Next.js
React
TypeScript

Back / Data

Supabase
PostgreSQL
RLS

Automation

n8n
Webhooks
Exports

Hosting

OVH
Scaleway
GDPR

Quality

CI/CD
Tests
Code review
06 — FAQ

Frequently asked questions

Your questions, our answers.

By sizing for peak load from the start, not average load. In practice: queries and indexes designed for day-of volumes, caching where it’s safe, and load testing on the actual event scenario—not theoretical traffic. It’s an architecture issue, addressed during scoping—not after the first incident.

Yes, that’s exactly what we did for SiteX: a gradual migration to a Next.js and Supabase application, with the old system running in parallel until full switch-over, and zero business interruption. We move one scope at a time, validate it in real conditions, then proceed to the next.

Yes: coordination tasks—clocking in, assignments, last-minute replacements—are done via phone, often in poor network conditions. Field interfaces are built for this, and degraded mode is part of the spec, not a patch.

As personal data in full: minimising what’s collected, defined retention periods, right to erasure, role-based access at the database level. Hosted in France (OVH, Scaleway), GDPR by design.

Yes: two-sided marketplaces, onboarding for both sides, operator back-office, moderation, and dispute management. It’s a common component in events, where the challenge is as much operational as technical.
Let’s discuss

A staffing tool, a matching platform, or a back-office to build—or to migrate from no-code? Let’s discuss volume, peak activity, and seamless transition.

Contact details
20 Rue des Taillandiers
75011 Paris
Response within 24 business hours.