Getting first users: 10 trials and what the calls taught me
by Richard Lovatt · updated 22 October 2026
Getting your first ten users comes from one-to-one outreach, not a funnel. I hit ten card-in trials on Underway by messaging people directly, offering a phone call before pitching anything, and only inviting the ones with a real use case onto a podcast interview. The calls taught me more about where people get stuck than the dashboard ever did.
In short
- Ten card-in trials is a real milestone, but it is not ten payments yet
- Reaching out one by one beats waiting for people to come to you, and most people will not want to talk
- A phone call before any pitch shows you exactly where someone gets stuck
- Freestyle Q&A surfaces problems you would never have thought to ask about
- One-to-one calls do not scale past the first handful of users, so plan the community rhythm early
Reaching the ten trial milestone
When I started this series I set the goal of getting to ten, and I genuinely could not tell you any more whether I meant ten users or ten paying users. I have now got to ten genuine humans trialling Underway, card in, which is its own kind of proof: they potentially could all turn into ten payments if they do not cancel.
I think it is a big milestone, and I say that carefully because a trial is not a sale. It is a strong signal that I am past the is anyone even interested stage, but it is not revenue, and I am not going to pretend otherwise on camera or off it.

Reaching out to the first users
I reached out to a bunch of the trial users myself, and it is quite funny because not everyone is so interested to speak. You realise quickly that signing up for a free trial and wanting a conversation with the founder are two completely different levels of interest, and most people sit at the first one.
Even so, I have had conversations on the phone with a couple of people, and a Google Meet interview with one of them, Ryan, who owns a very large clothing brand. I am not sure yet what he is documenting on Underway, but the conversation itself was worth having, because it was Ryan who gave me the idea that follows.
Two ways I run the calls
There are two ways this goes. One is a brief chat before I even ask about anything else, just to hear their story and what they are doing. The other is an actual interview, recorded as a podcast episode inside Underway, if they are up for it.
I only move from the first to the second once I have a good understanding of what someone is doing and think it is a good idea. The interview itself is them sharing their screen, going through what they are building, and talking about how Underway is helping them, not me talking at them.
That order matters to me. Offering help first, before asking for anything, is the only way I would want to be approached myself.
What the calls taught me
What I realised from both of the proper calls I have had is something I think is just true of humans. Both people wanted me to help them before they had had a go themselves, and I do not see that as a bad thing. New software is overwhelming, and I am exactly the same when I join anything new: overcoming that first bit of friction is hard for me too.
Neither of them had really tried clicking this or clicking that first, and that is fine. Right now, with ten users coming through, I am absolutely happy to just show people and direct them, because that is what people need at the end of the day, to feel like they have got help.
It has helped me as well, in terms of where I can improve things. The person I spoke to on the Google Meet call had a genuine application he wanted to run, and it made me actually change the code base for him.

Turning users into interviews
Ryan's call gave me an idea I had not properly used before, even though the feature already existed: Underway has a podcast section where you can invite people and run an actual episode with a guest. So why not interview Underway users directly and hear from them on what they are documenting, rather than guessing.
In a perfect world I would do this frequently, scheduled, maybe every Monday. But for now I am starting lightweight: reach out, see who is game, and let it grow into a rhythm if it clicks, rather than forcing a format before I have enough willing people.
The flow stays the same as the calls above: chat first, interview only when I think it is a good idea and they are comfortable, then the episode is them sharing their screen and talking through how Underway is helping their work, which keeps it useful rather than extractive.
Community calls at scale
At ten users I can offer everyone a call. That will not hold once there are more. One thing I have thought of doing at scale is a Monday, Wednesday and Friday community call where people can jump in and I can tutorial for them and walk them through things, rather than doing it one-to-one every time.
That keeps the one-to-one help for the handful of people I can reach now, and turns it into a structured rhythm later without me doing endless individual calls. It could double as onboarding and discovery at the same time, since the questions people bring in a group setting are usually the same questions everyone else has too.

Lessons versus freestyle Q&A
For those future community calls, I thought about making them lesson-oriented, like setting up, or recording your first session, almost like a short course. I could build that properly, a tutorial from the ground up: this is how you do this.
But I think there is a lot of value in just freestyle Q&A, how would I do X, how would I do Y, because there are so many things and ways it works that I would never predict them all in a lesson plan. Freestyle brings real, messy problems you could not have anticipated.
If I want a bit of shape without losing that, I would open with a tiny demo or a today's tip for a few minutes, then hand it over to questions. That gives people something concrete to start from without turning the whole call into a script.

Questions people ask
Should first user calls be lesson-oriented or freestyle Q&A?
I lean towards freestyle because it surfaces the messy, specific problems a lesson plan would never anticipate. A lesson-oriented structure, like setting up or recording your first session, still has a place, but mostly as a short opener before handing the call over to questions.
How do you turn early users into content without it feeling extractive?
I call people first, with no camera and no pitch, just to hear their story and offer help. Only once I understand what they are doing and think it would be useful do I invite them onto an actual podcast episode, where they share their screen and talk about how the product is helping them.
What do you do once one-to-one calls stop scaling?
My plan is a Monday, Wednesday and Friday community call where people can jump in and I walk them through things as a group instead of individually. It keeps the help going without needing a call per person.
Is a card-in trial a better signal than a free sign-up?
Yes, in my experience people who put a card in behave differently, they have more skin in the game. Getting to ten genuine card-in trials felt far more meaningful to me than any number of free, no-card sign-ups would have.
What's the most common thing that trips up new users?
Both people I spoke to wanted me to explain how to do something before they had tried clicking around themselves. I think that is just how people are with new software, including me, so I now expect it and I am happy to just show someone directly rather than treating it as a flaw in the product.