Form orchestration

Forms that pass between people and AI agents.

Approvals, onboarding and reviews: one form, many hands. Build it once, in React. Clipless hands it from person to agent to person, shows each of them only what they may see, and records every step.

Try the playground Getting started
Drops into your stack
  • React
  • Next.js
  • TanStack Start
  • React Router
  • Astro
  • Vite

Any React 19 app. Your components, your models, your backend.

Flagged Within policy Approved Sent back Claim employee Submits the claim and the receipt Policy check AI agent Reads the receipt, checks the policy Review manager Approves it, or sends it back ✦ AI: over the $75 meal cap Payout finance Pays it out
Why not a form builder

A form builder stops at submit. Your process doesn't.

It collects one person's answers and hands you a spreadsheet. Everything after that, the approvals, the send-backs, the checks and the paper trail, ends up in email and Zapier. Clipless runs that part.

A form builder
Clipless
After someone submits
A form builderYou get a row in a spreadsheet and an email.
CliplessIt moves on by itself: to the next person, back for changes, or up to finance when two business days pass.
AI
A form builderA summary on top, if anything.
CliplessAn AI step reads the receipt or scores the risk, and its answer picks the route. It sees only what you give it and can't skip ahead.
The busywork
A form builderZapier, and hoping it runs.
CliplessEmails when it's someone's turn, one-time codes, identity checks, PDFs and signed webhooks, declared in the workflow.
The record
A form builderThe latest answers, overwritten.
CliplessEvery answer, hand-off and AI decision on a tamper-evident record, round by round.
Personal data
A form builderOne table with everyone's answers.
CliplessEncrypted per person. Erase one, and everyone else's record stays intact.
Where it runs
A form builderTheir hosted page or an embed, with their branding.
CliplessInside your app, built with your own components.
Changing it
A form builderEdited live in a builder, by whoever has the login.
CliplessOne file in your repo, reviewed like code. Sessions already running keep the version they started on.

Where Clipless has four stars, there's more to build.

One person, once? A form builder is the right tool. Clipless is for the forms that pass between people.

How it works

Define it once. Everyone gets their own form.

The whole process lives in one React file, so a change is one edit in one place. The build gives each person a form with only their stage in it, and keeps the AI step's prompt on the engine, out of the browser.

expense-claim.tsx 
<Workflow id="expense_claim_v1">
  <Stage name="claim" actor="role:employee">
    <Field name="description" required />
    <Field name="amount" type="currency" required>
      <Remarks />
    </Field>
    <Action id="policy" type="ai_prompt" blocking
      prompt="Is {{description}} within policy?"
      schema={VERDICT} />
  </Stage>

  <Stage name="review" actor="role:manager"
    renderIf={{ 'policy.flagged': { eq: true } }}
    transitions={[SEND_BACK]}>
    <Field name="decision" type="select"
      options={DECISIONS} required />
  </Stage>

  <Stage name="payout" actor="role:finance">
    <Field name="payment_ref" required />
  </Stage>
</Workflow>
  1. claim

    Employee

    fills it in

  2. policy

    AI agent

    checks the policy

  3. review

    Manager

    decides

  4. payout

    Finance

    pays it out

Try it

Six real workflows. Open one.

Each runs in your browser, nothing to install. Click through it, send it back, skip to a deadline, and watch the record fill up beside the form. Or describe your own below.

See it in action Filings

Repeating sections

A tax return with as many dependents and businesses as the household has. Every item is validated on its own; the accountant sees them as tables with totals.

See it in action Approvals

Send it back for changes

An expense claim the manager can return. It comes back as round 2, with notes on the amount that only finance can read.

See it in action Applications

Checks that take a while

A loan with four people, an identity check that finishes later, an AI risk read, generated PDFs and an email.

See it in action Recurring checks

The same check, every year

An annual supplier review that starts from last year's answers and shows the reviewer exactly what changed.

See it in action Regulated intake

Regulated intake

A patient intake with a one-time code, contact details kept out of caches, an encrypted history and consent that must be given.

See it in action Onboarding

Conditional stages

B2B onboarding where a risky industry or score routes the application through compliance.

Your process

Who does what, in what order. You get a working workflow to click through as every person in it.

For developers

It's just React.

The workflow is a file next to your screens, built with the components you already have. Deploy it with one command. Your backend starts sessions over HTTP and listens for signed webhooks; the engine does the rest. 

npx clipless login
npx clipless deploy ./expense-claim.tsx
Getting started

Your frontend

  • React
  • Next.js
  • React Router
  • TanStack Start
  • Inertia.js
  • Astro
  • Vite
  • TypeScript

Headless hooks and fields that drop into the app you already have.

Your components

  • Tailwind
  • shadcn/ui
  • Radix
  • MUI
  • Bootstrap
  • Ant Design
  • Your design system

Every field renders whatever you hand it, or start from ours.

Your models

  • Claude
  • OpenAI
  • Gemini
  • Groq
  • OpenRouter
  • Self-hosted

AI steps run on your own key, on any OpenAI-compatible API.

Your backend

  • Node
  • Bun
  • Deno
  • Express
  • NestJS
  • Django
  • FastAPI
  • Flask
  • Laravel
  • Rails
  • Phoenix
  • Spring
  • .NET
  • Go

Signed webhooks and an HTTP API. The engine is hosted; your servers just listen.

Pricing

Pay per session. Every feature on every plan.

A session is one run of a workflow: one claim, one onboarding, one annual check. Test environments are free and unlimited. You bring your own keys for AI, identity checks and file storage, so there is no markup on providers.

Free
$0
to build and launch small
  • Unlimited test sessions
  • 100 live sessions a month
  • Every feature
  • Community support
Get early access
Pro and Business
At launch
for teams running more sessions
  • Priced per live session; test sessions stay free
  • Every feature, on every plan
  • Your own keys for AI, identity checks and storage, with no markup
  • Early-access teams help set the prices
Get early access

Enterprise

A dedicated deployment with its own database and encryption keys, in the region you choose, plus single sign-on and custom terms such as multi-year retention, an SLA or a HIPAA business associate agreement, on request. Talk to us.

Clipless is in early access.

The engine isn't public yet. If you have a form that passes through more than one person, tell us about it, and we'll get you set up.

Get early access Try the playground Getting started