Some general feedback based on my experiences… I think it would depend on the exact functionality you need. You’ll need a paywall / membership management solution, of which a number are discussed in this thread.
As my project went on I hit too many limitations with the CMS (Webflow’s name for the database-like functionality). It’s a really nice Webflow feature and sets Webflow apart from Square, Weeby, etc., but it doesn’t match all of the features and functionality of dedicated database software, and as I went along I realized that’s what I needed.
I noticed in the summaries of the recent Webflow conference that one of the presenters (Unicorn Factory, I think) discussed an app building approach that tied together Webflow with a database provider and paywall provider.
I also recently came across bubble.is which promises to tie together the website design, database and paywall in one solution. I haven’t had the chance to check it out however.
In general, the challenge with systems I’ve used (3 so far) to build a data-driven app is that the systems don’t lay out all the limitations upfront, or not even in the documentation. So the only way to find the limitations is to build within the system, which takes a ton of time because you first need to learn the system. As you go along, you start hitting limitations and then need to decide if:
a) you can live with the limitation(s)
b) if there’s a coded work-around
c) you can wait for the system to address the issue (my advice is to not hold your breath unless the system has confirmed they are working on it and promised a date)
d) there’s another system you can integrate to provide what’s missing
e) if the number of limitations is getting so large that you need to look elsewhere
For a simple app, you might find a system that does everything you need easily. As it gets more complex, the above comes into play.