DEKREL
Start
Back to examples

CLIENT PORTAL

Client request portal

Start from a client intake form, approval step, or support request. DEKREL shapes the first portal your client can understand.

Start with this example

Who it fits

agencies, service operators, project-based teams

What to bring

  • - The questions clients must answer before work can start.
  • - The states clients may see and the states that must stay internal.
  • - Examples of approvals, files, or revisions that currently move through chat.

First thing to review

  • - A client intake structure with required fields and confirmation copy.
  • - A permission boundary for private notes, files, and internal decisions.
  • - A review loop showing what the client can approve or change.

What this helps with

A client-facing request page, internal review state, and approval boundary that do not expose private work by accident.

First flow

01Define what the client needs to request and what they need to see.
02Split public visibility from permission-sensitive actions first.
03Shape the result and next-step review flow from the client point of view.

Not a fit when

  • - A full customer account system with billing, identity, and live customer data on day one.
  • - A portal that needs legal, medical, financial, or regulated advice decisions.