← Blog

Trial-to-paid conversion: the first week

Which first-week events predict a trial converting, how to count them, and a worked example that shows how to read the gap between starters and finishers.

Stiro team ·

Trial-to-paid conversion is the number most SaaS teams watch, and the one they can do least about on the day it arrives. By the time a trial ends and a user pays or doesn’t, the decision was made days earlier, usually in the first week, usually during setup.

So the useful question isn’t only “how many trials converted?” It is “what did the trials that converted do in their first week, and how many of this week’s trials are doing it?” This post covers which events to measure, how to count them and how to read the results, with a worked example.

The headline number

Trial-to-paid conversion is the share of trials that become paying customers.

In words: take every trial that started in one period, such as one calendar month. Count how many of them became paying customers by the end of their trial (or within a short grace period after it). Divide the second number by the first and multiply by 100.

Two things keep it honest. Use one group of trials that started together, so you follow the same people to the end. And wait until every trial in the group has finished before you report it, or the last week’s trials will drag the number down. You can work out your own with the trial-to-paid conversion calculator.

The catch is that this number arrives late. With a 14-day trial, you learn how a month’s trials did weeks after they started. That is why the first week matters: it gives you numbers you can read while the trial is still running.

Which first-week events to measure

You are looking for actions in the first seven days that the trials that convert usually took, and the trials that don’t usually skipped. In most products they fall into three groups:

  • Finished setup. The user connected what needs connecting, imported their data or set the defaults, so the product can do its job. This is often the biggest one, because without it there is nothing to evaluate.
  • Reached first value. The first real result: a report shared, an invoice sent, a booking taken. If you already measure time to value, use the same event here.
  • Came back. The user returned on several different days, not just once. A count such as “active on 3 or more days in week one” works well.

Many products have a fourth: brought someone in, such as inviting a teammate or sharing a link. It matters most when the product is used by a team.

Pick three or four. More than that and the list stops being something you can act on.

How to count them

For each event, split last month’s trials into two groups: those who did it in their first seven days and those who didn’t. Then work out the conversion rate for each group.

Reading a first-week event
  1. Step 1Pick one month of trialsAll trials that started in the same month
  2. Step 2Split by the eventDid it in the first 7 days, or didn’t
  3. Step 3Convert each groupShare of each group that became paying
  4. Step 4Compare the twoThe bigger the gap, the more the event predicts

A few rules keep the split useful:

  1. Count people, not events. A user who imported data five times is one user who finished importing.
  2. Use a fixed window. Seven days from the trial start, the same for everyone.
  3. Wait for the outcome. Only compare groups whose trials have all ended.

A worked example

For example, say a reporting product had 200 trials start last month, each 14 days long. These numbers are made up to show the method.

By the end of their trials, 30 of the 200 were paying. That is 30 ÷ 200 × 100 = 15% trial-to-paid conversion.

Now split them by three first-week events:

First-week event Did it Converted Rate Didn’t Converted Rate
Finished setup 80 24 30% 120 6 5%
Active on 3+ days 60 21 35% 140 9 6%
Invited a teammate 40 14 35% 160 16 10%
ExampleTrial-to-paid conversion, by what users did in week one
Finished setup30%
Didn’t finish setup5%
Active on 3+ days35%
Active on fewer days6%
Invited a teammate35%
No invite10%
Show as a table
Finished setup30%
Didn’t finish setup5%
Active on 3+ days35%
Active on fewer days6%
Invited a teammate35%
No invite10%

All three events matter. Finishing setup stands out for another reason: 80 users did it, so it covers far more of the trials than the invite does, and 24 of the 30 paying customers had done it.

Starters and finishers

The most useful line in the example is hidden inside “didn’t finish setup”. Those 120 users are two different groups:

  • 50 never started. They signed up and never opened setup. Some were curious, some were in the wrong place.
  • 70 started and stopped. They opened setup, got part of the way and didn’t finish. These users wanted the product enough to begin.
Example
trials started setup
150
finished it in week one
80
started and stopped
70
trial-to-paid conversion
15%

The gap between starters and finishers, 70 users, is where most of the opportunity sits. They have already shown intent. If they converted like the finishers, at 30%, that would be about 21 paying customers instead of the handful they produce now. You won’t get all of that, but even a part of it moves the headline number more than most pricing or email changes.

To find where they stop, treat setup as its own funnel and count users at each step. The post on where new users stall during setup walks through it. Usually it is one step: a connection, an import, a page full of settings.

Read it carefully

  • These events predict; they don’t prove. Users who were going to buy anyway are also more likely to finish setup. Use the gap to choose where to look, then test a change and see whether conversion follows.
  • Watch it weekly. Each week, check what share of this week’s trials have finished setup. It is the early signal the headline number can’t give you.
  • Split by type of trial. A small team and a large one can stall at different steps.
  • Keep the definitions fixed. Same events, same seven days, every month.

Getting trial users through setup with an in-app agent

When starters stall, it is rarely because they don’t know what they want. They know they want their data in and their defaults set. The slow part is finding each screen and filling it in, often while they are still deciding whether the product is worth the effort. That is where an in-app AI agent fits: the trial user asks in plain words and the agent does the steps in your app.

Stiro is one. You add it with one script tag and there is nothing to train. A trial user can ask “connect our sales data and set the reporting week to start on Monday”, and Stiro clicks and types through your real interface to do it while they watch.

  • It does the setup steps. Starters get to finished without hunting for each setting.
  • It reads the live screen. When you change setup to make it shorter, Stiro works from what is on the page now.
  • It says so when it can’t. If a request isn’t possible in your app, it stops, says 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, while the trial is still running.

We tested Stiro cold in three open-source apps it had never seen, on everyday requests, each checked 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 every reply.

Measure the first week, then close the gap

Take last month’s trials, split them by finished setup, and count how many started but didn’t finish. That number is your clearest lead on trial-to-paid conversion. If the steps they stall on are ones they could simply ask for, AI onboarding with Stiro lets them ask. The free plan includes 50 runs a month on localhost and a staging address, so you can try it on your own trial setup first.