The difference is what happens after submit
Tally, Typeform, Jotform and Google Forms are genuinely good at collecting answers — if a survey is all you need, use one. A form builder ends at the results table. Faldaro begins there: the submission is a record that gets worked — calculated, routed, approved, documented, paid — on a platform built so none of it can be quietly rewritten. Which means the honest comparison is rarely another form builder. It is the stack a team wires together when the form tool runs out: the e-sign tool, the payment page, the automation glue and the spreadsheet that quietly became the system of record.
Mechanisms, not adjectives
Twelve things that work differently here
Not a feature checklist — those age badly and every vendor ticks every box. These are differences in where the truth lives, and each one is checkable in behaviour.
| In most form tools | In Faldaro | |
|---|---|---|
| A calculated total | Computed in the browser by the form widget. Whatever number arrives with the submission is what gets stored. | Recomputed on the server on every save and every read. A browser cannot fabricate a total, because nothing it sends is trusted as one. |
| A submission | A row in a results table. Working it — triage, approval, payout — happens somewhere else, after an export or a Zap. | A record with a state machine. Moving it from state to state is a separate, permissioned act from editing it, and every transition can notify, generate documents, call your systems. |
| Editing a live form | The form changes underneath the responses already collected; old answers are reinterpreted by the new questions. | Publishing creates an immutable version. Every submission keeps the exact definition it was filled against, forever. |
| The audit trail | An activity feed the application maintains — and could, in principle, rewrite. | Append-only because the database refuses updates and deletes on it, not because the application promises to behave. |
| Taking a payment | An amount field wired to a processor. The price is whatever the page said it was. | The server prices the submitted answers itself; the payment request has no field an amount could even ride in. Delivery of anything sold is gated on settlement. |
| Teams, clients and partners | Workspaces sharing one account, separated by convention. | An organisation tree with isolation enforced by row-level security in PostgreSQL. Share a form with a partner organisation — their submissions stay theirs, yours stay yours. |
| Changing a form you rely on | Preview it, publish it, hope nothing broke. | Named regression cases re-run through the real engine before you publish, so a change that would move a number someone pinned down is caught first. |
| A record that stalls | Reminder emails, at best — and someone still has to notice nobody acted on them. | States carry deadlines that fire real transitions: forty-eight hours in Review and Escalate happens by itself, with the same guards and notifications a person’s click would carry, audited as the deadline’s doing. |
| A form in another language | Duplicate the form per language and keep the copies in step by hand — two forms, two links, two piles of submissions to reconcile. | One form, one submission stream, a translation table per language substituted on the server. Choice values are never translated, so a French submission and an English one record the same data — and AI can draft the whole table for you to approve. |
| Form analytics | A tracker script in the embed, a cookie on the visitor, and a consent banner on you. | Views, starts and completions counted server-side — no cookie, no IP stored, no per-visitor row. Conversion numbers with nothing to disclose, because nothing is collected. |
| AI | A chatbot that drafts questions into the editor. | An agent acting inside the product with exactly your permissions — it builds forms, imports PDFs, wires logic and routes work, with no delete tools, no credentials of its own, and every step shown. |
| Who you pay for | Responses are the meter: growth in submissions is growth in your bill, and the tools that work them charge for every person who touches the system. | You pay for your team, never your audience. Submissions are never throttled and never billed by count, and the people filling your forms are not seats — a fifty-person organisation can collect from fifty thousand. |
The left column describes how form tools usually work, not any one product — check yours. The right column is spelled out mechanism by mechanism on the security page.
An honest sorting
Which tool actually fits
Recommending a competitor when they fit is cheaper than a churned customer who was sold the wrong thing.
-
A form builder
Surveys, polls, waitlists, one-off feedback. The answers are the product, nobody works them afterwards, and time-to-published is the only metric that matters.
-
Custom software
A process so specific that it is your competitive edge — a bespoke rating engine, a trading flow. Faldaro can be the intake in front of it, but not the engine itself.
-
Faldaro
Forms that start a process: claims, tickets, applications, inspections, registrations that take money. The submission has a lifecycle, and someone is accountable for it.
Weighing a specific tool? There is an honest page each for Typeform, Jotform, Google Forms, Microsoft Forms and SurveyMonkey.
Fair questions
Is Faldaro an alternative to Tally or Typeform?
For a survey, a poll or a waitlist — honestly, not the best one. Those tools are excellent at collecting answers quickly and Faldaro will not out-simple them. Faldaro is the alternative when the form starts a process: a claim to adjudicate, a ticket to route, an application to score, a registration to charge. If your responses end up in a spreadsheet that someone then works through, that spreadsheet is the part Faldaro replaces.
Jotform has approvals, PDFs and payments too. What is actually different?
Where the truth lives. In Faldaro, calculations run on the server so a browser cannot fabricate a total; payment amounts are priced server-side from the answers, never sent by the page; published versions are immutable and every submission keeps the definition it was filled against; and the audit log is append-only because the database refuses changes to it. Those are properties of the architecture, not features on a list — and they are what an auditor, a regulator or a dispute actually turns on.
We already have forms elsewhere. How hard is moving?
Forms rebuild quickly: upload the PDF and the agent turns it into a working, editable draft, or describe the form and it builds one. Your response history comes too — export it as CSV and import it: columns map to your fields by header, reference numbers survive the trip, workflow states come across, and every imported record is marked as imported in the audit log. History arrives as records, not attachments — and none of it replays: no notifications, no integrations, no freshly minted numbers.
We would be replacing more than a form tool — e-sign, payments, the tracking sheet. Is that the idea?
Yes, and it is the honest way to weigh the price. The loop a submission travels — collected, calculated, routed, approved, signed, paid, documented, delivered — is one record here, so the form tool, the e-sign requests, the payment page, the tracking spreadsheet and the automation glue between them are exactly what consolidates. Keep the tools that do work no form ever starts: general contract signing with no submission behind it, accounting, your CRM. The test is simple — if the work begins with something submitted, it belongs on the record.
Our process involves outside partners — brokers, franchisees, client firms. Can they work in it?
Yes, as organisations of their own rather than seats on your account. Share a form or a whole folder with a partner organisation: they see exactly what you shared and submit through it if you allow that, their submissions stay theirs, and only you can change the form — the database blocks cross-organisation edits outright. Privileges inherit down your own organisation tree, never up or sideways, so subsidiaries and chapters run the same way.
Why not Airtable, Quickbase or a work-management platform?
Those are strong tools for work that stays inside your company — and they price accordingly: per person who touches the system, with the public form as an afterthought. Faldaro is built the other way round: the public form is the front door, hardened for strangers — tokenised links, throttles, captcha, payments — and the people filling it are never seats you pay for. If your process starts with the outside world submitting something, that inversion is the whole difference; if everyone involved is an employee in a shared grid, they may fit better.
Is Faldaro overkill for a simple contact form?
No — the free plan has unlimited forms and ten thousand submissions a month, and a simple form is just a form. The difference only shows up when you need what surrounds it. Plenty of teams start with a contact form and discover the workflow, documents and payments when the process arrives.
When should we not use Faldaro?
When the form is the whole job and speed is everything, a lightweight builder is genuinely the better tool. And when your process needs deeply bespoke software — a custom underwriting engine, say — Faldaro is the intake and routing in front of it, not a replacement for building it.
Put your process on Faldaro today
The Free plan is free forever — unlimited forms, ten thousand submissions a month, and the same builder, logic engine and workflows as every paid plan.
No card required.