I Found Blue Ocean in the Most Crowded Market on the Internet

I would like to share something that surprised me as a builder. Forms might be the most boring, most crowded category in SaaS.

Google Forms is free. Typeform charges $29/month. Jotform charges $39/month. There are literally hundreds of form builders. Any rational founder would look at this market and walk away.

I did not walk away. And four months in, I believe I have found a gap that none of them are filling.

The Gap Nobody Is Filling

I spent years in digital marketing making forms for clients. Event registrations, lead captures, surveys, feedback loops. I got quite good at it. And the thing I learned was this: building the form takes five minutes. Running the form takes five hours a week.

Reviewing responses. Sending follow-ups. Routing hot leads before they go cold. Checking who opened what email. Exporting data to three different places. Bouncing between the form tool, a spreadsheet, email, and a CRM just to keep one workflow alive.

Every form tool on the market optimizes for creation. The pretty drag-and-drop builder. The AI that generates your form in one click. That is the demo. That is what gets the Product Hunt upvote.

But I could not find anyone building for what happens after you hit publish.

That is where I decided to focus.

How I Tested the Gap

In March 2026, I did something tedious but revealing. I signed up for every form service that claimed MCP support and tested what their chat interface could actually do.

For those unfamiliar, MCP (Model Context Protocol) is the protocol that lets AI assistants like Claude, ChatGPT, and Cursor connect to external services. It is becoming the standard way users interact with SaaS tools through conversation.

Here is what I found:

• Jotform: 5 MCP tools. Can create a form. Cannot change design, cannot preview, cannot manage responses from chat.
• stigmi: Claims 58 tools, actually has 24. Can create a form. Cannot change design or preview.
• Weavely: 1 tool. Creates a form. That is it.

Every single one stops at creation. Want to change the design? Back to the dashboard. Want to send a reminder to respondents? Back to the dashboard. Want to see who opened your email? Back to the dashboard.

The chat interface serves as a front door to a traditional product. Once you walk through it, you are back in the same GUI as everyone else. I saw an opportunity to do something different.

The Bet I Made

FORMLOVA has 127 MCP tools across 25 categories. Forms, responses, analytics, emails, webhooks, team management, A/B testing, scheduling, CRM export, Google Sheets sync.

You can go from "make me an event registration form" to "send a reminder to everyone who hasn't responded" to "show me the drop-off analysis" to "export the attendees to Sheets" -- all within the same conversation, without ever opening a dashboard.

The dashboard exists. It works well. But it serves as the supporting actor, not the lead.

I should mention something that still makes me a bit nervous to share. I actually built a drag-and-drop form builder UI for the dashboard. It worked fine. Then I deleted it. That decision freed up weeks of engineering time that I redirected to post-publish operations -- the boring, painful, daily work that nobody seemed to be building for from chat.

It was a difficult choice. But so far, the feedback from beta users has validated it. Nobody has asked for the builder back. Several have told me the response management and email tools are why they stayed.

The Economics That Make $3.20/Month Work

This is the part that tends to get the most skepticism, so I would like to be as transparent as possible.

FORMLOVA's Standard plan is $3.20/month (480 yen). Premium is $6.50/month (980 yen). The free tier has unlimited forms and unlimited responses. No cap. No "upgrade to see your data" hostage-taking.

For comparison:

• Typeform Standard: $29/month (10 responses/month on free)
• Jotform Bronze: $39/month (100 responses/month on free)
• formrun (popular in Japan): roughly $26/month (30 responses/month on free)

This is not a loss leader. It is an architectural advantage.

Here is why: LLM processing costs sit on the user's side, not mine. When someone creates a form or analyzes responses through chat, their Claude or ChatGPT subscription pays for the AI inference. My servers handle database operations, email delivery, and hosting. That is the entire cost structure.

I never call an LLM API from my backend. Zero AI inference cost on my side, regardless of how many users join or how much they use the product.

My running costs right now:

• Vercel (hosting): Pro plan
• Supabase (database + auth): Pro plan
• Resend (email delivery): Pro plan
• Multiple domains

These are fixed costs that scale gracefully. I am not watching a GPU bill climb with every new user. The margin on a $3.20/month subscription is real margin, not "we will figure out unit economics later" margin.

The Free Tier Philosophy

Unlimited forms. Unlimited responses. Full data export. No credit card required.

I made this decision for a specific reason: I do not want to hold anyone's data hostage.

The free-to-paid conversion needs to come from users wanting more operational power -- custom auto-reply emails, reminders, A/B testing, advanced analytics, email sequences. Not from locking their response data behind a paywall.

If someone collects 10,000 responses on the free tier and exports them all to CSV, that is perfectly fine. That is working as intended. The bet is that once they are running real operations on those forms, they will want the tools that save them hours per week.

What I Learned from 73 Beta Users

Before getting into the raw numbers, I want to share what the beta phase taught me.

I gave 73 people from my personal network full access to every feature -- no paywalls, no tier restrictions. I wanted honest feedback on whether the core idea worked, not on whether the pricing page was convincing.

What came back reshaped the product in ways I did not anticipate.

The most significant change was to the publish flow. Early testers kept accidentally publishing forms before they were ready. One person published a form with the placeholder thank-you message still in place. Another forgot to set up duplicate response prevention. The feedback was clear: the publish action needed guardrails.

So I rebuilt the entire publish flow as a server-side checklist. Now, when you say "publish this form," the system walks through each requirement one at a time -- preview confirmation, thank-you page check, duplicate prevention, privacy policy if needed. You cannot skip steps. Several beta users told me this was the feature they appreciated most, even though it technically slows them down by a few seconds.

