Skip to content
GullySales

Universities · CRM

Keep one record per applicant, visible to the admissions desk and the department.

A CRM for a university is the shared record of every enquiry, application and paid seat, tagged to a programme and an owner. GullySales sets it up with the fields, stages and permissions your admissions office and departments already use.

Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

A prospective student speaks with a university admissions adviser

What CRM means

A CRM is the record where every enquiry, call and quote is kept against a customer, replacing separate notebooks, spreadsheets and memory. GullySales sets up or cleans an existing CRM and reports from it by enquiry outcome rather than by activity logged.

Last updated 14 Nov 2026.

For universities

Where it usually goes wrong, and what we would do.

  • “Spreadsheets multiply across departments”

    Each school keeps its own list of enquiries and none matches the others. When the same student asks about two programmes, two coordinators contact them with different answers.

  • “Stages mean different things to different people”

    One department calls a student applied after the form is sent. Another waits for documents. A count of applications across the university is a sum of unlike things, and the registrar cannot trust it.

  • “Staff changes take the knowledge with them”

    When an admissions coordinator moves on, the notes on who was promised a call go with them. The next person starts from nothing and the applicant repeats the whole conversation.

  • “Student data needs a careful owner”

    A record holds names, marks, documents and parents' numbers. Who may see it, who may export it and how long it is kept are decisions that need an owner before the system is built.

What we do

What we deliver for universities.

The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.

  1. Stage definitions agreed by the registrar

    A written list of stages from enquiry to paid seat, with what each one means and who moves a record forward.

    Result: Every department counts an application the same way.

  2. Fields and programme tags

    The data fields for each record, including programme, entrance route, source and parent contact, set up in the system you choose.

    Result: Each record can be filtered by programme and source.

  3. Roles and access plan

    A list of who can view, edit and export which records, with a named approver for each level.

    Result: Applicant data is visible only to people who need it.

  4. Import of existing lists

    A clean-up and merge of the spreadsheets in use, with duplicates flagged for the desk to resolve.

    Result: Past enquiries sit in one place.

  5. Reports for admissions and deans

    Views that show enquiries, applications and paid seats by programme against the previous cycle.

    Result: The dean can see how a programme stands without asking.

How the result is measured

  • Enquiries logged in the CRM
  • Data completeness
  • Reports generated from CRM data

Recorded as a baseline before work starts, so every later report has an honest comparison.

Fields worth keeping

What an admissions CRM should hold for each applicant.

Programme and school
Filled by the form or the counsellor from a fixed list. Lets a dean see enquiries for one school without reading the whole sheet.
Entrance exam and score status
The counsellor enters it when the applicant shares it. Decides which applicants to call after results and which to call before.
Admission stage
Enquiry, applied, offered, fee paid or joined, as the registrar defines them. One list for every office so a count means the same thing.
Documents received
The admissions office ticks each certificate as it arrives. A reminder can then name the missing one instead of asking for all.
Source and agent
Set when the record is made: web, fair, school visit or named agent. It shows which source produced paid seats rather than forms.

Who it is for

This is written for these universities.

  • State universities with affiliated colleges
  • Private universities with a campus and hostel focus
  • Deemed-to-be universities with their own entrance
  • Universities with a dedicated research and PhD focus
  • Universities that recruit international students
  • Universities with strong professional schools such as engineering, law and management
  • Sector-specific universities in health, agriculture, technology or the arts
  • New private universities building their first admissions cycle

Before you decide

When this may not be the right fit.

  • The registrar has not agreed what each admission stage means, so a CRM would hold stages that every office reads differently.
  • Nobody holds responsibility for the applicant data, and a system with no owner turns into another spreadsheet.
  • You are still collecting applications on paper at the counter, with no step to enter them afterwards.

Before you decide

Agree the work. Know how to judge it.

CRM for universities: use these checks to prepare, choose the scope, and review what changes.

Bring the right evidence

List the records your team uses and show how an enquiry becomes an order today. Bring examples of duplicate entries, missing owners, and reports that require manual correction.

Make the scope clear

Agree the stages, required fields, access roles, and integrations before configuring the system. Separate software subscriptions from setup, data work, and training.

Check the work in use

Ask the people who will use the CRM to complete a real handover and find the next action without help. Check that the management report can be traced back to individual records.

Know when to change course

If the process is unclear, buying a more complex CRM adds more places for confusion. Start with the minimum fields and rules the team can use consistently.

These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.

Before we start

What to have ready before the work starts.

The records, access and decisions this work needs from universities. Anything missing is noted in the written scope, with who will supply it.

All existing applicant lists
Bring every list: spreadsheets, forms and portal exports. Messy is acceptable. Without them, the CRM starts empty and the first cycle has no history to compare. Include lists held by individual counsellors on their phones, since these are the ones that vanish first when a person leaves.
The registrar's stage definitions
The registrar should be ready to decide when an applicant moves from one stage to the next. If offices disagree, the decision is theirs, not ours. Undecided stages produce reports that nobody trusts. A meeting between the offices before we start saves long arguments later.
An IT officer for access and security
Someone from IT must approve how applicant data is stored and who may log in. They should attend the access meeting. Without them, we pause before any personal data is loaded. The IT officer also decides where backups are kept and who may export data.
A data-protection decision
The university must state who owns applicant data and how long it is kept. Take this to your own adviser if unclear. We build to that rule and do not set one ourselves. Any written agreement with applicants, such as a consent line on the form, should be shared with us.
Desk staff trained to enter data
The admissions desk needs time to learn the screens and practise. Plan for it outside the peak days of counselling. Untrained staff will return to spreadsheets. Include someone from the accounts office, so fee fields are filled correctly.

