Case file07
My Tennis App
A club counter lived in sticky notes and a notebook. It now lives in an application: stringing ticket, stock, follow-up — without replacing the club’s management software.
- BUSINESS APPLICATION
- FRANCE / MONACO / SWITZERLAND
- PUBLIC PROJECT
The project
A tennis club runs two flows that general club-management software handles poorly: the stringing workshop and the pro shop. A racket drop-off is written on a sticky note, a player’s preferred tension lives in someone’s head, stock in someone else’s, and any follow-up — if there is one — is sent by hand.
My Tennis App is an AIGYROS GROUP product, live at mytennisapp.com. It does not replace the club’s management tool: it sits beside it. The member list is imported from a file; the application then takes over the counter and workshop gesture.
Club and player data are hosted in France. Payments stay on the club’s terminal: no card data transits through the tool.
The starting point
What the diagnosis revealed.
Before any technical proposal, we write down the real state — including what unsettles. This description, validated by the teams, is what makes the rest verifiable.
- 01
Racket drop-off on paper
An unreadable sticky note, sometimes lost, with no shared state between reception and the workshop.
- 02
The player who calls back
Without a notification, the club is asked whether the racket is ready.
- 03
Named memory that cannot be found
Brand, string, tension: the detail lives with whoever took the last drop-off.
- 04
Stock in someone’s head
The pro shop has no shared state. Counter sales are not tied to the player.
- 05
An oral handover
The stringer who leaves earlier leaves a note. Reception does not always know what to answer.
- 06
A single access for everyone
Shared notebook or password: reception, workshop and management are not distinguished.
Constraints
What could not be compromised.
- 01
Fit the counter gesture
Drop-off, workshop, pick-up: the tool had to follow the real movement, not demand extra entry.
- 02
Do not replace the club’s software
Members, courts and licences stay elsewhere. A CSV or spreadsheet import is enough to start.
- 03
Host in France
Player records, stringing history and sales stay on servers in France.
- 04
No payment inside the tool
The club’s terminal takes payment. My Tennis App stores no card data.
- 05
Rights by role
Reception, workshop, management: each has an account. No shared secret at the counter.
- 06
A possible exit
Club data must be exportable. The product does not hold the member file hostage.
The AIGYROS answer
What we built.
The model is organised around the stringing ticket: dropped off, in progress, ready, collected. The player is notified when the racket is ready. The player record keeps rackets, tensions, purchases and history — the memory the notebook never held.
The pro shop is a catalogue with stock, margins and sales tied to the record. Internal messaging separates the workshop channel from the counter, with clickable stringing references.
Follow-ups leave according to a rule set by the club — email, SMS or WhatsApp, in the club’s name, editable copy. They do not replace the commercial gesture: they make it executable while the team is on court.
Operation is ours: hosting in France, backups, accounts and roles, export. The club remains master of its members and of its payments.
Conduct
Four stages, held in this order.
Stated durations are orders of conduct magnitude, never commitments: each engagement is recalibrated on its own ground.
- 01Immersion at the counter
Observe
Watching drop-off, workshop and sale. What is lost between two posts becomes the functional scope.
- The real drop-off and pick-up gesture
- Information passing between reception and workshop
- Pro-shop sales and stock tracking
- Written restatement of the need
- 02Design phase
Model
Ticket, player record, catalogue, roles. Fewer screens than uses, each justified by a club gesture.
- Stringing-ticket lifecycle
- Player record and history
- Catalogue, stock, sales tied to the player
- Reception, workshop and management profiles
- 03Development phase
Build
Application, follow-ups, member import, hosting in France, acceptance on the real gesture.
- Counter and workshop screens
- Email, SMS and WhatsApp follow-ups
- CSV / spreadsheet import
- Hosting, backup, encrypted traffic
- 04Operation phase
Go live
Opening club spaces, short training, support, export and subscription plans.
- Going live with a club space
- Training the team on the daily gesture
- Support and upkeep
- Data export on request
What changes
Before, after — no showcase figures.
We do not publish improvement percentages: they cannot be verified from outside. What can be described, on the other hand, is the daily gesture that changes.
- Initial situationAfter the engagement
Initial situation: Drop-off sticky note, sometimes lost
After the engagement: Tracked ticket: dropped off, in progress, ready, collected
Initial situation: The player calls to know if it is ready
After the engagement: Notification when the racket is ready
Initial situation: Tension and history in someone’s head
After the engagement: Player record: rackets, strings, purchases
Initial situation: Stock and sales in pencil
After the engagement: Catalogue, stock, sale tied to the player
Initial situation: A scribbled note between two posts
After the engagement: Team messaging, traced instructions
Initial situation: One shared access for the whole club
After the engagement: Distinct accounts by function
Deliverables
What stays in your hands.
An engagement is also judged by what it leaves behind. Every deliverable is written to be read without us.
- 01
Live application
mytennisapp.com — club space, six screens from counter to workshop.
- 02
Stringing-ticket cycle
States, ready notification, history on the player record.
- 03
Pro shop
Catalogue, stock, margins, sales tied to the player.
- 04
Follow-ups
Configurable rules, email, SMS or WhatsApp, in the club’s name.
- 05
Rights and import
Accounts by function, member import from a file.
- 06
Hosting and backup
Servers in France, encrypted traffic, daily backup.
Excluded scope
What the engagement did not include.
A blurry scope costs more than an incomplete one. So we write it down in black and white, from the proposal stage: what is handled, and what is not.
- Replacing the club’s management software (members, courts, licences).
- Taking payment: the club’s terminal remains the only payment channel.
- Bespoke development, multi-club and white-label, handled separately.
- Supplying the member list: the club imports its file.
The counter gesture,held all the way through.
Case file
My Tennis App
Case 07 — Business application
Area of operation: France / Monaco / Switzerland
Other case files
Prendre contact
Does your situation resemble one of these?
Tell us about your environment, your constraints and what cannot be compromised. We answer with analysis, not a catalogue.