I’ve been heads-down building a new Gravity Forms Add-On, I’m currently calling Form Style Canvas, for about a week now.
What started as a simple inspector idea, giving users an inspector tool that would allow them to click on any form element and get a block of CSS that they could copy and then modify, turned into a full-blown front-end styling editor that generates the edited CSS for you. Point and click. Open the canvas. Style your form. Save it exactly where you need it.
I was feeling pretty good about where it was headed. Then I read a post by Chris Lema titled When Everyone Can Build, Building Stops Mattering.
I’ve been following Chris for years. The man doesn’t write fluff. So I read it. And then I sat with it for a while, because it kind of punched me in the face in a way I needed.
Thanks, Chris!
What I Heard Lema Say
The short version of his argument is this: building used to be the hard part. Not anymore. AI has collapsed the barrier to entry so fast that going from idea to working prototype is basically free now.
Which means the thing that used to set technical builders apart from everyone else, the ability to actually make the thing, is gone.
But here’s the part that really landed for me.
He brought up a couple of powerful historical examples to help make his point.
When publishing democratized, the filter didn’t disappear; it “moved downstream”. Amazon reviews. Word of mouth. Social proof. What readers actually did with a book became the new gate.
When advertising democratized, the same thing happened. Facebook could give anyone an ad. So the platform started measuring behavioral signals: engagement, click-through, retention, and that became the new filter.
Software is next. And if you’re a builder, that means the competitive advantage just shifted out from under you.
The question is no longer “can you build it?”
Everyone can build it.
The question is: Can you make someone trust it enough to weave it into their actual business and workflow?
Thinking About Form Style Canvas
I’ve seen more than my share of support tickets from people losing their minds trying to style a form.
They’re fighting with page builders. They’re dropping random CSS into places where it doesn’t work. They’re copying code from forum posts that are three years out of date. It’s a real, consistent, well-documented pain point.
I built Form Style Canvas because I knew that pain firsthand.
The tool lets you open a sidebar canvas on the front end of your form page, style it visually, and write the CSS for you. You choose where to save it: the WordPress Customizer, your theme, a file the plugin manages, or scoped directly to that specific form’s settings if you don’t want it applied to all forms. It handles all of it.
But here’s what Lema’s article made me ask myself: Is the loop clean enough that someone will use it again and again?
The first time someone uses it, it might be out of curiosity.
They’ve had issues with Gravity Forms before; they installed it and played around with it. That’s not adoption.
Adoption is when they come back to use it repeatedly. When they stop reaching for the old, broken way, and this tool becomes a permanent part of their workflow, and they use it every time.
The Thing I Was Ignoring
I’ve been so focused on getting the tool to work correctly and constantly dealing with scope creep 🤦🏼♂️ and adding new features that I stopped thinking about the experience of someone using it for the first time
Take the save options.
CSS can land in multiple places: the Customizer, the theme, a plugin-generated file, or scoped to a specific form and saved in the form settings.
This adds a decision point that could freeze someone who doesn’t fully understand the difference. And if they pick the wrong one, say, they save globally when they meant to scope it to one form, they just broke every other form on the site.
That’s a trust-destroying moment. The kind of thing that gets a one-star review and a plugin uninstall.
That’s the downstream filter, I think Lema is talking about. Not what I say the plugin does. What actually happens when a real person uses it and something goes wrong?
He puts it plainly:
The new filter is retention curves, workflow integration, whether people build their process around a product or abandon it after the first session.
My Next Steps
I’ve stopped adding new features! And I am focusing on tightening the experience around the moments that matter most.
Making the save decision obvious
The save options need better in-context explanation at the point of decision. Not a doc link. Not a tooltip that says “save to theme.” Something that answers the real question: “Should I save this globally or just to this form?” I know the answer. I need to put it in front of the user at the exact moment they need it.
Tracking what actually matters
This might be the first time you’ll ever hear me say this, but I want users to open tickets and ask their questions. I want them to get the answers they need to know if this tool will work for their use case or solve their specific workflow issue. I want to hear about all the ways people are using the tool and how it can be improved to serve more people.
Better documentation
This is the part I probably undersell the most. I’ve been providing WordPress support for years. I know exactly how people describe the problem when they’re frustrated. I know what they’ve already tried. I know which page builder they’re fighting with.
I can write documentation that is at a completely different level, one that resonates with the person reading it. One that gets them from first-time use to long-time user.
The Shift
What I hear Lema saying is that the moat used to be technical. It was the code, the architecture, the years it took to learn how to make the thing. That moat is gone.
The new moat is trust. Behavioral evidence. Whether your users integrate your product into their process or abandon it after the trial.
For me, specifically with Form Style Canvas, that means I can’t just fix bugs and ship.
I have to obsess over what happens in the first five minutes.
I have to make sure that, the first time someone successfully styles a form, saves it, and sees it work on the front end, the loop closes cleanly, and they feel good about it.
Because that’s the moment that creates the habit.
Lema’s right. And I’d rather figure that out now than wonder later why a tool that solves a real problem never got any traction.