Lead Product Manager EdTech CRM / SaaS Forms Dot Star Admissions Suite

Building an EdTech SaaS Platform from Online Forms to Student Relationship Management

How we evolved a focused application form builder into SREM, a comprehensive student relationship management platform serving 500+ colleges and processing 5M+ applications.

Unified Funnel Student Lifecycle
Self-Serve Document Upload Hub
Automated Fee Reconciliation

Most education institutions do not lose students only because of academics, pricing, or competition.

They lose them in the gaps.

A student fills a form, but no one follows up quickly.
A counselor calls, but the context is incomplete.
Documents are submitted, but verification takes days.
Application fees are collected, but reconciliation is manual.
Management wants funnel visibility, but data sits in spreadsheets.
Marketing generates leads, but admissions teams do not know which ones are likely to convert.

This was the world in which Forms Dot Star started.

It began as a way to digitize application forms and enrollment workflows for colleges and universities. But as the product matured, it became clear that online forms were only one part of the bigger institutional problem.

Institutions did not just need digital forms.

They needed a system to manage the entire student journey.

That is how Forms Dot Star evolved into SREM — Student Engagement and Relationship Management.

The evolution was not just a rename. It was a product-market fit shift.

Forms Dot Star solved application digitization.
SREM solved student engagement, admissions CRM, communication, application processing, analytics, and lifecycle management as one platform.

CRM SaaS Student Lifecycle
Self-Serve Document Uploads
Automated Fee Reconciliation
Chapter 01

The situation

Indian educational institutions were going through a digital transformation, but the admissions operating model was still highly fragmented.

Many institutions were dealing with:

  • paper-based application forms,
  • manual data entry,
  • scattered student enquiries,
  • slow document verification,
  • inconsistent follow-ups,
  • limited counselor accountability,
  • offline fee collection,
  • spreadsheet-based admission tracking,
  • weak communication across SMS, email, and WhatsApp,
  • limited visibility into the admission funnel.

At smaller institutions, the problem was basic digitization.

At larger institutions, the problem was scale, conversion, funnel visibility, and process control.

The product had to serve both.

It had to be simple enough for institutions moving away from paper and powerful enough for institutions managing thousands of students, counselors, campaigns, and admission stages.

Chapter 02

What was actually broken

At first glance, the problem looked like:

“Institutions need online application forms.”

But that was only the visible part of the problem.

The deeper issue was that the student acquisition and admission journey was broken across multiple disconnected steps.

Application capture was fragmented

Students came through different sources:

  • website forms,
  • walk-ins,
  • campaign landing pages,
  • referrals,
  • education fairs,
  • calls,
  • social campaigns,
  • counselor outreach.

But institutions did not have a unified way to capture and manage all these interactions.

A form submission was often treated as an isolated record instead of the beginning of a student relationship.

Chapter 03

Admissions teams lacked follow-up discipline

A student enquiry loses value quickly if no one follows up.

Counselors needed to know:

  • who to call,
  • when to call,
  • what the student is interested in,
  • what stage the student is in,
  • what documents are pending,
  • whether payment is done,
  • whether the student is likely to convert.

Without a structured CRM, follow-ups depended heavily on individual discipline.

That created leakage.

Some leads were followed up well.
Some were ignored.
Some were contacted too late.
Some were contacted without context.

Chapter 04

Application processing was slow

For many institutions, application processing involved manual checks:

  • form completeness,
  • document verification,
  • fee payment confirmation,
  • eligibility checks,
  • status updates,
  • internal approvals.

Processing time affected both student experience and institutional efficiency.

If an institution took too long to respond, the student could move to another college.

Speed was not just an operational metric. It affected conversion.

Chapter 05

Communication was disconnected

Institutions used SMS, email, WhatsApp, calls, and sometimes physical notices.

But communication was often not connected to the student’s actual funnel stage.

A student who submitted documents needed a different message from a student who abandoned the form.
A student who paid application fees needed a different message from someone who only enquired.
A student who was admitted needed a different journey from someone still undecided.

The product needed to support communication as part of the lifecycle, not as a separate broadcast tool.

Chapter 06

Management lacked real-time visibility

Leadership needed to know:

  • how many enquiries were generated,
  • which sources were converting,
  • which counselors were performing,
  • where students were dropping off,
  • how many applications were complete,
  • how many documents were pending,
  • how much fee was collected,
  • which programs were underperforming,
  • what the final admission funnel looked like.

Without dashboards, decisions were reactive.

Institutions needed analytics that converted scattered admission activity into management insight.

Chapter 07

The product insight

The initial product solved a real need: digital application forms.

But over time, the bigger insight became clear:

“An application form is not the product. The student journey is the product.”

That insight changed the product direction.

Forms Dot Star had to evolve beyond form capture into a broader operating platform.

The question became:

How do we help institutions manage every student from first enquiry to final enrollment?

That is what led to SREM.

