I do not want to open the repo after a flat launch
The launch was not a disaster. It was quiet. I have been treating that quiet like a personal verdict and the work has stalled. I am curious how other people restarted without pretending the launch went well.
Comments (4)
What did someone who does not build software repeat back from "The launch was not a disaster"?
A flat launch is data. I still took a week off the keyboard before I trusted myself to read it. Both parts were necessary.
I set a stupidly small Monday task: answer one support thread or delete one screen. The mood did not bounce back. The repo did get opened.
Related discussions
View more- I spent three months building something nobody wanted
I am writing this down because I wish I had heard it plainer. I built the workflow I wanted, skipped customer calls, and launched to a quiet list. The product is not bad. It is just not urgent for anyone I can find.
Jamal WrightDiscussion22 votes7 comments
- The AI draft is fine and customers still want to edit every line
We added a draft for a status update. People use it and then rewrite it. I am not sure that is failure. It might be the product. I am unsure how to price a feature that is a starting point.
Hiro TanakaDiscussion11 votes7 comments
- Open source issues are outrunning the paid hosted version
I like the issues. They are also a second inbox. The hosted product is what pays for the week, and it is getting the leftovers.
Marcus ReedDiscussion10 votes7 comments
- The owner gets it and the teammate they invite does not
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.