4
4 Comments

Member/Paid Content Requirements

For those building products/ideas using no-code tools, how important is the ability to easily make some content/functionality membership only or paywalled?

It's an obvious requirement for most SaaS etc nowadays, but I wondered if it's less of a concern for many nocoders. As an internal tool for a company membership/auth-based login could be handy I guess, or if your whole thing is about being a content/subscription service.

on January 6, 2020
  1. 2

    My thoughts are it's super useful. Here's one example...

    You have a blog, instead of having a lead magnet at the bottom of every post for a newsletter signup, add even more value for them by creating a free members only area filled with downloadable content relevant to your post/blog.

    You can keep adding value to your members by adding new content in the members only area. Email them with the updates.

    Next, add a paid tier (for your free members) to get exclusive content gated in the paid members section. Etc...

    1. 1

      Yeah, that's kind of what I was imagining :)

  2. 1

    Useful functionality - so much so that I wrote a blog post about how to do something similar with Trolley for payments (shameless plug: I made Trolley) and webhooks with e.g. Zapier.

    Blog link: https://trolley.link/2019/03/03/paid-email-newsletter.html

    1. 1

      Thanks Rory :) I find that webhooks/zapier are awesome for so many things, but I'm interested from a slightly different angle. A friend and I are building a CMS (like wordpress, wix etc...but works on any devices) for nocoders and are wondering which stuff should just be 'built in' and which can rely on integrations and things like you're suggesting.

      Some things are obvious, but members-only areas (billable or not) are definitely a grey area!