What a study abroad consultancy should build first
Software for an education consultancy in Nepal: why the student pipeline comes before the website, what to track, and when a university search is worth it.
EK Ra Sunya team
EK Ra Sunya Inc.
Ask a study abroad consultancy where a student's file stands and you'll often watch a counsellor scroll through WhatsApp. The passport scan is in one chat, the IELTS result in another, and the offer letter was forwarded to the counsellor's personal email because the shared inbox was full.
That counsellor is good at the job. The system around them is a phone. When they leave, the history leaves with them.
We have built software for this industry at three levels: a consultancy website, a study abroad platform, and a multi-tenant admissions system for agencies. What that work taught us: a study abroad consultancy should build its student pipeline first, meaning one record per student, the documents attached to it, and the application stages it moves through. The website comes second, and its main job is to fill that pipeline with consultation bookings.
The website's job is a booking
A consultancy website is not where students decide. They decide in the counselling room. The site has one job: get a qualified student to book that conversation.
When we built the B&G Education website for a Lalitpur consultancy, the structure followed that job. There is a destination page for each of the five regions they advise on (the USA, the UK, Australia, Canada and Europe), test preparation pages for IELTS, PTE, Duolingo and the SAT, and consultation booking. A blog and FAQs answer the questions students search for before they're ready to call.
What it doesn't need is a feature that tries to replace the counsellor. Which brings us to university search.
University search is a product in its own right
The most requested feature in this industry is a searchable database of universities and courses. It sounds like the obvious upgrade from a brochure site.
My Abroad Friend has one. It searches more than 500 universities worldwide, with course discovery and application tracking. It works because My Abroad Friend is a platform business: the search is the product, and keeping it current is a job someone does every week.
For a single consultancy, that is the wrong first build. A university database is only useful if it's accurate. Fees, intakes and entry requirements change every year, and a stale database sends students to the wrong course with your logo on it. Most consultancies already recommend from a shortlist of partner institutions. A well-written page per destination, with the institutions you actually work with, does more for a student than a search box that knows 500 universities badly.
Build search when maintaining the data is part of your business model. Until then, write.
The pipeline: one record, its documents, and its stage
Here is what the pipeline needs to hold, in the order it matters.
Start with one record per student: name, contact, destination, intake, counsellor, source (walk-in, referral, the website form). Every conversation and document hangs off this record, not off a person's phone.
Then the documents, attached to that record: passport, transcripts, test scores, financial documents, offer letters. A consultancy chases the same set of documents for every student, so the system should show what's missing at a glance.
Next, the stages, written down: enquiry, counselling, documents, application, offer, visa, and whatever your process has in between. When we built Official Global Partner, a platform for international education agencies, the application tracking ended up with nine stages, plus a student CRM, a university and program database, and document automation. Your list may be shorter. The point is that a stage is something the whole team agrees on, so "where is this file?" has one answer.
Roles come last, and only once you have branches. One office can share everything. Several branches can't. Official Global Partner supports seven roles across branches, because a counsellor in one branch shouldn't see another branch's students, and the owner needs to see all of them. Plan for this before your second office opens, not after.
What to do this month
Before buying anything, write your stages on paper and count your students by stage. If you can't count them, that is the problem the software solves. Then decide whether you need a system built for you or an existing CRM configured to your stages. For one office with a simple process, configuring an off-the-shelf CRM may be enough, and we'll tell you so.
When your process has steps a generic CRM fights, such as multiple branches, partner agents, document automation or reports for institutions, that is where custom software earns its cost. Our education and admissions page shows what we've built for consultancies, agents and schools. If you want to talk through your stages, book a consultation.
Have a project in mind?
Let us help you build something scalable, fast, and built to last.
Start a conversationKeep reading
Website, web app, or mobile app: what to build first
Web app vs mobile app for a Nepali business: build the website when strangers need to find you, the web app when staff need a system, and the app last.
EngineeringWorking with a Nepal software team from Australia
Hiring a software team in Nepal from Australia? How the time difference and Nepal's Sunday-to-Friday week shape meetings, feedback and releases.