Form Plugin with CRM capabilities

alesas

When I started building Sobi Forms, the goal was simple: make a lightweight, fast WordPress form builder. No bloat. No performance-killing scripts. Just clean forms that send data from point A to point B.

But once you start managing form submissions, you realize something very quickly: an inbox is just a CRM in disguise.

I didn’t plan to build CRM features. I noticed that adding a few lines of clean PHP could turn a simple submission list into a powerful workflow tool for small businesses and freelancers, without adding weight to the plugin.

Here is what’s already baked into Sobi Forms right now:

The Current “Mini-CRM” Workflow:

  • Status Management: Read vs. Unread toggles with distinct visual styles so you know what needs your attention.
  • Starring / Favoriting: A simple “Star” system to flag important leads, complete with a quick global filter.
  • Internal Admin Notes: A dedicated textarea inside the submission detail view. You can leave notes on a lead, and it’s fully indexed in the global admin search.
  • Smart Inbox Routing: Filter by form, search through names, emails, custom fields…
  • Data Ops: Automatic deletion/retention settings per form to keep database storage clean and GDPR-compliant.

What’s Next (The “Quick Reply” Idea)

Looking at this workflow, there is an obvious next step: Quick Reply.

Instead of copying a lead’s email, opening Outlook or Gmail, and losing context, you could reply directly from the WordPress submission view. Sobi Forms would handle the email delivery and keep a clean thread attached to that specific submission.

Keeping the Marathon Clean (Avoiding the WordPress Trap)

The temptation right now is to keep adding features every single week until Sobi Forms looks like a cockpit. That is exactly what I hate about traditional WordPress plugins. They become bloated, confusing, and heavy. So, I’m slowing down on the CRM side.

My absolute priority for the next few updates is Form Capabilities and UX refinement. If I add a feature, it must hidden behind progressive disclosure. If you don’t use it, you shouldn’t see it. The core builder must stay minimal, fast, and lightweight.

I’m pacing myself on this project, one small improvement per week..