Skip to main content
GullySystem
Education

Lead Management for Cricket 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 enquire after seeing a trial day or a social post. Each child’s age and playing level are noted. A trial slot is booked and the outcome logged.

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.
Cricket academies

How the business operates.

A cricket academy teaches players of different ages in batches that meet at fixed hours. A morning group of juniors, an evening group of seniors and a weekend group for beginners may all share the same nets. Lanes are few. A coach can only be in one place, and a morning rain-off sends three groups scrambling for the same indoor hall.

Trials, enrolment and batches

Log each trial with the coach’s notes, enrol the player into an age group and batch, and move the player up when a coach recommends it.

Net and ground booking

Book net lanes, the turf wicket and the indoor hall by hour. Clashes between batches show before the session, and rain-offs move whole groups.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Enquiries and trials. Record each enquiry, fix the trial slot and keep the coach’s notes on batting, bowling and fielding with the player’s file.
  • Players, parents and batches. Hold the player, the parent contacts, the age group and the batch, with a history of every move from one batch to the next.
  • Net and ground booking. Book lanes, the turf wicket and the indoor hall by hour for each batch, and see clashes and rain-offs on a single day view.
  • Session attendance. Mark attendance by batch from a phone at the nets, with notes on injuries and late arrivals kept against the player.

Operational bottlenecks to check

Batches overbook the nets

Two coaches plan a session on the same lane at the same hour. One group waits.

Fees lapse without a prompt

A monthly fee falls due on a date that differs for every joiner, so reminders depend on the front desk remembering whose month ended. Some are missed. Parents then pay two months at once, or stop.

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. Enquiry and trial

    A parent’s enquiry becomes a record with the player’s age and level sought. A trial slot is fixed, and the coach’s notes from the net session are added afterwards.

  2. 2. Enrolment

    The player is placed in an age group and batch. The fee plan, kit list and parent contact are set, and the first fee is received.

  3. 3. Sessions

    Net lanes and the turf wicket are booked by batch and hour. The coach marks attendance, and injuries or drills are noted on the player.

  4. 4. Progress

    Each term the coach rates skills and fitness on the card. The head coach reads the card before moving a player to a higher batch.

  5. 5. Matches

    Squads are picked from attendance and form. Consent is collected, travel is planned, and runs and wickets are logged against each player after the match.

  6. 6. Fees and renewals

    Reminders go out before a cycle ends. Each payment gets a receipt, and anyone whose cycle lapses lands on the desk’s call list.

Industry reports to connect with

  • Enrolment by age group and batch
  • Attendance by batch and by player
  • Fees due, received and lapsed by plan
  • Net and ground use by lane and hour

Questions before implementation.

When should cricket 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