For the analyst

Stop assembling the pack.
Start doing the analysis.

The tagging still happens, you just are not the one doing it. MGPT builds the opponent pack and the post-match review on your club's definitions, with the clips, so your time goes into what you make of it and the conversation with the staff.

How well it knows your game

It works on your definitions. So the pack reads like your club wrote it.

MGPT measures the game on your club's definitions, not on someone else's. It remembers the reports you built and the structure your staff reads, so every answer can go from the opponent's whole game to one pattern to one player, and land in your code window if you want it there.

Club DNA · Definitions

Your definitions

What counts as a high regain, a progressive pass or a counter-press at your club. Change a definition and every report follows.

Club memory

Your structure

The reports you built before, the order your staff reads them in, and the code window your XML goes into.

Match data

Every match in your league

So it knows what is normal at your level, and every number comes with where it ranks against the rest of the league.

Video

The video

Every number is linked to the moments it was counted from. You never have to take an answer on trust.

How MGPT works →·Teach it your game model in Club DNA →

One opponent, three levels deep

Example conversation, illustrative numbers
  1. 1The team

    How did our next opponent build up against a mid-block in their last six matches?
  2. They build in a back three with the 6 dropping between the centre-backs in 71% of their build-ups against a mid-block. 64% go down their left, through the left back and the left 8. They lose the ball in their own half in 14% of them, 4th-most in the league.

    132 clips
  3. 2The pattern

    Only the ones where they lost it in their own half.
  4. 19 losses. 13 came when the 6 received facing his own goal, and a press from his blind side won the ball within five seconds in 9 of them.

    19 clips
  5. 3The player

    Profile their 6 under pressure, and export the moments to our code window.
  6. Under pressure he plays backwards in 58% of his passes, and 2 of every 3 of his losses come when he is pressed from his left. The 41 moments are in your XML, one row per moment, in your own codes.

    41 clips
1

Match week · before the game

The opponent pack, done before Monday's meeting.

The same structure your staff already reads, every week, pointed at the next opponent.

Try it on your own next opponent.

Start on the live platform with your professional email. Your first report is one question away.

2

After the game

The review, before you are home.

You review and add instead of starting from an empty template.

3

In your workflow

Into the tools and the meetings you already have.

Nothing about how your staff works has to change.

4

Over the season

The questions nobody had time for.

Once the weekly pack runs itself, the deeper work becomes possible.

Get the most out of it.

1

Write your definitions down once

What counts as a high regain or a progressive pass at your club. Every answer and every report is measured on them from then on.

2

Re-run instead of rebuilding

A report you liked works for the next opponent. Point it at them and change only what differs.

3

Edit by asking

Too long, wrong order, missing a phase? Tell MGPT and it changes the report. Then share it with the staff.

Ask it about your own matches.

Start on the live platform with your professional email, or talk to us about how your staff would use it first.