AI Form Builder for SaaS Founders: Churn Surveys, Onboarding and Feature Requests

You already know which forms your product is missing. The cancellation survey has been on the list since the second churn. The onboarding question you keep meaning to ask new signups. The feature request inbox that is currently your DMs, a starred email folder, and a Notion page nobody has opened since March.

None of them get built because each one is a 40-minute job, and a 40-minute job never wins against shipping. So: the four forms a small SaaS needs, what to ask, what to skip, where the answers go.

The churn survey, and the one question that matters

Most cancellation surveys are a checkbox list: too expensive, missing features, switching, not using it enough. A list of reasons hands people the socially easy option, and "too expensive" is what most of them pick when the real answer is "I never got it to work".

Ask one open question instead: "What were you hoping this would do for you when you signed up?" That gets the job they hired you for, in their words, at the moment they have nothing to lose. Compare it against what you ship and you learn whether you have a product gap or an onboarding gap, which need different fixes.

• Ask the expectation question first, required, free text.
• Ask what they use instead as a single select. That one is just a bucket.
• Ask for an email only if they want a short call, and say who is calling.
• Don't ask NPS. They are leaving. The number is not a decision input.
• Don't make anything required except the first field.

Where they end up: nowhere fancy. Read them monthly, export the CSV if you want, and don't build a dashboard for 14 answers.

The real prompt, typed into Claude or ChatGPT (Brieform runs as an MCP server, there is no builder to click through):

Build me a cancellation survey in Brieform. Create it as a draft, don't publish it yet, and show me the preview URL when you're done. Context: I run a solo B2B SaaS called Sitewire, project tracking for construction subcontractors, $39/mo, around 300 paying accounts. People cancel from a settings page and I have never once asked them why. Title it "Before you go", one screen, five fields, in this order: (1) long text, required, "What were you hoping Sitewire would do for you when you signed up?" with help text "One or two sentences. Be blunt, it helps more than being polite." (2) long text, optional, "What made you decide to stop?" (3) single select, optional, "What are you using instead?" with options Another tool / Spreadsheets / We built something internal / Nothing / Prefer not to say. (4) short text, optional, shown only when field 3 is "Another tool", "Which one?" (5) email, optional, "If you're open to a 10 minute call about this, leave your email" with help text "No sales pitch. I'm the founder, I just want to understand what went wrong." Nothing required except field 1, no rating scales, no NPS. Theme: quiet and low key, muted stone, plain sans serif, nothing cheerful. People see this page on a bad day.

Reading the answers back

Forty free-text answers in a CSV is forty answers you never read. The responses sit behind the same MCP server that built the form, so ask for the analysis directly.

Pull all the responses to my "Before you go" form and read the free text. Group the answers to "What were you hoping Sitewire would do for you" into at most six buckets, organised by the job they were hiring the product for, not by the reason they gave for leaving. Those are different things and I care about the first one. For each bucket: how many responses, two verbatim quotes (don't clean up the grammar), and whether Sitewire ships that job today. If we do ship it and they never found it, call it an onboarding failure, not a product gap. Then cross-check against field 2 and flag where the stated reason for leaving doesn't match the expectation. Finish with the single bucket I should fix first and why. Plain prose, no scores, no priority matrix. If the sample is too small to conclude anything, say that instead of guessing.

That last line matters: with a handful of responses you are reading anecdotes, not data.

Onboarding intake: segment before the welcome email

New signups all get the same first week, which means it is written for nobody. One short form on the post-signup screen fixes that.

• Ask "What are you trying to get done in the next two weeks?" as free text. That is the whole form.
• Ask role and team size as single selects. Enough to pick an email track.
• Don't ask for a phone number. You are not calling them.
• Don't build eight steps. Multi-step exists, but six fields belong on one screen.

Where they end up: your email tool. Ask your AI client to read the week's answers and draft the sequence per segment.

Feature requests: why a form beats a public board

A public roadmap board looks like the mature choice and is usually wrong for a team of one to five. It is a backlog you have to moderate, votes get read as promises, and it collects feature names instead of problems.

• Ask "What are you trying to do that you can't do today?"
• Ask "What do you do instead right now?" The workaround shows urgency better than any rating.
• Ask how often it comes up: daily, weekly, monthly, once.
• Don't ask for an importance score out of 10. Everyone picks 9.
• Don't offer a dropdown of your internal module names. Users don't think in your architecture.

Where they end up: a Friday reading session. Ask your AI to group the batch, flag duplicates, and turn the top cluster into issues in your tracker. No file uploads, so if you want screenshots, add a URL field and ask for a link.

The user interview recruitment form

Four fields, and it exists so you stop recruiting by DM.

• Ask one screening question about the workflow you are studying, so you filter the right users.
• Ask how long they have been using the product.
• Ask for a timezone and two or three availability windows, free text.
• Don't try to book inside the form. There is no calendar step.
• Don't collect demographics you have no plan for.

Where they end up: your calendar. Give the list to your AI client and let it draft the invites.

What this setup cannot do

The edges matter more here than for most audiences:

• No outgoing webhooks. You cannot fire the churn survey from inside your app the moment someone hits cancel, so you link it from the cancellation flow and repeat the link in the confirmation email. Expect it to convert worse than an in-app modal.
• No query string prefill. The URL cannot carry an account ID, so anonymous stays anonymous unless you ask for the email in the form.
• No native integrations. No Zapier, no Slack app, no Sheets sync. Your AI client is the bridge: connect Brieform and the destination tool to the same assistant and ask it to move the data. It runs when you ask, not while you sleep.
• No file uploads. Screenshots and recordings arrive as links or not at all.
• One published form on the free plan. Drafts are unlimited, but a draft collects nothing. Four live forms means a paid plan.

When something else wins: if you need the survey to fire on the cancel click with the account attached, an in-app survey widget (PostHog and similar) beats a linked form, and it is not close. If you want public voting, use a roadmap board.

🚀 Try it now — Build your churn survey with Brieform →

Free to start. No credit card required.

FAQ

Can I trigger the churn survey automatically when someone cancels?

No, there are no outgoing webhooks. You link the form from your cancellation screen and the confirmation email.

How do I get responses into Notion, Slack or Linear?

Through your AI client. Connect Brieform and the other tool to the same assistant, then ask it to read the responses and create the pages, messages or issues. No native integration, no Zapier.

What does it cost to run all four forms?

Free is $0 with 1 published form and 50 responses a month, so four live forms means Starter at $29/mo (20 published forms, 2,000 responses a month, analytics, branding removed). Pro is $69/mo for unlimited; annual billing takes 20% off.

Can users attach a screenshot to a feature request?

Not directly, file uploads are not supported. Add a URL field and ask for a link to the image or recording instead.

Do I have to use AI to read my responses?

No. Every plan includes CSV export and the dashboard lists submissions. The AI reading is a convenience for free text, not the only way in.