File
SMF·FILLOUT
Received on
31.07.2026
Reviewed on
28.09.2026
Exhibits annexed
3
Questions
4

SMF·FILLOUT

Can a prompt replace Fillout?

Forms & surveys — forms, surveys and lead capture

Yes Verdict recorded on 28.09.2026 · Verified on 31.07.2026
Price
$19/moSource: fillout.com · Checked on July 31, 2026
Per year
$228
Build time
One sitting
Votes
0 votes
Yes (checked)AlmostNot yet

Exhibit tracking slip

Exhibit A The prompt
Exhibit B What you lose
Exhibit C Why people still pay: integrations, deliverability, and workflow depth
Exhibit Q Questions

Verdict

A form that collects a payment as part of submission, not just data, is a real weekend build once Stripe's own Checkout or Payment Element does the actual payment handling — you should never build custom card processing yourself. What doesn't survive: Fillout's polished embed-anywhere behavior across Notion and any website, and its calculation engine for computing prices or scores from multiple answers.

Exhibit B — What you lose

Exhibit A — The prompt

Received on31.07.2026
Build a form tool that can collect a payment as part of submission — using Stripe Checkout for the actual charge, never custom card handling. Use Next.js/TypeScript with SQLite. Support standard field types (text, select, number) plus one payment field type: when present, submitting the form creates a Stripe Checkout session for a configured amount, fixed or computed from a simple sum of numeric answers such as quantity times a per-unit price, and redirects there. Only mark the submission as paid and complete after Stripe's webhook confirms the payment — never trust the client-side redirect alone, since that can be spoofed or interrupted. Store submissions with their payment status in SQLite, with a dashboard showing paid versus pending or abandoned submissions. Add a basic one-level conditional field, showing field B only if field A has a specific value, to support simple pricing logic. Email the form owner a notification on completed, paid submissions via a transactional email provider. Do not build embedding into third-party tools like Notion, a general calculation or scoring engine, or multi-level branching — those are out of scope; this is a form with an optional Stripe-backed payment step, nothing more. Needs a domain, a transactional email provider, and a Stripe account (test mode works with no real charges for development).

Opening prefills the prompt — press enter to run it.

Exhibit B — What you lose

  • B.1 polished embed-anywhere behavior across Notion and any website
  • B.2 a calculation engine for prices or scores from multiple answers
  • B.3 advanced conditional logic and branching
  • B.4 a large integration library beyond payments

Prior art

Exhibit C — Why people still pay: integrations, deliverability, and workflow depth

Wiring up Stripe once is a weekend; making a form that embeds cleanly everywhere, computes complex scores from answers, and branches through dozens of conditions is the ongoing feature work.

Questions

How does it actually process the payment?

Through Stripe Checkout — this build never touches card details directly. Stripe handles the payment; the app only records the result after Stripe confirms it via webhook.

Can I embed this form inside Notion or another website?

Not with the polish Fillout has — you could iframe it into a page, but native embed behavior across many platforms is real integration work this build doesn't attempt.

What if someone closes the tab after paying but before the redirect completes?

The webhook confirmation is what actually marks the submission as paid, independent of whether the redirect back completes — so the payment still gets recorded correctly even if that happens.

What does it cost to run?

A domain, a transactional email provider's free tier, and Stripe's standard per-transaction processing fee — no separate subscription cost for the form tool itself.

Receipt

Already built this yourself?