Clients were asking for tasks that required javascript. Up until this point I was only able to implement a javascript library to a site. If the docs were simple and clear, and I was lucky, I could implement a library. I tried to stay 100% native Webflow. Javascript was this thing that I tried to avoid and had trouble understanding. I really wanted to understand it, but it didn’t come natural to me.

I was learning so much and making our new websites more custom with javascript. We were meeting the needs of our clients through javascript. Sometimes leads ask for functionality that is not possible natively in Webflow. On a sales call, instead of saying, “We can’t do that because blah blah blah”… I could now say “Yes, we can do that”. I knew how javascript worked enough to know what was possible and what was not possible. Maybe I didn’t know how to do what the client was asking myself, but I had a javascript developer that did. I knew what was possible and what was not possible. The most important information I know about javascript is what it’s capable of. I know what it can do, I know what it can’t do. With that knowledge, you can say, “Yes, we can do that” on the phone. That leads to more sales and more client satisfaction.

Adding a javascript developer to the team was a key move in Finsweet growth. Today we are heavily invested in javascript inside Webflow. We love implementing custom javascript on a client’s website. Now we always say, “Yes”. We can do anything that is technically inside Webflow. We have full control. We have come up with the most ridiculous, fantastic, confusing, simple, amazing solutions inside Webflow. If a client needs something to work a certain way, we will figure out how to do it. As long as it is technically possible, we will do it. This type of mentality started in the beginning of year 3. Learning how javascript works was key.