Our Projects In Webflow

Published on
August 22, 2023
2 minutes
Written by

In 2021 we decided to start using no-code / low-code solutions in our commercial projects that required frontend development for several reasons:

  1. We assumed that frontend projects, such as websites or small web apps (PoC, MVPs, etc.), can be built by UX/UI designers who know what must be done and how it should be designed to look right and meet our clients and their end-users expectations.
  2. Tools available on the market were mature enough to give them a try.
  3. Communication between devs and designers usually took more time than needed to deliver what was actually discussed. Plus, it caused frustrations and friction and wasn't helping us to keep our team motivated while working on quick and straightforward projects.
  4. We wanted to let our designers work entirely independently to see if it could help deliver projects faster (thus at a better price for the clients).
  5. In 2020-2022, there was so much work for frontend developers that we had to use their capacity wisely. Obviously, we wanted them to focus on the most demanding projects where frontend skills and knowledge would pay off in well-designed architecture, optimized performance, etc. 
  6. In 2020-2022, frontend developers became too expensive for simple projects, and it took a lot of work to hire new ones (I guess you remember how hot the tech market was in those days.).

The list is longer, but you understand what we're saying here. It made perfect sense to try it, and we decided to go with Webflow.
(Disclaimer: this post is not sponsored, and we don't have any commercial relationship with Webflow.)

Below we present some of our projects made in Webflow:


A website for our friends who run a small engineering team specializing in data projects.

hero section of faro website: www.faro.team
Faro's home page


It's a tech startup building a platform for running ML models in production. Since this is still an early-stage product and things change there every week, the founders wanted to have an option to quickly update content and make necessary changes without spending too much time on the technical side of the website. In this case, Webflow was a perfect choice.

MLnative's home page


A wholesaler of heat pumps and other HVCAR equipment wanted to launch a website in a couple of days. Our scope of work covered everything (from logo through copywriting to CTA and buyer persona), so we worked under a bit of pressure. Webflow helped us a lot because we could deliver the whole project in our private workspace, where the client could share their feedback instantly. We built a good relationship with their team, and the website was ready for publication after a few iterations. Before going public, we seamlessly moved the website to the client's space so they had complete control.

Airco's home page


A local accounting company that needed an online presence to open their doors to new clients who search for information mainly on the Internet. It was a simple project, but it gave enormous returns to the company's owner as it took a couple of weeks to acquire new clients through the website, which paid off the budget spent on the project.

Margo's home page

Mechanik Wrzeszcz

A family-owned car mechanic firm wanted to refresh their website design and make some improvements compared to the previous version. It's similar to Margo, where a UX/UI designer shipped a whole project solely. 

Mechanik-Wrzeszcz's home page

Web apps

We used Webflow in two web application projects, and it worked surprisingly well.

In the first case, our UX/UI designer created a whole website and exported it for our frontend team. The code structure generated by Webflow was good, so we could use it and leverage JavaScript that allowed for integrations with backend services.

In our second project (we can't share the screens), we built a mockup of a healthcare application to show how an actual application would work when it's ready. As a side product, we already created layouts and a lot of HTML and CSS structure that fronetend devs could reuse in later stages of the project. Most importantly, stakeholders and end-users could share their feedback while playing with the mockups. It was a huge time saver and significant value-added before the development took off.

To summarize, low-code/no-code tools like Webflow are the future for more and more business needs, and they have pure advantages over traditional or hybrid solutions (like Wordpress). We will continue our work with these tools and highly recommend trying them to see how it fits your needs.

Until next time!

Thanks for reading!

If you'd like to talk about it, please reach out to me via email: tomek@appstral.eu