How to Learn from Early B2B Product Users

How to Learn from Early B2B Product UsersHow to Learn from Early B2B Product Users

The network for creativity

Join 1.25M professional creatives like you

Connect with clients, get discovered, and run your business 100% commission-free

Creatives on Contra have earned over $150M and we are just getting started

Back to feedPost

Kaleab Eshetu

max

• Sep 29

i once worked with a founder who was about to start testing his product with 4–5 real industry users.

they were super early and b2b btw.

then his internal team started talking about analytics

→ what should we track? → what KPIs matter? → what should go into posthog?

i had to weigh in, “it’s too early for that” i said.

told them that at this stage (honestly at any stage) we had to do only 2 things…

1. watch what they do

→ where they stopped → what confused them → what they completely ignored

2. talk to them

→ we’ll understand the problem we’re solving better → we build rapport and trust. they tell us what’s actually bothering them

that’s it.

you don’t need more data, especially when you’re this early.

pink kids product

Kaleab Eshetu

max

• Sep 29

p.s. images not related to the project i was talking about 🧐.

[context for images] calendar design for JustLiv.

a planning and booking platform that helps parents find, schedule, and manage their kids’ activities.

Roman Avshalumov

max

• 1d

AI startups are in a peculiar position:

1. People need AI products. 2. People are fatigued and skeptical of AI products. Address the AI skepticism by showing, not making claims: put one CTA in the hero - a prompt box.

They try the product before creating an account. By the time you ask for a signup, they’re already hooked.

saas Web Design Brand Strategy

Gonzalo Hernandez

• 1d

One catch: an empty prompt box leaves people stuck on what to type. A few one-click example prompts fix that.

Francis Favour

• 10h

Adding more features doesn't mean you're building a better product. You're just giving users more things to figure out. I've seen products introduce so many features in the name of innovation that the original purpose gets lost. Founders, please stop treating every new idea as a feature request. 😂 Your users don't need to see how much your product can do. They need to understand what it does, how it helps them, and how to use it without getting confused. Especially at the early stages, familiarity is more valuable than complexity. Build something people understand before building something that does everything.