For SaaS onboarding teams
Ask new users for a testimonial right after their first real win
A user who signed up yesterday has nothing to say yet. A user who just finished the job they bought your product for has a story. Enter the date someone activated and get a dated plan for when to ask, remind and stop.
- Anchored to activation, not to the signup date
- A check-in before the ask, so you only ask happy users
- Reminder spacing that matches StoryProof’s follow-ups
The problem, solved
Why signup-day requests fall flat, and how StoryProof waits for the win
Situation 1 of 4
No outcome yet
Someone still connecting an integration can only describe the setup screen. That is not proof a buyer cares about.
How StoryProof solves it
Contacts and smart lists come with every plan, so a request goes only to the users you add once they hit the milestone, not to every new signup.
Situation 2 of 4
Competing with the welcome sequence
In week one your request lands between the welcome email, the setup tips and the invoice. It is the easiest one to skip.
How StoryProof solves it
From Pro, two spaced reminders resurface a skipped request after the onboarding emails have quietened down, then end as soon as the user replies.
Situation 3 of 4
Asking someone who is stuck
A user who has not activated is more likely to need help than to praise you. Asking first feels tone deaf.
How StoryProof solves it
If a frustrated user answers anyway, from Pro a rating of 2 stars or fewer can alert your team at once and send them a personal apology, and the reply stays private unless you approve it.
Situation 4 of 4
Asking the buyer, not the user
The person who signed up and paid is often not the one who uses the product each day. The admin can only summarise; the daily user has the story.
How StoryProof solves it
The collection link can be shared by hand, so the admin can forward it to the teammate who lives in your product and that person answers directly.
Pick the milestone that means “it worked”
Your anchor is the first moment a user gets the result they signed up for. Some common ones by product type:
Free planner
Plan the ask from the activation date
Enter the date a user hit your milestone. The plan spaces a check-in, the request and two reminders so the ask arrives while the result is still fresh.
Day 0
Milestone reached
Tag the user as activated in your product or CRM. Do not ask yet: give them a few days to see the result land.
Day +4
Check in, no ask
Send a short note asking how it is going and whether anything is in the way. Only users who reply positively, or who show steady usage, move to the next step.
Day +7
Send the testimonial request
Reference the milestone by name, ask two questions (before and after), and offer video, an audio note or a few written lines.
Day +10
First reminder
Three days after the request. Resend the link and say a written answer is fine if recording feels like too much.
Day +14
Last reminder, then stop
Four days after the first reminder. If there is still no reply, leave it until the next natural moment, such as a renewal or a feature launch.
Day +30
Second chance at the next win
For users who did not respond, look for the next milestone in the following month and ask once more around that, not on a calendar date.
Dates are worked out in your browser. Nothing you enter is sent or stored.
In StoryProof
Run the plan in StoryProof
- 1
Write a form around the milestone
Ask what the job looked like before your product and what changed after the milestone. One link accepts a video, an audio note or written text.
- 2
Send the request on day 7
Add the activated user as a contact and send the request by email from StoryProof. Review request emails per month: Free 10, Starter 100, Pro unlimited.
- 3
Let reminders run on their own
On Pro and up, the follow-ups automation sends the day 10 and day 14 reminders for you, stops when the testimonial arrives and respects your quiet hours.
- 4
Approve and tag by milestone
Review each answer before it is public, and tag it with the milestone and plan so you can match stories to prospects later.
What happens next: Approved stories tagged by milestone are ready for the pages where new trial users decide whether to activate.
Before you start
Limits worth knowing
StoryProof does not see your product events
Spotting the milestone happens in your product or CRM. StoryProof sends the request once you add the user as a contact.
Requests go out by email
For in-app asks, paste the collection link into your own in-app message or checklist.
Skip users with an open support ticket
A request in the middle of a problem reads badly. Wait until the ticket is resolved and the user has used the product since.
The day counts are a starting point
The 4, 7, 10 and 14 day spacing suits products used most days. If your users log in weekly, stretch the gaps so each email lands after a real session.
FAQ
Questions people ask
Short answers to what usually comes up next.
How many days after signup should a SaaS company ask for a testimonial?
There is no single number. Anchor on the first meaningful result for that user and ask about a week after it, which may be day 3 for one user and day 40 for another.
Should trial users be asked before they pay?
Only if they have reached the milestone during the trial. A paying customer who has used the product for a while usually gives a more credible answer.
What if the user only wants to give a quick rating?
Let them write a single sentence. A short, specific line about the result is more useful on a website than a long general one.
Should customer success or marketing send the request?
Whoever the user has actually spoken to during onboarding. A request from a person they recognise tends to read as more personal than one from a general marketing address.
Still have a question? Ask the StoryProof team or book a demo.
Ask at the moment it worked
Set up the form, add your first activated users, and let the reminders run.
Last updated 2026-11-04.