I like the concept of sharing successful case studies of people starting software(!) businesses without writing code. Many people want to leverage the benefits of running an online software business, but coding might seem too intimidating. I think there's a wide audience interested in this idea.

I don't love the name. It's pretty bland. Somewhat descriptive, but not really inspiring. Not very memorable either. I'm not even sure it should include "no code" as I'm not sure everyone is familiar with that term. (We makers are, but I think your audience an be much wider than that).

"You don’t need to code to launch your startup."

Launching a startup is not a goal. I think it should be something along the lines of "You don’t need to code to run a software business."

• The 3 interview cards on the homepage could use more information. Perhaps a short description of the business, how much revenue, how old the business is, that kind of thing.
• Centered text is fine for headlines, but not for paragraphs of text. Hard to read.
• The interviews themselves could use some typography love. The paragraphs are too wide. Try to aim for 50-60 characters per line. You can do this by increasing the font size and limiting the container width.
• Scanning the interviews, they don't really draw me in. People don't read from top to bottom, unless they are already convinced it will be worth their time. Highlight the most interesting parts with some pull quotes, add visuals, etc. That will pull people in and get them to actually read the articles.
• The interview titles don't really pull me in either. They are descriptive, but don't really tell me why I should read them. Tell me something surprising or what I'll learn from reading the article.

I think it has potential and I love that you already got a bunch of articles published. That's the best way to start. That said, personally I didn't feel intrigued enough to actually read the articles. Perhaps I'm not the target audience, but I also think you can do a better job at convincing a visitor to become a reader with the suggestions mentioned above.

Try to gradually pull in the reader. From an appealing image, to an intriguing title, with an informative intro. You should be able to pull me in step by step.

I keep going back to the same places and tend to stay there for quite a while (at least a month) so it's not a big problem if my first few days aren't as productive. If I were hopping from one place to the other, I'm not sure I'd be able to work as consistently as I'd feel bad for not experiencing my new surroundings.

I also think over time it becomes easier to just sit down and do the work. Motivation used to play a bigger role in my life, but nowadays I can just mostly go sit somewhere and start. Even in the rare cases I don't feel like working, I know that if I start anyway I'll be back in the zone pretty soon regardless.

I think it comes down to learning to ignore the lack of motivation and start anyway. The same way it's best to just go to the gym even if some days you don't feel like it. Once you're exercising it's usually alright. Same with work.

Basecamp open-sourced theirs: github.com/basecamp/policies

I read the article, but still not sure what role machine learning would play haha

Great points. I agree retention is the most important. Without good retention, the other metrics don't matter. I think there's also a lot of opportunity for improving Activation. WIP is really a habit-driven product and if people don't get into the habit of using it early, they tend to churn quickly.

Thanks for sharing. Could you elaborate how you see ML helping in this case?

Having said that, these are two services in this area I think are the most promising:

• shipright.co
• canny.io

There are a bunch of services for this, but in my experience 1) most customers prefer to just message you via Intercom/etc than go through a 'feature request' website, and 2) feature requests by themselves aren't very useful. When someone request a feature, you'll want to dive deeper into the problem they are trying to solve and then figure out yourself what the feature should look like.

So my recommendation would be to stick with email or however else customers currently reach out to you. Try to better understand their reasoning for requesting a feature. And if you absolutely must, keep track of these requests using a tool such as Trello, etc. But if you're just starting out it's probably fine to do it in your head as more common requests tend to resurface anyway.

Haha yes I considered just doing it without mentioning it. That's what most people tend to do. But it just didn't feel right for WIP as we tend to be an open community.

Great points! And I 100% agree they are probably not a good fit if they weren't willing to pay.