# How to build a client intake form with Claude

Build a client intake form with Claude that does more than a form tool: a public form with file uploads, answers saved in Postgres, a team review page behind sign-in, and a status the client can be told about. Hosted on floo.

Canonical URL: https://getfloo.com/blog/how-to-build-a-client-intake-form-with-claude

## TL;DR

**To build a client intake form with Claude, describe the questions, the files, and what your team does next. Claude builds a public form, saves each submission in Postgres with its uploads in private storage, and adds a review page your team signs in to. On floo, two routes make the form public and the review page invite-only.**

- Public form at `/`, team review at `/review` behind sign-in.
- Uploads go to a private bucket, never the app's disk.
- Each submission has an owner and a status, so nothing sits unread.

An intake form is where most client work starts: a new matter, a new patient, a new project, a new vendor. With a form tool, the answers land in a spreadsheet and someone copies them into the real process. An app Claude builds can be the start of that process.

## 1. Describe the intake

> Build a client intake form for our accounting practice. Ask for the business name, contact name and email, entity type (LLC, S corp, C corp, sole proprietor), tax year, and last year's return as a PDF. Business name, email, and entity type are required. On submit, show a confirmation and email us. The review page at /review lists submissions newest first with status (new, in review, missing info, accepted). A reviewer can assign it to themselves, change the status, add a note, and open the uploaded PDF. Put every reviewer API route under /review/api, never under /api.

## 2. Host it

```toml floo.app.toml
[app]
name = "intake"
access_mode = "public"

[services.web]
type = "web"
path = "."
port = 3000
ingress = "public"

[[routes]]
path = "/"
service = "web"
access = "public"

[[routes]]
path = "/review"
service = "web"
access = "accounts"

[managed.default]
type = "postgres"

[managed.files]
type = "storage"
```

- **The form at `/` is public.** The review page at `/review` asks for sign-in first, and its requests carry the reviewer's email in `X-Floo-User-Email`. Everything outside `/review` is public, so the endpoints that change a submission or sign a file link must live under `/review` as well.
- **`[managed.files]`** gives the app a private bucket for the PDFs. The app's environment gets `STORAGE_BUCKET_FILES` and S3 keys.
- **The gateway limits request bodies to 10 MB by default.** Raise it with `max_request_body_mb` in `[resources]`, up to 100, if clients upload large files.

Invite the reviewers with `floo apps invite`, or "Invite the reviewers" in Claude chat.

## 3. Things to get right

- **Validate on the server.** The page can check required fields, but the server must check them again.
- **Never trust the file name.** Store uploads under a generated key like `uploads/<submission id>/return.pdf`.
- **Rate-limit the public form.** A public form gets bots. A limit per IP or a simple challenge keeps the table clean.
- **Tell the client what happens next.** The confirmation page should say who will reply and by when.

For uploads in more detail, see [how to add file uploads to an app Claude built](https://getfloo.com/blog/how-to-add-file-uploads-to-an-app-claude-built). If clients should come back and see their status, that is a portal: see [how to build a customer portal with Claude](https://getfloo.com/blog/how-to-build-a-customer-portal-with-claude).

## FAQ

### Can Claude build a client intake form?

Yes. Describe the questions, which answers are required, what files the client uploads, and what your team does with a new submission. Claude builds the form, the review page, and the status flow. On floo the form is public, the review page is invite-only, and uploads go to private storage.

### Why build an intake form instead of using a form tool?

Because intake is the start of a process, not the end. A form tool collects answers; an app can also check them, assign the submission, track its status, and keep the files next to the record. Use a form tool when you only need the answers in a sheet.

### Where do uploaded documents go?

Into floo's managed storage, a private bucket per environment. The app saves the file's key on the submission and gives your team short-lived signed links to open it.
