Startup School
Curriculum0/19
Module 1
Idea and problem
Module 2
Customers and validation
Module 3
Building the MVP
Module 4
Growth and metrics
Module 2Lesson 75 min
Testing demand cheaply
Customers and validation
Landing pages, pre-orders and doing it by hand: ways to test demand before writing code.
Interviews show that a problem exists. But will people actually spend money or time on your solution? The best way to find out is to test demand before you build the full product. A week or two of experiments can tell you more than months of programming.
Why test before you build
Building a product is expensive: time, money and, above all, the team's energy. If you build something customers do not need, all of that is lost. Testing demand cheaply helps you find the mistake early, while it is still cheap. If the experiment fails, you lose a few days, not a few months.
A landing page
Make a simple page that explains your offer clearly: who it is for, which problem it solves, what result it gives. Give the page one clear action: "Sign up", "Get early access" or "Pre-order". Then bring the right audience to it: industry Telegram channels, a small ad, sending it to the people you interviewed. Measure how many people saw the page and how many of them took the action.
A sign-up alone is a weak signal: leaving an email or phone number is easy. But it beats nothing, especially when you compare two different offers on the same page.
Pre-orders and deposits
The strongest signal is money. If someone pays in advance for a product that is not ready yet, the problem really does hurt them. You can take payment through a Payme or Click link or a bank transfer. Check with an accountant beforehand how to document it and what tax obligations it creates.
With business customers this often takes the form of an advance payment for a small pilot, or a letter of intent: the company states in writing on what terms it is ready to buy once the product is ready. A letter of intent is weaker than payment, but far stronger than a verbal "yes".
Doing it by hand
Instead of building the product, deliver the result to the customer by hand. Say your idea is automatic order analytics for restaurants: for the first five restaurants, prepare the report in Excel yourself and send it every week over Telegram. The customer gets the result, and you see what they really need, which numbers they look at and what they ignore.
This kind of work does not scale, and that is fine. Doing things that do not scale at the start is one of the most reliable ways to win your first customers and learn from them. You start automating once you know exactly what needs automating.
A Telegram bot or channel
In Uzbekistan many people spend all day in Telegram. A simple bot or channel is often enough as a first product: taking orders, sending reminders, sharing information. People do not have to download a new app, which makes it easy for them to join in.
What counts as a signal
Before you start an experiment, write down what success looks like. For example: "If, within two weeks, at least ten of the hundred people who see the page sign up and three pay a deposit, we continue." The exact number matters less than setting it in advance. Otherwise you risk reading any result as a success.
Rank signals by strength: praise is the weakest, then sign-ups, then people giving their time and joining a trial, and the strongest is money.
Common mistakes in experiments
- Changing too many things at once. You will not know what caused the result.
- Attracting the wrong audience. Your friends visiting the page says nothing about your customers' interest.
- Stopping too early. A day or two of results is often just chance.
- Hiding a negative result. A failed experiment is valuable information too; discuss it openly with the team.
Honesty
Do not take money for something you cannot deliver. Tell customers openly that the product is at an early stage, when it will be ready and what happens if it is late. If you cannot keep your promise, refund the money straight away. The trust of your first customers is the foundation of every future recommendation.
Try this
Pick one of the methods above and run it within seven days. Write down your success criterion before you start. At the end of the week, compare the result with the criterion and decide the next step: continue, change the offer, or try a different group.
Resources
- Paul Graham: Do Things that Don't Scalepaulgraham.com
