← Blog

Onboarding survey questions for new users

Five short questions to ask in a new user’s first session, and how each answer should change the first steps they see in your product.

Stiro team ·

A new user signs up and your app asks them a few questions: what’s your role, what brings you here, how big is your team. They answer, press continue, and land on the same dashboard everyone else gets. The answers go into a spreadsheet and nothing about their first session changes.

That is a missed chance. A short onboarding survey is one of the few moments a new user will happily tell you what they want. If the answers shape what they see next, they reach something useful sooner. If they don’t, the survey is just one more screen between sign-up and the product.

This post gives you five questions worth asking in the first session, and what each answer should change.

Keep it short and make every answer count

Before choosing questions, set two rules for the survey itself.

  • Every question must change something. If no answer to a question would change the user’s first steps, drop it or ask it later. Questions asked only for your marketing team belong in a later email, not in the way of setup.
  • Five questions at most, one tap each. Use choices rather than free text, with an “Other” option and a way to skip. A user who wants to get going should be able to finish in well under a minute.

Ask on one or two screens straight after sign-up, before the empty dashboard. Say why you’re asking: “Tell us a little about you and we’ll set things up to match.” Then keep that promise.

The five questions

1. What’s your role?

Offer the three to six roles that actually use your product differently, such as “Founder”, “Manager”, “Sales”, “Support” or “Developer”. Don’t list job titles for their own sake. Each role should map to a different first screen or first task.

What it should change: the default view and the first task. A manager might land on a team overview with “invite your team” as step one. Someone in sales might go straight to importing contacts. A developer might see the API key and install steps first.

2. What do you want to get done first?

This is the most useful question in the survey. Offer the four or five jobs most people sign up for, written as outcomes: “Book meetings with clients”, “Track my team’s projects”, “Send invoices”. Keep the wording in your users’ terms, not your feature names.

What it should change: the checklist. Put the steps for that job at the top of your setup checklist and hide the rest until later. If someone picked “Send invoices”, the first three steps should be adding a client, creating an invoice and connecting payments, not customising their profile.

3. How big is your team?

Use simple ranges: “Just me”, “2 to 10”, “11 to 50”, “More than 50”. You only need enough detail to tell solo users from teams.

What it should change: whether teammates show up in setup at all. A solo user doesn’t need an invite step in their first session, and asking for one feels like a hurdle. For a team, the invite belongs early, with the roles explained. Why users don’t invite teammates covers how to make that step work.

4. Which tools do you use today?

List the handful of tools your users most often move from or connect to, by category if you prefer: “Spreadsheets”, “Another CRM”, “A calendar app”, “Nothing yet”. Let them pick more than one.

What it should change: whether setup starts with an import or a blank start. Someone coming from spreadsheets should see “Import your list” as the main action. Someone using a calendar app should be offered the connection on day one. Someone with “Nothing yet” needs sensible defaults and a simple first item, which our post on empty states covers.

5. Have you used a tool like this before?

Three choices are enough: “Yes, often”, “A little”, “No, this is new to me”.

What it should change: how much you explain. Experienced users want shortcuts and the advanced settings close at hand. New users need plain words, fewer choices on screen, and a clear next step after each one. This answer is also a good guide to who might want a call with your team.

From answers to first steps

The survey only pays off if its answers are wired to what the user sees. A table like this, filled in for your own product, is a good way to agree it as a team:

Answer What the user sees first
Role: manager Team view, invite step early
Goal: send invoices Checklist starts with client, invoice, payments
Team: just me No invite step in the first session
Tools: spreadsheets Import as the main action
New to tools like this Fewer options, plain wording, help close by
From survey to first result
  1. Step 1AskFive one-tap questions after sign-up
  2. Step 2Pick the pathGoal and role set the checklist
  3. Step 3Trim the stepsHide what this user doesn’t need yet
  4. Step 4Do the first jobThe step that gets them a result
  5. Step 5Check it workedCount who finishes, by answer

Then measure it. Split your setup funnel by each answer and see which groups still stall. If users who picked “Send invoices” keep dropping out at connecting payments, that is the step to fix next. Where new users stall in setup shows how to build that funnel, and the SaaS onboarding flow template helps you map a path for each kind of user.

How an in-app agent like Stiro does the matching setup

A good survey tells you what each user needs. The hard part is still the setup itself. Knowing that a user wants to send invoices and uses spreadsheets doesn’t import their client list for them. An in-app AI agent fits here: the user asks for the result in plain words, and the agent does the steps in your app.

Stiro is one. You add it with one script tag, with nothing to train and no flows to record. A user who said they want to book meetings with clients can type or say “set up a 30 minute intro call I can share”, and Stiro clicks, types and moves through your real interface to create it while they watch. Your survey picks the path, and Stiro walks it with them when they ask.

  • It works on the screens you have. Stiro reads the live screen, so when your setup flow changes after you act on the survey results, there is nothing to update.
  • It says so when it can’t. If a request isn’t possible in your app, it stops, explains why and changes nothing.
  • The user keeps the final say. Anything that sends, spends or deletes is set up and handed back for them to press.
  • Stuck goes to your team. If it can’t finish, a signed-in user can message your team or your help desk from the same panel.

We tested Stiro cold in three open-source apps it had never seen, a CRM, a project tracker and a scheduling app, and checked every result in the app’s own database:

requests done, first run, cold
44 of 44
on a repeat run of the same code
43 of 44
median time from request to reply
19.5 s
Source: Stiro benchmark

The benchmark lists every task and the reply Stiro gave.

Ask less, change more

Five questions are plenty: role, first goal, team size, current tools and experience. Ask them in one short step, wire each answer to what the user sees next, and check which groups still stall. When users know what they want but not where to click, let them ask. Stiro does those setup steps in your app, and the free plan includes 50 runs a month, so you can try it on your own onboarding first.