There's a version of onboarding feedback that treats signup as the moment. One question fires the second someone creates an account, you catch their expectations before the product overwrites them, done. That's real, and it's worth doing. I wrote about it separately in what to ask users after they sign up, because that opening window is genuinely its own thing.
But the first week isn't one moment. It's a week. And a lot of what decides whether someone sticks around happens in the days between "created an account" and "this is now part of how I work," which is exactly the stretch most feedback programs skip. They ask on day zero, then go quiet until an NPS email three months later, by which point the person has either activated or churned and nobody asked them anything while it was being decided.
The first week is a sequence of different people
The user on day one and the user on day five are not the same person answering the same question. On day one they're guessing. They have hopes, a vague plan, and no experience of the product. By day five they've either hit the thing that made the product click for them or they've bounced off something and started drifting. Asking both of them "how's it going?" gets you two answers that mean completely different things.
So the useful move is to stop thinking about "the onboarding survey" as a single event and start thinking about which question belongs at which point. Not on a fixed timer either. Tie it to what the person has actually done, because that's what tells you where they are.
Right after signup: what did you come here to do
This is the expectations question, and it belongs in the first few minutes. What are you hoping to get done? What were you using before? The answers are about context rather than the product, which is right, because they haven't used the product yet. You're capturing the picture in their head before reality edits it.
Keep it to one question, maybe two. Someone who just signed up has zero patience for a form, and a wall of questions at this moment is the fastest way to teach a new user that your prompts are worth ignoring.
At the activation moment: did that do what you wanted
Every product has a moment where it clicks. Sending the first campaign, connecting the first integration, getting the first report, whatever "aha" looks like for you. That moment is the single best time to ask a question, and almost nobody does it, because it's harder to build than a timed email.
Right after a user completes that first meaningful action, a short "did that do what you expected?" catches something you can't get any other way. If the answer is no, you've found a gap between what the feature promises and what it delivers, from a person who was motivated enough to reach it. That's high-grade signal. If the answer is yes, you've confirmed your activation moment is actually landing, which is worth knowing too.
The reason to tie this to the action rather than the calendar is that users activate on wildly different schedules. One person gets there in twenty minutes, another takes four days. A day-two email asking about a feature the second person hasn't touched yet is noise. A prompt that fires when they finish the action is always on time. Timing a question well matters as much as the question you ask, and the activation moment is where that's most obvious.
Mid-week: what got in the way
By day three or four, the users who are going to struggle have usually hit their wall. Something confused them, some setup step didn't fit their situation, some feature they expected wasn't where they looked. This is the moment to ask an open question and actually leave room for an answer. "What's been harder than it should be so far?" or "anything you got stuck on?"
The people who reply here are handing you your onboarding friction list, ranked by whatever annoyed them enough to type. The people who don't reply aren't necessarily happy, but the ones who do are pointing straight at the parts of your first-run experience that leak users. This is also where you find out that the thing your team argued about for a month isn't what anyone's actually stuck on.
End of the week: was this worth it
By day six or seven, someone has enough experience to make an early judgment. Not a final verdict, but a real one. A single question here, light and easy to answer, tells you whether the first week did its job. "One week in, is this looking like it'll be useful for you?" And if they say no, a follow-up box asking why is where the actual reason lives.
Not nagging is a design constraint, not an afterthought
Four touchpoints in a week sounds like a lot, and it would be if each one were a five-question survey. The whole thing only works because each ask is small and tied to something the person just did, so it reads as relevant rather than random. One question at signup, one at activation, one open prompt mid-week, one light check at the end. Skip anyone who's clearly disengaged rather than chasing them. A user who hasn't logged in since day one doesn't need your day-five email, they need a different conversation entirely.
The output of all this is a pile of short answers arriving on different days from different people at different stages, which is genuinely hard to read by hand once you have more than a handful of new signups a week. This is where Qria earns its place: it pulls the structured responses together with whatever's showing up in your public reviews and reads the open text for you, so instead of a spreadsheet of first-week answers you get a summary of what new users keep saying they came for, where they keep getting stuck, and what's actually clicking. For the broader picture of running feedback in a product context, the SaaS feedback guide covers how this fits alongside NPS, churn surveys, and the rest.
The first week is when a new user decides whether you're going to be part of their working life or a tab they forget to close. That's a lot to leave to a single day-zero email.
