Cheap Experiments: How to Test Hypotheses Without Lengthy Development
A catalog of simple, fast, and cheap techniques for testing product hypotheses.
Sometimes product teams fall into a trap: an idea seems promising, they want to 'make it beautiful,' and a week goes into design, a month into development, only to find out that the user doesn't need it at all. Cheap experiments are a way to quickly check if a hypothesis has life before burning resources.
Why Are Cheap Tests Needed at All?
The goal is simple: get the truth before we invest in a misconception. When an idea meets reality—statistics, clicks, rejections, willingness to pay—illusions evaporate. Quick experiments provide three things:
- Learning before development. First, we understand the value, then we build the system.
- Minimum cost. We use already available tools: no-code, manual processes, posts, forms.
- Honest feedback. If people aren't interested, it's immediately obvious, without trying to 'save' the feature.
Key Approaches
- Landing page + form/payment. A quick way to check if the value proposition is engaging. A click on 'Buy' is the most honest vote.
- Pretotype. A minimal presentation of an idea: a screenshot, a description, a short video. The goal is to see if people react at all or just scroll past.
- Concierge / Manual-first. Everything that seems like an automated service is temporarily done by hand. This is cheaper and faster than building a system for the first 10 users.
- Wizard of Oz. The user thinks an algorithm is at work. In reality, you are on the other side. This is an excellent way to test value without algorithms.
- Smoke test. An ad or post with a CTA. We look at clicks and sign-ups without a product. Essentially, a demand heat map.
Each method answers one question: 'Is it worth building the product at all?' If not, all the better—we've saved time.
Quick Checklist Before an Experiment
- Formulate the hypothesis and success criterion: what needs to happen to say 'yes' or 'no'.
- Ask yourself: what can be done manually here instead of with code?
- Define minimal resources: a limit of 48 hours and a budget of up to €20–50 simplifies life.
- Plan short CustDev interviews with the first respondents—this adds context to the numbers.
Example: A Pretotype in 48 Hours
- Build a simple landing page describing the value (Tilda, Readymag, Notion—whatever works).
- Add a CTA: 'pre-order,' 'get early access,' 'get a demo.'
- Drive minimal traffic: one post in a relevant community + €20 for targeted ads.
- Collect sign-ups, contact each person, and ask the main questions: What were you trying to solve? Why did the tool seem interesting? Would you pay for it?
The trick is that a pretotype tests not the product, but the user's desire to move forward, even if the product doesn't exist.
How to Evaluate Results
- Compare conversion rates with target numbers. For initial tests, a 2–5% conversion to a sign-up is usually sufficient.
- The quality of leads is more important than the quantity: pay attention to who is willing to pay, what problems arise, and how real the pain is.
- If people click but don't complete the form, the problem is in the value proposition. If they complete it but get lost in the interview, the hypothesis is raw.
A Small Rule That Saves Weeks
An experiment is considered successful only when it kills something. If a test didn't help close at least one idea, it was too soft. Our goal is to learn to say no quickly.
If you want, I can add ready-made blocks for a landing page, interview templates, or a mini-CAC calculator for quick smoke tests. Think about which experiment you want to test next—we'll start there.
High-Conversion Landing Page Structure Template
Only main links and a 'sticky' CTA.
• What is your USP?
• What are you selling?
• Use the language of benefits, without vague or clever words.
Headline
Sub-headline
• What is the next step you want visitors to take?
Logos of major companies for social proof.
Benefits
How it works?
Case studies, logos of well-known companies, verification badges, reviews.
Testimonials
Simple answers to common questions.
Frequently Asked Questions
A high-contrast, action-oriented CTA.
The footer includes:
• logo,
• copyright,
• privacy policy,
• contact information,
• social media icons,
• subscription form, etc.