Big stories

An edtech founder on year one: “We changed the product three times”

An app for tutors grew into a homework service for schools. The founder describes how, in the first year, the team searched for who would pay and for what.

For you: Before building a product, find out not only who will use it but who will pay for it — that can save you months.

An edtech founder on year one: “We changed the product three times”

Many startups make the same mistake: if people like the product, there must be a business. The founder of one edtech startup learned in the first year that these are two different things. The team changed its product three times.

A simple app for tutors ended up as a homework service for schools. Here is why the first versions did not work and why the third one paid off.

Version one: schedules for tutors

The first version helped tutors manage their schedules. The idea made sense. A tutor has many students, lesson times keep shifting, and it is easy to get confused.

People really did use the app. But they would not pay. The reason was simple: a spreadsheet on their phone did just as well. When someone already has a free, familiar solution, a new one has to be much better to be worth paying for. “A bit more convenient” is not enough.

The lesson: users are not revenue. People happily use free things. Paying is a completely different decision.

Version two: reports for parents

The second version targeted parents, with progress reports. Parents care about how their children are doing at school, so this direction looked safer.

Parents read the reports. But they did not pay either. The information was interesting, yet it did not solve a daily problem. Reading something is one thing; reaching for your wallet is another.

At this point the team noticed an important signal. Plenty of people praised the product. Nobody was ready to pay for it.

Version three: teachers and schools

Help came from an unexpected direction. Teachers asked for a tool to set and mark homework. That is a real, daily burden for them. A teacher collects notebooks, checks them, gives marks and hands them back. It takes a lot of time every day.

The team built a third version, for schools. It paid for itself in six months. Why did this one work?

  • The problem is specific and comes up all the time.
  • The product saves time, and time can be counted.
  • The buyer is an organisation with a budget, not a private person.

One thing to keep in mind: selling to a school can take longer than selling to a tutor. Approvals and paperwork take time. But one deal brings in many users at once.

The three versions side by side

Put the three versions next to each other and the difference is clear:

  • Tutors used the product, but it had a free substitute.
  • Parents read the reports, but for them it was not an urgent problem.
  • Teachers asked for a specific tool, and the school could pay for it.

Every version had users. Only in the third did the user’s pain and the payer’s money meet in one place. The team spent a year finding that point. It may sound long, but it is far cheaper than spending years heading the wrong way.

The main lesson: talk to the people who pay

The founder sums up the first year in one line: talk to the people who pay, not the people who praise.

Praise feels good but misleads. People do not want to hurt your feelings, so they say “great idea”. Willingness to pay is an honest signal. With a possible buyer, these questions are useful:

  1. How do you handle this task today?
  2. How much time or money does it cost you?
  3. When did this problem last really annoy you?
  4. Who decides whether to buy a solution?

These questions reveal what people actually do today, not what they imagine they might do.

What this means for you and what to do now

Kazakhstan has many education startups. Students, teachers and programmers want to bring their ideas to life. This story can save them a lot of time.

Steps you can take today:

  1. Work out who pays. The user and the buyer are not always the same person. In a school product the student uses it, but the school pays.
  2. Compare with the free option people use now. How much better is your product than a phone spreadsheet, a chat or a paper notebook?
  3. Ask for money early. Even a small payment tells you more than praise.
  4. Do not be afraid to change the product. Three versions are not failure; they are how you search.

A chatbot can help you prepare for customer interviews. Copy this prompt and fill in your details:

I am building [product] for [who]. Write 8 questions for an interview with a potential customer. The questions should find out how they handle this task today, how much time and money it costs them, and who makes the buying decision. Avoid leading questions.

Adapt the questions to your situation and write the answers down word for word.

Ad Your ad hereA banner on the homepage, in stories and sections. Formats and prices on our Advertise page.

Comments

No comments yet. Be the first.