The target audience for this product is really Webflow developers. The selling point of this is simplicity and less dev time. I wont sell a client $15/month for my convenience. Spend some time learning Swiper and build your own to sell with the site build. A pricing model similar to Relume with the use of say 3 projects sounds better. However not until the rest of the products release. I love the amazing work and support systems you guys put out. Personally I'm not prepared to pitch this to a client
I've been messing with it and I see no difference on using this or doing it with native webflow components and attributes. This saves literally no time.
Same here. I would be willing to pay for some Finsweet products, but not this specific product and not with this price structure. If it was a very large library like Relume, and it was a reasonable monthly subscription I pay, then maybe. In other words, the price and convince has to provide enough value that learning to do, or make, it myself is not worth it. I clicked on this video because I thought it was an instructional video on how to build a slider, but wasn't expecting it to be a paid product.
I've been waiting for something like this for a long time - dynamic sliders with CMS in Webflow that are easy to use. I really appreciate the dedication of the Finsweet team in creating this no-code slider. While the subscription model isn't a major concern, it could be challenging to justify the additional cost to clients for one component, especially for smaller marketing websites. It makes sense for large projects with multiple components, but explaining the extra expense for one functionality might be difficult for simple to medium-sized business sites. A more flexible pricing model that accommodates different use cases would be helpful. It would also be beneficial if freelancers and agencies could manage usage across multiple sites from one account, without requiring clients to add a subscription on their end.
This is absolutely amazing. you guys are doing really great things for the webflow community. I wish there were more companies like finsweet who contributed useful functionality to webflow without becoming another monthly subscription service, parasiting webflow users. Edit: LOL, I redact my previous praise, but the irony is too good to remove.
@@joekrug8980 I think something more similar to how Relume works. I'd gladly pay for a subscription that gives me access to use this wherever I want. But to force this per project and have clients pay for it...I don't know, seems a bit much.
@@joekrug8980 webflow costs $14 per month - you are charging $10 per month for a better slider and cookies consent. (with more to come) Not only that but you are charging this per site. Ya all crazy :)
This is great but is it that different to your previous CMS slider using attributes solution? If so, how? With both this and your previous solution - is there a way to lazy load or defer loading of items that are not in view? CMS slider with say 50 image items all on page load really slows the performance down and 10X if some/any of those items are videos. Link to solution if there is one? Thanks!
@@joekrug8980 I mean, selling a second monthly subscription, in addition to Webflow, is not easy. I didn't mean to criticize, and I realize that in some way the producer must have his own economic return;
The slider tool looks awesome, love the built in functionality, much nicer than having to play around with Swiper / Splider libraries to get working well. Is the subscription pricing 'per project' or 'per Webflow account'?
If it's per project, will there be a pricing model for 'Webflow account'? Similar to @avliviu said, so one team can manage multiple projects in an agency format. Otherwise, I'm not sure the cost would outweigh the time saved (in most projects).
My slider doesn't work. I have installed the CMS slider into my webflow site and whenever I preview the site, the slider section automatically grows in size and doesn't stop.
Where I can purchase services/apps to deliver better results for my clients, I will. BUT, If you are going to create a product for designers there should be one monthly fee for designers. You are providing a design function for designers, not an additional service for the clients such as Memberstack or other 3rd party software. This is to improve design, and the cost should therefore be on the designer or absolved within the Webflow fee. I cannot justify this cost to clients, no matter how many wonderful components you create or how large the client. I would absolutely not pay this per project, its almost half the Webflow cost for CMS. I wish the pricing structure was different because I was very excited to see this. If anyone has a different perpective, I'd love to hear it. Perhaps you can get me to see another way.
We see it with a different perspective. Finsweet Components provides an additional service for clients (Such as third-party tools like Memberstack, Zaier, and Elfsight). We are serving javascript-driven components to your website project. On every load, Finsweet Components provides an advanced web component to the end user.
I got really excited till i saw it was a subscription thing. How can Webflow, which is a whole builder + hosting, so a whole infrastructure, cost $14 and this is $10…
My thoughts exactly. This is a near impossible sell to my client since the benefits lie at my end, not theirs. Having to keep paying the sub just to keep it live for ever would cost a fortune. I'd much rather use Finsweet Attributes to build a CMS powered slider or wait for Webflow to add a decent slider.
@@ConnectCreativeDesign "This is a near impossible sell to my client since the benefits lie at my end" ---- This is like saying you (as the developer) should pay for Webflow because the benefits of building in it lie at your end. The published project is the client's, so THEY should have to pay for this subscription. Same answer goes for any third-party tools you use on your website: Zapier, Make, Elfsight, Cookie consent tools, etc.
@@TheMarouuu It is definitely a service. We manage every load of your component on the web page. We'll release more information to explain the architecture of Finsweet Components.
@@joekrug8980 It's a slider. it's not a service and it's a really REALLY hard sell for either us the devs or the clients. I am not about to charge the clients for a block, and I'm absolutely not about to pay it for them either. It's a really gray area of a partial functionality that's neither here nor there. And this is my opinion, my feedback as a potential customer. You don't have to refute it, just take it for what it is. If you re-imagine this as a dev tool I can use on client sites, I am buying it 100%. Something like Relume for example. But this is out of the question for me, and I bet it will be for most people. Just charge me $30 bucks a month like you do with Relume and we're good to go. But the way it's setup now, nope. P.S. Just imagine this scenario: "Hi client, I'm a pro webflow developer, but I'll need you to subscribe to this slider component because I can't build you a custom one for just this one section of the website...." , I mean it's EMBARRASSING to even offer it.
Please specify at the beginning of your video that this is a paid slider component. I spent over an hour getting to grips with it before realizing the price, and the fact that you have to buy it for each project. Such a shame, I was so excited at the idea of finally mastering this aspect. It's good work as usual, but I don't see how I can explain to a customer that they have to pay 10$ a month for a slider on their home page...
Obviously, very very cool. But $10 a month to have this on a custom domain? Hmmmm... not a great look. I really can't understand how the Webflow developers STILL CANNOT make this internally, Finsweet - please just buy out them out and add this type of function and dev to the designer.
They haven't built it internally because it's very challenging to build. We spent a lot of resources to get it done and that's why we're charging for it.
The target audience for this product is really Webflow developers. The selling point of this is simplicity and less dev time.
I wont sell a client $15/month for my convenience. Spend some time learning Swiper and build your own to sell with the site build.
A pricing model similar to Relume with the use of say 3 projects sounds better. However not until the rest of the products release.
I love the amazing work and support systems you guys put out. Personally I'm not prepared to pitch this to a client
I've been messing with it and I see no difference on using this or doing it with native webflow components and attributes. This saves literally no time.
Same here. I would be willing to pay for some Finsweet products, but not this specific product and not with this price structure. If it was a very large library like Relume, and it was a reasonable monthly subscription I pay, then maybe. In other words, the price and convince has to provide enough value that learning to do, or make, it myself is not worth it. I clicked on this video because I thought it was an instructional video on how to build a slider, but wasn't expecting it to be a paid product.
I've been waiting for something like this for a long time - dynamic sliders with CMS in Webflow that are easy to use. I really appreciate the dedication of the Finsweet team in creating this no-code slider. While the subscription model isn't a major concern, it could be challenging to justify the additional cost to clients for one component, especially for smaller marketing websites. It makes sense for large projects with multiple components, but explaining the extra expense for one functionality might be difficult for simple to medium-sized business sites.
A more flexible pricing model that accommodates different use cases would be helpful. It would also be beneficial if freelancers and agencies could manage usage across multiple sites from one account, without requiring clients to add a subscription on their end.
Thanks for this feedback. We'll be releasing a lot of tools to help you serve your clients with Finsweet Components.
thx it is very helpful from any other youtube video in 2024. love from Bangladesh🥰
This is absolutely amazing. you guys are doing really great things for the webflow community. I wish there were more companies like finsweet who contributed useful functionality to webflow without becoming another monthly subscription service, parasiting webflow users.
Edit: LOL, I redact my previous praise, but the irony is too good to remove.
I was thinking the same, then boom - pay me!!
most awaiting feature. thanks to Finsweet team for your amazing stuff in webflow. Really appreaciated .👏
You are unbelievable! We've all waited so long for this, but we didn't even expect it from you. Thank you so much !!!
Thank you!
Really guys, a subscription for this.
What would you like?
@@joekrug8980 Just a one off payment - even if it was for each component.
@@joekrug8980 I think something more similar to how Relume works. I'd gladly pay for a subscription that gives me access to use this wherever I want. But to force this per project and have clients pay for it...I don't know, seems a bit much.
@@joekrug8980 webflow costs $14 per month - you are charging $10 per month for a better slider and cookies consent. (with more to come) Not only that but you are charging this per site. Ya all crazy :)
@@joekrug8980 Not a subscription. A one time payment per component would be fine (I guess)
Thank you Finsweet 😍😍
This is great but is it that different to your previous CMS slider using attributes solution? If so, how?
With both this and your previous solution - is there a way to lazy load or defer loading of items that are not in view? CMS slider with say 50 image items all on page load really slows the performance down and 10X if some/any of those items are videos.
Link to solution if there is one?
Thanks!
I think it's a bit too expensive to be sold to a client.
We'll release tools to help you sell this to your clients
@@joekrug8980 I mean, selling a second monthly subscription, in addition to Webflow, is not easy. I didn't mean to criticize, and I realize that in some way the producer must have his own economic return;
It is too expensive.
fr. idk how anybody can justify using webflow for clients who need anything more than a blog site.
Very strange, my slider does work on the 'staging' but NOT on the actual live website... Any ideas how to resolve this?
Can we create before/after sliders with this?
Awesome,
When will you release the rest components ?
The slider tool looks awesome, love the built in functionality, much nicer than having to play around with Swiper / Splider libraries to get working well.
Is the subscription pricing 'per project' or 'per Webflow account'?
If it's per project, will there be a pricing model for 'Webflow account'? Similar to @avliviu said, so one team can manage multiple projects in an agency format.
Otherwise, I'm not sure the cost would outweigh the time saved (in most projects).
Quick question. Can the gap between the slider be in rems?
Unfortunately, it can not. I wish that wasn't the answer, but it is. We use Swiper JS as the base of this slider and it requires px.
I've been trying to learn Swiper the past month, and holy shit it has been difficult for me. This looks very promising!
missing a step in the tutorial, how do you post the team card component pls ?
@saraCarter-g1v We copied and pasted for the sake of tutorial agility. You can add div blocks and any elements you need inside the 'slide' item.
Very slick! We'll get over the pricing I suppose! ha
A lot more info coming soon. 👍
Wow, looks great, do we need a subscription to export site code that has the component?
Exports will not work. This is a Webflow-only product
My slider doesn't work. I have installed the CMS slider into my webflow site and whenever I preview the site, the slider section automatically grows in size and doesn't stop.
Mindblowing❤🔥
how do I delete components entirely?
hello, why I have nothing in "collection list settings"? I have only "none" option
@vianosuze You have to create a CMS collection in the CMS panel first.
u sure it woeks cuz some of the options I see in the vid do not exsist when I try to follow along
These features should be native in Webflow considering how far Webflow has come its confusing as to why they are not already?
Craaaaaazyy bruv
Where I can purchase services/apps to deliver better results for my clients, I will. BUT, If you are going to create a product for designers there should be one monthly fee for designers. You are providing a design function for designers, not an additional service for the clients such as Memberstack or other 3rd party software. This is to improve design, and the cost should therefore be on the designer or absolved within the Webflow fee. I cannot justify this cost to clients, no matter how many wonderful components you create or how large the client. I would absolutely not pay this per project, its almost half the Webflow cost for CMS. I wish the pricing structure was different because I was very excited to see this. If anyone has a different perpective, I'd love to hear it. Perhaps you can get me to see another way.
We see it with a different perspective. Finsweet Components provides an additional service for clients (Such as third-party tools like Memberstack, Zaier, and Elfsight). We are serving javascript-driven components to your website project. On every load, Finsweet Components provides an advanced web component to the end user.
memberstack is shameless, highway robbery. I literally left webflow after realizing they were the only viable option for user accounts.
@@joekrug8980 you cannot seriously compare a slider to a fully fledged membership service with custom accounts. come on man.
@@joekrug8980 Also Elfsight is a bang on comparison. But they charge $5 for 3 components and unlimited websites.
I got really excited till i saw it was a subscription thing.
How can Webflow, which is a whole builder + hosting, so a whole infrastructure, cost $14 and this is $10…
My thoughts exactly. This is a near impossible sell to my client since the benefits lie at my end, not theirs. Having to keep paying the sub just to keep it live for ever would cost a fortune. I'd much rather use Finsweet Attributes to build a CMS powered slider or wait for Webflow to add a decent slider.
@@ConnectCreativeDesign Pretty much this. It's not a service... I don't get it. I mean, I get it duh, but it doesn't make sense for me.
@@ConnectCreativeDesign "This is a near impossible sell to my client since the benefits lie at my end" ---- This is like saying you (as the developer) should pay for Webflow because the benefits of building in it lie at your end. The published project is the client's, so THEY should have to pay for this subscription. Same answer goes for any third-party tools you use on your website: Zapier, Make, Elfsight, Cookie consent tools, etc.
@@TheMarouuu It is definitely a service. We manage every load of your component on the web page. We'll release more information to explain the architecture of Finsweet Components.
@@joekrug8980 It's a slider. it's not a service and it's a really REALLY hard sell for either us the devs or the clients.
I am not about to charge the clients for a block, and I'm absolutely not about to pay it for them either. It's a really gray area of a partial functionality that's neither here nor there.
And this is my opinion, my feedback as a potential customer. You don't have to refute it, just take it for what it is.
If you re-imagine this as a dev tool I can use on client sites, I am buying it 100%. Something like Relume for example. But this is out of the question for me, and I bet it will be for most people.
Just charge me $30 bucks a month like you do with Relume and we're good to go. But the way it's setup now, nope.
P.S.
Just imagine this scenario: "Hi client, I'm a pro webflow developer, but I'll need you to subscribe to this slider component because I can't build you a custom one for just this one section of the website...." , I mean it's EMBARRASSING to even offer it.
Dear webflow, know you know what to do.
Wohoooo ✨
Please specify at the beginning of your video that this is a paid slider component. I spent over an hour getting to grips with it before realizing the price, and the fact that you have to buy it for each project. Such a shame, I was so excited at the idea of finally mastering this aspect. It's good work as usual, but I don't see how I can explain to a customer that they have to pay 10$ a month for a slider on their home page...
Obviously, very very cool. But $10 a month to have this on a custom domain? Hmmmm... not a great look. I really can't understand how the Webflow developers STILL CANNOT make this internally, Finsweet - please just buy out them out and add this type of function and dev to the designer.
They haven't built it internally because it's very challenging to build. We spent a lot of resources to get it done and that's why we're charging for it.
@@joekrug8980 you know what else was challenging to build? Webflow. And they did that.
🎉
i don't understand what this does. Looks like exactly the same amount of work as doing it from scratch.
I echo, what most state here. I am not willed to pay yet another SaaS fee while webflow itself is really stretching it themselves.
Ooooo lala
too expensive unfortunately