Software for the institutions we already equip
Two systems the company builds and operates itself. One is sold to institutions; the other is here because it is the evidence that we can run the first one. Both are quoted the way a laboratory is quoted — scoped with you first, then priced.
Learning Management System for Institutions
One deployment across the whole institution, aimed at the two numbers a Philippine college is ranked on.
Philippine institutions are ranked on retention and board passing rates. Those are the two numbers this system is built to move, and the reason it is bought as an institutional deployment rather than a departmental tool.
- Course materials become practice
- Readings and slide decks uploaded to a course are turned into questions grounded in that material — practice sets, flashcards, and spaced repetition scoped to the subject rather than to the internet at large. A student revising for a subject drills the subject, not a generic question bank.
- An early-warning view, not a report you have to ask for
- Attendance, grades, and engagement are read together rather than in three separate places, so a student drifting toward failure surfaces while there is still term left to act. The flag reaches the student, the instructor, and the adviser.
- Faculty time back
- Assessment drafts generated from the syllabus and rubric-assisted feedback, so preparation and marking stop consuming the hours that teaching needs. The instructor edits and approves; nothing is published unreviewed.
- Institution-wide from the first day
- One tenant spanning every program, department, and section, with role-based access for administrators, faculty, students, and advisers. It is not a per-department licence that later has to be stitched together.
Who it is for
Colleges, universities, and private basic-education institutions.
What it does not do
It does not replace your student information system, enrolment, cashiering, or accreditation reporting. Those stay where they are; this sits alongside them and is scoped so the boundary is written down before anything starts.
The build is at foundation stage and runs with one pilot institution. It is offered for pilot deployment, scoped with the institution first — not sold as a finished product with a delivery date.
CRM and Sales Automation
A managed sales system we run for clients — and the reason the software above is not a first attempt.
It is on this page for a reason that has nothing to do with selling it to a university. The fair question about the system above is whether an equipment supplier can build and operate software at all. This is the answer: a production system, deployed per client and kept running, with the support and uptime obligations that implies.
- An isolated deployment per client
- One instance per client rather than shared tenancy, hosted in the client's own region, so a client's records are not sitting in a pool with everyone else's.
- The automation around it
- Lead capture, routing, and follow-up wired to the CRM, with reporting on pipeline and on what the automation actually did.
- Operated, not licensed
- Set-up followed by monthly operation. There is no per-seat licence, and the running of it is our obligation rather than the client's.
The CRM itself is Twenty, an open-source project we deploy and operate. We did not write it and do not claim it; what we build is the deployment, the automation, and the reporting around it. In service for clients today.
What an institution asks first
These are the questions that decide an academic software purchase, and they are answered in the scoping document in writing before anything is installed. The specifics are commercial terms, so they are settled with you rather than published here.
- Where does our data live, and who can reach it?
- Fixed in writing during scoping, before anything is installed: the hosting region, who holds administrative access, and what is logged. An institution-wide deployment is a single tenant, so your records are not pooled with another institution's.
- What happens if we stop, or if you do?
- Your data is exportable and the exit terms are part of the agreement rather than a conversation held later. Ask for them in writing at scoping; a supplier who will not put them in writing is telling you something.
- Does it replace our student information system?
- No. Enrolment, cashiering, student records, and accreditation reporting stay where they are. The boundary is written into the scope so there is no ambiguity about what each system owns.
- How is it priced, and how does it get through procurement?
- Quoted the same way as laboratory equipment: scoped with the institution first, then priced, in a form your bid documents can carry. Nothing on this site carries a published price because a public procurement process does not work that way.
- Who trains our faculty, and who answers the phone afterwards?
- The same people who scope it. Faculty orientation and after-sales support are part of the engagement, as they are on the equipment side — that is the whole reason this company builds the software rather than reselling somebody else's.
Start a quotation for your laboratory
Send the specification your bid documents require and we will match it, quote it, and tell you what happens after delivery.