What makes a client intake form production-ready

Ask for enough, then continue the conversation

A first enquiry should establish who is contacting you, what they want to improve, useful timing context and enough detail to decide what should happen next. Requiring a complete technical specification before the first conversation moves discovery work onto the client.

The server needs stricter rules than the browser

Client-side required fields improve usability, but the server still needs its own size limits, schema validation, throttling and abuse controls. Submission identifiers make retries idempotent so a slow connection or repeated click does not create several copies of the same lead.

Failure also needs a useful recovery path. If storage or an optional notification fails, the visitor should still know what happened and have a direct contact route rather than being left with a generic error.

Intake should end in a next action

Saving a row is not the end of the workflow. A usable client desk should surface the new enquiry, its commercial stage, the next owner action and any follow-up date. That is what turns a website form into an operating system for client work.