Back
Roast
Posted

Roast NoCodeIt.com

Hey!

There's no denying that we see a lot of nocode stuff being made nowadays. That's why we (I'm doing this with my GF) started nocodeit. At #nocodeit we interview people who run profitable nocode side projects or businesses. I've kind of soft-launched it by putting all the interviews we have online and tweeting about it.

Roast away 🔥

https://nocodeit.com/


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.

Thanks! Some solid advice here, I'm not at all a writer and I'm having a hard time pulling people in, I get what you're saying tho. I'll try to highlight some of the important stuff and write better intros, to try and get people more hooked :)

One thing you can do throughout the week is bookmark the articles you end up reading. Perhaps you already bookmark them anyway. And then every once in a while take some time to analyze them. What made you want to read them? How did you know it would be worth your time without having read it first? (Kind of a paradox when you think about it.)

Reverse engineering, smart. Thanks for the tip!

Hi Dennis,

I'm addicted to the indiehackers-podcast, so probably your target-audience :). I like the idea and concept and see a market. I am in general interested in your interviews.

I read one interview for a few paragraphs.. then went somewhere else. The internet today is not very friendly to long-form text, I'd say... Too many distractions.

I believe I would perceive your content as much more valuable if presented in better digestible format
- smaller paragraphs
- subheadings
- original quotes
...

Also... As you anyways do these interviews - wouldn't it be feasible to make a podcast out of them directly? You still can use the transcript for seo-purposes.
And I think video-interviews would be even better. Make one interview, distribute video, podcast, transcript.