# Business website or client portal: project brief

Prepared by Shailpar, Rajat Malik's independent digital studio.
Guide: https://shailpar.com/guides/business-website-vs-client-portal
Copy and adapt this checklist for your own planning. Do not include real customer records or credentials.

## Outcome
- The user should be able to:
- We will know the workflow works when:
- Website, portal or both? Why:

## People and access
- Public visitor can:
- Customer can:
- Staff can:
- Administrator can:
- Information each role must not access:

## One complete workflow
- Trigger:
- Required example fields:
- First owner:
- Next handoff and owner:
- Status visible to the customer:
- Completion condition:
- Missing-information path:
- Unassigned or failed-request path:

## Existing tools
- Current source of records:
- Available integrations to confirm:
- Manual steps to retain:

## First release
- Must have:
- Can wait:
- Content owner:
- Approver:
- Support owner after launch:
- Budget range and target date to discuss:

## Acceptance checks
- [ ] Public information is readable on a phone.
- [ ] An enquiry reaches the intended destination.
- [ ] A test request completes the agreed workflow.
- [ ] Each role has only its intended access.
- [ ] Customer records remain separate.
- [ ] Failures have a clear recovery or handoff path.
- [ ] Launch and support responsibilities are written down.