firstthousandusers
  1. Idea and validation
  2. Waitlist
  3. Private beta
  4. Launch
  5. First 100 users
  6. First 1,000 users
Direct outreach

Onboard every beta user on a call

Set up the first users yourself on a short call and note where they get stuck.

What's required30 minutes per user, plus 10 minutes to write notes right after.
Accounts
A free Calendly or Cal.com account, and Zoom or Google Meet.
Assets
A booking link with 20–30 minute slots, a notes template, a short list of questions.
Time
30 minutes per user, plus 10 minutes to write notes right after.
Cost
Free.
Prerequisites
A beta people can sign up for, and a way to reach new signups by email.

What to do

  1. Put a booking link in your welcome email. Use a free Calendly or Cal.com link with 20–30 minute slots. Write the email yourself, from your own address: “I’m the founder. I’d like to set you up personally and see where it’s confusing. Grab any slot here: [link].” See personal welcome emails for wording.
  2. Offer slots that fit their day, and not too many. Open 5–10 slots a week across a couple of time zones. A limited calendar looks like a real person, and a full-looking calendar gets more bookings than an empty one.
  3. Ask for permission to record at the start. “Mind if I record this so I can re-watch where things were unclear? It won’t be shared.” Most people say yes. If they hesitate, just take notes.
  4. Spend the first five minutes on their situation, not the product. Ask what they do, how they handle the problem today, and what made them sign up. This tells you whether they are the user you built for and gives context for everything that follows.
  5. Have them share their screen and drive. Ask them to sign in and do the first real task with their own data. Say: “Pretend I’m not here. Think out loud as you go.”
  6. Do not help unless they are truly stuck. Stay quiet when they hesitate. Count to ten before stepping in. Every pause, wrong click and “wait, where is…” is a bug report you cannot get any other way. When you do help, write down exactly where and why.
  7. Finish with a real result. Make sure they leave the call with the product working for them: a first project created, data imported, the first report sent. Users who reach a result on the call are much more likely to come back.
  8. Ask two questions before hanging up. “What would make you stop using this?” and “Who else do you know who has this problem?” The second one is the start of your referrals; ask them to introduce you by email while it is fresh.
  9. Write notes within ten minutes and fix the top issue that week. Log stuck moments, questions and exact quotes in one shared doc. When the same stuck moment shows up in three calls, fix it before the next batch.

Templates

Notes template, one per call:

Name / role / company size:
How they handle the problem today:
Why they signed up:
Stuck moments (timestamp, what happened):
Questions they asked:
Exact quotes worth keeping:
Reached first result? yes / no
Who else should use this:
Top fix from this call:

Follow-up email, same day:

Thanks for the time today, [name]. I’ve already fixed [small thing you noticed]. The [bigger thing] is on my list for this week. If anything else feels off, just reply to this email, it comes straight to me.

Why it works

Watching someone use your product shows problems they would never report, because most people quietly leave instead of writing in. Being on the call also means each user reaches a working result, so more of them stay. And people you helped personally are much more willing to refer friends, give testimonials and answer later questions.

How it gets users

Directly, very few: you can only do a handful of calls a week. Often a noticeable share of new signups book a call when the founder offers personally, and many of those become active users, which is far better than unassisted signups. The bigger effect is indirect: after 10–20 calls, your onboarding is usually much clearer, so every future signup from every other channel converts better. Most founders also get a few warm introductions from the “who else” question.

Common mistakes

  • Giving a demo instead of watching them use it.
  • Jumping in to help the moment they pause.
  • Using an impersonal “Book a demo” button from a no-reply address instead of a note from you.
  • Not writing notes right after, then forgetting what went wrong.
  • Collecting the same complaint in five calls without fixing it.
  • Skipping the “who else should use this” question.

Next steps

This guide is connected to these guides on the map. Numbered ones come next.

01 Idea02 Waitlist03 Beta04 Launch05 First 10006 First 1kCold outreach to your first 20 users1Ask your users for referrals2Email every new signup personally3This guide03 Beta04 Launch05 First 100Cold outreach to your first 20 users1Ask your users for referrals2Email every new signup personally3This guide
  1. 103 Private beta · Direct outreachCold outreach to your first 20 usersFind 20 specific people who have the problem, write to each of them individually, and offer to set them up yourself.
  2. 205 First 100 users · Direct outreachAsk your users for referralsAsk users who got value from the product to introduce it to one specific person, right after they got that value.
  3. 305 First 100 users · Direct outreachEmail every new signup personallySend each new user a short personal email asking why they signed up, and reply to every answer.