In real-world startups, you need to work at warp speed. User research has to keep up with development’s need for decisions — not slow it down.
User development and buyer research are critical disciplines that separate guesswork from informed product decisions. The trap most PMs fall into is either ignoring research because it feels slow or doing shallow surveys and focus groups that produce noise, not insight.
The actual job is to learn what real users and buyers think, feel, and do — quickly enough to influence your roadmap and design choices. You cannot afford to run months-long studies when your startup demands features yesterday. But skipping research entirely is a recipe for building the wrong thing.
This lesson gives you a practical approach to user development and buyer research that fits the pace and constraints of Indian startups and enterprises alike.
User research at warp speed is not a contradiction
Startups move fast. Waiting weeks for focus groups or large-scale surveys is often impossible. You need to tweak your research process to deliver insights in days, not months.
Focus groups and online surveys mostly fail in early-stage product research. Focus groups tend to be hijacked by loud participants, and they reveal more about differences between people than common patterns. Online surveys impose forced-choice answers that obscure the subtle, unexpected insights you need.
What works better is a blend of two approaches:
-
Extended, one-on-one, open-format interviews. Face-to-face if possible, phone otherwise. Use a loose question list that invites long answers: "Describe your needs in your own words," "How else would you solve this problem?" "How would you value a solution?" "What do you like and dislike about our current approach?" The goal is to pan for golden insights, not check boxes.
-
Narrow, goal-directed, lean startup style, single-issue research. When you suspect a specific problem — say, users struggle with your sign-up flow — focus tightly on that. Pull a list of relevant customers or prospects, reach out personally, and ask for 15 minutes to understand their experience. Confirm they fit your audience, then ask: "What were you thinking when you tried to sign up?" or "What were you trying to accomplish at that point?" Avoid sounding like you are spying by not parroting system logs.
If you do three extended interviews per week, you will know your customer base better than anyone else in 3-4 weeks.
The research approach depends on your product and stage
User research is not one-size-fits-all. It depends on your product type, company maturity, and decision time horizon.
For web products, ask:
-
Is this a consumer product or do you have business stakeholders like partners or vendors?
-
Are you trying to learn about customer interests or actual user behavior?
-
How soon do you need to make decisions?
User development starts with a germ of an idea. Maybe a customer hinted at a feature, or you saw a competitor’s innovation that sparks a thought. You then refine the idea with a clear value proposition and simple feature outline.
Socialize the idea widely inside your product, technology, sales, and marketing teams. Include stakeholders early to get their input and build alignment.
Size the market opportunity and write a press release as if the product already launched. This helps crystallize your vision and assumptions. (For more on this, see Marty Cagan’s Inspired and Naeem Zafar’s Market Research on a Shoestring.)
When to apply quantitative vs qualitative research
If you have a large budget, plenty of time, and a risk-averse organization, you might sequentially conduct:
-
Surveys to get quantitative insights on customer perceptions and needs.
-
Focus groups to build on survey findings with qualitative depth.
-
Prototype testing with eye-tracking and task completion to measure usability.
-
A/B testing to compare different implementations against key metrics.
-
Ongoing analytics to track long-term user behavior.
But for most startups and product refinements, this is overkill. The bottom line is:
-
If it’s low-effort and low-risk, throw it out there and test it in the market.
-
If it’s a larger effort, line up your customers, sell the concept before you build, and use research to refine your implementation.
Buyer research is a different challenge
In B2B and enterprise products, users are only half the equation. You also need to solve problems for the buyers and decision-makers — the people who write the checks.
The single best way to get information from buyers is to sit in a room with them and ask targeted, probing questions. Your goal is to understand their problems, needs, and goals deeply.
This is easier when you already have relationships with these buyers. But if you only talk to existing customers, you ignore the most profitable segment: those you have not sold to yet.
Therefore, spend most of your time trying to talk to potential customers. This is hard.
-
Executives are protected from non-urgent meetings.
-
Cold outreach often gets ignored or viewed as a sales pitch.
-
You may need to travel extensively to meet them in person.
-
$50 gift cards or small incentives will not work at this level.
-
Sales teams want to join calls and pitch, which invalidates your research.
To succeed:
-
Build a solid understanding of the buyer’s core problem.
-
Source a list of potential candidates from CRM tools, LinkedIn, social channels, and your network.
-
Prioritize candidates connected to you (2nd/3rd level on LinkedIn).
-
Reach out via phone, email, and social media in that order.
-
Prepare a succinct pitch that shows you understand their domain and pain points.
-
Offer something of value in return — coffee, lunch, or future discounts.
-
Be patient and persistent. The first time I sent 40 LinkedIn InMails and got only one response.
If you do this well, you build a network of contacts, advisors, and potential customers.
Tips for conducting effective user sessions
When inviting users for interviews or testing:
-
Invite a select group: current customers, potential customers, influencers, and even random individuals unfamiliar with your product.
-
Conduct sessions in person or over phone with screen sharing.
-
Early morning sessions are best: participants are more energetic, and breakfast is cheaper than lunch.
-
Compensate participants fairly: $20/hour for in-person, plus a $5 gift card for phone participants.
-
Prepare rough wireframes and high-level product specs to guide the conversation.
-
Encourage questions and short conversations throughout to keep users engaged and avoid a long Q&A at the end.
-
Include usability and behavioral questions such as "Do you know where to click for this?" or "How would you open that?"
-
Track time spent on each screen or slide, normalizing for complexity.
-
Conduct at least two sessions per test to get better averages.
-
Debrief immediately with facilitators and scribes.
Doing this earns credibility with developers — showing you can answer real customer questions fast is almost as valuable as coding.
Synthesizing research: turning data into decisions
Conducting research is only half the job. You must synthesize your findings clearly and simply to influence your team.
Two tools I use repeatedly to convey market and competitive research are:
The 2×2 matrix
This visual tool simplifies complex competitive landscapes into two axes you define. It helps answer: How will we fit into the market?
Steve Jobs famously used a 2×2 to explain why competitors’ phones were inferior and to focus Apple’s product lineup.
You can customize the axes based on your product’s context and plot competitors and your product accordingly.
Feature Gap Analysis
This is a detailed table comparing your product’s features or value propositions against competitors.
Use “harvey balls” or similar symbols to indicate how well each product performs on each feature.
Look for gaps in competitors’ offerings that you can exploit.
This analysis also guides marketing and branding — focusing on your unique benefits and strengths.
Research synthesis reading
For more on synthesizing research, see:
The trap of ignoring context and pace
User research is not a luxury. It is the foundation for building products that matter.
That said, the way you do research must fit your product’s stage and your company’s culture.
Early-stage startups move fast and tolerate risk. You must deliver fast, focused insights.
Later-stage companies with bigger budgets and risk aversion can afford more exhaustive research.
Convincing stakeholders to invest in research often means appealing to their heart, head, or wallet:
-
Show them the human stories and pain points (heart).
-
Present data and patterns that prove a problem exists (head).
-
Quantify the cost of building the wrong thing or missing market opportunity (wallet).
Test yourself: Buyer research in a manufacturing SaaS startup
You are a PM at a Series A SaaS startup targeting manufacturing firms in Pune. You need to understand the buying process for your product, which targets VPs of Sales in these firms. You have limited access to buyers, and sales wants to join all calls.
The call: How do you approach buyer research effectively without compromising data quality or sales relationships?
Your reasoning:
Where to go next
-
If you want to master user research techniques: User Research Methods
-
If you want to learn how to synthesize and communicate research: Research Synthesis Techniques
-
If you want to understand buyer personas and B2B research: Buyer Research and Personas
-
If you want to apply research to product discovery: Product Discovery and Validation
-
If you want to build a strong product vision from insights: Product Vision and Strategy