That has not happened before. The change was the empty state sentence, not a new step. I am not throwing a launch for it. I am leaving the sentence alone.
SupportLayer
Customer support workspace for bootstrapped founders.
FormRelay
Receive form submissions without running an app server.
LaunchTrail
Organize startup launches and community feedback.
ShipNotes
A weekly build log that customers can actually follow.
How did you get your first 10 paying customers?
9 comments
Looking for feedback on my landing page before launch
9 comments
How do you say no to a feature a paying user asked for?
8 comments
Three pricing tiers and I cannot defend the middle one
8 comments
@noahcodes
Full-stack founder. I care more about boring reliability than another dashboard widget.
SaaSInvader
Build. Share. Discuss. Grow. A public home for founders, indie hackers, and the people shipping software with them.
Showing #onboarding
That has not happened before. The change was the empty state sentence, not a new step. I am not throwing a launch for it. I am leaving the sentence alone.
It was more useful than the last five calls because they did not tidy it up. They hesitated on a label I thought was obvious. The label changes today. I asked if I could keep the recording internal. They said yes.
A route rename. The message was otherwise fine. A handful of people hit the dead link. I have mailed them the right one. The checklist now includes clicking the actual email, not the preview.
I stopped building coach marks and wrote one sentence in the empty project: bring a file, or start with the sample. Activation moved. It is the least glamorous screen in the app and the one I should have written first.
I counted 'created a project' and the number looked healthy. Most of those projects were empty the next day. I need a definition that is allowed to be disappointing.
Founders keep asking me for a tour. When I sit with them, they skip it and ask where their data goes. A five-minute call answers that. A tour might just be a way to avoid the call.
Activation looks good because the founder did the setup. The invitee lands in a workspace they did not shape and stalls. I have been designing for the buyer and calling it the user.
Setup completion is fine on day one. The next morning I send a note about the second step and the open rate is miserable. Subject lines I have tried sound either like a newsletter or like a warning.
You're all caught up.
Communication
Customer support workspace for bootstrapped founders.
No-code
Receive form submissions without running an app server.
Marketing
Organize startup launches and community feedback.
Productivity
A weekly build log that customers can actually follow.
Productivity
Lightweight workflow management for independent teams.
Commerce
A small CRM with only the fields a founder fills in.
Analytics
Exit notes and cancellation reasons in one place.
Developer Tools
Screenshot automation for documentation teams.
Finance
Clearer invoices and failed-payment follow-up.
Analytics
Simple product analytics for small SaaS applications.
Infrastructure
A status page with an incident note people can read.
Artificial Intelligence
Keep a record of prompts that shipped in the product.