Skip to main content
GullySystem
Education

Lead Management for Football academies

Give each enquiry an owner, status and next action.

CRM

Does this function belong in your operation?

Use when enquiries arrive through several channels or follow-ups are missed.

A prospective buyer makes contact.

Parents who enquire after a trial day or a school visit are held as leads. Coaches record the child’s age group and trial result. The registrar follows up before the next intake.

Bring the records the workflow depends on.

  • Lead sources
  • Assignment rules
  • Follow-up stages

Outputs to check

  • Assigned enquiry register
  • Due follow-up list
  • Qualification and closure record

Follow the lead management workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Capture the enquiry

    Record the prospect's requirement and source.

  2. 2. Check duplicates

    Review matching contacts while preserving distinct needs.

  3. 3. Assign ownership

    Set the responsible person and next action.

  4. 4. Qualify the requirement

    Record discussions and the reason to progress, pause or close.

  5. 5. Handover to sales

    Create the relevant opportunity or order reference without losing enquiry history.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Sales executive

Opens today’s call list, rings, writes one line and sets the next date.

Sales head or branch manager

Reviews unassigned or overdue leads and transfers actions when a salesperson is unavailable.

Owner

Reviews enquiry sources and the orders linked to them, using the recorded outcome of each lead.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Repeated enquiry

Review matching contact details and preserve distinct requirements before merging.

Owner unavailable

Reassign the next action with the interaction history intact.

Prospect requests no contact

Record the restriction and stop the relevant follow-up activity under your communication policy.

Can this work independently?

Lead tracking can start with manual entries or file imports. Website forms and messaging channels are optional supported connections. Qualified leads hand over to opportunities or orders using a retained reference; qualification itself does not create revenue or a confirmed customer commitment.

Systems and records it connects with

  • Opportunity management: Deal requirements, values, stages and decision history.
  • Quote and proposal management: Commercial proposal versions and acceptance details.
  • Trade portals and business directories: Permitted enquiry imports retaining their original source references.
  • WhatsApp: Permitted message content and channel delivery responses.

Configure, test and introduce the workflow.

  • Name every channel enquiries use. A note comes back with the sources and the fields each can fill.
  • Name your hot, warm and later stages and your reasons for dropping. They appear on a screen. Try them. Share the sheets executives keep. The trial import flags duplicates for the sales head to resolve.
  • Executives practise logging a call and setting a next date. Each gets a note for the phone. The review meeting opens with the untouched list. After a cycle, source figures are read together.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Active leads have owners.
  • Duplicates can be reviewed together.
  • Closed leads retain reasons.
Football academies

How the business operates.

A football academy is a small organisation with registers, fees, kit and fixtures all moving at once. Nothing stands still. Players sit in age-group squads, coaches cover several squads, and the ground is shared between training and fixtures. Parents pay in instalments and expect a message the moment a session moves to another pitch or is cancelled because of rain. Messages matter.

Trials and registration

Log each trial request, the date played and the coach’s verdict. Convert an accepted child into a registered player with a consent form, medical note, emergency contacts and a squad.

Squads and age bands

Group players by birth year and ability. Move a child up a band at season change. Coaches open only their own squads, while the head of youth reads every group and can see which age bands are short of goalkeepers or a second coach.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Trial requests and verdicts. Log each trial request with birth year and position, schedule the session, and keep the verdict and notes so an offer is made to the right child.
  • Player registration and files. Hold the consent form, medical note, guardian contacts, photograph and birth date for each player, with expiry dates for forms that need renewing each season.
  • Squads and age bands. Place players in squads by birth year and ability, allow a child to train up, and keep the squad history after the season changes.
  • Training registers. Mark attendance on a phone at the touchline, note injuries and absences, and list players who have missed several sessions in a row.

Operational bottlenecks to check

Squad lists live in several notebooks

Each coach keeps a list of names for the under-ten, under-twelve and under-fourteen groups. The office keeps another. They drift apart. When a player moves up an age band, one list is updated and the others stay as they were. Match sheets then carry the wrong names. Coaches notice on the touchline.

Attendance and fee status are never read together

A player may miss six sessions in a row and still be marked as paid up. Another may attend every drill while an instalment sits overdue. The head coach and the accounts clerk work from separate sheets, so neither sees the whole child. Families drift.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Trial

    A trial request is logged. It carries the child’s birth year, position and the date offered. After the session, a verdict and a note are recorded against the child.

  2. 2. Registration

    An accepted child becomes a player. The consent form, medical note, guardian contacts, photograph and chosen fee plan are attached, and a squad is assigned by birth year.

  3. 3. Training

    Sessions are planned against pitch slots. Registers follow. Coaches mark them on a phone, noting injuries or absences, so the head of youth sees who is missing from which group.

  4. 4. Match day

    The fixture is entered with opponent, venue and kick-off. The squad is named, the starting eleven and substitutes are recorded, and parents get the time and meeting point.

  5. 5. Assessment

    Every term, the head coach scores technical, tactical and physical marks and adds a written note. The family receives a short report for their child.

  6. 6. Fees and season close

    Instalments fall due by plan, receipts are posted and arrears are listed. At season end, kit is counted back in and players are moved up an age band.

Industry reports to connect with

  • Players by squad and birth year, with consent forms pending
  • Training attendance by squad and by player
  • Minutes played and appearances by player across the season
  • Assessment marks by player and term

Questions before implementation.

When should football academies consider lead management?

Use when enquiries arrive through several channels or follow-ups are missed. A prospective buyer makes contact.

What should we bring to the requirements discussion?

Bring anonymised examples of Lead sources; Assignment rules; Follow-up stages. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Give each enquiry an owner, status and next action. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Lead tracking organises enquiries already received. Demand generation and the buyer’s sales decision remain separate activities.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Active leads have owners. Use this check when reviewing the first working version.

Talk to us

Discuss lead management for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements