From the match to the next session.

Evening match under floodlights: a player in white controls the ball as an opponent in navy approaches.

Software for football staff

TeamHub AI builds tools to analyse video, prepare training sessions and organise the work of a club’s staff.

Sequence to review61:20 → 61:48
Illustrative example

01How it works

Monday morning, the weekend’s work is in pieces.

The sequence is in a video, the coach’s remark in a chat, the session in two files. Follow what the staff has to do with them before Tuesday.

Skip the example

Illustrative example · fictional data
  1. 01

    Everything is there, in five places.

    A chat, a video clip, a session plan, two versions of one file and a training slot. Nothing yet says what to work on.

    Fictional “Coaching staff” group chat, Monday. Head coach: “Can you send the sequence before the goal?” Analyst: “Done. I’m also keeping the lost ball just before it.” Assistant: “Shall we show it to the group on Tuesday?” Analyst: “Yes, I’m adding it to Tuesday’s preparation.”, with the file tuesday_session_v3.pdf.
    Fictional shared folder “Tuesday preparation”: session v2 (assistant, Sunday), session v3 (analyst, Monday, selected), the clip before the goal, the pressing observation and the group list.
  2. 02

    Review the moment that matters.

    The analyst isolates the lost ball and the move that leads to the opponent’s goal. The coach asks to keep both.

    Vionex · Gamescope

    Match image: a winger in burgundy runs with the ball along the touchline, chased by a defender in yellow.61:20 → 61:48

    Match · second half

    Sequence before the goal

    Match image: a player in navy carries the ball as an opponent in white tracks back.
    • 61:20 Ball lost
    • 61:41 Opponent shot

    Coach’s observation

    After the loss, the midfield drops instead of pressing. Nobody closes the middle.

  3. 03

    Turn the remark into a drill.

    The coach’s observation becomes the objective of a pressing game, drawn on the pitch and approved by the staff.

    Plexo · Mentis

    Session · Tuesday

    ObjectivePress within five seconds of losing the ball.

    Tactic board: after winning the ball, the blue team attacks with two overlapping runs and a through ball, ending in a shot on goal.

    Win it back, then attack fast: overlaps and a through ball

    Full pitch · 4 × 6 min

    Fictional task list “Tuesday preparation”: isolate the sequence before the goal (analyst, done); prepare the pressing game (assistant, in progress); approve Tuesday’s session (head coach, not started); inform the group (assistant, not started).
  4. 04

    Get the group ready for Tuesday.

    The agreed version of the session, the time and the video to watch are kept in one place, then announced to the players.

    Syntra · Playerhub

    Fictional shared folder “Tuesday preparation”: session v2 (assistant, Sunday), session v3 (analyst, Monday, selected), the clip before the goal, the pressing observation and the group list.
    Fictional task list “Tuesday preparation”: isolate the sequence before the goal (analyst, done); prepare the pressing game (assistant, in progress); approve Tuesday’s session (head coach, not started); inform the group (assistant, not started).

This scenario describes the staff’s work. It does not mean the products already exchange this information automatically.

See the full example

A coach watches a training session from the touchline; balls, cones and bottles on the bench.

Monday · 16:00Session review

The staff stays in charge of every decision.

Skip the products section

02The products

Seven tools, three staff jobs.

Scroll through the match file: for each job, what it produces and the products that contribute.

  1. Monday · 08:00The weekend's video

    Review the match

    1. Starting pointThe match video and the data you own.
    2. WorkCut sequences, tag actions, compare with other matches.
    3. ResultAn edited, tagged sequence ready to show the staff.
    VionexInterface capture to come
  2. Monday · 14:00The coach's remark

    Prepare the session

    1. Starting pointA training objective taken from the analysis.
    2. WorkDraw the drill, write the plan, lean on performance reports.
    3. ResultA session sheet the staff reads and approves.
    PlexoInterface capture to come
  3. Tuesday · 09:30The group's week

    Organise staff and players

    1. Starting pointFiles, times and instructions.
    2. WorkRequest documents, keep the calendar, inform each player.
    3. ResultEach player’s schedule and content, up to date.
    SyntraInterface capture to come
  4. Seven products, one family.

    No connection between products is in service yet.

    See all seven products

03Progress

What exists. What is still to prove.

We would rather say where we stand than show figures we do not have.

Each line restates a fact established in our product files.

Today

  • A documented scope for each of the seven products, including its limits.
  • Syntra, the first product in development, on test data only.
  • Architecture and product decisions recorded and dated.

Not yet

  • No product is on sale and no price has been set.
  • We publish no usage figures, partner clubs or fundraising terms.
  • Connections between products are planned; none is in service yet.

Where we stand, product by product

Evening match under floodlights: a player in white carries the ball, an opponent in navy comes in from behind.

Contact

The next session starts here.

Tell us what your staff wants to prepare better: video review, sessions or the week. You talk directly with the team building the products.