From Idea to First Customer
Audience & Promise
This talk is for anyone who has an idea they want to turn into something real — a teenager building their first business, an adult with a product concept they have been carrying around for years, or someone who works at a small business that keeps building features nobody uses. By the end, you will understand why most ideas fail not because they are bad but because they are never tested against the people they are supposedly for. You will have a complete customer interview method you can use this week without any technical skill or budget. And you will have a framework for running the rest of your early-stage experiments — pricing, landing pages, and product-market fit — as learning loops rather than bets.
Speaker Notes by Timestamp
00:00 — Ideas are cheap, evidence is expensive
Here is the uncomfortable thing about ideas: having one costs nothing, and believing in one costs nothing, and the pleasure of working on an idea you believe in is real and sustaining. The problem is that none of those things tell you whether the idea solves a problem that real people have badly enough that they will pay to have it solved.
Most early product failures are not failures of execution. They are failures of assumption. Someone built the thing before they understood the problem. They chose the features they liked. They used the interface they found intuitive. They priced it at what seemed fair to them. And when the first customers arrived — if they arrived — the customers had a different problem, used the product in an unexpected way, found the interface confusing, and balked at the price.
This is not unusual. It is the default outcome when you build before you understand. And the only fix is to go get evidence before you build.
The central premise of this talk is that evidence is more valuable than ideas, and that the most important skill in early-stage entrepreneurship is not building — it is learning. Specifically, learning about the people you want to serve, the problem you think they have, and whether the gap between that problem and any current solution is real, large, and painful enough to build a business around.
We are going to spend the next hour building three specific skills. The first is the customer interview — asking better questions about the problem before you pitch your solution. The second is the pricing and landing page experiment — finding out whether people will pay without building the full product. The third is understanding product-market fit as a learning loop — a repeating cycle of hypothesis, experiment, and revised understanding.
None of these require technical skills. All of them require honesty about what you do not yet know.
08:00 — Customer interview without pitching
The customer interview is the most underused tool in early-stage product development, and the most frequently misused when it is used.
Here is the most common way it gets misused: the founder schedules a meeting, describes their product idea for most of the meeting, and then asks "would you use this?" or "does this sound interesting?" The answer to those questions is almost always "yes" or "it sounds interesting" because people are polite and because a well-described solution to a problem often sounds appealing in the abstract. The founder walks away feeling validated, the potential customer goes back to their life unchanged, and nothing useful has been learned.
The useful form of the customer interview is the problem interview, and it has one rule that is harder to follow than it sounds: you do not mention your solution until after you understand the problem. You might not mention it at all in the first interview. Your goal is to understand how the person currently experiences the problem — what they do today, where the friction is, what they have already tried, what they pay for it now, how often it comes up.
Let's make this concrete with a generic example.
Suppose you have an idea for a tool that helps people organize their grocery shopping and meal planning. You think the problem is that people forget things at the store and waste food. Before you build anything, you need to know: do the people you are imagining actually experience this as a significant problem? How do they currently handle it? What have they tried? What do they still struggle with?
Here is a set of customer interview questions that follow the problem interview approach:
"Can you walk me through what planning this week's meals looked like?" — This is a behavior question. It asks about what they did, not what they want.
"What part of that process felt like the most friction?" — This is a pain point question. It asks them to locate the problem rather than confirming your hypothesis about it.
"Have you tried anything to make it easier?" — This reveals what already exists, what they found acceptable, and where they dropped off.
"What made you stop using [whatever they tried]?" — This is the most valuable question in the set. The reason someone abandoned a previous solution is often the clearest signal about what a better solution must do.
"How often does this situation come up in a week?" — Frequency is a proxy for severity. A problem that comes up daily is worth more attention than one that comes up monthly.
What you are listening for in these answers is not confirmation. You are listening for stories — specific moments, specific words the person uses, specific emotions about specific situations. When someone says "it's fine" in a flat voice, that is different from when they say "honestly it drives me crazy every single time." The exact words people use to describe their problems are often the same words you should use in your eventual marketing — not because you manipulated them, but because they tell you how the problem lives in their head.
Practical notes on running the interview:
Keep it short. Thirty to forty-five minutes is the right length. Longer interviews tend to drift.
Take notes in the interview — ideally capture exact quotes. A paraphrase introduces your interpretation before you have earned it.
Avoid hypothetical questions. "Would you pay for something that..." almost always gets a misleading answer because people are imagining a perfect version of a thing that does not exist. Behavior questions ("what do you do today?") get more honest responses than hypothetical questions ("what would you do if...?").
Do not pitch during the problem interview. If the person asks what you are building, you can say: "I'm still figuring out what the right solution looks like — that's why I'm asking these questions." This is honest and it is also the right frame, because you should still be figuring it out.
After five to eight problem interviews with people who match your target customer profile, you will have either confirmed that the problem is real and significant — in which case you have evidence to proceed — or you will have found out that the problem is smaller, different, or less painful than you assumed. Either outcome is valuable. The second outcome saves you from building something that will not work.
24:00 — Pricing and landing page tests
Once you have evidence that a real problem exists, the next question is whether people will pay for a solution. This is a separate question from whether they want one.
Pricing is one of the areas where founder assumptions are most consistently wrong. Most first-time entrepreneurs undercharge because they are uncomfortable asking for money and because they have not tested what the market will bear. Some over-price because they have heard "charge more" advice without context.
The useful approach is to test pricing before you build, using a landing page experiment or a direct pricing conversation.
A landing page experiment describes the solution at the level of specificity that makes a purchase decision meaningful — what the product does, who it is for, what problem it solves, and what it costs — and asks visitors to take a real action that indicates real intent. The strongest signal is a purchase, deposit, or entry of payment information for a product that does not yet exist but will be built. The next strongest is email signup with explicit commitment language ("notify me when this is available"). The weakest useful signal is general interest without commitment.
The reason real commitment matters is that stated interest and actual purchase behavior are poorly correlated. People can genuinely want something and still not pay for it when the moment arrives. The gap between "yes I would buy that" in a conversation and "yes I am entering my card number now" is enormous, and the only way to cross it is to ask for the real action.
For a teen founder or someone with a very small budget, the landing page can be simple: a one-page description with a price and an option to pay a small deposit or join a waitlist with a real card entry. The technology cost for this is low. The point is not the technology — it is the discipline of asking for real commitment rather than validating on enthusiasm.
Pricing conversation as an alternative: in direct-sales contexts, you can have a pricing conversation as part of a later-stage customer interview. You describe the solution, you name a price, and you watch the reaction. If they say "that seems really high" or "I'd need to think about it," that is data. If they say "actually that's less than I expected," that is also data — and it suggests you may be underpricing. The goal is not to negotiate in the interview; it is to observe the reaction without leading it.
A note on landing page experiments for teen founders: you need a clear, honest description of what the product is and what the purchase is for. If you are taking deposits for something that does not exist yet, you need to be explicit that it does not exist yet and explain what happens if you do not build it. Honesty at this stage is both ethically necessary and strategically useful — the people who sign up knowing it is a pre-order are more committed than people who are surprised later.
40:00 — Product-market fit as a learning loop
Product-market fit is a phrase that gets used so often it starts to lose meaning. But the underlying concept is important: there is a state where the product you have built fits the market so well that growth becomes easier — the product gets used repeatedly, customers tell others, and churn is low. Before you reach that state, growth is hard and expensive regardless of how well you execute.
The key insight for early-stage builders is that product-market fit is not found — it is learned toward. It is the product of a repeating cycle of hypothesis, experiment, and revised understanding. You never arrive at a moment of certainty; you arrive at a state of evidence that is strong enough to increase your investment.
Here is what the learning loop looks like in practice:
Hypothesis: you believe a specific type of customer has a specific problem, and your product solves it better than the alternatives they currently have. You can state this in one sentence: "People who [description] currently [behavior], which causes [problem], and our product solves it by [mechanism]."
Experiment: you run the smallest test that could falsify the hypothesis. Problem interviews for the problem part. A landing page for the solution part. Real usage data for the retention part. The experiment is not designed to confirm the hypothesis — it is designed to find the edge of what you currently believe.
Revised understanding: you update the hypothesis based on what you found. Maybe the customer type is right but the problem description was wrong. Maybe the problem is real but the mechanism you chose to solve it is not the one customers care about. Maybe the pricing is wrong but the product is right. Each experiment answers one question and opens two more.
This is not comfortable. It is designed to make you wrong in productive ways before you have spent too much money. The faster you run the loop, the faster you learn, and the smaller the cost of each wrong turn.
For teens and first-time founders specifically: the learning loop is the thing that distinguishes people who eventually build something that works from people who spend years working on ideas that never quite connect. It is not intelligence, not technical skill, not capital. It is the willingness to design experiments that can prove you wrong, and the discipline to update when they do.
Product-market fit signals worth tracking:
Retention: do customers come back? If you have users who return repeatedly without being prompted, that is a stronger signal than a large number of one-time users.
Referral: do customers tell others without being asked or incentivized? Organic word-of-mouth is one of the strongest early signals that you have built something genuinely useful.
Response to loss: if your product became unavailable tomorrow, how would your best customers feel? If the answer is "disappointed but there are other options," you probably have not found product-market fit yet. If the answer is "I would have a real problem," you are closer.
Churn: what percentage of customers stop using the product in the first thirty days, sixty days, and ninety days? High early churn usually means the product is not solving the problem as well as it promised.
54:00 — Teen founder and operator templates
This section is a practical roadmap for the two main audiences in this talk: a younger person building their first business and an operator at a small organization who wants to apply the same evidence-over-ideas discipline to internal projects.
For the teen founder, the minimum viable starting kit is:
A clear one-sentence hypothesis about your customer, their problem, and your solution. Write it down. It will be wrong. That is fine — the point is to have something to test.
Five to eight problem interviews with people who actually match your customer description. Not your friends unless they genuinely match. Real potential customers.
A landing page or direct sales attempt with a real price and a real call to action.
A decision rule: if you get N positive signals (define N in advance), you proceed to build a minimum version. If you do not get those signals, you revise the hypothesis and run another set of interviews.
For the operator at a small organization, the same discipline applies to internal product decisions. Before building a new tool, a new process, or a new feature: who is this for, what problem does it solve, how do those people currently handle the problem, and how will you know if the solution worked? Skipping these questions is why internal tools get built and never used.
The templates available in Koydo Catalyst's entrepreneurship track include: a one-page customer interview guide with the five core questions and note-taking structure, a landing page brief with the key components (problem statement, solution description, price, call to action, honesty statement), a pricing experiment tracker for recording the results of pricing conversations and landing page experiments, and a learning loop log for tracking hypothesis revisions across multiple experiment rounds.
These templates are starting points, not formulas. The discipline matters more than the specific template. The discipline is: form a specific hypothesis, test it as cheaply and quickly as possible, record what you find, and update honestly.
Worked Demo
This demo is tied to the first-customer-interview module.
Scenario: a seventeen-year-old named Priya has an idea for a service that connects high school students with tutoring for standardized test preparation. She believes the problem is that most families find tutoring expensive and hard to schedule. Before she builds anything or starts marketing, she wants to understand whether the problem she imagines is the one students and families actually have.
She recruits five people to interview: two students who took a standardized test in the past year, two parents of students who are preparing for an upcoming test, and one student currently in preparation. She frames each conversation as a research conversation: "I'm trying to understand how families currently handle test prep before I figure out what, if anything, I should build."
Interview with the first student (past taker): She asks about their actual experience. The student describes using a free online practice resource, taking two practice tests, and feeling underprepared on the actual test. When asked about tutoring, the student says: "We looked into it but my parents said it was too expensive, and by the time we found someone, there wasn't really enough time anyway." Key exact quote: "by the time we found someone." Priya notes this — the problem is not only cost, it may also be discovery and timing.
Interview with the first parent: The parent describes a frustrated search for a tutor. They called three services, received quotes ranging significantly, could not tell from the quotes what was included, and ultimately found someone through a word-of-mouth referral that took three weeks. Quote: "I didn't know if I was comparing apples to apples." Priya notes: the problem includes pricing opacity, not just price.
Interview with the current student: This student has already hired a tutor, is paying significantly per hour, and says: "Honestly the biggest problem isn't the cost — it's that she can only meet on weekends and it's hard to fit it around everything else." Key insight: flexibility may be more important than price for some segments.
After five interviews, Priya's original hypothesis — that the primary problem is high cost — has been complicated. The actual problem pattern across interviews is: difficulty finding a tutor quickly, pricing opacity, and scheduling inflexibility. Cost is real but is not always the primary barrier.
She revises her hypothesis: "Students and families preparing for standardized tests struggle to find qualified tutors quickly, compare pricing clearly, and schedule sessions around existing commitments." This is a more specific problem description than she started with, and it suggests that a service solving only the price problem would leave the discovery and scheduling problems unsolved.
She now has a much clearer direction for a minimum viable landing page experiment: describe a service that solves the discovery and scheduling problems explicitly, with transparent pricing, and see whether families will pay a deposit to join a waitlist.
Output Assets (drafts to produce)
Interview script — A one-page printable problem interview guide with the five core question types (behavior, pain point, previous attempt, abandonment reason, frequency), space for exact quote capture, and a post-interview debrief section with three questions: What surprised you? What assumption was confirmed? What assumption was challenged?
Landing page checklist — A single-page checklist for a minimum viable landing page with components: one-sentence problem statement, solution description (three bullet maximum), specific price, single call to action (deposit, waitlist, or direct purchase), honesty statement about product status, and one social proof element (if available). Includes a "what not to include" section: vague value propositions, claim-heavy language without specifics, multiple calls to action.
Pricing experiment tracker — A simple table with columns: date, audience, pricing option presented, reaction (quote), signal level (strong/moderate/weak/negative), and notes. Designed for five to ten pricing conversations before a landing page launch.
Public-Copy Candidate Summary (post-review)
From Idea to First Customer teaches the evidence-first discipline of early-stage entrepreneurship: learning about a real customer problem before building a solution, running a pricing and landing page test before spending on development, and treating product-market fit as a learning loop rather than a single discovery moment. The customer interview method at the center of this talk is practical, low-cost, and designed to produce honest findings rather than comfortable validation. Suitable for teenagers building their first business, adult founders, and anyone at a small organization who wants to stop building things nobody uses.
Cross-Surface Links
- Koydo Catalyst — Entrepreneurship track with interview guide, landing page checklist, and pricing experiment tracker (first-customer-interview module)
- Koydo Catalyst — AI Builder Workflows track for founders connecting product thinking to technical execution
- Koydo Mentor — Career skills track with workplace communication tools for early-stage team builders
- Koydo Certifications — Entrepreneurship fundamentals certification path (pending)