Plutonic Services

Industries · Education

The counsellor desk is the CRM. Parents already called.

Plutonic builds education software and AI for Indian campuses — admissions, fees, and student queries tied to the ERP and counsellor desk you already run.

  • The counsellor desk answers the same fee question forty times a day
  • Applications live in Excel. Follow-up is WhatsApp
  • Fees, attendance, and the website don't agree
  • Parents message the same deadline every term because the portal is dead

Overview

What a campus actually needs from software

A campus does not need another portal. You need admissions, fees, and the counsellor desk to agree before the parent calls. Plutonic builds that layer on the ERP you already have — then adds AI where it cuts the same query or a lost application, not where it looks clever.
Education industry — What a campus actually needs from software
Education

Challenges

If this is your week, keep reading

If two of these are already true, you don't need another workshop. You need the first workflow live.
01

Three student records. None trusted.

Admissions, academics, and fees live in different tools.

  • The counsellor quotes a fee the accounts sheet doesn't have
  • Attendance and the LMS don't match the ERP
  • Adjustments happen in Excel, then someone 'updates the ERP later'
02

The website lost the applicant

Slow pages, dead links, no next step before counselling starts.

  • Form dumps into a mailbox nobody owns
  • Program page is last year's brochure
  • Parent bounced before the counsellor called
03

The desk is drowning in the same question

Every term: deadline, hostel, exam, fee receipt.

  • WhatsApp groups are the helpdesk
  • New staff interrupt seniors for the handbook
  • No citation when a parent asks 'where is this written'
04

Nobody can find the right program

Students and parents hunt deadlines and PDFs.

  • Eligibility buried in a notice board scan
  • Scholarship rules in a circular nobody searched
  • Monday MIS is a workbook someone built on Sunday

Solutions

What we put on the campus and the desk

The mess in one line. What we put in underneath.

Solution 01

Admissions without the Excel pile

The mess

Applications, fees, and follow-ups live in disconnected tools.

What we put in

Every applicant stage with an owner and a reminder — tied to the ERP, not a side sheet.

  • Lead into a queue, not a mailbox
  • Counsellor follow-up that can be audited
  • No 'we'll update the ERP later'

Solution 02

One login for the things students actually need

The mess

LMS, fees, and notices feel like three campuses.

What we put in

Schedule, content, fees, and tickets in one student/parent picture.

  • Fee status the parent can see
  • Ticket the desk can close
  • Less counter traffic for the same answer

Solution 03

Answers from the handbook, not a guess

The mess

Policies and academic content are hard to find when the desk is busy.

What we put in

Q&A over approved handbooks — with the page they came from.

  • Cited from your circulars
  • Escalate when confidence is low
  • Log of who asked what

Solution 04

Numbers before the board meeting

The mess

Leadership waits on Excel for enrolment, attendance, and desk load.

What we put in

Exceptions from the live file — not a war-room workbook.

  • Enrolment and fee aging first
  • Desk queue the registrar can see
  • Meeting starts with facts

Capabilities

What we actually build for campuses

What we actually build here — not a menu copied onto every industry page.

01

ERP modules the desk will use

Admissions, academics, fees — workflows that match the campus, not a generic school product.

  • Applicant to enrolment in one file
  • Fee the accounts sheet will honour
  • No second student universe

02

Campus sites that don't lose the parent

Program, deadline, and inquiry into a queue — not a brochure PDF with a form.

  • Inquiry the counsellor owns
  • Pages that load on a phone
  • Update without a vendor ticket every notice

03

Student and parent portals

Status, receipts, and notices without a counter visit for the same answer.

  • Fee and exam status
  • Document the parent can download
  • Ticket the desk can close

04

Handbook Q&A with a citation

Approved content only. Escalate when it's not in the circular.

  • Cited from your handbook
  • Human when confidence is low
  • Log for the registrar

05

Admissions as a pipeline

Capture, counselling, application — an owner on every name.

  • Lead off the website into the queue
  • Follow-up the counsellor can be asked about
  • Stage the director can see

06

Content that isn't a brochure dump

When you need more than a site — structured learning the LMS can live with.

  • Program content in one place
  • Works with the LMS you have
  • No parallel Drive classroom

07

Payments, LMS, identity — once

Connect what you already pay for. Stop typing the same student twice.

  • Fee gateway hooked
  • LMS and ERP agree
  • Login the campus already uses

08

Numbers before the board pack

Enrolment, fees, desk load — exceptions, not spreadsheet archaeology.

  • Aging applications first
  • Fee outstanding by program
  • Meeting starts with facts

Use cases

Jobs a campus will pay for

Stop losing applicants at the form

Pilot capture and counsellor follow-up on one program. Expand when conversion moves.

  • One program first
  • Owner from the inquiry
  • Roll out when the miss rate drops

Get the same question off the desk

Handbook Q&A and a parent portal for the queries that repeat every term.

  • Cited answers
  • Escalate the messy ones
  • Counter load you can measure

One student file the accounts office trusts

Admissions, academics, and fees in a picture the ERP will honour.

  • No parallel Excel student
  • Fee status parents can see
  • Fewer 'we'll update later'

Kill the Sunday MIS

Enrolment and desk queue to the phone, not a 40-tab workbook.

  • Live pending list
  • Term handover in the system
  • Meeting starts with facts

Recommended services

Where to start in our practice

Jump into the service pages most relevant to this vertical.

Why it matters

Why campuses stay with us

We talk desks, not 'campus digital'

If we can't name the counsellor and the fee receipt, we don't belong in the kickoff.

  • Enquiry-to-enrolment
  • Counter volume
  • No buzzword kickoff

We plug into the ERP you have

A portal that lives beside fees is a toy. We wire it in.

  • No rip-and-replace as the pitch
  • Admissions + fees + desk
  • Pilot on one campus

Screens a parent will finish

Phone, confusion, a deadline tonight — not only an admin laptop.

  • Big targets
  • Phone-first for students
  • Handover that survives the term

You can point at a number

Application lag, desk queries, fee TAT — not 'AI adoption'.

  • Baseline before we start
  • One owner per metric
  • Expand when it pays

FAQ

Education questions

Straight answers before the call.

Sometimes. More often we fix the module that's hurting — admissions, the parent portal, or the public site — then expand. Rip-and-replace is not the opening move.

Map the highest-ROI campus use case

Book a strategy call to prioritize admissions, the desk, or fees on the ERP you have.

Book Strategy Call
Book Strategy Call