Other feedback led to smaller but meaningful changes: adding sort options to the response list, showing email configuration status on form cards, improving how the system auto-selects which form you are talking about when you have multiple forms. These were not features I would have prioritized on my own. They came directly from watching real people use the product.

The pattern I noticed was encouraging. Beta users were not asking for a better form builder. They were asking for better post-publish tools. That told me the bet was directionally right.

Numbers (Transparent)

Since this is Indie Hackers and I know you all appreciate honesty over polish:

Product:

• 4 months of development, solo founder
• 127 MCP tools across 25 categories
• 29 field types (text, rating, NPS, ranking, file upload, signature, and more)
• 86 database migrations
• 3,155 unit tests + 90 E2E tests
• Works with Claude, ChatGPT, Cursor, Windsurf, Codex -- any MCP client

Traction:

• 73 beta users from personal network (full feature access, no paywalls)
• Average of 2-3 forms created per user
• No paid acquisition yet
• No public launch yet

Revenue:

• $0. Pre-launch.
• Target: 10,000 users in 3 years (roughly 280 net new per month)

My situation:

• Solo founder, based in Japan
• Background in digital marketing (years of form operations for clients)
• Working on this full-time, while also maintaining some digital marketing projects
• Not VC-funded, not planning to be

73 users is a small number. I know. But the signal I am reading is not the number itself -- it is the behavior. They are using the post-publish tools. They are managing responses and sending follow-up emails from chat. They are not asking for a better form builder. That gives me some confidence heading into the public launch.

The Hardest Engineering Problem Nobody Sees

The thing that consumed the most engineering time was not any feature. It was safety.

When you let an LLM orchestrate real operations -- sending emails to 500 people, deleting a form with 2,000 responses, publishing something publicly -- you need serious safety guarantees. LLMs skip instructions. They hallucinate user approval. They decide the user "probably" wants to proceed.

Prompt instructions are not enough. I tested this extensively. An LLM will cheerfully bypass "always confirm before sending" if it believes the user's intent is clear enough.

So I built server-side enforcement. Twelve tools that can cause irreversible damage (bulk email, form deletion, data deletion, publish) require a confirmation token: HMAC-SHA256 signed, bound to the specific tool and user, with a 5-minute TTL. The LLM literally cannot execute these operations without the server issuing and then verifying the token. No prompt injection, no creative interpretation, no "I will just do it" can bypass the check.

Nobody will ever look at FORMLOVA and think "great token design." But without it, the product would be dangerous to use. If you are building anything that lets LLMs take real-world actions, I would strongly recommend building the harness before you build the features.

What I Learned That You Can Steal

Three things from this build that I believe apply well beyond forms:

1. Red oceans have blue pockets.

The form market is incredibly crowded. But "form operations from a chat interface" had zero direct competition when I started building. I think every crowded market has a dimension that nobody is competing on. For forms, it was post-publish operations. For your market, it might be a different phase of the workflow that everyone ignores because it is not demo-friendly.

2. Make the user pay for the expensive part.

FORMLOVA's economics work because the most expensive component -- LLM inference -- runs on the user's existing subscription. I did not plan this as a business model hack. MCP simply works this way. But the principle generalizes: if you can architect your product so that the most expensive computation happens on infrastructure the user already pays for, your margins get much healthier.

3. Build the harness before the features.

If your product involves AI taking real-world actions (not just generating text, but actually doing things), the safety layer will take longer than you expect and matter more than any feature. I would encourage you to budget for it generously. I spent more time on the confirmation token system than on the entire analytics module. I would do it again without hesitation.

Share Campaign: Premium Free for 3 Months

To coincide with the launch, I am running a share campaign. If you share FORMLOVA on social media or write about it on your blog -- anywhere with a link to formlova.com -- you get the Premium plan completely free for 3 months. That is the full feature set: auto-reply emails, reminders, A/B testing, advanced analytics, email sequences, team management, Stripe Connect, and everything else.

The campaign runs until the end of May 2026. One share is enough. No strings attached. After 3 months, you can continue at 980 yen/month (roughly $6.50) or stay on the free tier with unlimited forms and responses. Your data stays either way.

If you would like to participate: Share campaign form

I built this campaign form using FORMLOVA itself. It is a small proof of concept -- if the form tool works well enough to run its own marketing, that says something.

Product Hunt: April 15

FORMLOVA is launching on Product Hunt on April 15, 2026.

If you are reading this before launch day, I would genuinely appreciate your support. If you are reading this after, the product is live and free to try.

• Free to start: formlova.com
• Setup guide (connect to Claude, ChatGPT, etc.): formlova.com/en/setup
• Share for 3 months Premium free: formlova.com/en#pricing
• Product Hunt launch: April 15, 2026

Further Reading

If you would like the deeper cuts:

• I Built a Form Builder, Then Deleted It -- the full build story on Hashnode
• AI Should Not Stop at Making Forms -- the thought piece on Medium
• 118 MCP Tools, 4 Safety Levels: Building a Server-Enforced Form Ops Layer -- the technical deep-dive on DEV
• Most Form Tools Stop at Creation -- FORMLOVA Starts After Publish -- the flagship blog post
• Route Post-Publish Responses by Intent -- proof of post-publish ops in action

A Genuine Question

I am about to put this in front of the internet for the first time, and there is something I am still uncertain about.

The whole value proposition depends on people understanding that form operations -- not form creation -- is where the time goes. That is obvious if you have run forms at scale. But for someone who has not, "I manage your forms from chat" might sound like a solution to a problem they do not know they have.

To those of you who have launched products that solve a pain point people do not yet realize they have: how did you bridge that gap? Did you lead with education, with a specific use case, with a free trial that creates the aha moment? I would love to hear your experience, because I have not fully figured this out yet, and I am launching in 10 days.