We closed our seed round last week. €1.8M, led by Early Game Ventures, with participation from several angel investors who have built and sold ed-tech companies in European markets. I have been asked by a lot of people — customers, potential customers, people in the Romanian startup community — what this means, what we are doing with the money, and why we took it at all. This post answers those questions directly.
What the money is actually for
The short version: product and people. We are hiring four engineers over the next eight months. Two will work exclusively on the mobile apps — the teacher app and the parent app — which have the highest usage volume and the most active feature requests from customers. One will own the data reporting layer, which schools have been asking us to improve since the beginning. The fourth will work on integrations: connecting Kinderpedia to the national student record systems in Romania and Poland, which is a prerequisite for expanding in those markets at scale.
The second category is go-to-market. We have been almost entirely inbound since launch. Word spread between school directors, referrals from existing customers, some search traffic. That is how you get to 1,200 schools. It is not how you get to 5,000. We are building a small sales team focused on school groups — networks of 5 to 20 schools that make a single purchasing decision — because that is where the unit economics work best at this stage.
We are not spending it on rebranding, offices, or anything that does not directly translate into product or customers. That is not a virtue signal — it is a constraint the team set before we started the fundraising process.
Why Early Game Ventures
Early Game Ventures focuses on founders in Central and Eastern Europe. That matters because the problems Kinderpedia solves are specific to how schools operate in this region — national curriculum requirements, local payment infrastructure, GDPR implementation in markets where enforcement has been inconsistent, and the particular dynamics of private school pricing in Romania and Bulgaria. A generalist VC from London or Berlin is going to have strong opinions about product direction based on how schools work in the UK or Germany. Those assumptions are often wrong for our market.
Beyond geography, Early Game Ventures operates up to €6M tickets and covers pre-seed through Series A. That means they are not going to be out of step with us as we grow. The lead partner has direct experience in enterprise SaaS sold to institutions, which is closer to what we do than consumer ed-tech, and that distinction matters when the conversation turns to sales cycles and renewal rates.
We looked at six funds before taking this meeting seriously. The others either had no portfolio companies in education or were structured in ways that would have required us to grow faster than the product could support. Neither of those is a good reason to take money.
What we have built so far
Kinderpedia launched in Romania in 2018 with a simple attendance and parent messaging tool. The core insight was straightforward: parents wanted to know what was happening at school every day, and teachers did not want to answer 30 WhatsApp messages a night to tell them. We built the channel that sits between those two frustrations.
Over seven years the platform expanded to cover the full administrative surface of a K-12 school. The student information system now holds medical records, IEP documents, sibling relationships, and enrollment history. The gradebook supports national grading scales for Romania, Bulgaria, Hungary, and the UAE — four markets with four completely different conventions. Billing handles multi-currency invoicing and integrates with Stripe for card payments, which matters as soon as a school has more than 200 fee-paying students and a finance team of two people.
The number that defines where we are: 850,000 active student profiles across 14 countries. That is not a projection. Those are records that a teacher or administrator updated in the past 90 days.
The problem we are solving is not going away
Every K-12 school in the world has an administrative problem. The nature of the problem varies by context — a 3,000-student international school in Dubai has different pain points than a 200-student private school in Cluj — but the underlying cause is the same. Schools are run by people who became educators, not administrators. The paperwork, compliance tracking, parent communication, and billing that surround the act of teaching have grown faster than the infrastructure to handle them.
The existing software market is fragmented. There are national SIS systems mandated by governments that handle compliance data and nothing else. There are consumer apps designed for individual teacher use. There are expensive ERP platforms built for university administration that have been force-fitted onto secondary schools. None of them was designed from the ground up to cover the full day-to-day operational reality of a K-12 school. That is the gap Kinderpedia fills.
The EU's investment in digital education infrastructure under programs like eTwinning and the Digital Education Action Plan is accelerating school procurement decisions. Schools that were deferring purchases are now making them, because the funding is available and the expectation that they have digital systems in place is increasingly embedded in inspection frameworks. We are in the right market at the right time — and now we have the capital to move faster.
What this means for existing customers
Nothing changes in how your school uses Kinderpedia. Contracts do not change. Pricing does not change. The support team you contact is the same. Taking investment does not mean we are shifting focus away from the schools that got us here — it means we can build the features that have been on the roadmap for two years and staff a support organization that matches where we are going.
The reporting improvements will start rolling out in Q3 2025. The national system integrations for Romania and Poland are scheduled for Q4. We will communicate both on the product changelog and directly through the account manager for any school that will be affected by changes to how data flows.
A note on the fundraising process itself
We started seriously exploring external funding in September 2024. We were generating revenue that covered the team's salaries and had been doing so for two years. The decision to raise was not about survival — it was about whether we could hit the scale required to build a durable business before a well-capitalized competitor moved into CEE specifically to take the market we had spent six years building.
The process took five months from first conversation to close. That is typical for a seed round in this region. We ran a tight process: six funds, two term sheets, one close. We did not run a wide, open process because we knew what we were looking for and a fund that did not understand our market from the first conversation was not going to understand it after three more.
If you are a founder in ed-tech and have questions about the CEE funding landscape, the specifics of fundraising while operating a B2B SaaS with school customers, or anything about what this process actually looked like, reach out directly at daniel@kinderpedia.tech. I am happy to talk through it.
What comes next
We have a clear 18-month plan. The hiring is underway. The product roadmap is locked through Q1 2026. The markets we are expanding into — Poland and Turkey — have been selected based on two years of demand signal from inbound inquiries, not speculation. We have design partners in both markets who have been on the waitlist and will help validate the localization work before we open general availability.
The goal is not to be the biggest ed-tech company in Europe. It is to be the platform that every serious K-12 school in Central and Eastern Europe uses to run their operations. That is a focused, achievable goal with a clear path. The seed round is what closes the gap between where we are and where we need to be to execute it.
Thank you to the customers who got us here. Every feature on the platform exists because a school director, a teacher, or an administrator told us exactly what they needed and trusted us to build it.