PepechuraPepechura
Free scoping call
Industry solution

Software for education institutions

Student tracking, mock-exam analysis and exam software for tutoring centres, courses and schools.

We build management software for tutoring centres, courses and schools: student tracking, mock-exam analysis, homework, exam preparation and parent updates. We do the same work with thousands of users in our own products: Hippotenus, Logaritim and SoruVerse.

Problems we often see in these businesses

Mock-exam results live in Excel, so nobody can see which student is weak on which topic
Teachers, parents and management get the same information through different channels, at different times
Preparing exams and homework takes up much of a teacher’s week
Payments and instalments are tracked in a separate ledger
Off-the-shelf school management software doesn’t fit how your institution works

What we build

Mock-exam analysis at learning-outcome level, with a gap list for each student
Role-based screens for admins, teachers, parents and students
Exams and homework from a question pool, with PDF output
Homework, attendance, payment and instalment tracking
A mobile app with notifications for parents and students

We know this field from our own product

We built Hippotenus around the day-to-day running of an education institution: 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 the data gets stuck, and we bring that experience to the software we build for you from day one.

Off-the-shelf or custom?

If your institution runs in a standard way, off-the-shelf school management software gets you started quickly. If you have your own exam system, your own reports or several branches, or if what you want to show parents differs from what the package offers, custom software is the better fit. 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

01
Mock-exam results
02
Outcome mapping
03
Student gaps
04
Homework and review
05
Parent report
Results go in once; every role sees its own screen built from the same data.

A mock exam that ends in Excel stays a ranking and a list of scores. The value starts when each question is linked to a learning outcome: you can see which topics a student is dropping marks on, the teacher sets homework to match, and the parent sees the same picture. In Hippotenus, mock-exam analysis, student tracking and homework are linked in just this way.

What admins, teachers, parents and students need on screen

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

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

  1. 01

    Talking through your current setup

    30 min

    On a free call we cover your mock-exam format, your reports and where the data lives today.

  2. 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.

  3. 03

    The first flow

    2-4 weeks

    For 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.

  4. 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.

  5. 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.

Avoid switching mid-term, and above all during heavy exam weeks. The easiest window is usually a few weeks before term starts or the mid-year break, so the pilot runs on a real mock exam without everyone under pressure.

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.

How long does it take?

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?

You do. On final payment the source code and IP are transferred to you, with documentation and setup instructions included. We fix bugs free of charge for 30 days after launch, and after that we can carry on under a monthly retainer.

Our own products in this field

What we have written about this industry

Related services

Let’s talk about how your institution runs

Tell us how you handle mock exams, reports and parent communication today; we’ll work out together what belongs in a first version.