

When you’re building a product in a small startup, “doing discovery” sounds easy in theory - talk to users, test ideas, learn, iterate.
But how can we leverage even the initial first batch of early customers? Welcome to early-stage product discovery.
This is how we did it at Solid.
Your sales calls are gold mines. Every conversation reveals what excites people, what confuses them, and what makes them hesitate.
When you listen, focus on:
👉 Don’t rely on AI summaries alone! They miss nuance.
Listen to the leads’ tone and emotion, replay important snippets, and note the exact words they use. Those words will later shape your positioning and messaging.
Sit in on every conversation you can. At Solid, I asked Yoni, our CEO, to join sales calls and dedicate 10 minutes at the end of each one specifically for product discovery. Customers often open up more after the formal pitch is done, and the insights you’ll get from these unscripted moments are pure discovery magic.
Don’t wait for a UX team or user researchers - be your own researcher.
Talk to:
👉 End every call with, “Who else should I talk to?” - it keeps the momentum going.

Talk to Your Users Every Week, Even If You Only Have a Few
Even if you have just a few customers - make it a weekly habit to talk to them.
You don’t need a big user base to learn. Each conversation helps you see your product through fresh eyes. Rotate who you speak with so every week you meet someone new, and focus on understanding how they actually use the system, what’s working for them, and what’s missing.
These short (30 min Zoom call), honest conversations often reveal things no dashboard ever will:
Summarize your findings on a monthly basis and share them with your customers. Data leaders appreciated learning how their teams are using the product, what challenges they face, and what they are currently focusing on - it gives them valuable visibility into their own organization.

Talk is great, but nothing beats watching how people actually use your product.
Record sessions using tools like Amplitude, Mixpanel, Heap, etc. Observe workflows. See where users hesitate or take unexpected paths.
Summarize the most interesting sessions and share them with your colleagues. At Solid, this has been a powerful way to identify issues that often turn into Jira tickets. It’s also been one of the biggest drivers behind continuously improving our chat capabilities.

Those small moments reveal what no interview ever will.
The best time to ask for feedback is right when users need help or are trying something new.
Add micro-feedback prompts inside the product - short, contextual, and easy to answer.
Example: “Was this result helpful?” or “Did you find what you were looking for?”
At Solid, we added a simple thumbs-up/thumbs-down option to collect feedback on every chat response, along with an optional field for users to explain why a response was good or bad. This feedback often results in Jira tickets, helping us continuously improve the product.
However, we realized that the vast majority of users do not click on these thumbs. To address this, we worked closely with our customer’s champions, explained how critical this feedback loop is to the success of the deployment - and they helped drive adoption by promoting it internally.

Well, there are tons of blog posts, articles, podcasts, and meetups that cover this topic, but here are the principles I cherish most:

Building great products in early-stage startups isn’t about having a big research team - it’s about curiosity, empathy, and making the most of every conversation.
When you learn fast from a few users, you’ll be amazed how far that small sample can take you.