How to get your first product users

To find your first product users, identify people with a specific problem, show how your product helps, and invite them to complete one useful task. Watch what happens and improve the invitation or experience before expanding.

Your first objective is learning whether someone can get value—not collecting a large number of registrations.

1. Define one person and one problem

Write down:

This helps [specific audience] do [specific task] when [recognisable situation].

For example:

This helps independent consultants turn a discovery call into a first proposal draft when they need to follow up quickly.

This tells you whom to approach, what to demonstrate and which result matters. If you cannot complete that sentence clearly, start with conversations about the problem.

2. Find people already dealing with it

Look at relevant professional communities, your existing relationships, discussions about the problem and people using a cumbersome workaround.

Build a small research list. Record the person or business, evidence of the problem, appropriate contact route and reason your product might fit. Do not mistake a job title or follower count for evidence of need.

3. Make a personal, specific invitation

Explain why you approached them, what the product does, and the small action you are asking for. Be clear about price and any trial conditions before asking someone to commit.

Example:

Hi [Name], you mentioned that proposals take longer than you would like. I’m building a tool that turns discovery-call notes into a first draft. Would you be open to trying it on one proposal and telling me where it falls short?

Offer a real task rather than asking “What do you think of my startup?” Praise is pleasant; observed use is more informative.

4. Help them reach the first useful result

Choose the action that demonstrates value. For a proposal tool, that might be reviewing a usable draft. For a scheduling product, it might be arranging a real meeting.

If they agree, offer a short walkthrough. Notice where they hesitate, what they misunderstand and whether the result is useful enough to keep. Ask permission before observing or recording a session.

5. Ask about the experience

Useful questions include:

• What were you trying to get done?
• Where did you hesitate or get stuck?
• What would you normally use instead?
• Would you use this again? In what situation?
• If there is a price, what would make it worth paying?

Avoid treating hypothetical enthusiasm as a purchase commitment. Separate requests from people using the product from suggestions made without trying it.

6. Follow up around their next need

Ask whether the task came up again and whether they returned to the product. With permission, follow up when that need is likely to recur.

A weekly reporting tool and an occasional event-planning tool have different natural rhythms. Choose a review period that matches the job rather than forcing every product into a daily-retention target.

Measure the journey

Record the counts and the reasons people stop. A useful conversation can explain a small dataset better than another dashboard.

A one-week working plan

• Days 1–2: define the audience and useful task; identify a manageable group to approach.
• Days 3–4: make personal invitations and help interested people try the task.
• Days 5–6: address observed friction and follow up appropriately.
• Day 7: review what brought people in, what they completed and what to test next.

This is a planning structure, not a promise of users within seven days.

How FirstLook can support discovery

FirstLook can give a product a focused place to be introduced. If someone clicks through, the product still needs a clear explanation and a useful first experience.

Use a showcase as one measured acquisition experiment. Keep customer conversations and product learning running alongside it.

Understand the FirstLook showcase →

Common questions

Choose your next step

Compare places to promote your startup, or explore a FirstLook showcase.