The problem
Schools, colleges, coaching centres and training institutes rarely fit the shape of a packaged student information system. Your academic year may run on terms, semesters, quarters or rolling batches. Your fee structure may involve admission fees, tuition instalments, transport slabs, hostel charges, exam fees, sibling discounts and scholarship waivers — each with its own due dates and its own approval path. Your attendance may be per-period, per-day or per-session. Off-the-shelf systems force you to bend your calendar and your fee policy to their data model, and when they cannot, the gaps end up in spreadsheets.
Meanwhile you may already run Zoho. Enquiries sit in Zoho CRM, invoices and receipts belong in Zoho Books, staff records live in Zoho People — but nothing between them understands what a batch, a section, a roll number or a fee instalment is. There is no object for a student, no link from a guardian to two children in different grades, and no way for a parent to see a balance without an email.
What ECOSIRE builds
ECOSIRE builds a school and institute management application inside your own Zoho environment. Nothing here is a pre-built product you download — it is scoped against your academic structure, then written, installed and handed over.
Academic structure in Zoho Creator
The core is a set of Zoho Creator forms and reports modelling the entities your institute actually uses: Academic Year, Term, Programme/Course, Batch or Section, Subject, Student, Guardian, Enrolment, Staff Allocation and Timetable Slot. Relationships are modelled as lookups so a guardian record can carry multiple students, and a student can hold multiple enrolments across years without duplicating the person record. Deluge validation rules enforce your own constraints — batch capacity, prerequisite completion, age eligibility, document checklists at admission.
Admissions from enquiry to enrolment
Enquiries are captured in Zoho CRM as Leads with education-specific custom fields (programme of interest, intake, source, counsellor). Deluge custom functions and Zoho Flow move a converted enquiry into a Creator Admission record, creating the Student, Guardian and Enrolment rows in one transaction and generating a roll number using your own numbering rule. Application forms are published as Zoho Creator public pages or Zoho Forms so applicants and counsellors write into the same dataset. Document uploads (birth certificate, previous transcript, ID) are stored against the admission record with a completeness check before enrolment can be confirmed.
Attendance
Attendance is captured against Timetable Slots at whatever granularity you define — daily, per period, or per session for a coaching batch. Faculty mark attendance from a Creator page or a mobile layout; Deluge aggregates it into per-student, per-subject and per-batch percentages. Threshold rules trigger notifications to guardians and to the academic coordinator. Where you already use Zoho People for staff, staff attendance stays there and the application reads it rather than duplicating it.
Fee schedules, invoicing and collection
Fee heads and fee plans are defined in Creator — admission fee, term tuition, transport by route, hostel, exam, late fee — and attached to programmes, batches or individual students. A fee schedule generator produces the instalment plan per enrolment with due dates derived from your academic calendar. Instalments are pushed to Zoho Books through the Books REST API as Invoices against a Customer record for the guardian or the student, so receipts, credit notes, taxes and the general ledger stay in Books where your accountant already works. Where GST or VAT applies to non-exempt heads such as transport or uniforms, the correct tax treatment is configured on the Books item and the Books organization's tax settings rather than recalculated in Creator. Payment status flows back so the Creator record shows paid, part-paid and overdue without anyone re-keying it.
Discounts, sibling concessions and scholarships are applied as rules at schedule-generation time and recorded with an approval trail, so a waiver is always traceable to who granted it.
Parent and student portal
A Zoho Creator portal gives guardians a login scoped to their own children: fee schedule and balance, payment history with downloadable receipts, attendance percentage, timetable, exam results, circulars and leave requests. Portal permissions are configured so a guardian can never see another family's data. Students can be given a separate, narrower login where you want that.
Exams, grades and reporting
Exam schedules, mark entry per subject and grade computation against your own grading scale are handled in Creator, with report card generation as a PDF via Creator's print templates. Management dashboards report on collections versus expectation, admissions funnel by intake and source, attendance exceptions, and batch utilisation. Where you want board-level analysis, the dataset is exposed to Zoho Analytics.
Integration surface
Zoho Flow handles cross-application automation — a confirmed enrolment triggering a welcome email, an overdue instalment triggering a reminder sequence. Deluge custom functions in CRM and Books handle the transactional pieces that must be immediate. Where an external SMS or payment gateway is required, it is integrated through its REST API from Deluge, using credentials held in your own account. Sigma widgets are used where a screen needs behaviour beyond a standard Creator page — a timetable grid, a bulk attendance marker, a seating plan.
Who it is for
K-12 schools, colleges and universities with a defined academic calendar; coaching and tuition centres running rolling batches; vocational and skills-training institutes with cohort intakes; music, language and driving schools with per-session billing; multi-campus groups that need consolidated collections reporting with campus-level operational separation.
How delivery works
1. Scoping call. We walk through your academic calendar, fee policy, attendance rules, admission workflow, portal expectations and the Zoho applications you already own. We ask for sample fee structures and a sample report card. 2. Fixed quote. You receive a written scope with the forms, workflows, integrations and portal screens to be built, and a fixed price. Nothing starts until you approve it. 3. Build. ECOSIRE develops the Creator application, Deluge scripts, CRM customisations, Books integration and Flow automations against your specification. Typical build time is 2 to 4 weeks depending on scope. 4. Install in a test environment. The application is deployed to a sandbox or a test Creator environment with sample data. You run your own admission, a fee cycle and a month of attendance before anything touches live records. 5. Production go-live. After your sign-off we deploy to your production Zoho org, migrate opening student and fee-balance data from your existing sheets or system, and configure user roles and portal access. 6. Support window. A post-go-live support period is included for defect fixes and configuration adjustments, with the terms stated in your quote.
You own the application in your own Zoho account. The Deluge source, the workflow definitions and the documentation are yours.