SREM became the broader platform that brought together:

  • enquiry management,
  • online applications,
  • admissions CRM,
  • lead scoring,
  • document processing,
  • payment collection,
  • multi-channel communication,
  • analytics,
  • role-based access,
  • institutional workflows,
  • lifecycle engagement.

This was a better market fit because institutions did not want to stitch together multiple tools. They needed one platform to solve the full admissions and student engagement journey.

Chapter 08

How Forms Dot Star evolved into SREM

Forms Dot Star started as a focused application and enrollment platform.

It helped institutions digitize:

  • application forms,
  • document submission,
  • application fee collection,
  • application tracking,
  • basic analytics,
  • institution-branded forms.

But once institutions adopted the platform, the next pain surfaced naturally.

They asked:

  • How do we follow up with applicants?
  • How do we prioritize leads?
  • How do we track counselor activity?
  • How do we send SMS, email, and WhatsApp updates?
  • How do we understand the admission funnel?
  • How do we reduce processing time?
  • How do we improve conversion?
  • How do we manage the full student lifecycle?

That pushed the product from a form platform toward a relationship management platform.

SREM was the answer.

It expanded the product from:

form submission

to:

student engagement and admissions relationship management.

This was the key product evolution.

Chapter 09

What I shaped

I led end-to-end product strategy for SREM and owned the product evolution from Forms Dot Star into a broader EdTech SaaS platform.

The work covered:

  • product strategy,
  • roadmap,
  • product-market fit refinement,
  • application workflow,
  • admissions CRM,
  • student engagement,
  • lead scoring,
  • document processing,
  • communication workflows,
  • analytics dashboards,
  • payment integration,
  • role-based access,
  • mobile-first experience,
  • institutional deployment,
  • scaling the product across India.

I also built and mentored a cross-functional team of 8+ members across engineering, design, and operations.

The product grew from serving a narrower enrollment need to becoming a comprehensive student engagement and relationship management platform.

Chapter 10

Track 1: Digital application and enrollment workflow

The first product foundation was digitizing the application journey.

The platform allowed institutions to move away from paper-based forms and manual application handling.

The application workflow supported:

  • online form submission,
  • institution-specific form configuration,
  • document upload,
  • payment gateway integration,
  • application tracking,
  • student record management,
  • workflow customization,
  • white-labeled institutional experience.

This was especially important for institutions that needed digital transformation but did not have the internal capacity to build their own admissions technology.

The product helped make admission processes faster, cleaner, and easier to manage.

Chapter 11

Track 2: Automated document processing

Document verification was one of the most painful operational steps.

Students submitted documents.
Institutions had to check them.
Missing or invalid documents delayed the process.
Manual verification consumed staff time.

The platform introduced automated document verification and OCR-based document scanning/validation.

This reduced processing time and manual data-entry effort.

For Forms Dot Star, automated document verification reduced processing time by 70%.

This was one of the strongest operational improvements because it directly attacked the admission processing bottleneck.

Chapter 12

Track 3: Admissions CRM and student lifecycle management

As the product evolved into SREM, the admissions CRM became central.

The platform helped institutions manage students across the funnel:

  • enquiry,
  • application started,
  • application submitted,
  • documents pending,
  • payment pending,
  • counselor follow-up,
  • admission offered,
  • enrollment completed.

This converted student acquisition from scattered follow-up into a structured lifecycle.

Counselors could work with better context.
Managers could track funnel movement.
Institutions could identify where students were dropping off.

The product shifted from record keeping to active admission management.

Chapter 13

Track 4: Intelligent lead scoring

One of the most important SREM capabilities was intelligent lead scoring.

Admissions teams cannot treat every enquiry the same.

Some students are high intent.
Some are browsing.
Some need immediate follow-up.
Some need nurturing.
Some are unlikely to convert.

The intelligent lead scoring system helped institutions prioritize leads and improve counselor productivity.

It improved conversion rates by 45%.

The value was not only in the score itself. The value was in changing counselor behavior.

Instead of calling students randomly or chronologically, counselors could focus on the students most likely to move forward.

This is where the product became more than CRM. It became a decision-support system.

Chapter 14

Track 5: Automated admission workflow

Admissions processing was reduced from 7 days to 2 days.

That improvement came from automating the admission workflow and reducing manual handoffs.

The workflow improvements included:

  • digital application intake,
  • structured document processing,
  • automated status movement,
  • payment capture,
  • counselor visibility,
  • admission-stage tracking,
  • communication triggers,
  • dashboard visibility.

This had direct impact on student experience.

Faster processing means students get clarity sooner.
Institutions reduce administrative load.
Counselors focus on conversion instead of chasing paperwork.

Chapter 15

Track 6: Multi-channel communication platform

Student engagement depends heavily on communication.

The product supported communication across:

  • SMS,
  • Email,
  • WhatsApp.

The communication platform achieved 95%+ delivery rates.

This mattered because admissions are time-sensitive.

A delayed message can mean a missed payment.
A missed reminder can mean an incomplete application.
A late follow-up can mean a lost student.

The communication system helped institutions send the right message at the right stage of the student journey.

Chapter 16

