Before You Build
Web AppLow Traction

Teacher Finder

Teacher Finder is a language-teacher marketplace that matches students with private teachers across selected European cities.

View source

Product snapshot

What it was

Teacher Finder matched language students with private teachers and coordinated teacher availability, referrals, invoices, and payments.

Who it was for

language studentsprivate language teachersexpats seeking lessonslocal European language-learning markets

Problem / value

It reduced the friction of finding a local teacher and gave teachers qualified student leads.

Core workflow

  • Find a private language teacher
  • Refer student leads to available teachers
  • Manage matching, updates, invoices, and payments

Product form

marketplaceWordPress siteBubble backendZapier-automated operations

Pricing model

Teachers paid a one-off fee after four successful lessons; the marketplace did not take an ongoing percentage.

What happened

Summary

Teacher Finder made money but could not turn a fragmented local matching workflow into a large, repeatable marketplace.

Outcome

Still online but limited in scale. The case is best read as a source-dated low-traction marketplace lesson, not a total shutdown.

Demand signal

The source shows real demand and revenue, not a pure demand failure. The constraint was uneven local liquidity: some cities had students without enough teachers, while others had teachers without enough student demand.

Distribution issue

Student acquisition relied heavily on Google search rankings, while teacher supply required manual outreach through expat forums, listing sites, and direct messages.

Timeline

  • The founder started by referring student inquiries to language teachers after seeing demand from his own teaching attempts.
  • The first version used WordPress, Gravity Forms, Google Sheets, and Zapier, then later moved some operations to Bubble.
  • The marketplace launched internationally at the end of 2015 after starting in Budapest.
  • It peaked in early 2018, then traffic and inquiries declined as search rankings weakened and competition increased.
  • The business was later reduced from 60-70 cities to about 10 core European cities and became a smaller low-maintenance operation.

Before you build

Why it matters

Marketplace builders often discover one side first and assume software will connect the rest. Teacher Finder shows that city-level supply, search demand, logistics, and payment follow-up can cap the business even when revenue exists.

Primary check

Validate marketplace density city by city before automating a two-sided marketplace around local services.

Relevant if

  • You are building a marketplace for local services.
  • Your matching depends on geography, availability, or category-specific supply.
  • Your acquisition plan depends heavily on SEO rankings.

Less relevant if

  • Your product is not two-sided.
  • Supply and demand happen fully online with no local logistics or city-by-city constraints.

Pre-build tests

  • Manually match ten students and teachers in one city before building a platform.
  • Track the ratio of usable supply to real student inquiries by city and language.
  • Estimate how many manual follow-ups are needed per successful match and price the model around that workload.

Transferable lessons

  • Validate one city and one category before expanding.
  • Run the marketplace manually long enough to see recurring supply and demand patterns.
  • Treat SEO ranking as a channel to validate, not an asset you permanently own.

If you build this today

Start with one city, one language pair, and manual matching; only automate after both sides repeat without constant founder intervention.