Schema-driven forms. Submissions become real entities.

The wedge

Form builders make a form and dump CSV. Odexy Forms make a form and route the submission into the actual module — a contact form becomes a CRM lead, an application form becomes a Recruitment candidate, a support form becomes a ticket — without a Zapier in the middle.

What ships today

• FormDefinition — schema-driven form definitions: fields, types, validation, conditionals.
• FormRenderer — drop-in React renderer; native validation; URL-resumable drafts.
• Public submissions — signed token routes for unauthenticated submitters.
• Goes somewhere real — a submission creates the actual record: a lead in the CRM, a candidate in recruitment, an expense in the ledger.
• Embeddable widget — /widget/v1/forms.js for embedding on third-party sites.
• Field types — text, email, number, select, multi-select, date, file upload, signature, scorecard.
• Self-ID / EEOC fields — optional, separated from the main payload.
• Event tracking — view / start / submit / abandon events for funnel analysis.

How it integrates

• CRM — /contact form → crm.lead.create.
• Recruitment — /apply/<job> form → recruitment.application.create.
• Support — public help form → support.ticket.create.
• Forms-as-survey — internal forms for any module workflow.

How the AI helps

• "Fill this application form from the candidate's LinkedIn export — flag anything I should review."
• "Translate the careers application form to Spanish."
• "Show me drop-off rates by field across all public forms in the last 30 days."

AI form-fill is read-write but always proposes before submitting.

Built for scale

• Validation — the rules you set while building the form are the same rules checked on the server when someone submits it.
• Idempotency — resume tokens prevent double-submits.
• Audit log — every submission with its dispatch outcome logged.
• Permissions — public forms gated by signed tokens; admin forms by role.
• i18n — definitions support per-field translation; submissions stored in the originating language.

Odexy Forms vs. the category

| | Odexy Forms | Typeform | Tally |

|---|---|---|---|

| Submissions become entities, not CSV | ✓ | webhook | webhook |

| AI fills submissions on your behalf | ✓ | — | — |

| One audit log with the rest of your work | ✓ | — | — |

| Per-org pricing | ✓ | per-seat + per-submission | per-seat |

Typeform and Tally are excellent stand-alone form builders. Both leave the entity creation to webhooks you maintain. Odexy Forms is the entity-creation layer — the form is the front of an action.

Design-partner take

> "We deleted the Zapier between Typeform and our CRM. The contact form is the CRM action — same lead, same audit row." — Design partner, 14-person team