How it works

How the CRM work runs

The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.

  1. 1

    Draw the path an applicant takes

    With the registrar, we draw each step from first enquiry to paid seat on one sheet: enquiry, counselling, application, document check, offer, fee payment and joining. You mark who owns each step and where applicants disappear. The sheet is the first version of the stages the CRM will hold. Steps taken outside the office, such as a fair or a school visit, are drawn in as well.

  2. 2

    Fix the stage definitions with the registrar

    We write what each stage means in a sentence, such as which document turns an applicant from enquiry to applied. You and the registrar settle any disagreement between offices. Stages that two offices read differently would give two different reports, so we resolve them in this step. Stages that no applicant ever reaches are removed from the list.

  3. 3

    List the fields each office needs

    Admissions wants contact details and source, the accounts office wants fee status, and the deans want programme and intake. We list the fields once, agree which are required and drop the rest. A form with a crowd of fields will not be filled in at the desk.

  4. 4

    Set who sees which records

    A department head should see applicants for their own programme, and the finance office should see only fee fields. We draw a plain access sheet with the registrar and the IT officer. Roles are set up according to that sheet, and nobody gets wider access by default. Departing staff lose access on their last day, and the access sheet says who removes it.

  5. 5

    Import the old lists into one place

    Spreadsheets from fairs, counsellors and past cycles are cleaned of duplicates, tagged with their source and loaded. Counsellors check a sample of records against their own notes. Records the desk cannot confirm are placed in a separate pile. A source tag is added to each batch, so later reports can tell a fair from a form.

  6. 6

    Read the first reports with the deans

    After a stretch of use, we show the registrar and the deans the stage counts for each programme, then compare them with the previous cycle's register. You decide which report the offices will actually use, and we drop the ones nobody opens. Reports that need a manual workaround are replaced with simpler ones before the next cycle.

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales management. A target, a review routine and someone who owns the number.

  1. Step 1

    Sales audit

    Find where deals are being lost and what to fix first.

    Start here if you cannot say where orders are lost.

  2. Step 2

    Sales process design

    One written way to sell, from first enquiry to repeat order.

    Start here if every salesperson sells differently.

  3. Step 3 · you are here

    Sales management

    A target, a review routine and someone who owns the number.

    Start here if the team has targets and no routine.

Tell us what you need Your brief is read before we call. Scope, fee and term in writing.

FAQ

Questions owners ask before they call.

Not here? More answers, or ask on WhatsApp.

Which CRM should a university use?
The one your team will keep updated. Some universities start with a widely used tool such as Zoho or HubSpot, or the system their ERP already offers. We compare the options against your stages and users before suggesting one.
Can the CRM connect to our admission portal?
It can, through an integration or an import. Whether it is worth building depends on how the portal stores data. We check what the portal exports before promising any connection.
Who owns applicant data?
The university does, and a named officer should be responsible for it. Data protection law in India applies to personal data, so take advice from your own legal adviser on consent, storage and sharing.
Can a department see applicants from other schools in the CRM?
Not by default. Give each school the records for its own programmes and let the admissions office see all. Applicant data is personal, and a lecturer browsing unrelated records has no need. Set roles when the system is built, and remove access when a staff member leaves.
Can the CRM be connected to our admission portal?
It can, if the portal offers a way to send data out, but that depends on who built the portal and what the contract allows. We ask the vendor or your IT officer in the first step, and tell you plainly whether a live link is possible. If it is not, a regular export and import keeps the two in step. We do not recommend a link that your team cannot maintain.
Should every department use the same CRM?
Yes for the shared stages, such as enquiry, application and paid seat, because the registrar needs one count. Departments may add fields of their own, for example a portfolio link for a design programme, so long as the shared fields stay the same. We set this up so a department sees only its own applicants. Separate systems in each school would make the registrar's report impossible to trust. The registrar sees all of it, and each school sees its own.
How much does it cost?
There is no price list, because the work differs by business. The fee is scoped after we have read your brief and spoken to you, and put in writing before anything starts, split into our time, your media spend and production.
How long is the contract?
The term is agreed in writing after we have spoken, along with the fee and the reporting. It is never a default twelve months, and renewal is decided on the numbers against the baseline recorded at the start.
How soon will we see results?
It depends on the trade, the channel and what is already in place. After we have read your brief and spoken to you, we say what we would expect to move first and how it will be measured against the baseline. Nothing here is guaranteed.
Who will actually do the work?
The person you speak to before anything starts. We work from one office in Nagarbhavi, Bengaluru, with no account managers in between.

Your next practical step

Tell us what you are trying to grow, and we will read it before we call.

Eight short steps, mostly taps. Skip anything you would rather answer on the call.