A healthy sign-up graph and an empty app
Sign-ups look fine. People find the product, create an account, confirm their email. Then most of them do not come back. You look at their accounts and they are empty: no projects created, no data imported, no teammates invited. Some logged in once, clicked around for a minute and left.
You have probably sent them a welcome email and perhaps a tips email. Few open them. You are left guessing whether the product is wrong, the audience is wrong, or something in between.
Why they leave after the first visit
The most common cause is simple: the first session asks for work before it gives anything back. A new user lands in an empty dashboard and has to configure settings, import data or invite people before they see what the product does.
- The product starts blank, so there is nothing to look at.
- Setup steps that matter to you, like company details, come before steps that matter to them.
- The "aha" moment needs data the user has not got to hand.
- Nothing prompts them to come back with the missing piece.
- Tracking is so thin you cannot see where people stop.
Onboarding tools, the kind that add product tours and checklists, can help here, but only once you know which step people are stuck on. A tour that explains an empty screen does not fill it.
What silent drop-off costs
| Cost | Why it matters |
|---|---|
| Wasted acquisition spend | You paid to get people to sign up and they never used it |
| False signals | You may conclude the idea is wrong when the first session is |
| Misdirected roadmap | New features for people who never reached existing ones |
| Trial-to-paid stays low | Nobody pays for something they never saw work |
How we rebuild the first session
- Instrument the journey. We add product analytics events for each step from sign-up to first useful result, using a tool such as PostHog, Mixpanel or your own event table, so the drop-off points are visible.
- Define activation. Together we pick the action that best predicts a user sticking, such as creating their first report or connecting their first data source, and measure it.
- Shorten the path. Setup steps that are not needed for first value are moved later. Required steps are simplified, prefilled or made optional.
- Fill the empty state. Sample data, templates or a guided first project so the user sees the product working before they have added anything of their own.
- Make imports easy. Where first value needs their data, we build importers for the formats they already have, like spreadsheets or common tools.
- Follow up on behaviour. Emails and in-app prompts triggered by what a user has not done yet, such as a reminder to connect their account, instead of a fixed drip.
- Hand warm leads to a person. For B2B products, accounts that show intent but stall can be flagged for a quick personal message.
Where an off-the-shelf onboarding tool fits, we use it. Where the product needs custom empty states, importers or in-app logic, we build those into the app.
New users who reach something useful
For the founder, the biggest change is usually clarity. When activation is measured, a disappointing month can be traced to a specific step or a specific source of sign-ups, and you can tell a product problem from a marketing one.
You can see, step by step, where new users stop and whether a change moved that point. New users see the product doing something useful in their first visit. Follow-ups say something relevant to where each person got to. And product decisions are based on what activated users do, not on guesses about everyone who signed up.
Is this your churn problem?
- Most new accounts stay empty after the first day.
- You cannot say which step in onboarding loses the most people.
- New users face a blank screen after signing up.
- Your follow-up emails are the same for everyone.
- You are unsure whether to change the product or the onboarding.