File
SMF·FORMSTACK-FORMS
Received on
31.07.2026
Reviewed on
28.09.2026
Exhibits annexed
3
Questions
4

SMF·FORMSTACK-FORMS

Can a prompt replace Formstack Forms?

Forms & surveys — forms, surveys and lead capture

Not yet Verdict recorded on 28.09.2026 · Verified on 31.07.2026
Price
$99/moSource: www.formstack.com · Checked on July 31, 2026
Per year
$1,188
Build time
One sitting
Votes
0 votes
YesAlmostNot yet (checked)

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

Filling a PDF template with submitted form data automatically — Formstack's actual document-automation angle — is a real weekend build using an existing PDF-form-filling library. What doesn't survive: Formstack's large template library and its e-signature integration.

Exhibit B — What you lose

Exhibit A — The prompt

Received on31.07.2026
Build a form tool that fills a PDF template with submitted answers automatically — Formstack's actual document-automation angle. Use Next.js/TypeScript with SQLite, and a PDF-form-filling library such as pdf-lib, which can fill existing PDF form fields programmatically. Let the form creator upload a PDF that already has fillable form fields, created in any PDF editor, and map each field to a question in the form builder. Support standard field types (text, select, date, signature-as-typed-name) in the form builder itself. On submission, fill the mapped PDF fields with the submitted answers using pdf-lib, and generate a completed, downloadable PDF — store it alongside the raw submission data in SQLite. Send the form owner, and optionally the submitter, the generated PDF via a transactional email provider. Do not build a large template library, real e-signature (cryptographically verified) integration, or approval-routing workflows — those are out of scope; a typed name in a signature field is not a legally verified e-signature, and the README should say so plainly. Needs a domain and a transactional email provider; no other external service required.

Opening prefills the prompt — press enter to run it.

Exhibit B — What you lose

  • B.1 a large library of pre-built document templates
  • B.2 e-signature integration
  • B.3 advanced workflow routing and approvals
  • B.4 enterprise compliance attestations

Prior art

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

Filling one PDF template is a library call; a large template library plus e-signature integration and approval routing for real business documents is the much larger ongoing product.

Questions

Does it generate a legally binding e-signature?

No — a typed name in a signature field is not cryptographically verified the way real e-signature services are. If you need legally binding signatures, that's a real reason to use a dedicated e-signature tool.

Can I use any PDF as a template?

It needs to be a PDF with actual fillable form fields already defined, created in a PDF editor — this build fills existing fields, it doesn't add them to a flat PDF.

How many document templates does it support?

As many as you upload and map yourself — there's no pre-built library like Formstack's, which represents real accumulated content.

What does it cost to run?

A domain plus a transactional email provider's free tier — typically nothing beyond what you already pay for the domain.

Receipt

Already built this yourself?