Skip to content
Faldaro

Form tools collect answers. Faldaro finishes the work.

The form’s own rules price the quote, route the approval, take the payment, generate the paperwork and deliver the files — every number computed on the server, where nobody can tamper with a total. Don’t take the claim: drop the PDF you make people print and watch it come back as a working form, right here.

Free forever — unlimited forms, ten thousand submissions a month, AI credits included. No card required.

— the form you make people print, the intake sheet, the application —
and watch it come back as a working draft. PDF or photo, up to 5 MB.

Read once to draft this preview — nothing is stored, no account is created.

Somewhere in your company, a form ends in a spreadsheet

The answers arrive, someone exports them, and the real work starts: a total checked by hand, an approval chased by email, paperwork assembled by copy-paste. The spreadsheet is the system — and everything wrong with it happens after submit.

  • The total checked by hand

    The server computes it from the answers, on every save and every read. There is no number to double-check, because there is no number a browser can send.

  • The approval chased by email

    A workflow state with an owner and a deadline that escalates itself. Forty-eight hours in Review and the record moves — nobody has to remember to chase it.

  • The paperwork assembled by copy-paste

    Documents generate from the submission the moment its state changes — and anything sold is priced by the rules and delivered on settlement, from the same record.

That spreadsheet — and the inbox around it — is the product Faldaro replaces.

Folders group forms. Forms produce submissions. That's the whole model.

An insurer configures a Policies folder and a Claims folder. A support desk configures Tickets. Neither waits on a developer, because nothing in Faldaro is specific to a business domain — the platform takes the shape of your work.

An agent that does the work, not a chatbox that describes it

Ask for a form and the assistant plans the steps, builds the draft, wires the logic and takes you there — using the same product surface you would, with exactly your permissions, showing every step it took. It has no powers of its own to misuse: no delete tools, no admin tools, no credentials. The agent proposes; you dispose.

See everything the agent can do
  • Import a PDF as a fillable form

    A working, editable draft — not a screenshot.

  • Prefill from a document

    Matching fields fill themselves for your review.

  • Plain English to a filter

    “Unpaid claims over $5,000” becomes the exact query.

  • Reports on demand

    Describe the report; refine it in the builder it seeds.

Records that travel

A submission isn’t filed to be forgotten. It becomes a card someone drags, a status a submitter tracks, an approval decided from an inbox, a chart on someone’s site, a template someone clones — each behind its own revocable link that carries the projection and never the data.

  • A board you can drag

    The same records as a table, a board, a calendar or cards. The board’s columns are your workflow’s own states — dragging a card takes the exact move the record page offers, every server-side rule intact, and a drop the rules withhold says why.

  • “Track your request”, per record

    Mint a status link and the submitter watches their own record move — stage, reference number, last update, and nothing else. Drop {{status_link}} into a confirmation email and every record ships with the package-tracking experience.

  • Charts that leave the building

    Share a grouped report as a live read-only page, embed the chart in any site, or schedule it as a daily or weekly email digest to people who never log in. Aggregates travel; individual records never do.

  • A portal from just an email

    Submitters see all their records in one place with nothing but their address: a secure link, mailed to the mailbox itself, listing each record’s live status. You choose the one field that identifies them — nothing else ever matches.

  • Publish a form as a template

    One link makes your form’s design cloneable by anyone — fields, rules and workflow travel; your data, datasets and integrations never do. The clone lands in their workspace, not yours.

  • Approvals from an inbox

    A workflow action mails each approver their own approve/decline link — no account, no login. You choose which move each verdict takes and exactly which fields they see; the decision lands on the record with a name, comment and timestamp.

Boards, tracking links, approvals, shared reports, the portal and templates — all of it on every plan, spelled out on the records page.

Form builders end at the results table. Faldaro begins there.

Tally, Typeform and Jotform are genuinely good at collecting answers. The difference is everything that happens to a submission afterwards — and where the truth about it lives.

  • The total

    Elsewhere it is computed in the browser, and whatever arrives is stored. Here the server recomputes it on every save and read — a browser cannot fabricate a number.

  • The submission

    Elsewhere it is a row you export. Here it is a record with a state machine: routed, approved, documented and paid, with every move permissioned and audited.

  • The form itself

    Elsewhere editing changes it under old responses. Here publishing makes an immutable version, and every submission keeps the definition it was filled against.

Every difference, side by side

Underneath it all: tenant isolation enforced by the database, immutable published versions, an append-only audit log. Each claim is checkable in behaviour, spelled out on the security page.

Your first five minutes

Leave with a working form, not a trial

No demo call, no sandbox tour, no imported sample data pretending to be yours. The first session ends with your own process taking real submissions.

  1. 1 Say what you run

    Sign up — no card — and tell the agent what you need: “a maintenance-request form with an urgency score and an approval step.” Or upload the PDF you use today. Either way, a working, editable draft appears in the builder. Twelve templates, if you would rather start from one.

  2. 2 Make it yours

    Adjust the fields on the canvas, watch the logic react in the preview, name the states work moves through. Publishing creates version one — immutable from that moment, like every version after it.

  3. 3 Share one link

    Issue the public link and send it to anyone. No account on their side, never a seat on yours — and the first submission arrives not as a row but as a record: values the server computed, a state to move it through, an audit trail already started.

Or watch the whole run

Forty-five seconds, no signup: a PDF becomes a form, the form takes a submission, the server computes the total, and the record routes itself to review. Every scene is the product as shipped — nothing mocked, nothing sped past.

A looping demo of Faldaro. An agent reads a claim-intake PDF and turns it into a real, editable form; wires the estimate calculation and its conditional rules, validated against the form's own fields before saving; adds a workflow that routes any claim over $10,000 to risk review; a submitted claim is priced at $12,400 by the server and stamped with the reference CLM-2026-0147; and the phrase “unpaid claims from July over $5,000” compiles into an exact submissions filter. Throughout, the agent acts with your permissions, has no delete tools, and saves nothing until you publish.

import_pdf_as_form

The next form you send could be the last one you export

Describe the process — or upload the PDF you use today — and share a live link in the same sitting. Free forever: unlimited forms, ten thousand submissions a month, AI credits included.

No card required.