Building Pathfinder CRM by Qylantis for Nepal’s Education Consultancies
Pathfinder CRM by Qylantis for Nepal Consultancies
Imagine a counsellor in a cramped Putalisadak office at 4:30 PM.
She has three WhatsApp chats open, two Excel files named something like Applications_v2_FINAL_really.xlsx, one shared Gmail inbox, and a folder full of student documents. A student’s admission offer is in one chat. The scholarship document is in another. The visa checklist is a photo sent last week. The payment confirmation is with the accountant. The student’s flight is next week.
Now she has to answer a simple question:
Is this student actually ready?
That question should take ten seconds to answer.
Instead, it takes one hour.
She checks WhatsApp. Then Gmail. Then Excel. Then Google Drive. Then asks the accountant. Then calls the branch manager. Then asks the counsellor who handled the student first. Meanwhile, commission calculations are sitting in a separate ledger, the accountant wants IRD-friendly invoice records, and the owner wants to know how many students are actually moving toward enrollment this month.
This is how many study-abroad consultancies in Nepal still operate.
Not because the owners are careless.
Not because counsellors are lazy.
Not because the industry is small.
The problem is simpler and more painful:
The software most consultancies use does not match how Nepali education consultancies actually work.
That is why we are building Pathfinder CRM by Qylantis.
Pathfinder CRM by Qylantis is a CRM and student management platform built by Qylantis for Nepal’s education consultancies. It is designed to replace scattered Excel sheets, WhatsApp follow-ups, paper files, fragmented payment records, and disconnected branch reporting with one structured operating system for the consultancy.
The goal is not to build another generic CRM.
The goal is to build the CRM that a counsellor in Putalisadak, Bagbazar, New Baneshwor, Chitwan, Pokhara, Butwal, Dharan, Itahari, or Biratnagar can actually rely on every working day.
The problem is bigger than messy spreadsheets
Nepal’s study-abroad industry is not a small niche.
In FY 2023/24, Nepal issued 112,593 No Objection Certificates to students planning to study abroad. In the first five months of FY 2024/25 alone, Nepali students reportedly spent around NPR 47.34 billion on foreign education.
Those numbers tell a serious story.
Thousands of students are leaving Nepal every year for higher education. Families are spending large amounts of money. Consultancies are handling critical decisions, documents, applications, financial records, visa timelines, and compliance-sensitive information.
Yet many consultancies still run their daily operations on:
- Excel sheets
- WhatsApp messages
- Shared Gmail inboxes
- Paper files
- Google Sheets
- Manual payment ledgers
- Verbal follow-ups
- Personal phone contacts
- Unstructured Google Drive folders
That mismatch creates expensive problems.
Operational friction slows everyone down
A counsellor’s job should be to guide students, not hunt for documents.
But in many consultancies, counsellors spend too much time answering questions like:
- Where is this student’s passport copy?
- Has the student submitted the latest academic transcript?
- Who uploaded the SOP?
- Did the offer letter arrive?
- Which university application is active?
- Who followed up last?
- Has the student paid the second installment?
- Which branch owns this student?
- Is the NOC process started?
- What is the visa status?
When information is scattered, every small update becomes a search operation.
This wastes time, frustrates counsellors, and creates a poor student experience.
Missed follow-ups directly cost money
Education consultancy is a follow-up-heavy business.
A student may not decide on the first counselling session. They may need to talk to their parents. They may compare two consultancies. They may ask about Australia today and Canada next week. They may disappear for ten days and then suddenly become serious again.
If your counsellor forgets to follow up, another consultancy gets that student.
This is one of the most common ways consultancies lose revenue.
Not because they lack leads.
Because they lack a reliable follow-up system.
Pathfinder CRM by Qylantis is designed to make follow-ups visible, trackable, and accountable.
A manager should know:
- Which students need follow-up today
- Which follow-ups are overdue
- Which counsellor owns which student
- Which leads are active
- Which students have gone cold
- Which inquiries came from which source
- Which counsellor is converting properly
- Which branch is losing leads
Without that visibility, the owner is managing by guesswork.
Compliance risk is real
Study-abroad consultancy work involves sensitive student information and important documentation.
Consultancies deal with:
- NOC-related records
- Passport copies
- Academic documents
- Financial documents
- Visa documents
- Guardian details
- Payment details
- University offer letters
- Embassy documentation
- Branch records
- Commission records
Manual systems are fragile.
If important records are stored across personal devices, WhatsApp chats, shared inboxes, and loose spreadsheets, the business becomes exposed to mistakes.
A proper CRM should help build:
- Structured records
- Audit trails
- Role-based access
- Document tracking
- Payment history
- Application timelines
- Owner-level reporting
For a consultancy, better records are not just about convenience. They are about professionalism and risk reduction.
Accounting becomes painful without structure
Education consultancies do not only manage students. They manage money from multiple directions.
Students pay the consultancy. Universities may pay commissions. Agents may need commissions. Counsellors may have incentives. Branches may have their own revenue targets. Some students pay in installments. Some receive discounts. Some need refunds. Some payments come by cash, some by bank transfer, some through wallets, and some through mobile banking.
If all of this is tracked manually, the result is predictable:
- Delayed invoices
- Confusing commission sheets
- Incorrect payment records
- Pending dues that no one follows up
- Poor branch-wise financial visibility
- Stress for the accountant
- No clean owner dashboard
Pathfinder CRM by Qylantis is being built to connect student records, application records, payment records, and commission records in one workflow.
That matters because money should not live separately from the student journey.
Owners lack visibility
Many consultancy owners are still dependent on verbal updates.
They ask:
How many leads came this week?
The team says:
Around 50.
They ask:
How many converted?
The team says:
Maybe 12.
They ask:
Which counsellor performed best?
The answer becomes subjective.
This is not management. This is guessing.
A consultancy owner should be able to see:
- Total leads
- Leads by source
- Leads by branch
- Leads by counsellor
- Follow-up completion
- Active applications
- Pending documents
- Offer letters received
- Visa status
- Payments collected
- Payments pending
- Branch-wise revenue
- Counsellor-wise performance
- Commission status
A CRM should give the owner a real picture of the business.
That is one of the biggest reasons we are building Pathfinder CRM by Qylantis.
Why existing CRMs often miss the mark
There are many CRMs in the market.
Zoho, Salesforce, HubSpot, Pipedrive, Freshsales, LeadSquared, and many others are powerful tools.
The issue is not that these products are bad.
The issue is fit.
Most CRMs are built around generic sales processes. They usually think in terms of:
- Contacts
- Companies
- Deals
- Pipelines
- Tasks
- Notes
A Nepali education consultancy needs something different.
It needs to manage:
- Students
- Guardians
- Counsellors
- Branches
- Countries
- Universities
- Programs
- Intakes
- Documents
- Applications
- Offer letters
- Visa stages
- NOC status
- Payments
- Commissions
- Agents
- Reports
A student is not just a contact.
An application is not just a deal.
A consultancy is not just a sales team.
That is the core problem.
Local payment workflows matter
Many consultancies in Nepal receive payments through:
- Cash
- Bank transfer
- eSewa
- Khalti
- Mobile banking
- Cheque
- Installments
A CRM designed mainly for Stripe, PayPal, or card payments does not fully match how Nepali consultancies collect money.
Payment tracking needs to understand local reality.
A consultancy needs to know:
- Who paid?
- How much did they pay?
- Which service was the payment for?
- Which branch collected it?
- Which counsellor handled the student?
- Is there a due amount?
- Was a receipt generated?
- Is a refund needed?
- Is commission expected from the university?
- Is an agent commission payable?
If the CRM cannot handle this cleanly, the finance team goes back to Excel.
Once the finance team goes back to Excel, the CRM becomes incomplete.
Dates and local operations matter
Nepal has its own operating context.
Many stakeholders still use Bikram Sambat dates. Local holidays matter. Festival seasons affect follow-ups. Visa appointments, application deadlines, document timelines, and internal reporting all depend on accurate date handling.
If a system ignores local working habits, counsellors feel friction every day.
Friction kills adoption.
A CRM can have many features, but if the daily user experience feels foreign, the team will avoid using it.
Pathfinder CRM by Qylantis is being built with Nepali consultancy operations in mind from the beginning.
Compliance and documentation need structure
NOC-related records, visa documents, embassy checklists, offer letters, financial documents, and academic records should not be floating across chat apps and random folders.
A consultancy CRM should support:
- Student-wise document records
- Application-wise document status
- Required document checklists
- Uploaded document status
- Missing document alerts
- Verification status
- NOC-related fields
- Visa document tracking
- Audit logs
- Role-based access
This is not a fancy feature.
This is basic operational hygiene.
Branch and role management are not optional
A growing consultancy may have:
- Owners
- Admins
- Branch managers
- Counsellors
- Accountants
- Application officers
- Document officers
- Field agents
Each role should not see or edit the same data.
For example:
- A counsellor should see assigned students.
- A branch manager should see branch-level data.
- An accountant should handle payments and invoices.
- The owner should see everything.
- A document officer may need document access but not financial control.
This is why role-based access is important.
A CRM without proper roles creates either too much restriction or too much exposure.
Both are bad.
What we are building
Pathfinder CRM by Qylantis is a multi-tenant SaaS platform built by Qylantis for Nepal’s education consultancies.
We are focused on solving the real work, not adding buzzwords.
Pathfinder CRM by Qylantis is designed to help consultancies manage:
- Student inquiries
- Student profiles
- Guardian information
- Counsellor assignment
- Follow-up reminders
- Application tracking
- University records
- Program records
- Document checklists
- Offer letter tracking
- Visa workflows
- NOC tracking
- Payment records
- Commission accounting
- Branch management
- Role-based access
- Reports and dashboards
The product is built around the student lifecycle, not just a sales pipeline.
Student and application management
Every student should have one clear record.
That record should show:
- Personal details
- Guardian details
- Academic background
- English test status
- Preferred destination
- Preferred course
- Preferred intake
- Assigned counsellor
- Lead source
- Follow-up history
- Documents
- Applications
- Offers
- NOC status
- Visa status
- Payment history
- Notes and timeline
A student may have more than one application.
For example, one student may apply to three universities in the UK. Another may start with Australia and later switch to Canada. Another may apply to both Japan and Korea.
The CRM should handle that naturally.
Pathfinder CRM by Qylantis is being built to support that kind of real consultancy workflow.
University and program records
A consultancy needs structured information about universities and programs.
This may include:
- University name
- Country
- Program list
- Intake availability
- Application deadline
- Required documents
- Application fee
- Scholarship information
- Commission rules
- Contact person
- Partner status
- Notes for counsellors
Without structured university and program records, counsellors rely on memory or old PDFs.
That creates inconsistency.
A good CRM helps every counsellor work from the same source of truth.
Visa workflows
Visa processes differ by destination.
The steps for Australia are not identical to the UK, Canada, the USA, Japan, Korea, or Europe.
A proper consultancy CRM should support step-based visa workflows, reminders, and document tracking.
Pathfinder CRM by Qylantis is designed around country-specific workflow thinking, so consultancies can manage different destinations without forcing everything into one generic pipeline.
Counsellor performance tracking
Counsellor performance should not be based only on opinion.
A CRM should show:
- Leads assigned
- Follow-ups completed
- Follow-ups missed
- Students converted
- Applications submitted
- Offer letters received
- Visa outcomes
- Revenue influenced
- Lost leads
- Reason for lost leads
This allows owners and managers to coach based on data.
It also helps good counsellors get recognized.
Without performance visibility, the loudest person in the room can look like the strongest performer.
That is bad management.
Branch management
Multi-branch consultancies need clean visibility.
The owner should be able to compare:
- Branch-wise leads
- Branch-wise conversion
- Branch-wise applications
- Branch-wise revenue
- Branch-wise pending payments
- Branch-wise counsellor activity
- Branch-wise visa outcomes
At the same time, branch managers should not necessarily see everything from every branch.
Pathfinder CRM by Qylantis is built with multi-branch access and reporting in mind.
Commission accounting and invoicing
Commission tracking is one of the messiest parts of consultancy operations.
A student enrolls. The university owes commission. The commission arrives later. It must be linked to the right student, university, counsellor, and branch. Sometimes an agent is involved. Sometimes counsellor incentives depend on the outcome.
If this is handled manually, mistakes are likely.
Pathfinder CRM by Qylantis is being built to support:
- Student-wise commission records
- University-wise commission status
- Branch-wise commission reports
- Counsellor-wise performance reports
- Agent commission tracking
- Payment reconciliation
- Invoice records
- Finance-ready reports
This helps the owner understand where revenue is expected, received, or delayed.
Compliance-friendly records
Pathfinder CRM by Qylantis is designed to support structured records for:
- NOC numbers
- NOC status
- Student documents
- Application records
- Payment history
- Foreign education-related records
- Visa timelines
- Audit logs
- Branch-level activity
The aim is to make important information easier to find, review, and report.
A consultancy should not need to panic when it needs to produce records.
The technical foundation
Pathfinder CRM by Qylantis is built as a modern SaaS platform.
The technical stack includes:
- FastAPI backend
- PostgreSQL database
- React web application
- React Native mobile application
- Cloud-based deployment
- REST API architecture
- Role-based access structure
The product is designed to be fast, maintainable, and practical for daily consultancy work.
The technical stack matters because consultancies do not need fragile software. They need a system that is responsive, predictable, and easy for the team to use.
Counsellors should not be slowed down by laggy interfaces.
Owners should not need to think about servers, databases, background jobs, or technical maintenance.
The product should simply work.
Why our approach is pragmatic
We are not building Pathfinder CRM by Qylantis from a boardroom fantasy.
We are building it from conversations with consultancy owners, counsellors, branch managers, and operators.
The approach is simple.
Start with the real work
We focus on the student lifecycle and the financial flows that matter.
Not abstract lead scoring.
Not unnecessary enterprise complexity.
Not features that look good in a demo but are ignored in real life.
The product must help with the work consultancies actually do every day.
Localize properly
Localization is not just translating labels.
For Nepal, localization means thinking about:
- NOC tracking
- Local payment methods
- Local branch structures
- Local support expectations
- Bikram Sambat usage
- Document-heavy workflows
- Nepali consultancy pricing realities
- Practical onboarding from Excel and WhatsApp
A CRM that ignores these details will not fit properly.
Make it auditable
Important actions should leave a trail.
A consultancy should be able to understand:
- Who updated the student record?
- Who uploaded a document?
- Who changed the application stage?
- Who recorded a payment?
- When was a follow-up completed?
- What changed in the student timeline?
Auditability builds trust inside the business.
Ship small and improve fast
We are early, and that is an advantage if used correctly.
Instead of pretending we already know everything, we want to work closely with consultancies and improve based on real usage.
The best feedback is not vague praise.
The best feedback is sharp and specific:
- This report is missing.
- This workflow is too slow.
- This field should be required.
- This permission should be different.
- This screen does not match how counsellors work.
- This export needs to support our accountant.
That is the kind of feedback that improves the product.
Be transparent about support and pricing
Consultancies do not need surprise fees.
They need clear pricing, clear onboarding, clear support, and a real migration plan.
Buying software is easy.
Getting the team to use it properly is harder.
That is why onboarding matters.
The product today
Pathfinder CRM by Qylantis is designed to support daily consultancy operations.
Current and planned workflow areas include:
- Student profile management
- Lead capture and assignment
- Counsellor follow-up tracking
- Application tracking
- Document dashboards
- University and program records
- Offer letter status
- Visa workflow tracking
- NOC-related fields
- Payment records
- Invoice records
- Commission reports
- Branch-level views
- Role-based access
- Mobile-friendly counsellor workflows
- Owner dashboards
The product is not pretending to be perfect.
Some features will continue to improve as more consultancies use the system.
But the direction is clear:
Build a focused CRM for Nepali education consultancies, not a generic sales CRM with an education label.
Where we need help
We need three things right now: pilot customers, honest feedback, and useful partnerships.
1. Pilot customers
We are looking for consultancies that want to trial Pathfinder CRM by Qylantis as early partners.
The ideal pilot consultancy is one that:
- Has outgrown Excel
- Has multiple counsellors
- Handles many active students
- Struggles with follow-up tracking
- Wants better document management
- Needs better payment and commission visibility
- Wants branch-level reporting
- Is willing to give honest feedback
In exchange, we want to work closely with early users to tune the product around real workflows.
2. Honest feedback
If you are a counsellor, branch manager, accountant, document officer, or consultancy owner, we want to hear from you.
Tell us:
- What wastes your time?
- What do you still track manually?
- Where does student information get lost?
- What report do you prepare every week?
- What do you wish your owner could see?
- What do you wish your counsellors updated properly?
- What part of the application workflow causes the most confusion?
The sharper the feedback, the faster we can improve.
3. Integrations and partnerships
We want to prioritize integrations that save real time.
That may include:
- Payment providers
- University portals
- Immigration partners
- Accounting workflows
- Messaging tools
- Document verification workflows
- Lead capture channels
But we do not want integrations for the sake of looking impressive.
We want integrations that reduce actual manual work.
What we will not do
We will not force every consultancy into one rigid workflow.
That does not work.
Different consultancies operate differently. A small single-branch consultancy does not operate like a multi-branch consultancy. A Japan-focused consultancy does not work exactly like an Australia-focused consultancy. A consultancy with a dedicated application team works differently from one where counsellors handle almost everything.
Pathfinder CRM by Qylantis will provide structured defaults but still allow practical flexibility.
We also will not treat onboarding as an afterthought.
Most CRM failures happen because implementation is weak.
So onboarding must include:
- Understanding current workflow
- Cleaning existing data
- Importing active records
- Training counsellors
- Training managers
- Training finance users
- Setting reporting expectations
- Reviewing adoption after launch
A CRM is not successful when it is installed.
It is successful when the team uses it daily.
Why Kathmandu, why now
We are proud to build Pathfinder CRM by Qylantis from Kathmandu.
Nepal has strong engineering talent and deep market knowledge. More importantly, we understand the local paperwork, the payment habits, the office culture, the festival calendar, the student pressure, the parent expectations, and the reality of running service businesses here.
That matters.
Software built for this market should understand this market.
Nepal’s education consultancy industry is large, competitive, and increasingly professional. The student flow is significant. The money involved is significant. The operational responsibility is significant.
But the software infrastructure serving this industry is still weak.
That is the opportunity.
Not just to build a SaaS product.
But to help a real local industry become more organized, transparent, auditable, and scalable.
If you run an education consultancy
If you run a consultancy and any of this sounds familiar, you probably already know the problem.
Maybe your follow-ups are inconsistent.
Maybe your payment tracking is messy.
Maybe your commission reports are confusing.
Maybe your counsellors use different spreadsheets.
Maybe student documents are scattered.
Maybe branch reporting is weak.
Maybe you are growing, but your internal system is not growing with you.
That is exactly the kind of problem Pathfinder CRM by Qylantis is built to solve.
Visit:
https://pathfinder.qylantis.com
Request a demo, start a pilot, or reach out with your workflow.
We are especially interested in working with early consultancy partners who want software that fits how they actually operate.
If you are a counsellor
If you are a counsellor, we want Pathfinder CRM by Qylantis to make your day easier, not harder.
The system should help you:
- See today’s follow-ups
- Track student notes
- Upload documents
- Update application status
- Check missing requirements
- Avoid forgotten students
- Reduce repeated questions
- Work from mobile when needed
- Keep your manager updated without constant verbal reporting
A good CRM should not feel like extra work.
It should reduce confusion.
If you are a branch manager
If you manage a branch, Pathfinder CRM by Qylantis should help you see:
- Leads assigned to your branch
- Counsellor workloads
- Follow-up completion
- Active applications
- Pending documents
- Payment status
- Branch revenue
- Lost leads
- Visa outcomes
- Team performance
Branch management should not depend only on end-of-week verbal updates.
You need live visibility.
If you are an owner
If you own a consultancy, Pathfinder CRM by Qylantis should help you answer the questions that matter:
- Are leads increasing or decreasing?
- Which lead sources work best?
- Which counsellors are converting?
- Which branch is performing?
- Which applications are stuck?
- Which payments are pending?
- Which commissions are expected?
- Which students need urgent attention?
- Where is the business leaking money?
- What should we improve this month?
A CRM should give you control without forcing you to micromanage every staff member.
The honest bet
We are not trying to build the next billion-dollar platform overnight.
That is not the goal.
The goal is more grounded:
Build software that a Nepali education consultancy can trust every day.
If that sounds modest, it is deliberate.
Small operational improvements compound.
Better follow-ups create more conversions.
Better document tracking reduces delays.
Better payment visibility reduces leakage.
Better branch reporting improves management.
Better student records improve trust.
Better workflows reduce stress.
That is how a consultancy becomes more professional.
Pathfinder CRM by Qylantis is our bet on that future.
A future where Nepali consultancies do not need to run serious businesses on broken spreadsheets, scattered messages, and memory.
A future where counsellors have better tools.
A future where owners have better visibility.
A future where students get better service.
And a future where serious software for Nepal’s education consultancy industry is proudly built from Kathmandu.
Try Pathfinder CRM by Qylantis
If you run an education consultancy in Nepal, we would love to talk.
Visit:
https://pathfinder.qylantis.com
Or contact:
Built by Qylantis.
Made for Nepal’s education consultancies.
