Usertick
SaaS

SaaS surveys for every stage, from the trial to the renewal

Ask users inside your web app and by email when a trial stalls, a feature ships or a renewal comes up. Usertick reads every written answer, files it under the topics software teams track, and sends the ones that need a person to Jira, Linear, Slack or HubSpot.

One place for feedback across the customer lifecycle

A software company hears from users at five moments that shape the business: the trial, onboarding, the first weeks with a new feature, the renewal and the cancellation. SaaS surveys at each of them tell you why people convert, stall, stay or leave, which your product analytics can count but can't explain.

With Usertick, one script tag in your web app shows surveys to signed-in users, and Usertick.identify() passes each user's plan, role and company, so every answer belongs to an account. Your code can open a survey when something happens in the product, and email and link surveys reach the users who aren't signed in.

Every written answer is filed under categories made for software, such as ease of use, integrations and getting started, with a type, a sentiment and an urgency. Workflows send bugs to Jira or Linear, customers about to leave to the account owner in HubSpot, and the answers that can't wait to Slack.

Plans
Website, email and link surveys, Results and AI reading on every plan, the free plan included
Install
One script tag in your web app, with Usertick.identify() for signed-in users
Targeting
Pages and repeat rules on every plan, your own events on 1 survey on Free, user traits and events on every survey from Starter, smart triggers from Pro
Tools
Slack, Microsoft Teams, Jira, Linear, HubSpot, Intercom and Segment on every plan

Ask at each stage of the customer lifecycle

Five moments where a short question explains what the numbers can't.

Before the trial ends

Two days before a trial ends, ask who plans to subscribe and what holds the rest back. Pass the days left as a trait to ask in the app, or email the list of trials that end this week. Trait rules are Starter and above.

When setup is done

Your code tells Usertick when someone finishes setup, and a check-in asks how easy getting started was and what they came to do. Starter and above, and 1 survey on Free.

Two weeks after a feature ships

Ask on the page where a new feature lives whether people have tried it, and what keeps the rest away. To ask only the plans that include it, add a trait rule on Starter and above.

Before the renewal

Email a customer health check to active accounts twice a year, with the first question inside the message, and see who is looking at other tools while there is still time to talk.

In the cancel flow

Show one reason question on the cancel page, above the final button, and one open question about what could have been better. A page rule works on every plan.

Feedback filed the way a product team works

When you choose SaaS at sign-up, Usertick files each written answer under ease of use, speed and reliability, features and gaps, integrations, pricing and plans or getting started, with a theme, a type and an urgency. Rename categories and themes on any plan, and add your own within your plan's limit, from 5 categories on Free to 30 on Business.

Know which account said it

Signed-in users answer as themselves, with the details your app passes.

Ask the users a question is for

Pass plan, role, seats or days since sign-up with Usertick.identify(), and show a survey only to trial admins or to customers on a paid plan. Starter and above.

Every answer with its account

Each answer carries the user's ID, name, email, company and traits, marked Verified when your server signs it. From Starter, the inbox filters by any trait, such as the plan.

Send each answer to the team that owns it

Workflows route answers by their type, their urgency or the customer's plan.

Urgent answers in Slack or Teams

Post answers with high urgency, or from a customer about to leave, to your team's channel, with buttons to assign them or set their status. Every plan.

Bugs to Jira or Linear

Create an issue from each bug report, or one per theme, and once you turn on sync, the response moves to Resolved when the issue is done. Every plan.

Feature requests with the customer attached

Add a request to a Linear issue as a customer request, with the company taken from the email domain, so the roadmap shows who asked. Every plan.

A task for the account owner

Write the latest scores and their reading to the HubSpot contact, and add a follow-up task when a customer sounds ready to leave. Every plan, with the task from Starter.

A weekly report for the company

Send a dashboard with trial, onboarding and NPS scores as a PDF to email, Slack or Teams every week. Pro and above.

Works with the tools software teams use

Send answers to your issue tracker, your CRM, your product analytics and your team chat, so each one lands where the work already happens.

See all integrations

How software companies start with Usertick

