How to Collect Customer Feedback Before You Have Customers
The conventional model of customer feedback collection assumes customers: survey users, conduct interviews, analyze support tickets, review NPS responses. This model works well once a product has launched and a user base has developed. Before that point — when the product is being designed, when the fundamental user needs are being defined, when the strategic direction is being established — the conventional model doesn’t apply.
The answer isn’t to defer customer feedback until after launch. Products built without customer insight are far more likely to fail than those grounded in user understanding from the earliest stages. The answer is to collect customer feedback using methods that don’t require an existing customer base.
Method 1: Problem Interviews
Before any product exists, problem interviews investigate whether the problem you’re proposing to solve is real, significant, and common enough to warrant building a product around. Interview people in the target market about their current experience with the problem space: how they currently address the challenge, where the friction is, how significant it is, and what solutions they’ve tried.
The discovery that a significant number of target market members have the problem, that existing solutions are inadequate, and that there’s genuine willingness to adopt alternatives is the validation that justifies product investment.
Method 2: Competitive Product Analysis
Users of competitive products are a proxy for your potential users. Their reviews, their questions in community forums, their feature requests, and the pain points they express about competitive products are a form of customer feedback about the problem space your product will enter.
Mining this data — systematically reviewing competitive product reviews, community discussions, and feature request patterns — produces genuine user intelligence without requiring any existing relationship with users.
Method 3: Fake Door Tests
A fake door test presents a potential product or feature as if it exists, then measures interest before the product is built. A landing page describing a product capability, a sign-up form for a waitlist, or an in-app button for an unbuilt feature — each of these tests genuine user interest in a way that asking about hypothetical interest doesn’t.
The behavioral signal (clicking, signing up, requesting) is more reliable than the verbal signal (saying they would use it), because it requires real commitment rather than hypothetical prediction.
Method 4: Advisory Groups and Expert Interviews
For products targeting specific professional markets, potential users who are domain experts can provide sophisticated feedback on whether the proposed product would genuinely serve the domain’s needs — before any user base exists.
Assembling advisory groups from the target market, or conducting expert interviews with practitioners who represent the intended user, produces the domain knowledge that would otherwise only be available through user research with actual customers.
Method 5: Prototype Testing With Non-Users
Prototypes — whether wireframes, interactive mockups, or functional prototypes — can be tested with people who match your target user profile even before they become customers. Recruiting from professional networks, industry communities, or adjacent user populations provides representative feedback on whether the product design addresses the user need effectively.
Key Takeaways
Customer feedback doesn’t require customers. Problem interviews, competitive product analysis, fake door tests, expert advisory groups, and prototype testing with target-profile non-users collectively provide the user intelligence that grounds product decisions from the earliest stages. Building the habit of seeking this feedback before launch, rather than waiting until after it, produces products that are more likely to succeed because they were designed with genuine user understanding from their inception.
Asynchronous Culture as a Competitive Advantage
Teams that develop genuinely strong async communication practices — where written updates are comprehensive, where decisions are documented, and where teammates can be productive without real-time synchronization — often discover that their distributed nature becomes a competitive advantage rather than a compromise. The talent diversity enabled by geographic distribution, the time-zone coverage that enables faster response to global user needs, and the documentation discipline that makes organizational knowledge explicit can all create genuine business advantages that offset the coordination costs of distribution.