Client intake portal

Input example

Clients send vague requests by email. I want a page that asks the right questions and tells them what happens next.

DEKREL questions

• - Which client answers are required before the team can start?
• - What should the client see after submission?
• - Which notes, files, and approvals must stay internal?

What to build first

• - Client form, confirmation state, internal review state, and revision request path.
• - No live account portal, billing, or customer-data migration in the first version.

What you receive first

• - A client intake page draft.
• - A confirmation message and next-step copy.
• - A permission checklist for private fields and files.

Screen example

A first screen should show the main input, the current state, the next action, and what needs approval.

What files you would receive

You should receive preview notes, a field list, review points, and the files or links the owner can check.

Launch checklist example

External accounts, payment, domain, customer data, and production changes stay separate until approval evidence exists.

Review points

• - Does the form ask enough without feeling like paperwork?
• - Does the client know what happens after submitting?
• - Are internal review notes kept away from the client view?

Next step

Review the intake fields, then decide whether a login or file upload is needed.

Public boundary

Sample only. It does not claim customer proof or include private customer data.