Back
Roast
Can I ask for feedback about my next project?
I'm using a Typeform to present a paid newsletter that works as a job board for no-code developers.
I collect e-mails, names, and payment information before adding users to the newsletter.
https://nocodejobs.typeform.com/to/TArQOk
Any feedback about the presentation, content or price would be excellent!
I collect e-mails, names, and payment information before adding users to the newsletter.
https://nocodejobs.typeform.com/to/TArQOk
Any feedback about the presentation, content or price would be excellent!
👋 Join WIP to participate
Good job man. I don't know how many no-code developers still but how do you define them?
Thanks!
Actually, this is a good idea, maybe the no-code developer is a new term for most people so I should add a description of it.
Right now, no-code developers are experts in web flow/bubble or low code tools which allow them to build any kind of website in a short amount of time compared to building everything from scratch.
That doesn't mean they are eliminating 'coding' from the formula, most of these tools require an entry-level knowledge about CSS/HTML and Javascript.
Cool idea! Quick copy edits: "Webflow", "Airtable" and I would add more tools like Zapier, Memberstack to the list.
I get the logic jumps. However, I don't think you need the first one. Just write what is the project on the first page and don't ask the submitter if they know what this is.
Also, if this is a job board for no-code people, then your target audience should already be familiar with these tools, right? I don't think it makes sense to have that there.
Also, I get the monetization idea with the rise of Substack but I think job boards is a different beast. There are so many and it's not "premium" content... as in companies post opportunities literally everywhere from Facebook to Slack groups. I don't know if you can put an "insider" spin on it.
Thanks for your advice, especially the quick edits (I didn't see that I leave spaces). 😅
I have mixed reviews about not explaining what my service does. So I think I'll follow your advice and just put everything on the first page.
For the monetization, I believe this is going to be a small product of convenience, I have the hypothesis that most of the people (still need to test this in an MVP) that will use/try this service are not unemployed. So this product will become a convenience service to save them time, and possibly as a way to not discourage them in looking for a full-time no-code job.
If you look for no-code jobs in google, indeed or even Linkedin. Many of them have a wrong idea about no-code developers, some are asking for designers with +8 years of experience or software developers with webflow experience as a plus.
So the main benefit of the service, is that all job positions are going to be exclusive in the no-code market, with real requirements (Not 8+ years) and with the possibility to try the service first before paying.