What I do is a paradigm shift: it’s not about convincing the client buy into Webflow, but to get them to trust me as an empathetic, well meaning expert in the field that knows and puts their interests above all else. Then the platform used stops being the client’s concern, for most of my clients (SMBs without an internal dedicated team). They have business requirements, wants and needs for the project. If I do my job correctly in the sales and strategy part, my client will trust me and go with the sulution I suggest, regardless of it’s Webflow, Next, Web Studio, etc.
PS: Spot on about the strategy. Exactly what I do. Lots of beginners jump into the design phase and look to wow their clients with a flashy design that unfortunately lacks substance because there’s no solid strategy in place, no understanding of the problems the design needs to solve, or even what the goals of the website are and how it fits into the business’ sales and marketing funnel, let alone the clients brand or the customer profiles. Front load the strategy, copywriting content strategy and wireframing, then hear the “wow” from the clients when you present the prototype. You’ve done it, you’ve already won. The design and everything else that follows is just more bonus wins on top. They will give you a glowing case study and testimonial.
I tried on my last call, but since the client has a massive CMS with users with a massive database correlated to them I have to build it on WP. It's not gonna suck as much as I've found Bricks Builder very similar to Webflow. Wish me luck.
I would like to know your objective opinion why your clients should switch to WF. I personally can't see any reason to recommend WF. For low budget client is FW costly and big client prefer other tools _(not no-code)_ as they offer much more flexibility, are more reliable and secure. I agree that WF is suitable some way for specific niche clients as marketing sites but with new pricing models as Optimise ($300/m), Analyze ($30/m), Localization ($9/m per lang) it may narrow number of clients willing to use WF. Not talking about charging for connection to payment gate for each transaction, another extra cost that may come later when WF will monetize another small features or using Zapier etc. that may increase costs rapidly, based on complexity and amount of traffic, when with standard development you can implement these functionalities without using 3-rd party paid service. just with API's etc. etc. etc. IMO WF is great "Design" tool to create fast prototypes. But I understand that "no-code" is costly.
I see no reason why any of my current clients should switch to Webflow but a number of factors stick out for me that suggest a client should use Webflow. * startups - need quick changes exploring with copy and design while they figure out their business * cost - while Webflow is expensive in the long run, the alternative is hiring a design and a developer which is going to be more expensive. Hire a Webflow designer who can do it all. plus They don’t need to stay on Webflow forever I made another video on this, But each company is different and understanding their specific needs might result in WF being a suitable tool. I made another video on this “Building a Website in 2025” But in general I agree with you designers see Webflow as more of a solution than businesses. Businesses generally don’t care about the tool.
@@webflowandcode > "while Webflow is expensive in the long run, the alternative is hiring a design and a developer which is going to be more expensive" IMO cost of project should not been set based on time (how fast) but generally on project complexity. :) like I mentioned WF can deliver fast prototypes, on other hand when you have snippets or components you can use again and again , like connections to DB, payment gate or custom RTE you can be fast enough as it is almost identical approach like using (copy pasting) components in WF. I will still charge same amount for complexity but project will done be faster. :) > each company is different and understanding their specific needs might result in WF being a suitable tool. As I have mentioned there is a specific niche of clients to be suitable for WF, the question is if project can be done with another tool that is more flexible, easy to implement features clean way _(not hacking)_ and also future proof. > Businesses generally don’t care about the tool. totally agree, businesses not is on developer to use right tool. Anyway these only my opinions. BTW nice job, and I will check your 2025 video.
There are many more factors that go into the decision than you, the current person who is currently working on it. You needs to find out what those factors are
Are you trying to get your client to move into Webflow?
What I do is a paradigm shift: it’s not about convincing the client buy into Webflow, but to get them to trust me as an empathetic, well meaning expert in the field that knows and puts their interests above all else. Then the platform used stops being the client’s concern, for most of my clients (SMBs without an internal dedicated team). They have business requirements, wants and needs for the project. If I do my job correctly in the sales and strategy part, my client will trust me and go with the sulution I suggest, regardless of it’s Webflow, Next, Web Studio, etc.
PS: Spot on about the strategy. Exactly what I do. Lots of beginners jump into the design phase and look to wow their clients with a flashy design that unfortunately lacks substance because there’s no solid strategy in place, no understanding of the problems the design needs to solve, or even what the goals of the website are and how it fits into the business’ sales and marketing funnel, let alone the clients brand or the customer profiles. Front load the strategy, copywriting content strategy and wireframing, then hear the “wow” from the clients when you present the prototype. You’ve done it, you’ve already won. The design and everything else that follows is just more bonus wins on top. They will give you a glowing case study and testimonial.
I tried on my last call, but since the client has a massive CMS with users with a massive database correlated to them I have to build it on WP. It's not gonna suck as much as I've found Bricks Builder very similar to Webflow. Wish me luck.
I would like to know your objective opinion why your clients should switch to WF. I personally can't see any reason to recommend WF. For low budget client is FW costly and big client prefer other tools _(not no-code)_ as they offer much more flexibility, are more reliable and secure. I agree that WF is suitable some way for specific niche clients as marketing sites but with new pricing models as Optimise ($300/m), Analyze ($30/m), Localization ($9/m per lang) it may narrow number of clients willing to use WF. Not talking about charging for connection to payment gate for each transaction, another extra cost that may come later when WF will monetize another small features or using Zapier etc. that may increase costs rapidly, based on complexity and amount of traffic, when with standard development you can implement these functionalities without using 3-rd party paid service. just with API's etc. etc. etc. IMO WF is great "Design" tool to create fast prototypes. But I understand that "no-code" is costly.
I see no reason why any of my current clients should switch to Webflow but a number of factors stick out for me that suggest a client should use Webflow.
* startups - need quick changes exploring with copy and design while they figure out their business
* cost - while Webflow is expensive in the long run, the alternative is hiring a design and a developer which is going to be more expensive. Hire a Webflow designer who can do it all. plus They don’t need to stay on Webflow forever
I made another video on this,
But each company is different and understanding their specific needs might result in WF being a suitable tool.
I made another video on this “Building a Website in 2025”
But in general I agree with you designers see Webflow as more of a solution than businesses. Businesses generally don’t care about the tool.
@@webflowandcode
> "while Webflow is expensive in the long run, the alternative is hiring a design and a developer which is going to be more expensive"
IMO cost of project should not been set based on time (how fast) but generally on project complexity. :) like I mentioned WF can deliver fast prototypes, on other hand when you have snippets or components you can use again and again , like connections to DB, payment gate or custom RTE you can be fast enough as it is almost identical approach like using (copy pasting) components in WF. I will still charge same amount for complexity but project will done be faster. :)
> each company is different and understanding their specific needs might result in WF being a suitable tool.
As I have mentioned there is a specific niche of clients to be suitable for WF, the question is if project can be done with another tool that is more flexible, easy to implement features clean way _(not hacking)_ and also future proof.
> Businesses generally don’t care about the tool.
totally agree, businesses not is on developer to use right tool.
Anyway these only my opinions.
BTW nice job, and I will check your 2025 video.
Why does the client need to use Webflow? They arent the one developing their website... right? I'm confused
There are many more factors that go into the decision than you, the current person who is currently working on it. You needs to find out what those factors are