Vyasnex: Lost focus

Vyasnex was a complete school management SaaS platform built to consolidate student records, attendance, fees, exams, staff, communication, transport, and reporting into a single web application. The founder spent development cycles perfecting the feature set but never validated demand with real schools, leaving the product finished but commercially inert. With zero paying customers and only ten users reached, the project was listed on Saasgrave for acquisition rather than shut down.

Why Vyasnex built a full ERP before talking to a single school

The founder set out to replace the patchwork of spreadsheets, legacy desktop tools, and manual processes that most schools still rely on. The specification grew to cover nine distinct modules: student management, attendance, fee collection, examinations and report cards, staff management, communication, transport, documents, and administrative reporting. Each module was coded to a shippable standard before any principal or administrator saw a demo.

The assumption was that completeness creates credibility. In practice, completeness without a buyer is just inventory. The founder later admitted the mistake plainly: "I kept thinking that I needed to make the platform more complete before taking it to the market." Every additional feature delayed the first real conversation with a decision-maker.

The validation gap that killed distribution

Ten users touched the product. None paid. No pricing experiments were run. No retention data exists because there was no cohort to retain. The founder's retrospective is blunt: "I should have started talking to schools much earlier, shown them what I had, and used their feedback to decide what to build next."

Schools are not a monolith. A private K–12 chain in Delhi has different fee structures, exam boards, and parent-communication norms than a rural government school in Maharashtra. Building for an imagined "average school" produced a product that fits no specific workflow perfectly. The only way to discover which workflows matter is to sit in the office of a bursar or principal and watch them work.

What the codebase actually contains

The asset for sale is a feature-complete, web-based ERP with the nine modules listed above. It is not a prototype or an MVP — it is a finished application that can be deployed as a multi-tenant SaaS, customized per school, or white-labeled. The founder describes it as "ready for someone to take it forward."

No technology stack is disclosed in the listing. No documentation coverage, test suite metrics, or deployment architecture are provided. A buyer should treat the codebase as a starting point that requires a technical audit before any go-to-market plan.

Why school ERP sales cycles demand early relationship-building

EdTech sales in India (and globally) run on trust, compliance, and referenceability. A principal will not migrate student data to an unproven vendor without a pilot, a reference from a peer school, or a personal relationship with the founder. These relationships take months to cultivate.

The founder invested zero time in this cultivation. The result: a product that solves real problems — fee reconciliation, transport routing, report-card generation — but has no champion inside any school. The next owner inherits the code but not the conversations. Those conversations must start on day one, likely with a free pilot in exchange for feedback and a case study.

What a buyer gets

A deployed, multi-module school ERP codebase with no technical debt from legacy customers. Zero recurring revenue, zero churn, zero legacy pricing to unwind. Ten users who have touched the product — enough for early usability signals, not enough for validation. The founder's documented lesson: distribution is harder than development in this category, and the only way to learn what schools will pay for is to ask them before the next feature ships.

The project is listed on Saasgrave and can be acquired or revived.