Blog
Ideas for building better form systems.
Practical guides, engineering notes and product thinking for teams whose forms have become real software.
Stages: the part of the form that happens after you submit it
FormWork forms now have a process: stages with owners, due dates and actions, approvals by link, and My work. Why we built it this way.
Build from scratch with AI or use a SaaS form builder?
When a SaaS form builder is enough, when an AI-assisted custom build is justified, and when a platform such as FormWork is the better fit.
How we model complex repeatable data in forms
How FormWork models repeatable data so nested repeatable fields, groups, calculations and automations remain predictable as forms grow.
Admin fields are real forms: inside FormWork's team fields
Most tools treat internal admin fields as notes and status tags. FormWork's team fields use the full form engine, with automations and repeatable groups.
How data enrichment makes web forms smarter (without annoying users)
How data enrichment improves web forms by reusing existing data, calling APIs and pre-filling answers, without asking the same questions twice.
Forms for demanding applications
Why FormWork's mission statement is intentionally simple, and how it guides what we build, from architecture decisions to what we choose not to support.
Why FormWork processes everything server-side
Most form builders rely on client-side logic. We deliberately didn't. Why FormWork processes all form logic server-side, and what that makes possible.
Why paying for a hosted form can actually reduce your hosting costs
Forms often push business websites onto expensive hosting plans. Hosted forms can simplify hosting, improve performance and reduce overall costs.
Why we built FormWork
FormWork was not the result of a single idea or a sudden insight. It grew out of a pattern we kept seeing across projects, teams and industries.
New articles, product thinking and lessons from the workshop.
Follow the FormWork team for new writing and product updates.