A retry. Both customers were understanding and I still did not enjoy the mail. The sequence is locked now. Posting because billing bugs feel private and they should not be.
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.
to see posts from founders and products you follow.
A retry. Both customers were understanding and I still did not enjoy the mail. The sequence is locked now. Posting because billing bugs feel private and they should not be.
I thought I was sharing a lesson. The last paragraph was a link with a discount. The removal was fast and fair. I am rewriting it as the lesson only, and I may not repost it at all.
No link. The original poster had a specific snag. I wrote the steps. If the product is relevant they can find the profile. I am practicing the order.
They need to see that we received the event. I built a page that shows the last twenty, with the result. It is plain. Support used it the same day.
No launch. I fixed the import timeout and answered eleven emails. Writing it down so the week still counts. If your build log only allows victories, it will go quiet at the same time the product needs you.
It lists two products people confuse us with. A tester said it was the first moment they understood us. I was afraid it would sound defensive. It sounded like a boundary.
Last Friday's change was fine and I still spent Saturday wondering. The rule is dull. Dull is what I want from that part of the stack.
Someone paid for LaunchTrail this morning. The plan on the wall said January. It is fine, and it also took longer than I told my friends it would. I am leaving the old date up so I remember the estimate was the fiction.
The trial is still leaky. A higher price on a confusing setup is a louder complaint, not a better business. I will earn the increase when the first session is boring.
I showed up last time with a link and I could feel it. If I am not willing to answer other people there next week, I do not get to ask for attention this week.
The old headline was plain and a little dull. The new one sounds sharper and two people asked what the product actually does. I think I optimized for taste.
We shipped became I fixed, when it was me. The page sounds smaller and more accurate. I do not know if that helps distribution. It helps me reread it.
Defaults would make the usage chart prettier. A few customers do not want their text sent anywhere, even for a draft. The opt-in is a sentence on the screen and a quieter graph. I can live with the graph.
They wrote a fair note. Their team stopped doing the weekly review that made the product necessary. I spent a day rereading it as a verdict on the interface.
It was efficient and cold. The longer reply I use now is still a macro. It just does not begin with a policy sentence.