Four steps from the script tag to answers in your tools.

  1. 1

    Add Usertick to your web app

    Paste the script tag into your app once, and call Usertick.identify() with each user's ID, plan and company after they sign in.

  2. 2

    Pick the first stages

    Start from Trial check-in, Onboarding feedback, Feature adoption check or Customer health check, or describe what you want to learn to Create with AI.

  3. 3

    Choose the moment and the users

    Open each survey on a page, after an event from your code or on a set day of the trial, and choose how often it can return.

  4. 4

    Route the answers

    Add a workflow that sends bugs to Jira or Linear, urgent answers to Slack and customers about to leave to HubSpot.

How software teams keep surveys useful

Six habits that keep the questions short and the answers specific.

  1. 01

    Ask right after the moment

    Ask about setup when setup ends and about a feature when someone has just used it, while the details are fresh.

  2. 02

    Give each stage its own survey

    Keep trial, onboarding and renewal questions apart, so each score describes one part of the lifecycle.

  3. 03

    Ask the people who decide

    Use traits to keep setup questions for admins and pricing questions for the people who choose the plan.

  4. 04

    Space surveys out

    Leave a few weeks between surveys for the same user, and skip anyone who answered another survey recently.

  5. 05

    Read the words behind the score

    Two users can give the same score for different reasons. What they wrote tells you which one is stuck.

  6. 06

    Close the loop

    When a fix or a feature ships because of feedback, tell the users who asked for it.

Templates and questions for software companies

Start from a template written for one stage of the lifecycle, and change any question.

OnboardingTrial check-inCatch trial users who are stuck before the trial runs out, and learn what they came to test. Show it on the third day of the trial.
OnboardingOnboarding feedbackLearn how the first steps in your product felt, what new users came to do and where they got stuck. Trigger it when someone finishes setup or on their third day.
ProductFeature adoption checkFind out whether users have found a new feature, what keeps the rest away and what would make it part of their routine. Show it in the app two weeks after the release.
RetentionCustomer health checkSpot customers who might leave before they do: how often they use you, how well you solve their main problem, whether they are looking at alternatives and how sure they are to stay. Send it to active accounts every six months.

Questions from the library

Browse the question library
  1. What is the main thing holding you back from a paid plan?Multiple choice · Trial and conversion
  2. How easy was it to get started?Customer effort · Onboarding
  3. What did this replace for you?Text · Usage and habits
  4. What would make renewing an easy yes?Multiple choice · Renewals and staying

Frequently asked questions

Ask users inside your web app and by email at each stage, from the trial and onboarding to renewal and cancellation. Usertick reads every written answer, and workflows send bugs to Jira or Linear, urgent answers to Slack and customers about to leave to HubSpot.

Yes. Add the script tag to your app once, and page rules are checked again each time the route changes, so a survey can wait for the settings page or the billing page.

Yes, from Starter. Pass traits such as plan, role or days since sign-up with Usertick.identify(), and a trait rule shows the survey only to the users who match. Rules compare text or numbers, so pass the trial day as a number.

Yes, on 1 survey on Free and on every survey from Starter. Your code calls Usertick.trigger() with an event name, such as setup_completed, and the survey opens on that call, or on a later one you choose, such as the third export.

Usertick runs in web apps and in mobile browsers. It has no SDK for native iOS or Android apps, so reach the users of those apps by email or with a link.

Yes, on every plan. Jira and Linear get issues whose status, comments and assignee can sync back, HubSpot gets the answers on the contact, with a task for the owner from Starter, and Intercom gets an event on contacts it already has.

Each answer carries the user's ID, name, email, company and traits. The inbox filters by a person on every plan, and by a trait from Starter. Usertick keeps scores per survey and doesn't roll them up into one health score per account.

Set how often each survey returns, such as once every 90 days, and how long it waits after someone closes it. An earlier survey rule, on 1 survey on Free and on every survey from Starter, skips anyone who answered another survey recently.

Usertick holds no SOC 2 report or ISO certificate of its own. Its hosting providers are certified under ISO 27001 and SOC 2. Every customer gets a data processing addendum, and Business adds single sign-on and SCIM.

Website, email and link surveys, Results, AI reading and workflows to Slack, Jira, Linear, HubSpot and Intercom come with every plan, with 1 workflow per survey on Free. Starter adds trait rules, your own events on every survey and the MCP server, Pro adds smart triggers, scheduled reports and the REST API, and Business adds variants.

Listen better, act faster, and build what truly matters.

Start free, see what your customers mean, and get each answer to the person who can act on it.

  • 150 responses a month on Free
  • Every channel and AI analysis
  • No card needed