Formrule

A form backend that takes action

Visit Website
February 5, 2026 Changing one sentence on my homepage doubled my engagement

I got feedback that people didn’t understand what Formrule actually does from the headline. Phrases like “form backend that takes action” made sense to me but not to new visitors, especially those who are not technical. So I decided to experiment.

Before:
“A form backend that takes action”

After:
“Know which user feedback matters - and what to do with it - automatically”

I also decided to target my ICP in the headline and instead of saying "knowing which form submissions matter" use "user feedback". Technically it's the same thing because in the end this is a form backend and they are all form submissions, but the value is much clearer this way.

Results:

  • more replies expressing interest instead of what it is

  • More signups on the free plan

  • More engagement on Reddit posts

I realized I was describing how the product works instead of what changes for the user. Even though I read about that many times until I actually saw it in action, I did not grasp it fully.

Comment

January 22, 2026 I got tired of requests drowning in my contact forms, so I built a decision layer that understands them

Every form submission looks the same until you read it.

A frustrated customer canceling their subscription hits the same endpoint as "hey love your app". Critical bugs sit in the same queue as feature suggestions or support requests. By the time you realize what's urgent, it's too late.

What people usually do: Build Zapier workflows with 47 conditional branches that break every time you add a new use case.

What I built instead: Formrule - a request handling layer that runs before your forms hit anything else.

Every submission gets processed as a request, not just data:

  • Type detection - support request, bug report, feedback, sales inquiry

  • Urgency scoring - is this on fire or can it wait?

  • Sentiment analysis - are they happy or about to churn?

  • Custom categorization - based on your business logic

Then you set simple rules: "negative sentiment + high urgency + contains 'payment' → ping founders in Slack immediately"

The magic is that decisions happen upstream. Your Slack, email, CRM, and ticketing systems stay dumb and clean. No spaghetti logic. No "if this then that then maybe this other thing."

Each message understands what it is before it goes anywhere.

Formrule enables you to stop treating forms as data collection and start treating them as request handlers.

Your form isn't a database insert - it's the front door to your business. It should know the difference between someone asking for help and someone ready to buy.

Live at https://formrule.com - would love feedback from anyone dealing with customer feedback of any kind.

Comment

About

FormRule exists because form messages usually arrive as raw noise, forcing teams to manually figure out what’s urgent, what matters, and what to do next. I’m building it to turn those messages into actionable requests.