Video summary

Умный, но пока бедный? Что спросили инвесторы о ДЕНЬГАХ?

Main summary

Key takeaways

Business

Summary

The founder built a property-search tool that helped him find and buy two apartments. It expanded to 11 European countries and six languages, with three interface iterations: text search, a browsable catalog, and listing boards.

But product capability did not answer the central business question: Who would pay, for what, and when?

At his first investor pitch, investors challenged the business model. Was it a metasearch service or an advertising business? When would customers pay? They also questioned whether the model could scale. Renters, buyers, sellers, and agencies have different needs, making it difficult to serve them all with one offer. The founder could also end up competing with partner agencies for the same traffic. If customer acquisition costs match or exceed revenue from clicks, growth is not viable.

Frameworks and playbooks

  • Define the buyer and paid outcome before building. Identify the specific customer, what they are buying, and when payment occurs.
  • Test demand with a manual MVP. Instead of first building a global catalog, manually find five suitable rental listings for someone searching in an unfamiliar city and language. Translate key terms and help the person contact landlords.
  • Be explicit about the offer. The proposed test charges for the search, not for securing an apartment. The founder would disclose that the work is manual and avoid promising an outcome outside their control.
  • Use customer behavior to diagnose product problems. If the customer opens the five listings but gets no viewings, investigate whether the ads are unavailable or the search filters are inadequate before expanding the product.
  • Separate service value from software value. If customers pay because of the founder’s personal outreach and negotiation, a self-service search product may not replace what they value. Ask what they would buy again and at what price.
  • Validate before scaling a feature. Before translating an entire catalog into five languages, test whether translating a small set of listings helps one buyer place an order. Tie every major feature to a specific expected sale.
  • Build with a sales model in view. The founder says he would revisit the idea only with a team, funding, and—most importantly—a real sales model.

Metrics and concrete details

  • Product reach: 11 European countries and six supported languages.
  • Early validation: The tool helped the founder buy two apartments.
  • Proposed demand test: Manually select five listings for one prospective customer.
  • Potential unit-economics warning: Customer acquisition cost could equal or exceed revenue from clicks. No actual CAC, revenue, or margin figures are provided.
  • No confirmed commercial results: The subtitles do not report paying-customer numbers, conversion rates, revenue, or a validated repeat-purchase model.

Presenter and source

Presenter: Михаил Пискунов. Investor feedback is quoted from his pitch; the investors are not identified in the subtitles.

Rate this summary

Your feedback will help improve summaries.

Improve this summary

Reprocess with a stronger model when the summary feels incomplete or inaccurate.

Pro

Translate summary in another language

Pro

Ask questions to this video

Chat for follow-up questions, clarifications, and source-backed answers.

Coming soon

Share this summary

Original video