# Brief for a custom web application

Describe one task first. A sentence, a rough sketch or an anonymised example is enough. Do not include customer records, passwords or API keys.

## Worked example: a customer request portal

Today a customer emails a request and a coordinator asks for a missing attachment in a separate thread. Neither person can see at a glance who needs to act next.

| Role | Action | Done when |
| --- | --- | --- |
| Customer | Submit a request with the required attachment | The customer sees the new request as “Submitted”. |
| Coordinator | Return an incomplete request with a reason | The customer sees “Needs changes”, the reason and the option to resubmit. |
| Another customer | Try to open that request from a copied link | No details of the request are disclosed. |

First release: submit, return, resubmit and approve. Possible later addition: a report comparing time to approval across branches. This is an example, not a promise about project scope.

## Your first workflow

- What do people use today? Where do they lose time or have to ask someone for an update?
- Who starts the job? Who can see, change, approve or cancel the record?
- Which steps must work in the first version? Which can wait?
- Name one successful outcome, one action that must be refused and one failure the user needs to recover from.
- Which existing system holds the authoritative record? Name the integration and whether a test environment exists.
- Which languages and devices does each role use? For Arabic, note the screens and messages that need a right-to-left layout.
- Is there a required launch date or an existing hosting or support arrangement?

Discuss the brief with BEIZ: https://beizstudio.com/en/contact/?service=web
Service and examples: https://beizstudio.com/en/pages/web-application-development-dubai/