Track 7: Analytics and funnel visibility

The analytics dashboard gave institutions real-time insight into student engagement and admission funnel performance.

The dashboard helped answer:

  • How many enquiries came in?
  • Which sources are performing?
  • Which counselors are converting?
  • How many students started applications?
  • Where are students dropping off?
  • How many applications are complete?
  • Which documents are pending?
  • What is the conversion rate?
  • Which program needs attention?

This changed the management layer.

Instead of waiting for manual reports, leaders could see admission performance in real time.

Chapter 17

Track 8: Payment gateway integration

Application and admission workflows often require fee collection.

The product integrated payment gateways to support digital fee collection.

This helped institutions reduce cash/manual collection dependency and improved transaction traceability.

It also improved the student experience because students could complete application/payment steps digitally.

Chapter 18

Track 9: Role-based access and institutional hierarchy

Educational institutions are hierarchical.

There are admins, counselors, department users, finance users, reviewers, and management users.

The platform implemented role-based access control to support institutional hierarchies.

This allowed institutions to configure visibility and actions based on user role.

For enterprise SaaS adoption, this was essential.

A platform serving hundreds of institutions cannot rely on a flat user model.

Chapter 19

Track 10: Mobile-first accessibility

The product was built with a mobile-first responsive interface.

This mattered deeply in the Indian education market.

Many students applied through mobile phones.
Many rural or smaller institutions did not have desktop-first workflows.
Counselors and staff needed access beyond office systems.

The mobile-responsive application portal increased mobile submissions by 200%.

This showed that accessibility was not a cosmetic design choice. It affected adoption and conversion.

Chapter 20

How the workflow changed

Before the product, an institution’s admission journey often looked like this:

collect enquiry → record manually → share form → collect paper documents → verify manually → chase payment → update spreadsheet → call student → prepare reports manually.

After Forms Dot Star evolved into SREM, the workflow became:

capture enquiry → score lead → assign counselor → send communication → collect application digitally → verify documents → collect fee → track funnel → automate follow-up → view analytics → convert enrollment.

The biggest shift was from fragmented administration to lifecycle management.

The old process managed applications.
The new platform managed student relationships.

Chapter 21

What made this hard

This product was hard because education institutions are not uniform.

A platform had to support different institution sizes, processes, levels of digital maturity, geographies, languages, and operating habits.

Some institutions needed digitization

They wanted to move from paper to online forms.

Some institutions needed CRM

They wanted counselor tracking and lead follow-up.

Some needed analytics

They wanted funnel visibility and conversion data.

Some needed workflow control

They wanted document verification, payment tracking, and approval stages.

Some needed customization

They wanted branding, custom fields, and institution-specific workflows.

The product challenge was to build a platform flexible enough for different institutions but standardized enough to scale.

configurable for clients, but not custom-built for every client.

Chapter 22

What was achieved

The product achieved strong growth and business impact.

SREM scaled from 150 to 500+ institutional clients, achieving 233% growth in 2.5 years.

It served:

  • 500+ educational institutions,
  • 2M+ student interactions annually,
  • 5M+ student applications processed,
  • ₹15Cr+ annual revenue through platform subscriptions.

Key product outcomes included:

  • intelligent lead scoring improved conversion by 45%,
  • automated admission workflow reduced processing time from 7 days to 2 days,
  • multi-channel communication achieved 95%+ delivery rates,
  • customer retention reached 98%,
  • document verification reduced processing time by 70%,
  • platform adoption increased 150% year-over-year,
  • mobile submissions increased 200%,
  • customer satisfaction reached 92%,
  • institutions reduced operational costs by 40% through digitization.

Forms Dot Star, as the earlier product stage, served 300+ educational institutions across 15+ states, processed 1.5M+ student applications, and generated ₹8Cr+ ARR through platform subscriptions and transaction fees.

The evolution into SREM expanded the addressable problem and created a stronger platform-market fit.

Chapter 23

Why this mattered

The education sector was moving from offline admissions to digital student lifecycle management.

Institutions that could respond faster, communicate better, process applications digitally, and understand funnel performance had a competitive advantage.

SREM helped institutions modernize their admission operations.

It did not only digitize forms.
It helped institutions manage relationships.

That distinction is important.

A form is a transaction.
A relationship is a journey.

SREM turned student acquisition into a managed journey.

Chapter 24

What this says about my product approach

This product reflects my ability to identify when a product’s initial category is too narrow.

Forms Dot Star was useful as an application platform, but the market needed more.

The stronger opportunity was SREM.

That required a strategic product shift:

  • From forms to relationships.
  • From application capture to student lifecycle management.
  • From digitization to conversion intelligence.
  • From tool to platform.

This is one of the most important product lessons:

Product-market fit often improves when you stop defining the product by the feature and start defining it by the customer’s full problem.

The institution’s problem was not “I need an online form.”

The real problem was:

I need to attract, engage, process, convert, and manage students efficiently.

SREM solved that broader problem.

← All case studies

Related service: AI Product Strategy · Insights