We know this field from our own product
We built Hippotenus around how an education institution runs day to day: it analyses mock-exam results at learning-outcome level, finds each student’s gaps, and lets teachers, parents, students and the institution see the same data. It runs on a pool of more than 300,000 questions with over a thousand active users. It taught us which screen each person needs and where data gets stuck, and we bring that to your project from the first day.
Off-the-shelf or custom?
If your institution runs in a standard way, off-the-shelf school management software gets you started quickly. Custom software fits better if you have your own exam system, your own reports or several branches, or want to show parents something the package doesn’t offer. The common route is hybrid: standard work such as accounting stays in a ready-made product, and the layer specific to your institution is built separately.
From a mock-exam result to the parent report
The key step is linking each question to a learning outcome. Once that’s done, you can see which topics a student is dropping marks on, the teacher sets homework to match, and the parent sees the same picture. Skip it and a mock exam that ends in Excel stays a ranking and a list of scores. In Hippotenus, mock-exam analysis, student tracking and homework are linked in just this way.
What admins, teachers, parents and students need on screen
Each role should see what it needs to do its job, which is why the screens are designed separately for each role. An admin wants to compare the whole institution, while a parent only cares about their own child. Give everyone the same page and it gets crowded, and nobody finds what they came for quickly.
Admin
Branch and class comparisons, payment and instalment status, and what each teacher is doing with each class.
Teacher
Their class’s gaps by learning outcome, homework submissions, and quick exams drawn from the question pool.
Parent
Only their own child’s results, absences, homework and payment reminders.
Student
Their own gap list, homework due and the topics to work on before the next mock exam.
Student data is personal data, and most of it belongs to minors. The privacy notice and, where needed, consent under Türkiye’s data protection law (KVKK) are the institution’s responsibility. On the software side we plan from the start that each role sees only what it needs, parents can reach only their own child, and every opened record is logged.
What to have in place before custom software
Rules your institution has already agreed on are quick to turn into screens. If decisions such as the mock-exam format or scoring are left until development is under way, the same question comes back every week and the first version slips. Settling them before we start is the easiest way to keep the timeline short.
You’ll move quickly if
- Your mock-exam format and scoring are settled
- Your list of learning outcomes is written down somewhere
- Someone at the institution will own the project and try each weekly version
- You’re happy to pick a single flow for the first version
Sort these out first if
- Each branch runs and reports its mock exams its own way
- You expect every module to go live at once
- The switch has to land in the middle of your busiest exam weeks
Planning the first version around the school calendar
Time the switch for a few weeks before term starts or for the mid-year break; those are usually the easiest windows. Stay clear of mid-term, and above all of heavy exam weeks. That way the pilot runs on a real mock exam without everyone under pressure. We plan the steps backwards from that date.
- 01
Talking through your current setup
30 minOn a free call we cover your mock-exam format, your reports and where the data lives today.
- 02
Data model and migration plan
We look at your learning-outcome structure, how classes and branches are organised and your old exam files, and agree what gets migrated.
- 03
The first flow
2-4 weeksFor example mock-exam analysis and the parent report. You get a working version to try every week, with our product owner as your single point of contact.
- 04
A pilot with one class
One class or branch uses it first, with a real mock exam. Whatever trips the teachers up gets fixed here.
- 05
Homework, payments and the mobile app
These come in later releases. An iOS and Android app from a single codebase typically takes 4-8 weeks, plus some slack for the store release.
The budget follows the scope and is settled in writing after the scoping call. If you want to compare, our published budget bands, rates by role and scope timelines are on the pages below (as of October 11, 2026).
Cost and timeline guide
Every budget band, our rates by role and the timeline for each scope tier, on one page.
Pricing
The four engagement models, payment terms and what the price covers.
Frequently asked questions
Will it work with our own mock-exam and assessment system?
Yes. Your exam format, scoring and learning-outcome structure are built into the data model from the start, and the reports follow that structure. The most common problem with packaged software is that institutions end up bending their own system to fit it.
Can there be a mobile app for parents and students?
Yes. An iOS and Android app fed by the same data shows parents results and notifications, and shows students their homework and gap list. We shipped SoruVerse on both stores as our own product.
Can we bring over our existing student data?
Yes. Student, class and past exam data is imported from Excel files or your current system’s export; the migration plan is part of the first version.
When can the first education module be used?
A first version covering one flow (for example mock-exam analysis and the parent report) typically goes live in 2-4 weeks; modules such as homework, payments and the mobile app are added in later releases.
Where will the question pool content come from?
The software stores the questions, tags them by learning outcome and turns them into exams; the questions themselves usually come from the institution’s own teachers. Check the copyright status of questions scanned from published books before they go live. Tagging and approval are a workload to plan for too. In Logaritim, exams are also built from an approved question pool.
We have several branches. Can they share one system?
Yes. Branches are a layer in the data model from the start: the admin compares all of them, while branch managers and teachers see only their own. If branches run mock exams differently, agreeing on a common format first makes everything much easier.
Who keeps the software after delivery?
The source code stays with Pepechura; you get a perpetual licence to use the software, and your data is always yours. If you want the source code transferred to you, that is available for an additional fee, set out separately in the quote. If Pepechura ever ceases trading, the source code is handed over to you. User documentation is included. We fix bugs free of charge for 30 days after launch, and after that we can carry on under a monthly retainer.