Client Intake Organizer

Build a custom intake form, send your client a single file, and get back a clean, organized brief — no account, no server, and nobody's answers ever sitting on someone else's cloud.

Customize which questions your client answers — date, venue, must-haves, contact info, or your own fields — then download a self-contained form file to send them. They fill it in on their own device, watch a print-ready brief build itself as they type, and send it back to you as a PDF or a pre-filled email. There's no server anywhere in that chain: the form is a plain file, not a hosted service.

What it does

Most "free" intake form tools aren't free of trade-offs. Google Forms has no submission cap, but every answer your client types — their address, their wedding timeline, their guest count — is stored in your Google account on Google's servers, tied to whatever else lives there. Typeform's free tier was cut from 100 to 10 responses a month in February 2026, so it stops working after your first client of the month. JotForm's free tier disables every form you own once you cross 100 submissions total, not per form. HoneyBook and Dubsado do have real intake tooling, but they're full client-management subscriptions — $390/year and $200–480/year respectively — built for running an entire studio, not for the one task of asking a couple seven questions before their wedding.

This tool works differently. You customize the fields in a builder, then click one button to download a form: a normal, self-contained HTML file, not a link to somebody else's website. You attach it to an email or send it however you'd send a PDF. Your client opens it, fills it in, and — since there is genuinely no server on the other end of a single downloaded file — sends their answers back to you the same way: printed to PDF, or through a pre-filled email your form itself builds for them. Nobody's servers ever see the venue address or the guest list in between.

Who it's for: a wedding or event photographer (or any small service business that gathers structured details from a client before a job) who wants a proper form instead of a rambling email, doesn't want a monthly CRM subscription just to ask seven questions, and would rather not put a client's home address or event details through a stranger's cloud form service.

Example scenario: a wedding photographer books a couple for June. Instead of emailing "just send me the venue, timeline, and anything you really want photographed," they open the builder, tweak the default field set (rename "Must-have shots" to something more specific, add a "Guest count" dropdown, remove the phone field they don't need), and download wedding-day-intake-sarah-james.html. They attach it to their booking-confirmation email. The couple opens it on a laptop or a phone, fills it in over coffee, watches the brief build itself on the right as they type, and clicks "Email my answers" — which opens their own email client with the photographer's address, a clear subject line, and every answer already laid out, ready to send.

What it explicitly does not do: it does not parse a client's freeform, already-written email into structured fields — that would need an LLM, which breaks the zero-setup, nothing-leaves-the-device premise this whole tool is built on, so v1 is a well-designed form, not a text parser. It does not host or collect responses anywhere — there's no dashboard of "everyone who's filled this in," because there's no server to keep one. It doesn't sync a client's in-progress answers anywhere either, by design (see the FAQ below on why). It doesn't send email itself — the "Email my answers" button hands off to the client's own email app; nothing is transmitted by this tool directly. And it doesn't do e-signatures or contracts — that's a different tool.

Features

• A field builder with add, remove, reorder, relabel, and retype controls — six field types (short text, long text, date, phone, email, dropdown) covering every default field and any custom one.
• One click produces a real, separate, self-contained HTML file — not a link, not something hosted anywhere — ready to attach to an email or send however you'd send a PDF.
• A live brief preview that updates on every keystroke and is exactly what prints — no separate "generate" step to second-guess.
• Two built-in ways for the client to actually get their answers back to you, since there's no server to submit to: a print-ready PDF via the browser's native print pipeline, and a pre-filled mailto: email with every answer laid out as structured text.
• Required-field validation with live-updating inline errors on the client form, plus sensible input types (a real date picker for dates, a phone keypad on mobile for phone numbers) instead of one generic text box for everything.
• Builder settings and field customization are remembered locally between visits (localStorage), so reworking the same form for a new client takes seconds, not a rebuild from scratch.

Browser support

Plain-language summary for the listing: Verified on desktop Chrome (a full automated test of the builder, the exported client form, live validation, print, and the mailto hand-off), and visually confirmed on desktop Safari and Firefox — including opening a real exported form fresh, the way a client actually would. Not yet verified on a physical iOS or Android device; since clients are just as likely to fill this in on a phone as on a laptop, treat mobile as "very likely to work, built on only standard web features" rather than confirmed, until it's checked hands-on. ### Why the client form ignores dark mode The builder is theme-aware because it's used repeatedly by its owner, the same way the rest of this tool line is. The client-facing form is not, on purpose: it's filled in by a stranger who has never seen this tool before and has no relationship to the owner's theme preference. Inheriting the owner's dark mode there would be arbitrary, not a courtesy — and it would also have to match the print output, which is always going to be a normal light document regardless of anyone's screen theme. So the entire client shell (backgrounds, borders, buttons, the brief pane) uses hardcoded light colors, never the CSS variables the builder uses, and stays light in a dark-mode browser by design.

FAQ

Does my client's data get uploaded anywhere?
No. The form you send them is a single HTML file with no server, no account, and no network requests of any kind. Open your browser's developer tools and watch the network tab while filling it in if you want to verify it yourself — nothing happens. When your client is done, they choose how to get their answers back to you (print/save as PDF, or a pre-filled email) — it's genuinely them sending it, not this tool submitting it anywhere.

Can I customize the fields?
Yes — that's the whole builder half of this tool. Start from the default photography/event set (date, venue, must-have shots, contact name/email/phone, notes) and rename, remove, reorder, or retype any of them, or add entirely new fields, including dropdowns with your own options.

Does this work on my client's phone?
It's built on only standard web form features (plain HTML inputs, native date pickers, `@media print`, `mailto:`) with nothing Chromium-specific, so it's very likely to work — but it hasn't been verified on a physical iOS or Android device yet (see the platform-support table above for exactly what has and hasn't been checked). Don't take "very likely" as a guarantee until that's confirmed hands-on.

What happens to my client's answers if they close the tab before sending them?
Their in-progress answers are not automatically saved anywhere — a deliberate choice, not an oversight. Browsers can isolate (or in some cases share) `localStorage` unpredictably across plain `file://` documents depending on the browser, and a client's half-finished wedding details are exactly the kind of thing that shouldn't quietly persist somewhere unclear. The trade-off: your client should finish it in one sitting and print or email their answers before closing the tab. The builder side (your own field customization) does persist locally between visits, since that's you, on your own machine, working iteratively — a genuinely different situation.

Can I use this for client or commercial work?
Yes. Every form you build and every brief your clients send back is entirely yours — no attribution required, no restriction on client-facing or commercial use.

Is there a subscription?
No. This is a one-time purchase of a single, self-contained HTML file. No recurring charges, no per-form fee, no response cap ever, unlike every SaaS competitor found in the Phase 1 research below.