01 — The problem
Why a submission sitting in a spreadsheet isn't a workflow
Most form tools handle the first step well: answers land in a sheet or an inbox. Then the manual work starts. Someone reads each row, decides who should handle it, forwards it, and chases a status that lives nowhere.
Free-text fields invite typos in site names and cost centers. Conditional logic can't check your own lists. Over time, every team creates its own forms, and nobody knows which ones collect personal data.
02 — What to build
What a custom form builder should handle
Form definitions owned by process owners
fields, required rules and conditional sections.
Lookups against your data, so people pick a site, supplier or cost center instead of typing it.
Validation for dates, ranges and mandatory attachments.
Routing based on answers, such as category, amount or location.
A submission queue with status, assignee and internal comments.
An edit history showing who changed a submission after it was sent.
Reporting views by form, status, site and age.
Roles: submitter, reviewer, form owner and admin.
03 — How to build it
From blank project to working form app
Create a private project
It's a sandbox; nothing goes live until you publish.
Add mock data
your site list, reviewer list and a handful of fictional past submissions as CSVs.
Connect a database so submissions become structured records, not rows in a file.
Plan in Plan mode
The agent asks clarifying questions, for example what happens when a reviewer is away, and proposes a plan. Nothing is built until you choose to build.
Build, then test with real submitters from two sites. Fix gaps with new prompts.
Publish with access control tied to your company email domain and role-level permissions.
An example Plan-mode prompt:
Plan an internal incident report app for our warehouses and offices.
The form asks for site (from sites.csv), incident type, date and time, description and photos; injury incidents unlock an extra section.
Injury reports go to the site manager and the safety lead; all others go to the site manager only.
Reviewers set status (new, investigating, closed) and add internal comments.
Give the safety lead a view of open incidents by site and age.Paste it into a private Henosia project in Plan mode. The agent asks questions and proposes a plan first.
04 — Before you go live
Keeping forms from turning into app sprawl
Forms collect data fast, including personal data, so decide early who may create new forms, who owns each one and which roles can read submissions.
Use fixed rules for routing and validation, since they are predictable and easy to test. Add AI where interpretation helps, such as suggesting a category from a free-text description, and keep a reviewer confirming it.
If submissions must reach other systems, scope each integration per system, data direction and access level. Submissions that need sign-off can feed an approval workflow.
Start a private project in Henosia, pick your most annoying form-and-spreadsheet process, and plan it with the people who review it.
Start a private project05 — FAQ
Frequently asked questions
What is the difference between a form builder and a workflow app?
A form builder collects structured answers. A workflow app also decides what happens next: who reviews the submission, what status it has, and who closes it. For many internal processes the form is only the first step, so building both together avoids copying answers from a sheet into emails.
Is there an AI form builder that also handles approvals?
Henosia is an AI-assisted builder for internal business apps, so you can describe the form, the routing and the approval steps together in Plan mode. The first version comes quickly, but you should still test routing rules, edge cases and permissions with real submitters before relying on it.
Do I need developers to build a custom form builder?
Not for a first version. Process owners can plan and build form apps in Henosia without writing code themselves. Bring in IT when forms collect sensitive data, when submissions need to reach other systems, or when you want shared rules for who may create and publish new forms.
Who can see form submissions?
You decide that in the app's roles: submitters might see only their own entries, reviewers their assigned queue, and form owners everything for their form. Henosia describes access by company email domain plus granular app-level access. Agree on data owners and retention with IT before real submissions go in.