Nobody praised it. Two people repeated it back correctly. That is the test I said I would use, so I am using it, even though the sharper line is still in a draft.
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.
Community
A founder forum for questions, feedback, tutorials, and building in public.
Nobody praised it. Two people repeated it back correctly. That is the test I said I would use, so I am using it, even though the sharper line is still in a draft.
I left it empty and reread older notes instead. The code would have felt productive. The notes reminded me which sentence I keep skipping because it is inconvenient.
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.
Both people described a different workaround. I want a pattern. I have a pair of stories. The work this week is to book more calls, not to move the interface around.
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.
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.
They are not rude. They are stuck in a workflow I did not design. I am giving it this week as a product problem. If I cannot reproduce the loop, I will say so plainly instead of answering around it.
It was the flexible one. I am waiting for the mail that proves me wrong. So far the inbox is the same size, which is the result I was afraid to want.
Fourteen days gave people room to forget. Seven may just give them room to feel rushed. I will read the sessions before I trust the conversion line.
People think it records the screen. It takes stills for a docs page. I can live with explaining it, or I can change it before more pages quote the name.
They did not get the export they needed and I am not building it this month. The refund was the honest product decision. I wrote two sentences and stopped.
The list is short on purpose. Everyone on it has seen the problem. I will write about it afterward if there is something honest to say. I am done launching to people who owe me nothing.
I have one essay draft and a lot of opinions. The product page is still unclear. The draft can wait in a folder where it cannot pretend to be distribution.
Previously it failed with a generic message and I had to ask for the file. The row number will not delight anyone. It will make the next email shorter.
The picture on the homepage shows a button I have been meaning to move. I delayed the fix so the site would not be wrong. That is an absurd dependency. The fix ships tomorrow. The picture can be stale for a day.