Aaron worked with Webflow almost every day as part of his role at HBI Innovations.
For most website needs, Webflow gave the team what they needed. But forms were different.
When the team needed conditional behavior, like showing different sections based on a user’s answer, routing submissions to different people or cleaning up the data, Aaron had to build the logic himself.
That meant custom JavaScript, Zapier, and more maintenance every time something changed.
“Every time we update the forms on our side, it's like: "Great, I have to change the JS, I have to go to Zapier and make sure it's routing correctly." On top of that, Zapier isn't cheap and tends to time out sometimes”
The setup did the job, but it created another problem: Aaron was the only person who understood it and knew how to maintain it.
“Since I’m the one that built it, if I’m out, somebody has to figure out the JS and the Zapier integration.”
Aaron started exploring whether he could build a better solution himself.
Like a lot of builders, he was curious about vibe coding tools.
“I saw the appeal of it. And it was everywhere on YouTube.”
He tried Base44, Replit, Lovable and Cursor, among others. Each time, he hit the same wall.
The tools could help him generate code, but they didn’t help him understand or maintain what they produced.
“If it breaks, I don’t know how to fix it. I don’t know what’s wrong.”
He stepped back and started looking for something different.
Aaron found WeWeb in November 2025.
Because Aaron already knew Webflow, the interface felt familiar right away.
More importantly, WeWeb made the app logic visible. He could trace exactly what was happening, step by step, and fix it himself.
“Not only is the interface very similar to Webflow, I can see the workflows and see where things go wrong. Once I spent some time learning how the platform works, everything became clearer and a lot easier.”
Aaron first built a ticketing app to get comfortable with variables, workflows, and state management.
“I wanted to start with something that was less complicated.”
After that, he was ready to build Roolify.
Roolify is a Webflow integration app that gives Webflow forms the kind of conditional logic Aaron had previously built by hand.
The app connects to a user’s Webflow workspace through OAuth, scans their sites and forms, and lets them create rules in a visual builder.
From there, users can define conditions based on form fields and decide what should happen next:
✅ Show a field
✅ Hide a section
✅ Route a submission to the right team
✅ Clean up the notification email so it only includes relevant fields
Users can also design custom email templates with live HTML preview.
The backend runs on Xano. The frontend, including the marketing site, is built entirely in WeWeb.
By May 2026, Roolify was live.
The project was built entirely solo, mostly during nights, weekends, and early mornings.
“I never thought I was going to be building any sort of applications. WeWeb really made it easy to build this.”
Before WeWeb, Aaron could get things working, but maintaining them was hard.
Custom JavaScript and Zapier solved the immediate problem, but the setup was fragile, hard to maintain, and too dependent on Aaron.
Vibe coding tools helped him generate code, but not understand it when something broke.
WeWeb gave him a different way to build. He could see the workflows, understand how the logic moved through the app, and fix issues himself.
That changed how he thought about building.
“Now I’m just in this mode where I just want to build all the time. What else can I build? I don’t care what it is.”
