How to onboard SaaS users with no success team

Someone signed up. Or paid. Then nothing. No login tomorrow. No second session. You open the admin panel and see a name, an email, and silence. In 2026 shipping is cheap, so more products collect that first email and then go quiet.

You do not have a customer success team. There is no onboarding specialist and no health-score dashboard. Indiecity is for one person or a team under twenty. For you, that silence is your job. You are the success team: a few honest emails, one short call when it matters, and a product path that leads to one real win.

Ramli John’s Product-Led Onboarding (with Wes Bush) puts the leak plainly: many new users sign up once and never come back. You spent time to get them in. Product built the screens. Nobody walked them to the one thing that matters. That is the work this week.

Onboarding is a win, not a tour

User onboarding is not “explain every feature.” It is the process that takes someone from “I think this might help” to “I used it and it helped.” Ramli’s definition is useful: people need to perceive the value, experience it, and adopt it into how they work. Your checklist can wait. Their outcome cannot.

Samuel Hulick built a career on this. People do not buy products. They buy better versions of themselves. Your empty state, your emails, and your one call should all aim at that better version of them, not at a tour of every button.

Write one sentence before you touch the product or the sequence:

A new user is onboarded when they [do X] and can say [outcome in their words]. X is one action or small set of actions in the first week. Not “explored the dashboard.”

In Product-Led Onboarding, Wes Bush names the first action that delivers the job. For Zoom it is hosting or joining a meeting. For Canva it is exporting or sharing a design. Yours might be “sent the first invoice,” “published the first page,” or “invited one teammate who actually joined.” Name yours. Everything below points at that event.

Cut the path to that win in the product

Emails cannot save a first screen that dumps ten menus and a blank table. Before you write copy, sit through your own signup as a stranger. How many fields block the first useful action? How many empty charts stare back? What is the single next step the UI asks for?

• One primary button after signup that starts the success event, not “explore.”
• Sample data only if it helps them feel the outcome. Fake dashboards that never become their data waste a session.
• Hide advanced settings until they finished the first job.
• Show progress toward the win (“Invite one person” beats “Complete your profile 40%”).
• If an integration is required for value, say that on the marketing page and make that install the first step, not step seven.

You are not building a full in-app academy. You are removing extra steps. Time-to-value is the time until they feel the product worked for their problem. People who signed up alone will not wait long. They leave when the win is delayed and nobody notices.

You are the success team in the inbox

With no CS team, email is how you show up when they are not in the product. Wes Bush’s onboarding email guidance is blunt: the first track is about a quick win, not about selling. Welcome them. Push the next step. Follow up if they stall. Save upgrade copy for after they have felt value, or for the end of a trial when the clock is real.

Send from a human name. Reply-to should be you. Plain text often lands cleaner than a designed newsletter for these first notes. One CTA per email. If they already hit the win, do not keep mailing “create your first project.”

Hey [name]. This is [you], who built [product]. You signed up to [outcome they bought, in their words if you have them]. The one thing that matters first is [success event]. Here is the shortest path: [one link to the right screen]. If you get stuck, reply to this email. I read it.

Hey [name]. Checking in. Most people who get value from [product] do [success event] in the first session. If you want, I can look at your account and tell you the single next click. Or take 15 minutes this week: [calendar link]. If the timing is wrong, say so. I will stop pinging.

Nice. You [did the success event]. That is the core loop. Next useful step is [second action that deepens the habit], only if you want more of [outcome]. Reply if something felt broken. I fix those first.

Three messages cover most early products. Add a trial-expiry note only if you run a trial, and make it about what they already did (or did not do), not a generic “last chance.” Bush’s point on nagging is right: time-based blasts that ignore product behavior train people to ignore you.

One call, not a success program

A big company runs quarterly reviews. You run fifteen minutes when a real user is stuck or paid and quiet. Paul Graham wrote that you should take extraordinary measures to make early users happy, and that founders often underdo this because they fear it will not scale. You have almost nothing to lose. Delighting a handful of users is how you learn what to put in the product and the emails.

You should take extraordinary measures not just to acquire users, but also to make them happy.

Do not end with “I will send a help link.” Share the screen. Get them to the win while you are both there. Book the call only for people who already raised a hand, paid, or stalled on the one event. You cannot do this for a thousand free tire-kickers. You can do it for this week’s five serious accounts.

What were you hoping [product] would fix this week? [Listen.] Great. We will do only that. Click here with me. [Drive to success event.] You just [outcome]. The habit is repeating that when [trigger in their work]. If anything breaks, email me. Who else on your side should see this?

Record the phrases they use for the problem. Those words go into the empty state and the Day 0 email.

A weekly founder success loop

1. Monday. List every new signup and new paid user from the last seven days. Note who hit the success event.
2. Same day. Send or schedule the Day 0 / Day 2 notes for anyone who has not won yet. Personalize the ones who paid.
3. Midweek. Offer or run one 15-minute call for the highest-intent stuck user (paid, or trial with real setup data).
4. Friday. Count: signups, wins, calls, replies. Write one product fix that would have removed a call or an email.
5. Every week. Delete one step from signup or first-run that nobody needs for the win.

Keep a simple sheet: name, signed up, paid?, success event?, last email, call?, notes in their words. When you finally hire help, that sheet is the job description. Until then it is your Monday ritual.

What good looks like

People reply to the welcome. Someone hits the success event without you. Someone who was stuck gets there on a call and stays. Someone asks how to invite a teammate. Those are activation signals. “Looks cool” in a launch thread is not.

If you have real signups and almost nobody hits the event after clear emails and a few calls, the product path or the promise is wrong. That is useful. It is not a reason to hire a CSM so they can fail the same path at scale. Fix the win. Then invite more people. If they signed up, never won, and then cancelled, that is churn with twenty customers. If you still need buyers in the door, go back to how to get your first 10 paying customers without ads.

What to stop doing

• Building a full help center before anyone finished the first job.
• Sending feature digests that never name the success event.
• Offering “book a demo with our team” when the team is an empty calendar.
• Waiting until churn day to write the user.
• Counting opens as success while the product stays empty.
• Copying enterprise onboarding checklists you cannot staff.
• Adding more signup fields so marketing can “qualify” people who then never return.

Then put the path in the product

Founder-led onboarding does not mean you do every call forever. It means you learn the path by hand, then put the path in the product and the three emails. Graham’s delight section still holds: when you finally have too many users to hand-hold, that is a good problem. The emails and the empty state should still sound like the calls you already ran.

When a user actually got the win because of something you wrote or fixed, send us the story. When the product is real and the name is yours, put it on the map. You can join Indiecity while you run the Monday loop. That gives you people to talk to. It does not replace the emails or the one call.

This week: name the success event, ship the Day 0 note, and book one fifteen-minute slot for someone who is stuck. You are the success team. Act like it.